docs(devlog): open the meaning-preservation and request-scoped safety batch

[lidge-jun]

Summary

• Open devlog/_plan/260920_meaning_preservation_batch/ for the first six items of the post-2.60.0 assessment: request-scoped transport safety (fix(security): keep DNS pinning unless the proxy applies to the request #5087), managed-write symlink safety (fix(integrations): reject symlinked managed write targets #5241), and the four meaning-preservation defects (tool declaration fields are dropped on the outbound adapters #5210, tool choice policy is dropped on the Chat Completions path #5211, inline document bytes do not survive the inbound parse #5212, developer messages are folded into the system prompt on every Chat host except api.openai.com #5213).
• Records the governing contract for the batch — preserve on supported paths, refuse or apply the operator's conversion policy on unsupported ones, never drop silently and report success — and the two-lane split with acceptance per item.
• Fixes the delivery topology as one branch with ordered commits and one pull request per lane, with Co-authored-by attribution for carried contributor work, and restates the union-defect checks that blocked the 2.60.0 release.

Verification

• Documentation only; no source, test or workflow changes.
• Issue and pull request states were read back from the GitHub API before writing the lane tables.

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: 33b7e260-bd5e-4937-85f3-9e703c271c2b

📥 Commits

Reviewing files that changed from the base of the PR and between 64bad3e and 7d5d83d.

📒 Files selected for processing (1)

• devlog/_plan/260920_meaning_preservation_batch/000_plan.md

 _____________________________________________________________________________________________________________________________________________________
< Progress in a fixed context is almost always a form of optimization. Creative acts generally don't stay in the context that they are in. - Alan Kay >
 -----------------------------------------------------------------------------------------------------------------------------------------------------
  \
   \   (\__/)
       (•ㅅ•)
       / 　 づ

✨ 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 Summary

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

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-20T04:47:48.182819Z	7d5d83d	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.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 7d5d83db60

ℹ️ 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 unreleased safety triage out of the tracked devlog

Because this unit is explicitly OPEN, these rows publicly document two unfixed security weaknesses and their triggering conditions: an unpinned direct connection after proxy bypass or DNS failure, and a symlink-following managed-write race. Repository policy requires unreleased findings and pre-disclosure patch plans to remain in scratch space; move Lane B to .tmp/ until the fixes ship, then publish only the completed outcome under _fin/.

AGENTS.md reference: AGENTS.md:L124-L127

Useful? React with 👍 / 👎.