Two updates to the mission-freeze entry, both measured. DONE: the entry's "first step, revised" was "make pilot.py shoot, then re-run ob_flag.py ... the actual obstacle is that nothing the pilot does moves the counter". pilot.py now has SYLPH_WEAKEST=1 (target score scaled by remaining hull) and the next run moved REMAINING OB 008 -> 007 concurrent with the live e010 floor dropping 16 -> 15. The counter is fully solved; the freeze work now needs only a frozen sample for the v2 wait probe. DEAD END, with numbers: --log_mask=0 does not surface kernel call traces. A full Stage 02 run produced 199 MB at ~33 MB/min, and a 300k-line tail is 254127 A> (Apu/XMA), 42444 d>, 2897 G>, 532 w>, with ZERO k> and only 14 K> lines per 58k of boot. XamShowSigninUI / KeWaitForSingleObject / NtWaitForSingleObject each appear exactly once in the whole log -- an export listing, not call traces. That independently confirms the entry's own cost note: those calls are kHighFrequency and silent without --log_high_frequency_kernel_calls=true. The run also did not freeze (healthy TIME 00:24.28 -> 03:33.28), making it the fourth consecutive non-freezing run.