Scaffold Lifecycle Backlog Proposal
Scaffold Lifecycle Backlog Proposal
State: approved by the user and fully applied. See the verified provider result.
The sections below retain the pre-write proposal; exact original preview is at commit
c35ba7ea27b317e3afdb3debcc7cabe7c41dc29d.
Authority: immutable specification, verified against remote branch and
GitHub blob 9ec1a7e22f7fc7df67f1456d9867d5e1e5399edb. This proposal derives provider
items; the specification's eight outcomes do not prescribe their count.
Destination and reconciliation
- Workspace: Devpunks,
1081916c-55b9-46bb-b923-a80db9ffca35. - Root: HARNESS INTELLIGENCE,
164bcb79-1434-486e-956e-35347256b1a8. - Reuse unchanged CLI Product Area,
ad21ca0b-b4b0-48e1-91ee-291a111335c4, durable identityproduct-area-cli; Root membership, project/team and Kind/Area label IDs read back on 2026-09-05. - Intended items: 1 new Initiative issue, 1 child Epic, 5 Stories, 9 Tasks.
- New project milestone: V4.4 Reliable Scaffold Lifecycle. Its goal covers routine setup, authored-context preservation, truthful health, recovery, selective scoped work and faithful candidate validation. It is a delivery iteration, not a promised release date or npm version.
- Existing V4.1/V4.2 completed scope and V4.3 delivery-flow optimization have different goals; no existing item or milestone moves.
- Complete CLI project search returned 31 items and no continuation. Workspace searches for issue/spec identity and lifecycle wording were also exhausted. Historical IP-317/IP-318 and IP-426 were read with relations: completed distinct specifications, no new-scope durable identity. Preserve those records.
- No existing same-identity item or unresolved adoption candidate was found. Proposed exact-create identities are recorded in the mutation envelope.
- Existing views, owners, priorities and roadmap items receive no edits. All new issues start in Backlog; no assignee or date is invented.
Proposed topology
HARNESS INTELLIGENCE [existing Root]
└─ CLI [existing Product Area]
└─ Reliable Repository Context [new Initiative issue]
└─ Scaffold, Update and Check Lifecycle [new Epic]
├─ Complete routine quality and hook setup in the CLI [2 Tasks]
├─ Check editable context against its actual obligations [2 Tasks]
├─ Recover interrupted adoption without false completion [2 Tasks]
├─ Refresh only affected scoped guidance and agents [2 Tasks]
└─ Validate the planned workspace installation faithfully [1 Task]Every Story and Task belongs to the new V4.4 milestone. The CLI Product Area and
all issues retain Internal Projects team 62ed7329-f790-46ba-8013-da13eb7782fa. Kind labels use existing
exclusive Kind children; Area/CLI is additive classification.
Task ownership and blockers
Task keys below are durable proposed identities, not private implementation tasks. Creation replaces references with provider IDs; downstream planning preserves those IDs. Dependencies express required results, not arbitrary list order.
| Key | Owner-ready result | Story key | Blocked by | Acceptance |
|---|---|---|---|---|
| authority | Apply explicit artifact obligations across the shared lifecycle | truthful-check | None | AC-001, AC-008, AC-009, AC-010, AC-011, AC-012, AC-013, AC-014, AC-015 |
| check-report | Report independent health findings and exact unknowns | truthful-check | authority | AC-001, AC-002, AC-006, AC-007 |
| quality-defaults | Resolve supported quality defaults with repository overrides | routine-setup | authority | AC-001, AC-003, AC-004, AC-005 |
| routine-install | Install and verify the planned quality and Commit Gate setup | routine-setup | quality-defaults, publication, candidate-topology | AC-003, AC-004, AC-005, AC-020, AC-029, AC-031 |
| publication | Resume coupled output and receipt publication truthfully | recovery | authority | AC-017, AC-018, AC-019, AC-020 |
| portable-migration | Reconcile portable state and legacy artifacts without data loss | recovery | authority, publication | AC-016, AC-021, AC-022 |
| scope-invalidation | Invalidate scoped work through contract and scope identity | scoped-work | authority | AC-023, AC-024, AC-025, AC-026, AC-027, AC-032 |
| bounded-handoff | Complete bounded authoring through deterministic projection and proof | scoped-work | scope-invalidation, publication | AC-002, AC-008, AC-028, AC-029, AC-030, AC-031, AC-032 |
| candidate-topology | Preserve planned workspace topology in candidate validation | candidate | None | AC-033, AC-034, AC-035, AC-036 |
Authority and candidate-topology are initially unblocked. The complete proposed graph includes all five Stories, all nine Tasks and every blocker; no existing connected Task or unlanded stack dependency is asserted. Semantic graph validation must pass before writes and again after substituting returned provider IDs.
Exact mutation and readback
Mutation envelope contains the exact intended bodies, source links, durable identities, label IDs, project/team, state, parent, milestone and blockers. Task graph is the validator input. Every accepted outcome and criterion is traced to delivery items.
After approval: refresh targeted provider state, confirm zero same-identity matches, create/read back the milestone, then create/read back parent-first issues and native blocker relations in dependency order. Verify returned issue identity, body, Kind/Area, team/project, parent, exact milestone, Backlog status and blockers. Stop further writes on any mismatch. Record observed writes and exact residual operations; resume only after fresh reconciliation. No message/comment to others or historical-ticket normalization is included.
Approval boundary
The Requirements Phase invocation authorizes compilation and delivery projection. The new Initiative/Epic goal and V4.4 placement are concrete new structural choices. Write Backlog requires explicit approval of those choices after this preview. The user approved these choices with “approved” on 2026-09-05. The complete delta was then applied and read back; the result record contains every provider identity.