tasks

Use the mandatory task structure: Top Task Snapshot, current-state audit, user outcome, scope, dependencies, Definition of Done, and an ordered implementation runbook. Each file group ends with a named Checkpoint block containing success criteria, verification proof, and STOP conditions.

It classifies work as S0 trivial, S1 focused, S2 coordinated, S3 substantial cross-system, or S4 production-sensitive risk. S0 skips the orchestrator, S1 uses one execution path, and S2–S4 require a dependency-aware step graph with resumable Linear state.

Split using vertical tracer-bullet slices where each child ticket delivers one narrow, complete, independently verifiable outcome across all layers it needs. For wide mechanical refactors that cannot stay green vertically, use the expand, migrate, contract pattern instead.

No. Merge is not Done; post-merge verification must confirm the merge SHA on origin/main, main CI, deployment health, and the task's observable outcome. Only after all applicable post-merge checks pass can progress reach 100% and Linear move to Done.

Treat every review comment as a hypothesis, not authority. Classify each as valid-blocker, valid-in-scope, stale, incorrect, out-of-scope, or needs-research, verify against current code and domain evidence, then fix, reply with proof, and resolve only after verification.