Surface dark stages: transcript, documentation, feedback-loop summaries in run views

[richard-devbot]

Context

Audit §2: stages 01-transcript (stakeholders, goals, constraints, open questions), 03-documentation (BRD/FRD/SOW status, sign-off), 11-feedback-loop (consistency_report.json: traceability coverage, gaps) write rich JSON that no page renders.

Scope (one PR)

• Run Report gains three sections: Project Brief (from transcript: goals, stakeholders, constraints, open questions), Documentation status (docs produced, requirement counts, sign-off gate state), Consistency review (feedback-loop coverage % + gap list by severity).
• Open questions and unresolved gaps roll into the Command Center attention list.
• Spec-anchor: 03-documentation agent additionally writes spec-anchor.md (<200-token orientation doc: goal, stack, top-5 requirements, key decisions) — closes the HIGH finding in specs/pipeline-improvement-analysis.md; rendered at the top of run views when present.

Acceptance criteria

• All three artifacts fully rendered with designed empty states
• Open questions appear in attention list
• spec-anchor.md written by stage 03 (contract documented) and rendered
• npm test green

Key files

state/stage-reports.js, ui/client.js, agents/sdlc/03-documentation.md, docs/HARNESS.md