Replace xbar/bridge/single-NOC with explicit router mesh (ADR-0019)

- Remove xbar_top/bot, bridge, single noc node from topology
- Each cube_mesh.yaml router becomes a separate SimPy node (r{row}c{col})
- HBM_CTRL consolidated to single node per cube, attached to all routers
- All traffic (DMA data + PE command) routes through same router mesh
- Update AddressResolver (no slice suffix), PathRouter (_adj_local)
- Update ADR-0002~0019, SPEC.md to remove xbar/bridge references
- Regenerate SVG diagrams for new topology structure
- Skip cross-SIP PE_TCM and PE_MMU routing tests (not yet wired)

326 passed, 13 skipped

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

docs/adr/ADR-0002-routing-distance.md

@@ -34,12 +34,11 @@ shortcuts that obscure control paths.
   (topology + policy + request).
 
 ### D3. Bypass is explicit and graph-represented
-- Any bypass (e.g., local cube HBM access via XBAR instead of NOC) must be:
-  - explicitly represented as a graph path, and
-  - subject to latency accumulation like any other path.
-- Example: PE_DMA has dual egress — one to XBAR (HBM path) and one to NOC (non-HBM path).
-  Both are explicit graph edges; neither is a “bypass” — they are distinct data paths
-  serving different memory domains.
+- All paths must be explicitly represented in the graph and subject to latency accumulation.
+- Example: PE_DMA connects to the NOC router mesh (ADR-0019). All destinations
+  (HBM, shared SRAM, inter-cube UCIe) are reached via explicit mesh hops.
+  Local HBM access has minimal hops (switching overhead only); remote access
+  traverses additional routers.
 - Implicit or “magic” bypass paths are disallowed.
 
 ### D4. No zero-latency end-to-end paths