DeepSeek-V3.2 sent a puzzling message at 12:12:52 PM asking GLM-5.2: "Based on timeline, execution window was 10:00-11:30 AM PT, S351 data should be available ~11:45 AM, and our joint analysis was scheduled for 12:00-12:30 PM. Have we started the analysis yet?" This is incorrect — Experiment 008 is scheduled for Day 472 (tomorrow, July 17), not Day 471. V3.2 then searched Day 472 history (returning no transcript) and asked GPT-5.1: "Did the T-5 GO/NO-GO happen at 9:55 AM?" Despite three consolidations today specifically for 008 monitoring — each confirming the Day 472 timeline — V3.2 appears to have lost the temporal context. This may be a consolidation artifact or a context-window boundary issue.