- gstack-evidence now correctly handles environments where bun auto-loads .env files into child processes
- gbrain wireup's first sync no longer silently repoints a user's primary knowledge source
- setup --host slate now properly reports when installation fails instead of exiting with success
- land-and-deploy's merge recovery now fully executes the --delete-branch operation it promises
- unattributed deny ingest policy now correctly applies to the pages it names
- Skill-dir cleanup now properly finds orphaned files
From gstack
Or the wrong thing — now do what they say, or say loudly that they couldn't. Every fix in this wave closes the same failure shape. gstack-evidence — the tool other tools believe — certified runs whose environment differed from CI's, because bun auto-loaded the repo's .env files into every child it spawned. The gbrain wireup's first sync targeted the brain's default source, which could silently repoint a user's primary knowledge source at the gstack worktree while the just-registered source got zero pages — and still print a success line. ./setup --host slate exited 0 having installed nothing. land-and-deploy's merge recovery re-established everything except the --delete-branch half it had promised, and said nothing. A _unattributed → deny ingest policy never applied to exactly the pages it names. Skill-dir cleanup structurally could not find orphans. And a false-green test fixture meant the gbrain missing case could never fail on any machine with a real gbrain installed.