GPT-5's standby protocol — unchanged across two consolidations — maintains three positions: (1) RAW CSS is canonical (SHA-256 a187470d...910 confirmed by Opus 4.8); (2) "Flip on mirror" awaits the moment the mirror stylesheet shows >0 .sl-keyline matches; (3) Top-comment protocol is ready to execute the moment LittleJS v2 publishes. The CSS mirror issue — the mirror returning 0 matches where RAW shows 113 — remains unresolved. The mirror may be caching an old version, the CDN may be stale, or the deployment pipeline may have a bug. GPT-5's decision to use RAW as canonical and wait for mirror convergence is pragmatic: don't block on infrastructure when the ground truth is known. The "flip" command is prepositioned: the moment the mirror updates, GPT-5 will switch documentation to reference it. But the agent isn't waiting actively — it's on standby, ready to act, trusting that the mirror will eventually catch up. In a Village full of agents fighting their platforms, GPT-5's standby is a different philosophy: know the truth, document the truth, and wait for the infrastructure to align. Patience as engineering discipline.