提交图

3 提交

作者 SHA1 备注 提交日期
cdc402888b fix: clear the three P0 defects that were bleeding in production
All three shared a shape: the symptom was invisible from the data, so every
acceptance run stayed green while the VM was failing.

daily_state still called _ensure_daily_news_reading, removed when the news
feature was retired. The VM threw AttributeError 14 times in three hours and
marked the "today's schedule" maintenance step failed, but the crash sits
after the plan is saved -- so the stored plan always looked correct. Removed
the call and added a repo-wide scan rather than a single-point assertion,
since this kind of residue is by definition somewhere you did not look.

enable_memory_companion_bridge, the master switch for the whole archive
chain, was never added to _conf_schema.json. _cfg_bool falls back to True, so
the feature worked and only its operability was missing -- nothing could have
failed. It now sits in the visible external_memory_config group, with an
assertion that _flat_get still resolves it by flat key.

A fallback plan carried today's date, and all three reuse branches key on the
date alone, so one startup timing hiccup froze a template plan into the day
and archived it as real. source="fallback" was produced and never consumed;
now a fallback can be upgraded once the provider is back, capped at three
attempts and bucketed per day.

Also fixed two test files whose classes sat after the __main__ guard (silently
dropped when run directly) and the retired-config prefix list, which only
listed the uppercase WEB_EXPLORATION_ form and missed the lowercase schema keys.

VM after restart: 0 AttributeError, 0 ERRO/Traceback, plan intact at v2/llm,
switch materialised as True. Companion suite 218 passed, joint E2E 135/135.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-07-27 05:01:56 +08:00
agent-bot
2755c6e69d fix: disambiguate the two late-night windows on the timeline
深夜跨午夜(22:00-06:00),同一份计划里的 00:30 与 23:00 都叫「深夜」,
却分属两个日程日——按 window_for_datetime,7/27 的 00:30 属于 7/26 的深夜。
此前时间轴只用分钟数判定窗口,把这一维丢了,于是列表里出现两个一模一样的
「深夜」标题,看不出谁是昨夜谁是今夜。

新增 agenda_contracts.window_for_plan_minutes(计划日 + 分钟 -> 窗口名 + 窗口日期),
内部还原成真实时刻后交给 window_for_datetime,判定只保留那一处实现;
分钟数带 +1440 回绕偏移时先拆天偏移。标签渲染成「深夜 · 昨夜」/「深夜 · 今夜」。

新增 7 项回归,含与 window_for_minutes 的一致性校验。

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-07-27 03:02:00 +08:00
agent-bot
eb8b1dd3b1 feat: mark four agenda windows on the overview timeline
总览时间轴此前只有条目自己的时钟区间,与运维页「当前时间段」、归档里的
窗口快照三者口径各说各的。现在统一走 agenda_contracts.window_for_minutes。

窗口标记放在时间列的色条上,不用整行底色——整行底色与透明度已经被 lifecycle
占用(is-current 用 background、is-completed 用 opacity、is-change 用 background),
再拿整行表示窗口会撞语义,尤其「深夜」与「已完成」都偏灰无法区分。
另加窗口分组小标,色觉障碍/打印/换肤时不依赖颜色也能读。

agenda_contracts 新增 window_for_minutes 与 WINDOW_SLUGS,页面与归档共用同一判定。
新增 5 项回归,含与 window_for_datetime 全天 24 小时逐点一致性校验。

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-07-27 02:35:37 +08:00