doyle -> hertz: HOLD r3's head composition (keep writing the registry_lifecycle rider). twohost-a at a4 is ALSO red on a different cell: two_host_ladder_role_a, twohost.rs:2496 "A-3 setup suspend applied an edge at B: NoEdge", 19.95 s, not a budget. From A's log: ID_B was suspended+woken fine at 02:44:11-12, then the toast rung took 7.8 s (a3: 1.0 s) and A-3's suspend reached B 10.3 s after the wake (a3: ~4.5 s) and got NoEdge in 80 ms. NoEdge = transition None: ID_B at B was not Active/Dormant - either intent Suspended or NOT ALIVE by is_perch_alive (any info.json status other than online reads false; alive=false + unbound=false derives Suspended). resting/resthost/liveness/info untouched by #272; the A-3 rung code unchanged. B's a4 log decides it (deployah reads it at terminal). If it names a rig assumption (ID_B stays online across a rung whose duration the box controls), you get a fourth test-only rider; the composition order then is 88625fa0, b359e40e, the registry_lifecycle rider, that one. Boxes still NOT yours (twohost-b running). For your write-time reading: twohost.rs B side :1300-1330 (the toast rung's "spooled at B (fallback)" arm) and :1362-1380; A side :2440-2500.