docs(devlog): open the Codex sign-in lockout incident lane

[lidge-jun]

Summary

• Record the incident lane opened for 用Codex配置完opencodex后无法调用模型，重启后无法登录 #5261, where an applied Codex integration left a Windows user unable to sign in to Codex at all after a restart, with only "Unable to load sign-in requirements" and a Retry button visible.
• States why this outranks the roadmap bundles: an applied integration survives a reboot, so the lockout persists and the only control the user can reach is a retry against the endpoint that is failing.
• Lists what the lane must establish from source rather than assume, including whether the apply scope covers the authentication and sign-in bootstrap and whether a recovery path exists that does not require the proxy to be running.
• Adds an execution constraint specific to this lane: it may not run the proxy, start the service, or modify any credential or configuration file, because the incident itself is a configuration change that locked a user out.

Verification

• Documentation only; no source, test or workflow changes.
• The reported client, area, version, platform and labels were read back from the issue before writing.

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-20T05:21:33.222579Z	c6d8f3b	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: 373c7c42-8c55-4eac-ba5c-b275e40554f6

📥 Commits

Reviewing files that changed from the base of the PR and between b9483b3 and c6d8f3b.

📒 Files selected for processing (1)

• devlog/_plan/260920_meaning_preservation_batch/020_incident_5261.md

 _____________________________
< Here comes the bug bouncer. >
 -----------------------------
  \
   \   \
        \ /\
        ( )
      .( o ).

✨ 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: c6d8f3b899

ℹ️ 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 the open authentication incident out of devlog

Because this lane is explicitly still open and records an unfixed authentication lockout, its failure path, investigation targets, and proposed fix standard are pre-disclosure security working notes rather than publishable project documentation. Keeping it under tracked devlog/_plan exposes that material in permanent public history; keep the investigation in .tmp/ and publish only the fix, regression test, and post-fix outcome.

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

Useful? React with 👍 / 👎.