workflow-status

# Workflow Status (the orchestrator's sensor) One read-only pass over the project that answers, in a single fixed JSON envelope: **what exists, what is blocked on what, what is startable right now, and what the recommended next command is.** Built for external orchestrators (see `docs/workflow/ORCHESTRATION.md`) but equally useful to a human asking "where do we stand?". ## Turn contract — verify before ending the turn ``` ✓ Every claim comes from a RUN command or a READ file (git/forge output, roadmap, fix index, feature folders) — nothing inferred from memory ✓ Nothing was edited, committed, pushed, or created — read-only, always ✓ `next.recommended` is non-bare (carries the unit's slug/NN, never a bare `/plan-feature`) AND staged by the target unit's resolved status: `idea`/undesigned → `/design-feature <slug>`; `defined` → `/plan-feature <slug>`; `planned` → `/execute-phase <NN> P1` ✓ Every `design_candidates[].next` begins with `/design-feature ` — design candidates always route to design, regardless of anything else ✓ When `--last-envelope` is supplied: the no-progress guard ran (crash-recovery checklist) — a hint that recommended `/plan-feature`/`/design-feature` for a unit still at its pre-advance status produces a `workflow_observations` note, never a silently repeated bland recommendation ✓ `recommendations.product_audit` was computed by the step-16 mechanical two-condition check (never guessed), and `next.tier` was derived from the resolved `n...