gstack /cso now audits part of a big repo and lists what it skipped

1 hour ago

gstack 1.91.112.0 to 1.91.113.0: the /cso security audit takes --paths to cover part of a repository over its source cap and lists every path it skipped, a Capy install that has fallen behind says so with the fix, a skipped session-start upgrade now fails, and a lease held by a reused pid no longer blocks upgrades. Release notes 1.91.112.0: https://github.com/garrytan/gstack/blob/main/CHANGELOG.md#1911120---2026-10-17 Release notes 1.91.113.0: https://github.com/garrytan/gstack/blob/main/CHANGELOG.md#1911130---2026-10-17 Commits: https://github.com/garrytan/gstack/commits/main

Ask

Ask about this presentation

Answers are generated from this presentation.

Chapters

  1. 0:00Paths
  2. 0:14Diff
  3. 0:31Behind
  4. 0:42Upgrade
  5. 0:56Lease
Show transcript

Paths

gstack logo

gstack /cso now audits part of a big repo and lists what it skipped

$ gstack-cso start --paths src/core,src/mcp
Every path outside the prefixeslisted as skipped
Snapshot and history coveragemarked partial
PathsDiffBehindUpgradeLease
garrytan/gstack · CHANGELOG.md 1.91.112.0

gstack's /cso audit can now cover part of a repository too big for its 64 megabyte cap. Every path outside your chosen folders is listed as skipped, and coverage is marked partial.

Diff

A diff audit with --paths refuses changes outside its scope

A file changed, added or deleted outside the prefixesrun refused, file named
.npmrc, bunfig.toml, .claude/refused like any other
Only dependency trees such as node_modules are exempt. The 100,000-entry limit still counts every file.
PathsDiffBehindUpgradeLease
garrytan/gstack · CHANGELOG.md 1.91.112.0

In diff mode, /cso with paths fails closed. Any change outside your chosen folders stops the run and is named, including npm, Bun and Claude configuration. Only dependency trees like node modules are exempt.

Behind

A Capy install that has fallen behind says so in the ok line

gstack: ok <v> for=<skill> (behind=<n> (latest: <v>); fix: <command>)
A session 12 commits behind originused to read as current
fix:the command that closes the gap
PathsDiffBehindUpgradeLease
garrytan/gstack · CHANGELOG.md 1.91.113.0

On Capy, a session twelve commits behind used to look current. Now gstack's ok line says how far behind you are, and names the command that closes the gap.

Upgrade

A skipped upgrade at session start now fails

gstack: fail behind (UPGRADE_BUSY|UPGRADE_REFUSED)
Upgrade busy, refused or missingexit 1, workflows refuse until the fix runs
Upgrades switched off on purposestays ok, with the behind note
PathsDiffBehindUpgradeLease
garrytan/gstack · CHANGELOG.md 1.91.113.0

When the session start upgrade is busy, refused or missing, install mode now fails, and workflows refuse until you run the fix. If you switched upgrades off yourself, it stays ok and notes the gap.

Lease

A reused pid no longer blocks every upgrade

Lease pid now belonged to dbus-daemon or systemd-logindupgrades wedged, trailer said ok
gstack-lease stores the holder's start identitystale lease reclaimed
Older Capy checkouts are fast-forwarded at install-mode session start.
CHANGELOG.mdFull notes, with the /cso step for hand-trimmed copies
PathsDiffBehindUpgradeLease
garrytan/gstack · CHANGELOG.md 1.91.113.0

Upgrades no longer wedge behind a lease whose process ID now belongs to another program, such as dbus-daemon. The lease stores who holds it, and reclaims a stale one. Older Capy checkouts get fast-forwarded.