Repository navigation
Codex reviewed v0.5.0 and opened with "not release-ready" again. Its best finding was against the fix shipped in v0.5.0.
A silent log is not a dead writer. Codex goes quiet while it runs tests or blocks on I/O, so reclaiming a lock on log age would admit a second writer beside a live orphan — the exact failure v0.5.0 claimed to close. Age no longer authorizes anything. The resume helper records the pid of the codex child it launches, reclaim requires the bookkeeper and that writer to be gone, and a lock with no recorded writer refuses to clear itself and points at the new cl_lock_recover, which still refuses while anything it can identify is alive.
An approval described the state at record time, not the state that was read. Read a plan, approve it after it changed, and the approval covered text nobody read. Both gates now record what they showed, and cl_record_verdict refuses an approval that does not match.
cl_doctor read a logged-out codex as logged in, because "Not logged in" contains "logged in".
The fence check no longer claims to be injection defence. Findings and instructions are the same kind of text at the same level, so a heading or plain English does what the fence does. The check stays as a structural guard; the claim is gone.
Rejected from the same review: its lead critical said _cl_tree_id always fails because git rejects a zero-byte index. On git 2.50.1, the version it named, that read-tree returns 0. It reasoned from git's source instead of running it.
72 → 75 assertions.