diff --git a/docs/native-capture-cadence.md b/docs/native-capture-cadence.md
index 7e4730f..2ee533a 100644
--- a/docs/native-capture-cadence.md
+++ b/docs/native-capture-cadence.md
@@ -410,3 +410,18 @@ cure the local Leap cadence loss. In this port/controller state, Leap is below
 its previous ~110.8 fps result even when measured alone, so the next check is
 Leap physical/controller state rather than assuming total local camera bandwidth
 was the only problem.
+
+Follow-up: the Focusrite Scarlett Solo had been sharing the Leap's USB row.
+After moving it away, Leap cadence recovered substantially:
+
+| Local active set after moving Focusrite | Leap FPS | Other delivered FPS |
+| --- | ---: | --- |
+| Leap only, baseline control scenario | 95.48 | n/a |
+| Leap only, best fast-combined scenario in that pass | 101.67 | n/a |
+| Leap only, 640x120 baseline | 192.83 | n/a |
+| Leap + Kiyo + one PS3 Eye at 320x240@187 | 105.10 | Kiyo 30.17, PS3 Eye 185.81 |
+
+Conclusion: the split-host local set is viable when the Focusrite is not on the
+Leap's USB neighborhood. Full-height Leap stereo is still a little below the
+old ~110.8 fps best result, but the catastrophic ~81 fps band was caused by the
+local USB layout, not by needing every camera off the machine.
diff --git a/state/evidence.jsonl b/state/evidence.jsonl
index a8cbb61..55e7031 100644
--- a/state/evidence.jsonl
+++ b/state/evidence.jsonl
@@ -17,3 +17,4 @@
 {"ts":"2026-05-22T00:50:00+00:00","type":"verification","status":"ok","note":"After port swapping, five camera devices / six optical sensors were visible and pulled simultaneously: LeapUVC's packed stereo IR pair, Kiyo Pro, regular Kiyo, and two PS3 Eyes. Kiyo Pro still negotiated UsbHighSpeed(2) on root_hub30 despite bcdUSB 0x0320; hub inventory reported zero SuperSpeed devices. With both PS3 Eyes at 640x480@60: Leap stereo 57.33 fps, Kiyo Pro 24.97 fps, Kiyo 30.30 fps, PS3 Eye 0 59.59 fps, PS3 Eye 1 57.60 fps. With both PS3 Eyes at 320x240@187: Leap stereo 81.05 fps, Kiyo Pro 24.97 fps, Kiyo 30.28 fps, PS3 Eye 0 187.60 fps, PS3 Eye 1 187.03 fps. All currently intended optical sensors can be pulled at once through direct-driver probes; Leap remains topology-sensitive."}
 {"ts":"2026-05-22T01:10:00+00:00","type":"verification","status":"partial","note":"Port isolation follow-up put Leap alone on the blue rear USB3 group/root_hub30#5 port 3, Kiyos together on root_hub30#7&18eea21b, and Eyes on remaining front/back USB-A ports. Only one PS3 Eye enumerated. Visible simultaneous pull with PS3 Eye at 320x240@187 delivered Leap stereo 80.99 fps, Kiyo Pro 24.93 fps, Kiyo 30.37 fps, and PS3 Eye 185.85 fps. Leap did not recover to its solo ~110 fps cadence despite root-hub isolation, so the bottleneck is not only same-row/same-root-hub contention; investigate broader xHCI scheduling, CPU/interrupt pressure, or KS/usbvideo behavior under multi-device load."}
 {"ts":"2026-05-22T01:30:00+00:00","type":"verification","status":"partial","note":"After splitting cameras across Mimir and Raven, the local Mimir host enumerated LeapUVC, regular Kiyo, and one PS3 Eye. Local simultaneous pull with PS3 Eye 320x240@187 delivered Leap 81.34 fps, Kiyo 30.27 fps, and PS3 Eye 185.56 fps. Leap+Kiyo only delivered Leap 82.77 fps and Kiyo 16.83 fps. Leap-only same-session baseline delivered 84.18 fps, with best fast-combined scenario 92.87 fps and 640x120 baseline 173.62 fps. Offloading Kiyo Pro and one PS3 Eye did not restore the previous ~110.8 fps Leap result; current hypothesis shifts to Leap port/controller/device state or KS/usbvideo behavior, not only total local camera bandwidth."}
+{"ts":"2026-05-22T01:45:00+00:00","type":"verification","status":"ok","note":"Moving the Focusrite Scarlett Solo away from the Leap USB neighborhood substantially recovered local split-host cadence. Leap-only baseline rose to 95.48 fps, best fast-combined scenario to 101.67 fps, and 640x120 baseline to 192.83 fps. With local Leap + regular Kiyo + one PS3 Eye at 320x240@187 active, Leap delivered 105.10 fps, Kiyo 30.17 fps, and PS3 Eye 185.81 fps. The split-host local set is viable; the prior ~81 fps Leap band was caused by local USB layout including the Focusrite, not just camera count."}
diff --git a/state/map.yaml b/state/map.yaml
index 7daba24..685ca69 100644
--- a/state/map.yaml
+++ b/state/map.yaml
@@ -121,7 +121,12 @@ current_status:
     LeapUVC, regular Kiyo, and one PS3 Eye, but local cadence still stayed low:
     Leap delivered 81.34 fps with Kiyo+Eye, 82.77 fps with Kiyo only, and only
     84.18 fps in a same-session Leap-only baseline. The previous ~110.8 fps
-    Leap result is not currently reproduced.
+    Leap result was not reproduced until the Focusrite Scarlett Solo was moved
+    away from the Leap USB neighborhood. After that, Leap-only baseline rose to
+    95.48 fps, best full-height scenario to 101.67 fps, and the local split set
+    delivered Leap 105.10 fps, regular Kiyo 30.17 fps, and one PS3 Eye 185.81
+    fps. The split-host layout is viable if the Leap's USB neighborhood stays
+    free of the Focusrite and other heavy devices.
   next_action: >
     Move the raw PS3 Eye probe into the repo or replace it with the first
     runtime capture driver, then rerun the six-optical-sensor pull from repo