From eb7ef2153b8b299b942c17ffc1f26e8996471d9e Mon Sep 17 00:00:00 2001 From: Garry Tan Date: Sun, 15 Mar 2026 17:04:49 -0500 Subject: [PATCH] docs: add setup comments to .gstack-sync.json.example Explain what team sync gives you, that it's optional, and how to set it up. Points to TEAM_COORDINATION_STORE.md for full guide. Co-Authored-By: Claude Opus 4.6 (1M context) --- .gstack-sync.json.example | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/.gstack-sync.json.example b/.gstack-sync.json.example index 4803eb42..6dc6dce7 100644 --- a/.gstack-sync.json.example +++ b/.gstack-sync.json.example @@ -1,4 +1,9 @@ { + "_comment": "OPTIONAL: Team sync configuration for shared eval/retro/QA data via Supabase.", + "_docs": "See docs/designs/TEAM_COORDINATION_STORE.md for full setup guide.", + "_what_you_get": "Shared eval dashboards, cross-team trend tracking, retro aggregation, QA report history. Without this file, everything works locally — sync is purely additive.", + "_setup": "1. Create a Supabase project. 2. Run supabase/migrations/*.sql in order. 3. Copy this file to .gstack-sync.json and fill in your values. 4. Set GSTACK_SUPABASE_ACCESS_TOKEN or run gstack sync login.", + "supabase_url": "https://YOUR_PROJECT.supabase.co", "supabase_anon_key": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.YOUR_ANON_KEY_HERE", "team_slug": "your-team-name"