README changes:
- Rewrote the "Cross-machine memory with GBrain sync" section into
"GBrain — persistent knowledge for your coding agent." Covers the
three /setup-gbrain paths (Supabase existing URL, auto-provision,
PGLite local), MCP registration, per-remote trust triad, and the
(still-separate) memory sync feature.
- Added /setup-gbrain row to the skills table pointing at the full guide.
- Added /setup-gbrain to both skill-list install snippets.
- Added USING_GBRAIN_WITH_GSTACK.md to the Docs table.
New doc (USING_GBRAIN_WITH_GSTACK.md):
- All three setup paths with trust-surface caveats
- MCP registration details (and honest Claude-Code-v1 scoping)
- Per-remote trust triad semantics + how to change a policy
- Switching engines (PGLite ↔ Supabase) via --switch
- GStack memory sync + its relationship to the gbrain knowledge base
- /setup-gbrain --cleanup-orphans for orphan Supabase projects
- Full command + flag reference, every bin helper, every env var
- Security model: what's enforced in code, what's enforced by the leak
harness, and the honest limits of v1
- Troubleshooting: PATH shadowing, direct-connection URL reject,
auto-provision timeout, stale lock, policy file hand-edits,
migrate hang
- Why-this-design section explaining the non-obvious choices
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
