Review
gstack’s /ship now stops when the second-opinion review says not ready
gstack’s ship and Codex skills now stop when the outside reviewer says not ready. Before, a reply listing only minor P2 or P3 findings passed as clean, verdict and all.
Rust
/ship’s pregate now runs the tests for every Rust file you touch
In a mixed Rust repo, every touched Rust file failed pregate with no test lane, so ship never got a receipt. Now it runs cargo test for that crate and its dependents.
Nested
A nested Vitest or Jest package runs under its own runner
A nested Vitest or Jest package used to run under bun test from the root, causing about ninety-eight false failures in one repo. Now it runs through its own package manager.
Hardening
Three fixes harden the new Rust lane
Three fixes harden the Rust lane. A crate name can no longer run a shell command. A hostile workspace glob no longer stalls it for seconds. And a plain test function in source now counts.
GBrain
/sync-gbrain now names the autopilot that blocks it
When sync GBrain refuses because an autopilot is running, it now names each process and its command, then says how to stop it. The check stays machine wide, so another brain’s autopilot still blocks.
Next
If you run /ship on a Rust repo, I would upgrade now
docs/troubleshooting.mdHow the verdict is read from a reviewCHANGELOG.mdgarrytan/gstack · 1.91.197.0 to 1.91.199.0If you ship a Rust or mixed repo, I would upgrade now, because pregate finally runs your tests. The troubleshooting doc explains how a review verdict now blocks.
