docs(devlog): open phase 2 of the post-2.60.0 consolidation batch

[lidge-jun]

Summary

• Open phase 2 of the post-2.60.0 batch: bundles 7 through 16 of the assessment, recorded in devlog/_plan/260920_meaning_preservation_batch/010_phase2.md.
• These are units of existing issues and pull requests to reuse, not ten new pull requests. The file records which existing items each lane carries, the acceptance conditions that a passing request does not demonstrate, and the release grouping.
• Explains the two groupings that are not obvious: bundles 7 and 14 define the same stage and cause substrate and stay in one lane so two branches cannot contradict each other in the merge, and bundle 13 waits on the request-scoped route authority that the fix(security): keep DNS pinning unless the proxy applies to the request #5087 lane is building.
• Adds explicit ownership boundaries between concurrent lanes for send accounting, per-model cache views and the adapter queue budget.

Verification

• Documentation only; no source, test or workflow changes.
• Every referenced issue and pull request state, author and title was read back from the GitHub API before writing the lane table.

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.

[coderabbitai]

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: eeda682c-e5e3-451c-acdf-3463111d2221

📥 Commits

Reviewing files that changed from the base of the PR and between 0613aae and 34f9d3d.

📒 Files selected for processing (1)

• devlog/_plan/260920_meaning_preservation_batch/010_phase2.md

 ___________________________________________________________________________
< What can I say except 'You're welcome' for the bugs I found in your code? >
 ---------------------------------------------------------------------------
  \
   \   (\__/)
       (•ㅅ•)
       / 　 づ

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

---

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

Here are some automated review suggestions for this pull request.

Reviewed commit: 34f9d3dd7d

ℹ️ 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".

[chatgpt-codex-connector]

Move open authorization triage out of devlog

This OPEN plan records unfixed authorization-bypass scenarios—alternate routes reaching forbidden providers and inference credentials gaining management authority—in a tracked public directory. These details are unreleased security and bypass planning, which must remain in scratch space until the fix has shipped; move the security-sensitive acceptance notes out of devlog/ and commit only the published outcome.

AGENTS.md reference: AGENTS.md:L124-L130

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Align release groups with the atomic lane pull requests

The release grouping cannot be implemented with the topology above: lane D's single PR contains both 8 and 9, lane E contains 10/11/12, and lane F contains 13/15, while these lines assign those items to different releases. Because releases promote the integrated dev branch, merging a lane necessarily carries every item in its PR; split the mixed lanes or place all items from each lane in the same release group.

AGENTS.md reference: AGENTS.md:L351-L353

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Define completion conditions for bundles 13 through 16

Despite stating that each bundle has a completion condition, this section stops after bundle 12 and provides none for 13, 14, 15, or 16. Consequently lanes F and G—and bundle 14 in lane C—have no documented criterion preventing completion based only on a passing request, defeating the purpose of this section; add explicit acceptance conditions for all four omitted bundles.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Permit focused regression tests during implementation

When these lanes change the listed runtime behavior, forbidding even individual tests prevents contributors from running the focused regression checks required for each affected subsystem. Exact-head hosted CI does not replace the prescribed focused checks, particularly for dependencies expressed through subprocesses or source files read as data; revise this constraint to allow the relevant focused test files during implementation.

AGENTS.md reference: AGENTS.md:L215-L224

Useful? React with 👍 / 👎.

[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-09-20T04:57:24.745125Z	34f9d3d	PR opened

ℹ️ 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.