distributed-meshlisted

## SCOPE **✅ THIS SKILL PRODUCES (exactly these, nothing more):** 1. **`mesh.json`** — Generated from user answers about zones and squads (which squads participate, what zone each is in, paths/URLs for each), using `mesh.json.example` in this skill's directory as the schema template 2. **`sync-mesh.sh` and `sync-mesh.ps1`** — Copied from this skill's directory into the project root (these are bundled resources, NOT generated code) 3. **Zone 2 state repo initialization** (if applicable) — If the user specified a Zone 2 shared state repo, run `sync-mesh.sh --init` to scaffold the state repo structure 4. **A decision entry** in `.squad/decisions/inbox/` documenting the mesh configuration for team awareness **❌ THIS SKILL DOES NOT PRODUCE:** - **No application code** — No validators, libraries, or modules of any kind - **No test files** — No test suites, test cases, or test scaffolding - **No GENERATING sync scripts** — They are bundled with this skill as pre-built resources. COPY them, don't generate them. - **No daemons or services** — No background processes, servers, or persistent runtimes - **No modifications to existing squad files** beyond the decision entry (no changes to team.md, routing.md, agent charters, etc.) **Your role:** Configure the mesh topology and install the bundled sync scripts. Nothing more. ## Context When squads are on different machines (developer laptops, CI runners, cloud VMs, partner orgs), the local file-reading convention still works — but r