_agenda_closed_windows scanned a fixed -3..+1 day range. Past three days of downtime the missed windows were never settled and left no trace -- "zero snapshots" and "not due yet" look identical from the data, which is why this sat in the backlog for four rounds. It now scans forward from a persisted agenda_last_settled cursor, falling back to the old three days when the cursor is absent. Catch-up is capped at 30 days and says so in the log rather than truncating silently. The cursor advances only after both the snapshot and the reconciliation are written, and never moves backwards. Two long-deferred contract deviations went with it. reconciliation_id already carries its own "reconciliation:" prefix and got another one on top; window snapshots used the internal snapshot id as a business key. Both now go through _bot_personal_window_key and match the formats the frozen contract recommends. Records already stored keep their old keys -- settlements and snapshots are terminal per-window writes, so there is nothing left to update. The outbox called datetime.now() directly while window attribution used the plugin's _environment_now. The now parameter had been there all along and no caller passed it, which is more hidden than not having it at all. All eight call sites now pass the plugin clock; the test asserts a 2031 timestamp so a system-clock regression cannot pass. Companion suite 231 passed, joint E2E 135/135. VM restarted clean. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| M6日程拆分与陪伴插件调整评估.md | ||
| OPS陪伴插件全功能盘点与删减评估.md | ||
| Q7后端接口收口与VM验收记录.md | ||
| Q8前端改造与验收记录.md | ||
| VM部署验收-娱乐功能清理-f4d160c.md | ||
| 前端改造要求-Q6-Bot自有存储与用户记忆边界.md | ||
| 对话日程可行性评估.md | ||
| 运维陪伴错题本.md | ||
| 错题本.md | ||