docs: record scoped release stabilization and verification gates

[lidge-jun]

Summary

• Record the scoped release integration, contributor-source dispositions and native verification limits for the next production release.
• Keep independent parallel regression, complete candidate CI and publication as separate acceptance stages. This documentation PR does not declare the release ready or deployed; current follow-up work is explicitly listed.

Verification

• bun run privacy:scan: passed. git diff --check: passed.
• The branch differs from current dev only in seven release-record documents. Runtime verification and exact-head CI are linked as historical evidence, with unexecuted platform and final release checks identified.
• Independent fresh-reader/privacy review passed after three corrections: remove private chat identifiers, reconcile pending repairs and refresh source dispositions. The final small status update records fix(spend): refuse unbooked dispatches under applicable ceilings #6538 landing and fix(combo): preserve bounded nested HTTP refusal semantics #6540 publication against verified receipts.

Checklist

• Scope stays focused and avoids unrelated cleanup.
• Docs or release notes were updated when needed.
• Security-sensitive changes were reviewed for secrets, auth, and unsafe defaults.

Summary by CodeRabbit

• Documentation
  • Added release-planning guidance covering stabilization work, independent regression checks, candidate verification, and publication.
  • Recorded acceptance criteria, verification evidence, and platform coverage limits to clarify which release checks are complete and which remain outstanding.

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

⚙️ Run configuration

• Configuration used: Repository: lidge-jun/opencodex/.coderabbit.yaml
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: ee8418c6-2c93-4b07-9433-ca37b8440139

📥 Commits

Reviewing files that changed from the base of the PR and between efc20e7 and fe73745.

📒 Files selected for processing (7)

• devlog/_plan/261003_release_stabilization/000_plan.md
• devlog/_plan/261003_release_stabilization/010_stabilization.md
• devlog/_plan/261003_release_stabilization/011_native_and_merge_acceptance.md
• devlog/_plan/261003_release_stabilization/012_integration_evidence.md
• devlog/_plan/261003_release_stabilization/015_independent_regression.md
• devlog/_plan/261003_release_stabilization/020_candidate.md
• devlog/_plan/261003_release_stabilization/030_publication.md

 ___________________________________________________________________________
< Edge cases called - they'd like to be included in your 'done' definition. >
 ---------------------------------------------------------------------------
  \
   \   (\__/)
       (•ㅅ•)
       / 　 づ

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

✅ Deterministic PR hygiene checks passed.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-03T20:09:43.405978Z	fe73745	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: fe73745447

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[lidge-jun]

Maintainer integration decision: integrate the seven documentation-only release records into dev under the owner-authorized stabilization task and maintainer-integration policy. This is not self-approval. Independent fresh-reader/privacy review passed after removing internal conversation identifiers and reconciling source dispositions and pending gates. The public branch contains a clean planning-record commit, not the preserved unpublished coordination history. A small subsequent record update is bound to verified #6538 landing and #6540 publication.

The reviewed current dev base is already an ancestor of this head. The diff is exactly seven planning/evidence documents; no runtime, dependency, workflow or policy changes. Applicable docs-only CI ran the privacy scan successfully. Historical runtime evidence is labeled separately; independent final regression, complete candidate verification and publication remain pending, as stated in the documents. This is publication of the plan/evidence record, not a declaration of release readiness.

The optional external CodeRabbit review context is still pending and is not counted as a passing review. Current-head independent review is complete and every currently published finding is resolved; post-merge/final review checks remain mandatory.

Hosted receipt: https://github.com/lidge-jun/opencodex/actions/runs/37149194676, attempt 1, pull_request, tested head fe737454477e4c7607bbda1ad42f44b7cd43339d / base efc20e700b6fce67578e07b94336fc71aebc5a1c. Current reviewed dev base efc20e700b6fce67578e07b94336fc71aebc5a1c; conflict-free union tree fbcdac8f0de53fee3b6123c869b8b339e1ea1950. Applicable docs-only scope and privacy jobs succeeded. Runtime and platform jobs were excluded for this docs-only diff and are not counted as passing; final integrated lane=all remains required.