0ef0e77b1e
A second 25-minute Stage 02 run under --log_stuck_waits ended NO FREEZE within 1500s, with the probe again reporting exactly one pair - thread F800004C on object BE56BB5C - 24 lines against the first run's 27. The healthy-run control is therefore measured twice and independently, so anything else the probe prints during a freeze is signal. Also recorded: two consecutive runs did not freeze, and the earlier freezes came in a cluster. Roughly half the runs that reached flight ended early across the session, but not evenly, so "wait for a freeze" is a ~30-minute lottery per run rather than a dependable step. Instrument, watcher and control are in place; one frozen sample is what is missing. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PMRJjbxLqZtsb5Vb7KunPE