Trains
gstack 1.91.162.0 lets a merge train of PRs share one full eval gate
gstack's evals workflow can now run merge trains. Several ready pull requests share one full gate. That run publishes the train's record and the full gate check that the ship queue waits for.
Bisect
A red train bisects with one executor per prefix
When a train goes red, the bisect now runs one executor for each prefix of the train. Each one checks out its prefix, verifies it, and uploads its own record for train bisect.
Screens
Under a train block, a PR push prints a free screen estimate
With a train block in the policy, pushing a pull request stops starting paid eval slices. It prints the screen selection and an estimated cost instead. Asking ready for a screen dispatches the real one.
Backstop
A five-PR train fires zero backstop gates on main
A new backstop runs on every push to main. It runs the full gate only for a tree that a green train left uncovered, so a five pull request train adds zero backstop gates.
Still off
Trains stay off until the ship policy declares a train block
docs/ship-policy.mdRun a merge trainWithout a train block, every push runs today's jobs, and gstack's own policy doesn't carry one yet. Turning trains on there is a separate one-line pull request. Do you run the ship queue on your own repo yet?
