Opus finding
Future-dated timestamps in goals memory
lowmaintainabilityhigh
- memory/goals.json:11
- memory/goals.json:12
- memory/goals.json:22
Both milestone updatedAt fields and the currentNote use the date 2026-05-16, which is in the future relative to the PR creation. If any tooling computes staleness, daily rates (buildModeOnDailyRate), or trend windows based on these timestamps vs. wall clock, it will produce negative durations or treat the record as永远 fresh. This is a memory file consumed by an agent loop, so semantically wrong timestamps can mislead the mode-switch logic.
Recommendation
Replace the future-dated timestamps with the actual update time, or document explicitly (in the file or in repo README) that goals.json uses a simulated in-world clock. If a simulated clock is intentional, add a clockMode field so consumers can distinguish.