bridge-explorerlisted

# Bridge Explorer Visualize Bridge state as interactive HTML dashboards. Read the referenced file ONLY when triggered. ## Decision Tree ``` User wants to... ├── Ecosystem visualization → Read references/workflow.md ├── CORE/USER repo split visual → Read references/repo-layout.md │ (triggers: "repo layout", "core/user", "where do files live", │ "repo structure"; pick variant v1–v4 or c-prime, see below) ├── Information flow / network → Render + open the network variant │ (triggers: "network diagram", "constellation", "how is everything linked", │ "how does the bridge distribute information", "layers") └── Questions about ecosystem → Read ecosystem.yaml directly ``` ## Repo-layout variants All variants render the same CORE/USER + cluster-wrapper split, sourced from `docs/repo-layout/regions.yaml` (single source of truth — edit there, all variants pick up on regenerate). **Constellation (`network`) is generated, not hand-edited.** Its nodes/edges/flows live in `regions.yaml` under `constellation:` (schema v3). After editing them run: ``` python3 docs/repo-layout/build-constellation.py ``` This injects the JS data block into `network.html` between the `CONSTELLATION-DATA` markers and bumps the version badge. **Precondition:** `network.html` must have been rendered first — the script refreshes the data block of an existing rendered file; on a fresh clone there is no `network.html` yet, so render it via this skill first. Wire it