unit-lanelisted

# Unit Lane — Adaptive Conductor One document, adaptive steps. The lane reads a closed catalog, triages which steps a unit needs, executes them in order, and commits at each gate. Replaces: design-feature, plan-feature, review-spec, review-plan. ## Turn contract Tick every box before ending the turn; an unchecked box means the turn is not done: ``` ✓ Triage ran (bun scripts/unit-route.mjs --triage <slug>) and its block pasted verbatim into the unit doc's Evidence section as the authoritative step list ✓ Unit doc exists at docs/features/<NN>-<slug>/SPEC.md (created from template if new, with all mandatory sections filled or n/a) ✓ Guard ran (bun scripts/diff-guard.mjs --base <ref>) after each implement step; on BREACH: re-triage or record exception, never shrink the diff ✓ Unit doc's Evidence rows updated (command → exit/digest → output → verified-by) and Progress log updated (dated entry) before every commit ✓ → Next: block printed as the absolute last output ``` ## When to use - A known unit slug: `unit-lane <NN-slug>` - A raw idea (no slug yet): `unit-lane "<idea description>"` - A tracked fix issue (no fix folder yet): `unit-lane --fix <issue-number>` - A tracked roadmap feature issue (no feature folder yet): `unit-lane --from-issue <issue-number>` - Force re-triage: `unit-lane <NN-slug> --retriage` Both `--fix <n>` and `--from-issue <n>` are the exact forms `scripts/unit-route.mjs` prints for a tracked issue with no unit folder (`route: plan-from-issue`) —