iOS QA
gstack’s /ios-qa picks your iPhone session back up after a daemon restart
A restarted /ios-qa daemon used to relaunch your app to get back in, wiping its QA state. Now it resumes the same device session. It stays a draft until tested on a real iPhone.
Session key
The saved session key only goes to the device it came from
The daemon keeps that session key in a file only you can read, tied to one device, app and port. If anything differs, or the app rejects the key, it starts fresh the normal way.
Autoplan
/autoplan stops blocking healthy runs on a slow session journal
On Claude Code 2.1.292, the /autoplan guard could deny a healthy run's first step, because the session journal lagged. Now it waits up to two seconds for the journal. A run that skipped init is still stopped.
Office hours
The office-hours reviewer can’t patch its own verdict anymore
In /office-hours, the spec reviewer could fix its own verdict file with a quick edit after a seal error. Now it has to write the complete verdict again and rerun the seal.
Your setup
An /ios-qa restart keeps your app’s state, and /autoplan runs on
CHANGELOG.md1.91.170.0 · 1.91.171.0Both fixes ship in gstack's latest release, and the changelog has the detail. How often does your /ios-qa daemon restart in the middle of a session?
