Detector
gstack 1.91.127.0 runs the State Machines specialist in /review and /ship even when its detector fails
gstack-state-matrix detect exit 0uses its outputdetector failsSCOPE_STATE_MACHINE=unknownIn gstack 1.91.127.0, /review and /ship run the State Machines specialist even when its detector fails. A failure prints unknown, and unknown sends the specialist in.
Probes
/qa stops exploring only after one probe per input rule of each field
/qa now keeps exploring until each documented input rule of each field has its own probe. A value that breaks two rules at once covers neither. Rules still uncovered at the time cap get listed as limits.
Reruns
After a fix, /qa reruns every capture its verdict relies on
Once a fix lands, /qa treats every earlier capture as out of date. Each capture the verdict depends on gets run again, or the report lists it as open, so a pass describes the fixed code.
Fixes
Three smaller fixes you may have hit
gstack-docs-candidate snapshot --help and compare --help exit 0 before any side effectWithout Aside, consent options are now lettered B, C and D, matching the answer keys. Plan reality tier one rows are never not applicable, so runs stop looping past the deadline. And the docs candidate help flags exit before any side effect.
Notes
Which do you run before a merge: /review or /ship?
gstack-qa-evidence caller? The release notes have one step for you.CHANGELOG.md1.91.127.0, "If you…"If you write a caller for gstack QA evidence, the release notes carry one step for you. So, which do you run before a merge: /review or /ship?
