architecture

# /supergraph:architecture Three phases: explore → HTML report → grilling loop. Announce: "🏛️ /supergraph:architecture — mapping codebase structure..." ## Phase 1 — Explore **1a. Read CONTEXT.md:** ```bash cat CONTEXT.md 2>/dev/null || echo "No CONTEXT.md" ``` **1b. Codebase Memory overview (optional):** Use `CBM_PROJECT` with `get_architecture` aspects `overview`, `layers`, `boundaries`, `clusters`, and `hotspots`. After `get_graph_schema`, run shared contract recipes `hubs`, `bridges`, `cross-boundary`, and `test-gaps`. If codebase-memory-mcp is unavailable, label graph evidence `unavailable`, use Serena/filesystem evidence, and generate Mermaid diagrams from imports. **1c. Serena structure (optional):** ``` mcp__serena__get_symbols_overview() ``` **1d. Read 3-5 hub node files** — understand actual structure, naming, patterns. ## Phase 2 — Generate HTML Report Write self-contained `docs/supergraph/architecture-review-<YYYY-MM-DD>.html` with Tailwind+Mermaid header, architecture `graph TD`, per-candidate card (Problem/Proposal/Before/After Mermaid/Impact/Trade-offs with badge Strong/Worth exploring/Speculative), plus tables for Test Gaps and Unexpected Coupling. Open: `open docs/supergraph/architecture-review-<date>.html || xdg-open ... || echo "Report saved: ..."` ## Phase 3 — Grilling Loop For each Strong candidate, ask one focused question: > "Candidate N proposes [X]. Is this consistent with [constraint from CONTEXT.md / known business rule]?" Incorporate a...