journeys(fuzz): red journey for the desync findings G1, W1, W4 after Cmd-N
Summary
The red journey for the desync findings after Cmd-N (STATUS 1002, 1022): found-desync-cmd-n-page. In a fresh launch (first_in_app, fresh_app), one Cmd-N, a 3 s settle, then debug.desync check must check every window (unsettled empty) and list no G1, W1 or W4. W1/W4 need the app inactive while the cold New Tab page's Chromium page attaches; on feat builds the window becomes key in the capture slot, so only G1 makes it red on the feat base.
The fix is #29272 (into feat-cmux-next): W1/W4 are a real desync; G1 is a false finding of the app's check (ChildPageGeometry counted only browser tabs). No fuzzer code changes.
The Channels journey that was here (found-desync-channels-type) moved to the fix PR of the bug it found (STATUS 1582), per the coordinator.
Stacked on #29071 (base cp/journeys-action-fuzz).
Testing
python3 scripts/journeys/run.py --check: 62 journey files valid.
Observed / Not run
Observed (the first version of found-desync-cmd-n-page, before the review fixes; cmux19, exclusive slot, diagnostic):
- v2.2.11-opt (78ca62c225bb0943594e3cd2), app inactive: RED, W1 + W4 + G1.
- feat-tip-fixes-v2 (f2f3083bac80ab71101d03ac), app active: RED, G1 only.
- #29272 at 976b215 (build 568ad9fbd033e4ba0ac995fb): PASS.
Reviewed versions, whole host, app active, through the mini scheduler (spec desync-g1w1w4-journeys), 12:09-12:20Z:
- found-desync-cmd-n-page: feat base f2f3083b (cmux20) RED, G1 only; #29272 head ad21c67 (build ed24b7b111a5fe9b44eaf569, cmux20) PASS.
- found-desync-channels-type: moved out (see Summary).
Changelog
none
Proof
No capture: test-only change.