gstack 1.91.2.0: gbrain readiness, fail-closed secret scans, Aside on zsh

In gstack 1.91.2.0, /sync-gbrain can check whether this worktree's pages are readable without writing a probe page. And when the answer is uncertain, it keeps your existing guidance.

Slide text

gstack 1.91.2.0 checks your gbrain without writing to it

/sync-gbrain confirms this worktree's pages are readable, and keeps your guidance when the answer is uncertain.

01 gbrain 02 Aside 03 Reviews 04 Browse & setup

garrytan/gstack · CHANGELOG.md

Readiness first matches the registered source to this worktree. Then it checks that source's page count, and reads one page back from the same source before it calls the worktree ready.

A foreign pin, a failed read, an invalid count, or an unavailable service all come back as unknown, and your guidance stays in place. A source verified as empty can still offer a reindex.

With scan secrets turned on, memory ingest now runs gitleaks on the rendered page, the exact markdown it imports. The raw transcript escapes its quotes, so a key written that way slipped past the scan.

If gitleaks is missing, errors out, runs past a minute, or writes an oversized report, that file is skipped instead of imported unscanned. Skipped files stay pending and get retried on the next run.

Next, the Aside browser.

The Aside readiness check now works under zsh. It kept its timeout in a variable that zsh won't split, so a stock Mac always answered not running, and browsing skills fell back to bundled Chromium.

A failed check now reports a timeout, a missing way to bound the call, a command error with its exit code, or a missing ready signal. Only that last case asks you to open the app.

Reviews and debugging.

/plan-eng-review now follows its preparation and complexity gate paths in order, and every decision and required report write stays checkable. Calibration write-back stays off unless its explicit gate turns it on.

In /review, the outside Codex challenge is still informational. But its supported findings now enter the Fix-First step, where its approval and convergence gates apply.

/investigate now takes its edit lock with an owner token, and releases only that lock when the run ends. A freeze boundary you set beforehand stays exactly where you put it.

A /freeze boundary now persists until you run /unfreeze. Ending the conversation, or killing it, leaves the boundary in place, so run /unfreeze when you want your edits unrestricted again.

Browse and setup.

The browse upload command now resolves every file through its symlinks and checks the real path against the allowed directories. Before, a relative path skipped that directory check.

On Ubuntu 26.04, setup now picks Playwright's ARM Chromium build on ARM machines, instead of forcing the x64 build. On any other chip, it skips the install and says why.

Browse's stealth mode now keeps Chrome's own extension messaging calls. On Linux, it won't take over an X display that's already in use. And a busy local PGLite database reports as locked.