CI & Build / Python lint (push) Successful in 2s
CI & Build / Plugin hooks (push) Successful in 13s
CI & Build / TypeScript typecheck (push) Successful in 59s
CI & Build / integration (push) Successful in 1m32s
CI & Build / Python tests (push) Successful in 2m33s
CI & Build / Build & push image (push) Successful in 26s
Record, milestone, phase and plan citations go from every migration header; the "end before start" fix (0043) and the suppressed-count column (0095) state the condition they prevent rather than the incident. 0053 and 0055 pointed at design specs under docs/superpowers that are not in the repo; those pointers are removed. Kept: alembic's generated "Create Date:" headers (template metadata, not rationale), 0121's ARM_BORN justification beside the constant, and 0051's illustrative "update task 42" format example. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
33 lines
994 B
Python
33 lines
994 B
Python
"""milestone-as-plan-container: milestones.body holds the plan/design
|
|
|
|
Revision ID: 0066
|
|
Revises: 0065
|
|
Create Date: 2026-06-14
|
|
|
|
The milestone becomes the plan container: its `body` holds
|
|
the design/intent/purpose (markdown), `description` stays the one-liner, and
|
|
individual steps live as first-class child tasks (milestone_id) instead of
|
|
checkboxes crammed into a kind=plan task body. start_planning is reworked to
|
|
create a milestone instead of a kind=plan task (hard retirement going forward;
|
|
the 'plan' task_kind enum value stays valid so the historical plan-tasks are
|
|
left readable in place — no body-shredding backfill).
|
|
|
|
Schema change is just one nullable column; no data migration.
|
|
"""
|
|
from alembic import op
|
|
import sqlalchemy as sa
|
|
|
|
|
|
revision = "0066"
|
|
down_revision = "0065"
|
|
branch_labels = None
|
|
depends_on = None
|
|
|
|
|
|
def upgrade() -> None:
|
|
op.add_column("milestones", sa.Column("body", sa.Text(), nullable=True))
|
|
|
|
|
|
def downgrade() -> None:
|
|
op.drop_column("milestones", "body")
|