提交图

5 提交

作者 SHA1 备注 提交日期
d8a5c181cd feat: enable detail enhancement by default 2026-07-27 13:03:21 +08:00
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
fa0241ff99 fix: decouple MemoryCompanion bridge from LivingMemory switch; drop LivingMemory
关键修复:_memory_companion_bridge() 此前以 enable_livingmemory_integration
为总闸,而运维版把该开关硬编码成 False(原意只是「VM 不用 LivingMemory」),
把唯一长期记忆源一起关掉——Bot 个人归档链路在 VM 上整条静默停摆,
记忆库零条记录,页面显示「记忆插件 暂不可用」。改用独立的
enable_memory_companion_bridge(默认开启)。

同时删除全部 LivingMemory 代码:integration_status 的 7 个函数、
page_api 的 9 个函数与路由、main 的提示词槽位/关系网触发/状态命令/
WAL 候选路径/命令别名、group_observation 的群聊指引。

测试 178 项通过(新增 4 项钉住开关拆分与代码零残留)。

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-07-27 02:11:18 +08:00
f4d160ce86 feat: remove ops entertainment integrations 2026-07-26 01:32:07 +08:00
6eaf1b7634 chore: import companion baseline 2026-07-24 00:25:43 +08:00