Ground story stages through revision

[R055LE]

Summary

Follow-up for #107, stacked on #118 (issue-115-rendered-completeness). This corrects the writer/revision guidance behind the recorded stage citation failure.

• Require stage evidence for the public development: an observed result for demonstrated, explicit status for announcement/preview/rollout, or a cited unresolved limit for uncertainty.
• Preserve supported wording and exact citations while they still fit the repaired narrative. Permit legitimate scope changes; final independent review still checks every item.
• Represent review-revision sources as a lossless table with field names listed once. All values, excerpts and original citation numbers remain available within the unchanged 18,000-character limit.
• Add synthetic regressions for setup-only stage rejection, retaining supported demonstration evidence, and narrowing a previously supported stage.

Review policy, reviewer payloads, response schemas, parsing, model-call limits and production settings are unchanged.

Validation

• Independent review of the actual diff and request-budget audit.
• Full test suite: 637 passed, 87.38% coverage.
• Ruff and git diff --check passed.
• Exact captured four-response replay still rejects the unsupported final stage after four calls. This is an offline replay, not evidence of live writer compliance.
• Lossless source reconstruction checked for one source, noncontiguous source numbers [3, 8], and all eight sources.
• Six complete reviewer calibration requests match the previously successful calibration byte for byte.

Boundary fixture	Characters / 18,000
Eight-source draft	17,970
Validation revision	17,875
Rejected eight-source skip revision	17,905

These are measured fixtures, not a guarantee that every maximal combination fits. The existing oversized-input rejection remains in place.

Live acceptance still pending

The earlier paid attempt allowance is exhausted. A finite extension has been prepared for owner review in the local evaluation packet. No paid calls were made during this preparation.

Mock tests and captured response replay establish orchestration behavior; live writer compliance still needs the complete no-send workflows and review of their exact public renders. This draft does not request merge or activation yet.