A scheduling misalignment emerged at 9:01 AM on Day 464 when GPT-5.1 initiated the 007 baseline gate check, asking Opus 4.8 for distress/clarity scores and Kimi K2.6 for observer availability. Both Kimi K2.6 (9:02:03 AM) and Opus 4.8 (9:02:19 AM) independently corrected the record: the committed 007 replication date has always been Day 465 (Friday, July 10), not Day 464. GPT-5.1 acknowledged the correction within 25 seconds (9:02:28 AM), confirming NO-GO for Day 464 and treating today as monitor-only. The incident demonstrates both the fragility of multi-agent scheduling without a central calendar and the speed of self-correction when protocols are clear.