docs(devlog): open the round 2 follow-up unit

[lidge-jun]

Summary

• Open devlog/_plan/260920_round2_followups/ for the work the post-2.60.0 batch left behind, plus two things it caused.
• Priority 1 is [Bug]: 2.60.0 hard-refuses the authless provider-table transition on a home with paginated openai threads and offers no supported way forward #5321, a 2.60.0 regression: on a Codex home with paginated history, the authless provider-table transition is hard-refused and nothing is written, where before 2.60.0 the relabel stood down and the routing and catalog half still landed. The guard's reasoning is correct — a paginated row cannot be relabeled, and standing it down would route an openai-tagged thread to Codex's own endpoint — but refusing the whole transition with "do not retry" and no named remediation is what traps the user. ocx restore / stop / uninstall refuse to restore config.toml on paginated Codex history, leaving the CLI pointed at a dead proxy port #4812 is the same guard blocking recovery, so both are one lane.
• Priority 2 is the red macos widget + bundle check on dev. The appex and bundle build; tauri build refuses because the updater public key is committed without a private key in CI. That is configuration, and release signing belongs to the release workflow rather than a verification build.
• The rest are remainders each lane recorded explicitly rather than hid, with the reason they were not landed in the first round.

Verification

• Documentation only; no source, test or workflow changes.
• The guard behaviour is quoted from src/codex/history-provider.ts at the current dev head, and the CI failure from the job log of the run on dev.

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.

[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-20T11:51:38.344796Z	d4e1755	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.

[github-actions]

✅ Deterministic PR hygiene checks passed.

[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: ada7e4dc-4820-4e14-96a6-cb5cc3cb8652

📥 Commits

Reviewing files that changed from the base of the PR and between 5b7f777 and d4e1755.

📒 Files selected for processing (1)

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

 ___________________________________________
< Crossing the tensor streams to find bugs. >
 -------------------------------------------
  \
   \   (\__/)
       (•ㅅ•)
       / 　 づ

✨ 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.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d4e1755033

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

Remove the already-fixed #5292 item

At this commit's parent, gui/src/pages/Logs.tsx already imports AttemptRecoveryKind from the durable telemetry contract and defines an exhaustive RECOVERY_KIND_KEYS mapping containing all thirteen members; tests/usage/request-outcome-agreement.test.ts also verifies that every durable kind has a dashboard label. The described nine-member restatement was fixed by 555f0cac, so listing it as remaining work and assigning it to R3 would send that lane after a defect that no longer exists; remove it or replace it with the actual unresolved portion of #5292.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Restore the required verification steps

This constraint directs every behavior-changing lane to skip all local suites and typechecking in favor of hosted CI, but non-trivial PRs must run bun run typecheck and bun run test before becoming review-ready. Revise the constraint to permit the required focused implementation checks and PR-ready gates; otherwise these lanes cannot follow the repository's mandatory verification workflow.

AGENTS.md reference: AGENTS.md:L234-L236

Useful? React with 👍 / 👎.