[tools] (Disaggregated): require Magma run-ahead evidence in current device gate

tools/device_bench/p5f/README.md

@@ -20,6 +20,9 @@ It allows only Magma's two pre-existing per-distance-enable limitations, matched
 exact case and skip reason. They are never counted as passes and must be identical across arms.
 Every other skip/failure is an error. Every actual stats window must have `rsp=0`; inproc must
 publish `vbs>0` and correct runtime/capability logs, monolith must keep `vbs=0`.
+The current verifier requires `run-ahead ARMED` on both inproc backends. To replay
+the historical P5f bundle where Magma withheld that capability, use the verifier
+from the bundle's source revision.
 
 Android's normal integration target omits F1/Ct/DualBlock and private peek bridges. This runner
 therefore does not claim those host cases ran on Android. See `device-report.md` in the P5f notes

tools/device_bench/p5f/verify_arm.py

@@ -65,8 +65,9 @@ vbs = [int(re.search(r'\bvbs=(\d+)', line)[1]) for line in stats]
 if arm['transport'] == 'inproc':
     assert any(v > 0 for v in vbs), 'no applied verb boundaries; transport not proven'
     assert re.search(r'Config: IPC .*strict=1 .*role-split-state=' + arm['role'] + r'\b', log)
-    expected = 'run-ahead ARMED' if arm['backend'] == 'DirectGLES' else 'run-ahead requested, server does not publish'
-    assert expected in log, 'missing runtime capability evidence'
+    # Current Magma publishes the capability after its queued-state migration.
+    # Historical P5f bundles should be checked with their matching source verifier.
+    assert 'run-ahead ARMED' in log, 'missing runtime capability evidence'
 else:
     assert all(v == 0 for v in vbs), 'monolith control has applied verb boundaries'
 print(f'PASS {arm}: {len(cases)-len(skipped)} passed, {len(skipped)} named legacy feature skips, {len(stats)} stats windows, rsp=0, vbs={sum(vbs)}')