Aska
9c2a37c4ac
agent-98 面板批次:
- 会话管理面板改接 history.ListSessions(主web+次级) + 新建次级会话按钮
- 记忆面板手动添加入口 POST /admin/memories(owner)
- 知识库真正实现 IndexDocument(分块+落projectindex) + POST /admin/rag 导入端点
- 三面板空态诚实表述(去除'后端M10+提供')
- RAG嵌入降级到keyword/line(无直属embedder,不伪造语义,符合红线)
agent-99 design/16 §4.6:
- model.Message.SenderName + 迁移0006 sender_name 列
- 第三方身份边界: session.ResolveActor判定(非LLM猜) + [第三方·昵称]前缀(不改源content)
- 群聊/陌生人落独立sess-xxx(persistIsolated),不写主会话,不广播
- 黑/白名单(allowGroups/denyGroups/allowUsers/denyUsers)最前拦截,不进LLM
- 多账号 CHANNELS_JSON 配置 + 每平台多实例
- 管理只读 GET /admin/channels/{platform}/messages(该平台非主人消息流)
实机验证(JWT): 会话管理返回主会话web / 记忆添加成功 / RAG导入documents非空+Cyrene命中; 后端build/vet/test全绿 + 前端build绿
14 lines
850 B
SQL
14 lines
850 B
SQL
-- 0006_chat_sender_name: tag every chat message with the human-readable sender
|
|
-- display name (DevDocs/design/16 §4.6). Group chats and stranger private chats
|
|
-- carry the sender's nickname so the agent can see who is speaking and the IM
|
|
-- adapter log page can label the message stream; the owner's private chat on the
|
|
-- main session is intentionally left blank (the owner is never labeled).
|
|
--
|
|
-- The 0005 chat_messages table already exists at this point, so ALTER ADD COLUMN is
|
|
-- the correct, non-destructive step. The canonical schema (including this column) is
|
|
-- also re-issued idempotently by internal/runtime/history.NewStore so a fresh
|
|
-- in-memory store used by tests stays self-contained; the migration is the
|
|
-- authoritative path for an existing database.
|
|
|
|
ALTER TABLE chat_messages ADD COLUMN sender_name TEXT NOT NULL DEFAULT '';
|