IP-318 Delivery Phase Handoff

• Phase: delivery
• Status: complete; IP-327 T1/T2, IP-328 T3/T4, IP-329 T5/T6, T7 acceptance, T8 docs/evidence, final review, tracker reconciliation, and draft-PR/stack verification passed
• Scope: IP-318, including child stories IP-327, IP-328, and IP-329
• Artifacts: apps/wiki/content/docs/project/specs/cli/IP-318-govern-project-settings-and-scaffold-state-safely/{SPEC.md,PLAN.md,IMPLEMENTATION-NOTES.md,PHASE-HANDOFF.md}
• Sources: approved SPEC; completed Q18-Q31 CLI context architecture grill; live Linear IP-318, IP-327, IP-328, IP-329, and IP-326 descriptions, relations, and comments read 2026-07-16; accepted IP-319 implementation notes; relevant scaffold/update learnings; current CLI settings and lifecycle code
• Delivery evidence: T1/T2 remain complete for IP-327; T3/T4 complete the IP-328 compiler and lifecycle staging; T5/T6 complete deterministic reconciliation and truthful application; T7 proves the packaged init/ensure/check/update preview/write/retry lifecycle. Exact evidence and every review repair are recorded in PLAN and IMPLEMENTATION-NOTES.
• Review/debug/docs state: the root/routed runbook and canonical settings/setup/update/manifest pages match shipped per-entry outcomes, partial/failure exit semantics, settings authority, lockfile routing, user preservation, truthful receipts, and deterministic retry. Wiki tests 6/6, direct wiki type generation, full serial CLI 446/446, CLI build/typecheck, and root behavior 4/4 pass. The non-mutating wiki sync preflight reports pre-existing project-owned routing drift and would remove canonical routed specs, so its mutating wrapper was not run. Final autoreview and parent rereview report no remaining HIGH/MEDIUM finding.
• UI Evidence: not applicable
• Branch/base state: tracker-sync head adec65792416c561857623b0978b07e8929f7c72 is on draft PR #87. Live GitHub evidence confirms #76 remains the parent based on main; #77-#83 and #87 remain draft/open/unmerged sibling children based on team/stefan/refactor-cli-architecture. Restored stack status showed this exact fan-out, and the post-push dry-run reports Stack is current.
• Task order: IP-327 and cross-epic IP-326 both precede IP-328; IP-328 precedes IP-329; IP-327, IP-328, and IP-329 remain tasks inside this epic child PR, not separate PRs
• T4 boundary: init, check, and update consume one compiled desired state through distinct apply, compare, and reconcile stages. Check does not require writable temporary storage. Projection subprocesses isolate ambient plan state, validate explicit plans against canonical context, accept legitimate cross-kind trace reuse, reject malformed context or inconsistent traces, and clean only run-owned temporary plan directories.
• Tracker closeout: IP-328 Done at 2026-07-20T01:02:45Z (0697ea59-892c-42c9-b303-17ad87a48d99); IP-329 Done at 01:02:51Z (033824f7-107c-4239-a5c6-a236bc8bd751); IP-318 Done at 01:02:52Z (39c3facb-2696-4ac8-8721-ce2beb5c0a8a).
• Next route: maintainer review of draft PR #87; no merge, deployment, or further IP-318 delivery work is authorized here.
• Blockers: none.