docs: name what Codex caught in the #145 paragraph (improvise-1xfb.1)

Review nit on #305: after the new recipe paragraphs, "ChatGPT Codex caught
it" read as the cherry-pick. It now starts its own paragraph and names the
#145 base problem.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VdfEGXA7aJ6ftMsCc9PJze

AGENTS.md

@@ -163,8 +163,9 @@ mirror or a local `main`, as in #148 below. Only then, cut a fresh branch from
 the pinned `gh/main` SHA and cherry-pick only your own commits. `-x` keeps the
 link to each original. Open a new PR, and close the old one without
 force-pushing it.
-ChatGPT Codex caught it; nothing in CI could, because the result compiles and
-passes. The tell is a PR diff naming files the ticket has no reason to touch,
+
+ChatGPT Codex caught the #145 base problem; nothing in CI could, because the
+result compiles and passes. The tell is a PR diff naming files the ticket has no reason to touch,
 so **read your own PR's file list before asking for review** — and diff against `gh/main...<branch>`, never the local equivalent. **The second vector is the worktree base**: a branch cut from the orchestrator's *local* `main` inherits whatever that checkout has merged but not yet pushed, and nothing in the branch says so. That hit PR #148 with another PR's whole diff — including `.beads/`, `kb.pl` and `context/repo-map.md`, the three files agents are forbidden to touch, so the review read as a rule violation rather than a base problem. Note the window
 is transient — the two remotes are equal immediately after the orchestrator
 syncs — which makes it worse, not better: the hazard is absent exactly when