gstack 1.91.145.0 stops failing Opus 5.5 for harmless file reads in its /qa-only and docs-sync tests

1 hour ago

gstack 1.91.145.0: the /qa-only test stops failing Claude Opus 5.5 for harmless file reads. Reads may discard or merge their errors, stopping the browser counts as cleanup, and the docs-sync test forgives one wrong path. Thresholds and behavior checks are unchanged. Release notes: https://github.com/garrytan/gstack/blob/main/CHANGELOG.md#1911450---2026-10-19 Changelog: https://github.com/garrytan/gstack/blob/main/CHANGELOG.md Commits: https://github.com/garrytan/gstack/commits/main

Ask

Ask about this presentation

Answers are generated from this presentation.

Chapters

  1. 0:00Reads
  2. 0:13Errors
  3. 0:28Browser stop
  4. 0:43Docs sync
  5. 0:56Unchanged
Show transcript

Reads

gstack logo

gstack’s /qa-only test stops failing Opus 5.5 for reading a skill file

wc -l qa-only/SKILL.md; ls qa-only …
was: unsupported outer shell composition
same read, inside the fixture
now: passes
ReadsErrorsBrowser stopDocs syncUnchanged
garrytan/gstack · CHANGELOG.md

gstack's /qa-only test stops failing Claude Opus 5.5 for looking at a skill file. A line count and a directory listing inside the test folder now pass.

Errors

A read may now discard or merge its errors

ls; ls qa/templates; cat TODOS.md 2>/dev/null | head -20
passes
… 2>&1
passes
2> file · > · >> · | tee · /etc
still fails
ReadsErrorsBrowser stopDocs syncUnchanged
garrytan/gstack · CHANGELOG.md

Sending a read's errors to dev null, or merging them into its output, now passes in the /qa-only and docs sync tests. Every other redirect, and any read that leaves the test folder, still fails.

Browser stop

Stopping the browser now counts as cleanup

closetab
cleanup
"$B" stop
cleanup, after the last probe
stop before a probe · stop --all · outside the guard
still fails
ReadsErrorsBrowser stopDocs syncUnchanged
garrytan/gstack · CHANGELOG.md

Stopping the browser now counts as cleanup, the same as closing a tab, when the agent does it inside the guard after its last probe. A stop before a probe, or outside the guard, still fails.

Docs sync

The docs-sync test forgives one wrong path

<no such path>/gstack-docs-candidate
Exit code 127
same command, declared path
case passes
wrong path that exists · any other exit code
still fails
ReadsErrorsBrowser stopDocs syncUnchanged
garrytan/gstack · CHANGELOG.md

The docs sync test forgives one wrong path. An agent that calls the docs helper at a missing path, then reruns it at the declared path, now passes. A wrong path that does exist still fails.

Unchanged

Thresholds, trials and behavior checks stay the same

CHANGELOG.mdgstack release notes, every case that still fails
Which model runs your /qa-only checks: Opus 5.5 or Fable 5.1?
ReadsErrorsBrowser stopDocs syncUnchanged
garrytan/gstack · CHANGELOG.md

Pass thresholds, trial counts and behavior checks stay the same, and the changelog lists every case that still fails. Which model runs your /qa-only checks, Opus 5.5 or Fable 5.1?