fix(codex): retire native assignments from an earlier session lifecycle (#201306) Doctor kept Codex native assignments whose lifecycle revision appeared on only one side and reported a recoverable warning. Any plugin migration warning keeps the deferred Codex migration pending, so after updating, the Codex plugin stayed in pending-state-migration and new workers failed with owner-plugin-degraded. Repeating Doctor never cleared it. Native recovery restores only assignments whose revision equals the current owner's. A session reset keeps the session ID and mints a fresh revision, and revisions are never reissued, so a one-sided assignment can never be delivered again. Doctor now keeps an assignment only when the revisions are equal (including both absent on legacy owners) and retires the rest with their matching receipts, as it already does for mismatched revisions. Refs #197515 Co-authored-by: Peter Steinberger <steipete@gmail.com>
fix(codex): retire native assignments from an earlier session lifecyc…
Find Your Interest
- Fine-Tuning an AI – Part I
- The First Step Toward Ethical AI Edit
- 10 Books I Finished Recently
- This could be the golden age of the internet. Why not?
- The Agentic Web
- How my software engineering workflow has changed in the past year
- EP231: AI Terms You Need to Know
- Everything Is An API Now
- How to Build an AI-Native Business That Actually Saves Time
- Borrowed Time: How Rising Rates Reach the AI Build-Out





