Next write
gstack /qa now tells the agent where its report goes after a fail
beforethis verdict is final for this report root
nowthis verdict is final. Next, write the Markdown report beside evidence.json.
Next writeStray file/cso releaseYour setup
garrytan/gstack · CHANGELOG.md · 1.91.178.0
When a gstack /qa run fails, the verdict used to say it was final for this report root. Now it names the next write: the Markdown report, right beside the evidence file.
Stray file
That old hint led the agent outside its folder
verdict: fail
write ../qa-reports-placeholder-unused
write report.md
A write anywhere else, including the parent directory, still fails.
Next writeStray file/cso releaseYour setup
garrytan/gstack · CHANGELOG.md · 1.91.178.0
Twice, an agent read that hint and dropped a placeholder file in the parent directory before writing its report. The check that caught it is unchanged: a write outside the working directory still fails.
/cso release
The /cso runtime release can run to the end
candidate stepgh exit 4GH_TOKEN set
A new test fails any workflow step that calls gh without a token.
Next writeStray file/cso releaseYour setup
garrytan/gstack · CHANGELOG.md · 1.91.177.0
The /cso runtime release stopped after approval, before signing anything, because one step called the GitHub command line with no token. That step has one now, and a new test catches any workflow step missing one.
Your setup
Both fixes are in the changelog
CHANGELOG.md1.91.177.0 and 1.91.178.0Which agent do you run /qa in?
Next writeStray file/cso releaseYour setup
garrytan/gstack · CHANGELOG.md · 1.91.178.0
Both fixes are in the changelog. Which agent do you run /qa in?
