[outreach] ROADMAP supported-CLI matrix omits the Codex Stop / Gemini CLI AfterAgent hooks the README now documents #425

Outreach Opportunity

Type: contributor-onboarding
Target: rationguard users of Codex and Gemini CLI evaluating support levels

ROADMAP.md's supported-CLI matrix says its levels are "derived from what the repository tests or documents today", and the claude row cites "the README documents a Claude Code Stop hook for post-response detection" as evidence. Since #422 (merged after ROADMAP.md landed in #409), the README also documents a post-response hook for Codex (Stop, README "As a Codex Stop or Gemini CLI AfterAgent hook") and Gemini CLI (AfterAgent), and runbooks/stop-hook-not-challenging.md covers both. The codex and gemini rows still list only their --dangerous mapping, so a Codex or Gemini user reading the roadmap does not learn that a documented hook path exists for them.

Why Now

#421/#422 just widened the documented audience to two more CLIs; the roadmap is the page someone checks to decide whether their CLI is supported.

Proposed Action

Add the documented hook to the Evidence column of the codex and gemini rows. Keep both rows at Best-effort: there is still no CLI-specific test or fixture (no codex/gemini match in src/*.test.ts or .github/tests/), and ROADMAP.md's own promotion rule requires CI-run tests.

• codex and gemini Evidence cells in ROADMAP.md mention the README hook section

Decision taken by hive: evidence-only edit; support levels unchanged.

— hive: agent=outreach backend=copilot model=claude-opus-5.5 copilot=1.0.88