feat(ai): 新增聊天助手、智能检索与关注提醒,修复联系人加载及导出失败 - #142
Merged
Merged
Conversation
接入 models.dev 和上游模型元数据,移除 Agent 固定调用额度,集成可搜索模型选择。使用固定的 assistant-ui Vue 官方源码,增加会话导航与侧栏宽度调整,修复流式来源解析和弹窗拖选误关闭,统一工具流缩进与详情层级。 验证:前端 217 项、AI 后端及模型目录 156 项通过;生产构建及浏览器交互验收通过。
按 BLOB 读取收藏文本字段,交给业务层容错解码,避免单条异常数据中断列表或导致标签丢失;查询失败不再误报表结构不支持。 验证:61 项测试、20 个子测试通过,覆盖真实协议解析、异常字段、标签筛选及实时与本地读取一致性。Refs LifeArchiveProject#143
保留 AI 助手当前步骤的运行提示及终态图标。验证:Vitest 233 项、Node 62 项通过;Nuxt generate 完成 34 个路由;浏览器检查运行、折叠和完成状态通过。
执行过程入口仅保留文字与展开箭头,清理前置图标样式。验证:Vitest 233 项、Node 62 项通过;独立目录生产构建生成 34 个路由;浏览器验证完成态左对齐和展开收起。
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
为聊天记录增加 AI 问答、总结、关注提醒和本地智能检索,并修复联系人加载失败及并发导出完成后报 BUSY 的问题。
AI 聊天助手与自动任务
本地智能检索
联系人加载修复
关联 #135。
实时 contact 全表查询和备用接口原先会吞掉异常,上层将空列表判定为成功,仅从会话补出群聊,导致有好友数据的账号显示“好友 0”,也无法触发本地数据库回退。
本次调整:
已用合成数据库复现修复前“好友 0、群聊 28、接口仍成功”的情况;修复后可回退读取 306 个好友。尚未在 issue 提交者的机器上验证最初触发查询失败的底层原因。
导出完成后 BUSY 修复
实时数据库查询与 ZIP 完整性签名并发时,原实现会强制将同一个 native broker 切换成仅导出模式。已有操作持有租约时直接报 BUSY,导致消息已写完、界面显示 100% 后导出失败。
详细证据与验证边界见
docs/export-broker-busy-investigation-20260909.md。运行与兼容
验证结果
各功能本地验证(分批执行):
数据与密钥