On Codex, gstack's /review can no longer end a session with a required
step skipped: the end-of-session check reads Codex's own session log and
sends the agent back to finish, as it already does on Claude Code.
Why: Codex users got routing and the destructive-command check in #4512,
but not the /review checklist, so a review could stop after the diff
read with no second-model pass.
To use it: run `./setup` again and trust the new hook in Codex
(`/hooks`); turn it off with `GSTACK_SKILL_CONTRACTS=off`.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
Review-Finding: p1/specialist-batched#1 reader=testing
Review-Finding: p1/specialist-batched#2 reader=testing
On Codex, gstack's routing hint now names each skill by the `name:` in
its installed SKILL.md (`review`), the name Codex lists, so `$review`
loads the suggested skill.
Before, the hint said `gstack-review` (the folder name), which Codex
doesn't list, so mentioning it loaded nothing.
Nothing to do: the next `./setup --host codex` picks it up. Claude
Code's hint is unchanged.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
`./setup --host codex` now adds gstack's skill-routing hint and
destructive-command check to Codex's `~/.codex/hooks.json`, next to your
own hooks, so Codex users get the same guardrails Claude Code users
have.
Codex runs a hook only after you trust it, so nothing fires until you
accept gstack's hooks at Codex's startup prompt or in `/hooks`;
`gstack-doctor` shows whether you have.
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
Review-Finding: p1/red-team#1 reader=red-team