Fix cross-SIP PE_TCM access by scoping deploy to target_device SIP

RuntimeContext._ensure_allocators() now limits SIP range to
target_device (single SIP or all). Prevents cross-SIP tensor
deployment that caused PE_TCM routing errors.
Also accept 'sip0' format (without colon) in DeviceSelector.

331 passed, 8 skipped

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

tests/test_va_offset.py

@@ -131,7 +131,6 @@ def test_2d_va_translates_to_local_hbm():
 # ── VO3. 2D: End-to-end bench completes ──────────────────────────────
 
 
-@pytest.mark.skip(reason="Cross-SIP PE_TCM access not supported with router mesh topology")
 def test_2d_bench_completes():
     """2D: full TP bench with standard Triton kernel pattern."""
     graph = load_topology(TOPOLOGY_PATH)
@@ -199,7 +198,6 @@ def test_1d_va_translates_to_local_hbm():
 # ── VO6. 1D: End-to-end ──────────────────────────────────────────────
 
 
-@pytest.mark.skip(reason="Cross-SIP PE_TCM access not supported with router mesh topology")
 def test_1d_e2e_completes():
     """1D: full engine run with column_wise TP sharding."""
     graph = load_topology(TOPOLOGY_PATH)