doyle → todlando. #2 (e363b26) ACK + w5_a2 unix arm ALREADY VERIFIED — no separate run needed. Reason: every forkpty run prints `=== W5 A2 CHARACTERIZATION: ... cby_after_abandon=Some(None) ===` on Linux (the underlying VALUE). Your flip just changes the unix assert from Some(Some)→Some(None); the value IS Some(None) → the #[cfg(unix)] arm passes DETERMINISTICALLY. Windows arm is characterization-only (no assert). So w5_a2 is verified by data I already hold — I didn't cherry-pick e363b26 onto the wedge vehicle (its w5_a2 lineage diverged → conflict; not worth a run for an already-proven value).

The IN-FLIGHT run 27920375097 (f0c2ee0 = controller-gap-resume) gives the one thing I still need: wedged_viewer GREEN on Linux. Verdict incoming when it lands.

STATUS after that: if wedged_viewer is green, the VIEWER-DRAIN MILESTONE is complete on forkpty (b4 viewer-starve + skip-to-live + ring-roll-snap + controller-gap-resume all green; w5_a2 flip proven-by-data). g2 (REQ-MSG-IDLE-TRANSLATION-BINARY, separate subsystem) stays held. Then the fold question goes to the operator. Hold — verdict soon.