feat(feature-flow): questions deck, note tags, contract step, contract-check, acceptance deck, close-out Contract section

[itsdestin]

Implements docs/active/plans/2026-09-01-feature-flow-plan.md (design: docs/active/specs/2026-09-01-feature-flow-design.md). The plan was reviewed against the code first; its "Review changes" section lists what moved.

What the review deck can do now

• Words-only steps ("words": true): a question with 1–3 written options, or a statement to approve, no picture — the questions deck asked before anything is drawn.
• Note tags: fix now / fix later / just noting, stored as note_kind; shown only when stored.
• Contract step (rows): the definition of done, signed off as one step. review-cards.py contract-check reads the gate's three facts (holds / signed / accepted); acceptance builds the graded deck from <feature>.contract.verdicts.json. Guards may live on the contract's branch.
• close-out.sh gets a Contract section that relays those facts.
• Answers files under docs/ are committed (27 files); scratch/ was already ignored.
• The contract-agent prompt (scripts/ui-review/contract-agent.md), dry-run against the arcade's three decks: 5 rows, check holds (output in the commit message).
• Rule .claude/rules/feature-flow.md, skill/README/MAP/CLAUDE pointers, ROADMAP entries.
• The design's four assumptions are asked on the first questions deck (docs/active/design/2026-09-01-feature-flow/feature-flow.questions.json).

Verification on the head commit: 132 deck tests OK (5 suites run in CI, picture-free), 4 browser render tests OK, close-out-contract test OK, check-doc-commands.mjs OK, audit-anchors.mjs MECHANICAL PASS: OK. Each task was reviewed by a separate agent; a whole-branch review's three Important findings are fixed in bab1fdd. Deferred coverage debt is a ROADMAP line.

🤖 Generated with Claude Code

https://claude.ai/code/session_01F35AsThZGxRFAARcyurigf

[itsdestin]

Merged to master as 9d81045 (merge commit) + a01b651 (the trailing CLAUDE.md commit, cherry-picked because it landed after the merge was built). Closing manually — the cherry-pick means the branch tip is not an ancestor of master, so GitHub won't auto-close it, but every change is on master.

Conflicts resolved against master's roadmap restructure and archive gardening:

• ROADMAP.md — master split it into docs/roadmap/<area>.md; the three flat entries were re-filed into dev-workspace.md (rigs / knowledge / tests) in the new grammar, and roadmap-check.mjs --fix rewrote the index counts. Structure — clean.
• .claude/skills/ui-mockup/SKILL.md — kept the branch's build-stage steps 3–5, folded master's new roadmap filing path into step 4.
• docs/active/plans/2026-09-01-feature-flow-redesign.md — the branch supersedes it, so the deletion stands over master's link fix.
• Two links in the design doc repointed to docs/archive/ (perf-lab plan, roadmap-restructure design).

Verified on the merge result: 132 deck tests OK (all ten Python suites), 4 deck-render browser tests OK, close-out-contract.test.sh ok, check-doc-commands.mjs 1 run / 0 failed, audit-anchors.mjs MECHANICAL PASS (anchors 370/370, MAP paths 345/345). Workspace CI green on master.