M5-10: Maintainer release-candidate freeze and tag

[pillowtalk-Qy]

Type: Maintainer Release Action
Priority: P0
Initial status: Blocked
Owner: Maintainer only
Depends on: M5-08 Gate C PASS, M5-09 no P0/P1
Blocks: M6 final execution
Writable: release metadata/docs; no feature code

唯一目标

确认所有 Gate 和审计后冻结功能，创建可回滚 RC tag，并公布 8 月 6 日 hotfix policy。

验收

[ ] required Issues closed
[ ] conversations resolved
[ ] exact main rechecked
[ ] main quality-gate SUCCESS
[ ] Gate A/B/C linked
[ ] security/performance/deploy/visual reports linked
[ ] no P0/P1
[ ] Demo URL/video draft/screenshots accessible
[ ] hotfix policy posted
[ ] feature PR intake closed

仅 Maintainer 执行

git tag -a hackathon-rc-2026-08-05 -m 'Hackathon release candidate'
git push origin hackathon-rc-2026-08-05

Codex 指令

只读生成 RC freeze checklist 和 exact candidate evidence summary。
不要创建/推送 tag，不关闭 Milestone；缺 Gate/P0/P1 时结论 BLOCKED。

---

5.6 M6：Rehearsal and Submission

[pillowtalk-Qy]

依赖 #57 Gate C PASS 与 #58 P0=0/P1=0 已满足。开始对 main@ce5be8f4934002d8b117ea62a4a980ba6d8951bd 执行只读 RC freeze 审计；Codex 不创建或推送 Maintainer-only tag。

[pillowtalk-Qy]

RC freeze read-only audit - BLOCKED only by Maintainer tag

Exact candidate: ce5be8f4934002d8b117ea62a4a980ba6d8951bd

• Required M5 implementation and QA Issues M5-01: Create four deterministic scenario bundles #50-M5-09: Final desktop/mobile visual and judge comprehension QA #58 are closed; remediation P0: remediate production dependency advisories blocking Gate C #102 and P0: Gate C root live-smoke command is missing #107 are closed.
• PR M5-09: record final visual QA #110 has zero unresolved review threads and no open PR remains.
• Local main and origin/main are identical (0 0 divergence) and the worktree is clean.
• Exact-main quality gate 31296474714 is SUCCESS.
• Gate A, Gate B, and Gate C are linked and PASS.
• Security, performance, deployment, and visual QA evidence is linked. The security NO-GO condition was fixed by P0: remediate production dependency advisories blocking Gate C #102 and Gate C re-ran the production audit successfully.
• No open Bug Issue or release-blocking P0/P1 finding remains; M5-09: Final desktop/mobile visual and judge comprehension QA #58 recorded P0=0/P1=0/P2=0. Documented product limitations remain disclosures, not hidden PASS claims.
• Demo URL, demo/video draft script, visual report, and all four exact-candidate screenshots are publicly accessible (HTTP 200).
• Feature intake is frozen at this exact candidate: no feature PR will be accepted into the RC.
• Hotfix policy is posted below.
• Annotated tag hackathon-rc-2026-08-05 exists on the exact candidate.

Hotfix policy: after freeze, accept only separately tracked P0/P1 defects. Every hotfix starts from the frozen candidate, adds a focused regression, passes exact-head CI plus affected Gate re-runs, and receives merged-main CI. Never move or overwrite an existing RC tag; publish a new suffixed tag for a replacement candidate. Feature and P2 enhancement work waits until after the release decision.

Maintainer-only completion commands:

git fetch origin
test "$(git rev-parse origin/main)" = "ce5be8f4934002d8b117ea62a4a980ba6d8951bd" &&
  git tag -a hackathon-rc-2026-08-05 ce5be8f4934002d8b117ea62a4a980ba6d8951bd -m 'Hackathon release candidate' &&
  git push origin refs/tags/hackathon-rc-2026-08-05

Codex did not create or push the tag and did not close the Milestone, as required by this Issue. Once the Maintainer pushes the tag, verify its peeled commit equals the exact candidate before closing #59.