WORK-515
ID:WORK-515Status:ready

One-time lifecycle-drift cleanup pass over plan/

Run the new drift checks against refrakt's own plan/ and clear the accumulated drift, so the checks land on a clean repo and can gate CI without a wall of pre-existing warnings. SPEC-119's motivating audit already found 38 draft specs whose linked work was 100% done plus 32 accepted specs never advanced to implemented/shipped, along with stale blocked items and milestones left active/complete out of step with their members. This is the "land alongside a one-time migration pass so the repo starts clean" step from the spec's recommendation.

Priority:mediumComplexity:simpleMilestone:v0.30.0Source:SPEC-119
main View source

Criteria completion

Criteria completion: 0 of 6 (0%) checked; tracking started on Jul 24, no incremental history yet0%25%50%75%100%Jul 24Jul 30

Tracking started Jul 24 — check back for trends.

Relationships

Implements 1
Related 4
Branches 2
main current ready
claude/v0-30-milestone-review-hg592h doneclaude/plan-cli-docs-review-o4nmn6 ready
History 2
  1. 5d6f89e
    Created (ready)by bjornolofandersson
  2. 0ebc115
    Content editedby Claude
    plan: add v0.30.0 milestone — lifecycle validation & render-stack remova

Acceptance Criteria

  • plan validate reports zero lifecycle-drift warnings (spec-status-lag, spec-status-ahead, released-in-without-shipped, stale-blocked, milestone-complete-with-open-work) against refrakt's plan/ after the pass
  • Drifted specs are advanced to the correct terminal state (implemented, or shipped with released-in where a release actually shipped them) — assertions capped at implemented; shipped/released-in chosen by human judgement, never inferred
  • Specs whose linked work is entirely cancelled/superseded are retired (not advanced to implemented) — verified by hand, not by the drift-toward-done check
  • Stale blocked work items are moved to their correct status; complete/active milestones are reconciled with their members
  • All status changes are made via the plan CLI (plan update), not by hand-editing entity files
  • plan validate --strict passes on plan/ at the end of the pass

Approach

Sequence after WORK-513 and WORK-514 so the checks exist to enumerate the drift: run plan validate, work the list, re-run until clean. This is a content/status migration — no code changes — but it doubles as the real-world noise check the spec's open question calls for. Where a warning turns out to be a false positive rather than genuine drift, that's a finding to feed back into the check's predicate (WORK-513/514), not something to silence by mis-statusing an entity.

Blocked by

  • WORK-513
  • WORK-514

References

  • SPEC-119 — lifecycle-drift validation; the audit numbers and the "one-time migration pass" recommendation
  • SPEC-049 — spec lifecycle states (implemented/shipped, released-in) applied during the pass