Deploy
gstack’s /land-and-deploy stops halting parallel PRs on a false VERSION drift
gstack’s land and deploy stops halting parallel pull requests on a false version drift. All three false stops now pass, including the micro bump that failed with no other pull request open.
Collisions
A real VERSION collision still stops the land
The check now reads your ship policy first. A duplicate version on another pull request, or a base that has caught up, still halts the land. Under stamp at merge, a stale stamp halts and names the fix.
Office hours
/office-hours now sees your diff in a repo whose default branch is master
Office hours used to diff against origin main. On a master clone that failed with its error hidden, so the model saw no changes. It now follows the remote’s default branch.
Prompts
Three skill prompts stop contradicting their own code
Three more prompt fixes. /health gives one GBrain score instead of two that disagreed. Plan design review stops naming an old vision model. And in /ios-qa, demo mode now means visible taps only.
Next
If you land parallel PRs with /land-and-deploy, I would upgrade now
docs/ship-policy.mdWhat /land-and-deploy reads from itCHANGELOG.mdgarrytan/gstack · 1.91.195.0 and 1.91.196.0If you keep several pull requests open at once, I would upgrade now, because the false halts are gone and the real ones remain. The ship policy doc lists when each queue mode stops.
