mesalogo
d80d42b032
Main no longer opens desktop business SQLite. A single utility-process
storage owner holds the Assistant, Knowledge, attachment, document-result,
remote-binding and native model-ledger databases and runs whole domain
transactions; Main and Runtime callers use explicit async domain operations.
- Remove the Main readWithFallback path and the supervision worker's
separate business write connection; manifests are scanned read-only and
committed by the sole writer.
- Remote events are ACKed only after commit; process loss reports
unconfirmed writes instead of replaying them.
- Use native utilityProcess messaging with one in-flight bound (32) and
ordered waiting instead of capacity rejection and retries.
- Start the storage process before the window so startup overlaps.
- Keep short tool output in memory and store full output once in owned
storage; paging, branching, restart and deletion reuse that copy.
- Put required runtime launch files under goodbuddy-prefixed owned temp
directories and reclaim confirmed stale ones; stop writing duplicate
parsed.md.
- Add lint guards for SQLite ownership and architecture, concurrency
acceptance fixtures, and maintenance/architecture documentation.
Validation: typecheck and lint pass. Alternating baseline (edf019aa) vs
candidate runs show no regression on single-session, C01, C02, C04 and a
5-minute C06; Main p99 drops from ~21 ms to ~16.7 ms under concurrency.
Fresh portable copy (1.75M events) upgrade content unchanged; real-model
output paging passes with 4 external requests. Full npm test runs had
1-9 different timing-sensitive failures per run that pass when rerun.
Not covered: C03 review publication, C07 source body, app-level C05.
Smart Heartbeat
Smart Heartbeat 已提供按计划或手动执行的有界回顾，生成报告及后续建议。应用默认关闭；启用及计划条件见应用启停与执行。条件或事件唤醒仍需后续设计。
现有入口已升级为“监督者”，智能心跳作为其定期唤醒机制，驱动检查与整理；应用提供工作回顾、故事线图谱、自动监督、活动记录和设置五个页签。计划在自动监督管理，创建与编辑使用 Modal；设置只保留算法参数。定义见监督者应用产品设计，实施方案见监督者技术设计。现有计划和范围保留，监督调用继续禁止工具执行。
职责（2026-09-30 已实现）：心跳只负责定时触发增量回顾，并按计划配置的介入方式（生成建议／仅更新记忆）处理本次图谱变化；不再单独读取原文或生成报告。见心跳职责与介入。下文关于心跳报告、报告超时和报告增量的描述为历史行为，仅旧报告保持只读。
自动报告及监督回顾分别按来源版本和已读位置处理增量；没有待处理输入时记录无变化，跳过模型及新报告。手动历史重看和删除报告的边界见自动增量规则。
文档导航
当前心跳将到期计划交给监督回顾，不再额外生成独立报告。监督整理使用模型阶段超时和共享监督并发池，普通聊天不入池；模型超时不包含排队、采集和保存，也不是整次回顾期限。分页、批次持久化和暂停／继续已接入生产路径，范围及剩余限制见生产接线。超时、并发、重试及保留的历史报告设置由模型阶段调度定义，不据初稿控制表另建调度器。
监督者“活动记录”页签同时显示手动回顾和心跳执行，将新心跳报告与下游监督按运行 ID 合并，保留各阶段真实状态。心跳审计、运行概览、指标、趋势、自动监督报告阅读和建议处理与计划列表同在自动监督页；工作回顾只读取统一监督结果，设置只保留配置。当前布局见监督者 UI 设计。心跳审计继续读取报告自身状态，完整执行状态以活动规则为准。
| 文档 | 权威职责 |
|---|---|
| 智能心跳 PRD | 用户目标、范围、计划、运行和产品验收 |
当前尚无独立 User Stories、功能逻辑、UI、技术设计和进度文档。