Merge remote-tracking branch 'origin/main' into garrytan/workspace-aware-ship

Rebumped v1.8.0.0 -> v1.11.0.0 (minor-past main's v1.10.1.0) using
bin/gstack-next-version — the same queue-aware path this branch introduces.
CHANGELOG repositioned so v1.11.0.0 sits above main's new entries
(v1.10.1.0 / v1.10.0.0 / v1.9.0.0).

Conflicts resolved:
- VERSION, package.json: rebumped to v1.11.0.0 (util-picked)
- bin/gstack-config: merged both lists (workspace_root + gbrain keys)
- CHANGELOG.md: hoisted v1.11.0.0 entry above main's new entries

Pre-existing failures in main (4) documented but not fixed in this PR:
1. gstack-brain-sync secret scan > blocks bearer-json (brain-sync tests)
2. no files larger than 2MB (security-bench fixture, already TODO'd)
3. selectTests > skill-specific change (touchfiles scoping)
4. Opus 4.7 overlay pacing directive (expectation stale after v1.10.1.0
   removed the Fan out nudge)

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

README.md

@@ -359,12 +359,42 @@ I open sourced how I build software. You can fork it and make it your own.
 > Come work at YC — [ycombinator.com/software](https://ycombinator.com/software)
 > Extremely competitive salary and equity. San Francisco, Dogpatch District.
 
+## Cross-machine memory with GBrain sync
+
+gstack accumulates a lot of useful state on your laptop: learnings, CEO
+plans, design docs, retros, developer profile. Today, all of that dies when
+you switch machines. **GBrain sync** optionally pushes a curated, secret-scanned
+subset to a private git repo so your memory follows you, and (if you use
+GBrain) becomes indexable there.
+
+One command to turn it on:
+
+```bash
+gstack-brain-init
+```
+
+That creates a private GitHub repo (or any git remote you prefer —
+GitLab, Gitea, self-hosted). Every skill run syncs the queue at its
+start and end boundaries. No daemon, no background process. A one-time
+privacy prompt asks how much you want to share (everything allowlisted /
+artifacts only / off). Secret-shaped content (AWS keys, GitHub tokens,
+PEM blocks, JWTs, etc.) is blocked from sync before it leaves your
+machine.
+
+New machine?  Copy `~/.gstack-brain-remote.txt` over, run
+`gstack-brain-restore`, and yesterday's learnings surface on today's
+laptop.
+
+Full guide: [docs/gbrain-sync.md](docs/gbrain-sync.md) •
+Error index: [docs/gbrain-sync-errors.md](docs/gbrain-sync-errors.md)
+
 ## Docs
 
 | Doc | What it covers |
 |-----|---------------|
 | [Skill Deep Dives](docs/skills.md) | Philosophy, examples, and workflow for every skill (includes Greptile integration) |
 | [Builder Ethos](ETHOS.md) | Builder philosophy: Boil the Lake, Search Before Building, three layers of knowledge |
+| [GBrain Sync](docs/gbrain-sync.md) | Cross-machine memory setup, privacy modes, troubleshooting |
 | [Architecture](ARCHITECTURE.md) | Design decisions and system internals |
 | [Browser Reference](BROWSER.md) | Full command reference for `/browse` |
 | [Contributing](CONTRIBUTING.md) | Dev setup, testing, contributor mode, and dev mode |