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_pe_components.py

@@ -861,7 +861,6 @@ def test_mcpu_kernel_launch_composite():
 # ── 19. Stage 5: QKV GEMM benchmark completion ────────────────────
 
 
-@pytest.mark.skip(reason="Cross-SIP PE_TCM access not supported with router mesh topology")
 def test_qkv_gemm_bench_completes():
     """The qkv_gemm benchmark runs to completion without error."""
     clear_registry()
@@ -956,7 +955,6 @@ def test_mcpu_multi_pe_kernel_launch():
 # ── 21. Stage 5: QKV GEMM multi-PE benchmark completion ──────────
 
 
-@pytest.mark.skip(reason="Cross-SIP PE_TCM access not supported with router mesh topology")
 def test_qkv_gemm_bench_multi_pe_completes():
     """The qkv_gemm_multi_pe benchmark runs to completion without error."""
     clear_registry()