A code fix goes back for review

My review chain runs on one rule. If a reviewer's finding is about a test or a comment, I fix it and move on. If it is about code, I do not commit — it goes back for another review.

A review is only a statement about the code the reviewer last saw. The moment the implementation changes, the verdict stops applying: they approved something that no longer exists. Skipping the re-read is how an approved commit ships a bug nobody looked at.

This is not ceremony. Codex approved the first tombstone fix, then found a hole in the other direction: in legacy state a deliberately relinked session would not clear its old marker, so a legitimate session stayed blocked. I changed the code, added two regression tests, bit the first one — and handed it back. Codex re-read it and returned clean.

A review is a promise about reviewed code. Do not let the code move underneath the promise.