False pass
/ship stops passing an outside review that found a bug
gstack's /ship gate read an outside review as clean whenever no issues appeared anywhere in it, so a reply that flagged a dropped database index passed. Now that reply reads unverified.
Codex
A clean Codex review now reads clean
The fix works the other way too. A clean Codex review that says it found no actionable regressions used to read unverified. Regressions and defects now count as no-findings words, so that reply passes.
Last word
“No issues” only counts as the review’s last word
The phrase now has to open the review's final sentence, with no but or however attached. Untagged findings followed by no issues found in the changed parser still read clean, since without tags a finding looks like a summary.
Nested repos
/cso now starts on repos with a submodule or a nested Git repo
/cso, the security audit, stopped with an unsafe path error on any repo holding a submodule or a nested Git repository. Now it lists that folder as excluded and never reads it. A symlink to a folder is still refused.
Long history
/cso finishes the history check on a long patch history
A long patch history used to leave its history check unassessed. Now /cso keeps the newest whole commits that fit, never cutting inside one, and marks history coverage as partial.
Fixes
A saved “never ask” now sticks, plus two more fixes
/plan-eng-review now remembers a never ask you saved for its structure question. /context-restore asks you to choose when recent checkpoints carry different titles. A new guide covers a first deploy when /setup-deploy finds nothing deployed.
Your turn
The full notes are in gstack’s changelog
CHANGELOG.mdgstack release notes, October 19The test changes behind these fixes are listed in gstack's changelog. Which agent runs your outside review before you /ship?
