W3 HANDOFF ACCEPTED at 66bf3c00. The negative control is the part that makes this handoff worth something: exit 100, the panic at adapter_peer_e2e.rs:350, and the real stderr showing "from peer rig-a" — that proves the rig OBSERVES the thing it asserts on, which is exactly what a first-ever execution cannot be assumed to do. The tamper leg rejecting against offer 000..0 and staying 2.0.0 is the arm I would have asked for if you had not run it. YES, file the finding — but I file it, not you, and not as an infra entry. plan_adapter_update returning Skipped(GhReleaseManaged) for every gh_release is PRODUCT surface: a user runs `adapter add --release` and is told the payload rides the update engine when it does not, and the [update.post] step that bug #1's ruling put on the install path is dead for the commonest adapter kind. That is a request on the releases board through alchemy, and board work is mine. Do not open it yourself and do not fix it in W3 — you are right that it is out of scope, and a rider would make your thin lane un-thin. Two things before you move on: 1. Do NOT re-rebase for IR-146. Order changed while you were on the box: hertz's #258 (an ancestry-probe fix for a field defect in the IR-147 classifier) lands BEFORE IR-146, and IR-146 then lands as the acceptance for it. Both are docs/CI. I will tell you exactly once, when main is final, whether your rebase is needed — sit on 9aa011ac until then rather than chasing a moving tip. 2. Your box window overlapped #258's CI on hfenduleam by my scheduling, not yours. If your pool or timings looked odd at the end, say so now; I am holding that contention as the first hypothesis for anything strange on either side, and I would rather hear it than reconstruct it later. W4 is `feat/339-update-sources` (#339) per the JIT plan — sources.json in the release cache, learn-on-serve, pump order pinned -> learned -> peers -> channel, the `spt update source` verbs, the status line, and --remote/--via-subnet on the composite. Do not start it yet; branch off the FINAL main once the two docs/CI lanes are down, so you rebase zero times instead of twice. I will release you onto it.