docs(recipe): Needs review is not shipped without tip-native proof

Draft
OW
2mo ago
+42-0

What & why

Adds one docs page: docs/proof-gate-needs-review-receipt.md.

Needs review on the board is not shipped. Tip-native proof (check runs or a receipt pinned to the exact branch-tip SHA) is required first. Without that bar, Operators treat chrome as done and the product keeps lying about finished work.

How I tested it

  • Docs-only diff vs upstream main (single file) — branch cut from superset-sh/superset tip, not fork-main drift
  • Stay DRAFT — no undraft without CoS→Owen

Checklist

  • Thin docs brick only (no host-service / product code)
  • Attested board nouns; no invented ReadyVerified column
  • Fence Todd #7007 agentStatus SoT; no hooks #7252/#7263

Supersedes #7296/#7297 (those heads sat on fork-main commits not yet in upstream).

Summary by cubic

Adds a docs page establishing that a workspace in Needs review is not shipped: operators must first see tip-native proof, either CI check runs or a receipt pinned to the exact branch-tip SHA.

This is a draft docs-only rule; it does not change product behavior, board columns, or agentStatus.

Mechanism

Docs-only operator recipe. One page states that Needs review is a board column meaning needs review — not shipped — until a tip-native proof artifact (check runs or receipt) is pinned to the exact branch-tip SHA. No new columns, no host-service code, no agentStatus SoT changes (Todd #7007).

Session: OpenCode Alibaba overnight proof-gate → thin re-cut from upstream/main as docs/proof-gate-thin-upstream after fork-main drift closed #7296/#7297.

How I tested it