Trains
gstack merge trains now merge every PR, not just the first
gstack merge trains now merge every pull request in the train. The first live train stopped at slot two: once slot one merged, every later pull request conflicted with main, so GitHub couldn't squash it.
Verify
Main merged into the PR now passes verify
To clear that conflict, a lane merges main into its pull request. Verify used to refuse that as moved off its pin. Now it passes when the tree matches exactly what the train's gate tested.
Guard
Anything else is still refused
The guard stays. A head that adds even one file outside the train is still refused as moved. And the queue still freezes when earlier slots have merged.
Your setup
Lanes from slot 2 on follow a new procedure
docs/ship-policy.mdRun a merge trainThe ship policy guide now spells out what a lane does from slot two on. Does your ship policy turn merge trains on?















