luckytri 1.0.7 → 1.0.9

package/README.en.md

@@ -7,7 +7,7 @@
 <p align="center"><strong>Let the days she lives count.</strong></p>
 
 <p align="center">
-  <img alt="version" src="https://img.shields.io/badge/version-1.0.1-ff8fb1">
+  <a href="https://www.npmjs.com/package/luckytri"><img alt="npm version" src="https://img.shields.io/npm/v/luckytri?color=ff8fb1"></a>
   <img alt="license" src="https://img.shields.io/badge/license-MIT-7fd6c2">
   <img alt="node" src="https://img.shields.io/badge/node-%E2%89%A5%2024.5-8fb8ff">
   <img alt="channels" src="https://img.shields.io/badge/QQ-OneBot%2011%20%7C%20official%20bot-ffd37f">
@@ -92,10 +92,14 @@ The full design is in [Her life](docs/en/her-life.md) and [Architecture and exte
 
 ## What she can do
 
+Recent work focuses on continuity and clearer conversation. Account-based recognition links public encounters across groups and private chats. Relationships, forms of address, her own views and private promises retain their sources and visibility boundaries. An ordinary greeting need not bring back unfinished tasks or demonstrate how much she remembers.
+
+**1.0.9 update:** Add a separate Volcengine Ark Agent Plan category with its auto-router and all current text-model presets, using the dedicated endpoint and Responses API. Remove the unavailable OpenCode Zen Space Bunny Free and Step 5 Free presets, and clear their saved profiles on upgrade. Conversation fixes continue to prioritize the current speaker's question, follow-ups and quotations, with plain explanations when someone cannot follow. See the [changelog](docs/en/CHANGELOG.md). These changes still need testing in everyday interaction; automated scores are not a guarantee of conversation quality.
+
 | Area                     | What it does today                                                                                                                                                                    |
 | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | Time and solitude        | Lives a day on her own rhythm; in quiet hours sorts her thoughts, reads, writes a diary; reviews every so often, rewrites her story and turns to a new chapter                        |
-| Doing her own things     | Carries out the reading, writing, thinking and play plans she left herself; works are saved even offline and can be viewed under Lifetime and Time                                    |
+| Doing her own things     | Carries out her reading, writing and thinking plans; game activities primarily read and record reference material; works are saved under Lifetime and Time                            |
 | Self and mood            | Forms opinions, tastes, concerns and wishes from sourced experiences; changes can be looked back on and undone                                                                        |
 | Relationships and memory | One memory across groups and private chats; tells "public / private / confidential" apart; private things never surface in another room                                               |
 | Attention and choice     | Understands multi-person talk, @-mentions and quotes, and decides to read closely, to speak or to stay silent; can also reach out from her own thoughts                               |
@@ -202,7 +206,7 @@ To continue an existing source instance, stop it first, then use `luckytri --hom
 | `EMBEDDING_API_KEY` | Optional; a separate key for the knowledge embedding service |
 | `BACKUP_INTERVAL_HOURS` / `BACKUP_KEEP` | Automatic backup interval (24 hours by default, `0` turns it off) and how many to keep (7 by default) |
 
-Everything about her stays on your machine: the database, chat records, model keys and backups live in the ignored `data/` directory and are never uploaded. While running, the server makes one integrity-checked backup a day; backups share a disk with the database, so copy important ones elsewhere. Never commit `.env`, the database or logs. See [Security](.github/SECURITY.md) and [Backup and recovery](docs/en/recovery.md).
+The database, chat records, model keys and backups live locally in the ignored `data/` directory and are excluded from the repository and npm package. When you use a remote model, the context needed for a response is sent to your configured provider. While running, the server makes one integrity-checked backup a day; backups share a disk with the database, so copy important ones elsewhere. Never commit `.env`, the database or logs. See [Security](.github/SECURITY.md) and [Backup and recovery](docs/en/recovery.md).
 
 ## Documentation
 

package/README.md

@@ -7,7 +7,7 @@
 <p align="center"><strong>让她走过的日子算数。</strong></p>
 
 <p align="center">
-  <img alt="version" src="https://img.shields.io/badge/version-1.0.1-ff8fb1">
+  <a href="https://www.npmjs.com/package/luckytri"><img alt="npm version" src="https://img.shields.io/npm/v/luckytri?color=ff8fb1"></a>
   <img alt="license" src="https://img.shields.io/badge/license-MIT-7fd6c2">
   <img alt="node" src="https://img.shields.io/badge/node-%E2%89%A5%2024.5-8fb8ff">
   <img alt="channels" src="https://img.shields.io/badge/QQ-OneBot%2011%20%7C%20%E5%AE%98%E6%96%B9%E6%9C%BA%E5%99%A8%E4%BA%BA-ffd37f">
@@ -92,10 +92,14 @@ flowchart LR
 
 ## 能力一览
 
+近期更新集中在让相处更连贯、说话更清楚。她按账号认出同一个人，在不同群与私聊间衔接公开经历；关系、称呼、自己的看法和私人约定分别保留来源与可见范围。普通问候不需要带出旧任务，每次开口也不需要证明自己记住了多少事。
+
+**1.0.9 更新：** 新增独立的火山方舟 Agent Plan 模型分类，提供自动路由及全部当前文本模型预设，使用专属接口和 Responses API；移除已不可用的 OpenCode Zen Space Bunny Free 与 Step 5 Free 预设，并在升级时清理已有档案。对话修复继续优先理解当前说话人的问题、连续补充与引用；对方说没听懂，就换成能直接理解的话。完整变化见 [版本记录](docs/zh/CHANGELOG.md)。这些修复仍需真实相处检验，项目不把自动评分当作回复质量的保证。
+
 | 方面         | 现在能做什么                                                                                              |
 | ------------ | --------------------------------------------------------------------------------------------------------- |
 | 时间与独处   | 按自己的作息过一天；安静时整理想法、阅读资料、写日记；每隔一段时间回顾，改写自传、翻开新的一章            |
-| 做自己的事   | 执行自己留下的阅读、写作、思考与游玩计划；作品离线也能保存，在「一生」「时间」里查看                      |
+| 做自己的事   | 执行自己的阅读、写作与思考计划；游戏内容以参考资料阅读与记录为主；作品保存在「一生」「时间」中          |
 | 自我与心境   | 从有来源的经历里形成看法、喜好、关注和想做的事；变化可以回看和撤销                                        |
 | 关系与记忆   | 一份跨群、跨私聊的记忆；区分「公开 / 私下 / 保密」；私下的事不会出现在别的房间                            |
 | 注意力与选择 | 理解多人对话、@ 与引用关系，决定细看、开口或沉默；也能从自己的念头出发主动联系                            |
@@ -202,7 +206,7 @@ npm start
 | `EMBEDDING_API_KEY` | 可选；独立的知识向量服务密钥 |
 | `BACKUP_INTERVAL_HOURS` / `BACKUP_KEEP` | 自动备份间隔（默认 24 小时，`0` 关闭）与保留份数（默认 7） |
 
-她的一切都在本机：数据库、聊天记录、模型密钥和备份保存在被忽略的 `data/` 目录，不会上传。服务运行时每天自动做一份经过完整性检查的备份；备份和数据库在同一块磁盘上，重要的请自己复制到别处。不要提交 `.env`、数据库或日志。详见 [安全说明](.github/SECURITY.md) 与 [数据备份与恢复](docs/zh/recovery.md)。
+数据库、聊天记录、模型密钥和备份保存在本机被忽略的 `data/` 目录，不随源码或 npm 包发布。使用远程模型时，回复所需的上下文会发送给你配置的模型服务。服务运行时每天自动做一份经过完整性检查的备份；备份和数据库在同一块磁盘上，重要的请自己复制到别处。不要提交 `.env`、数据库或日志。详见 [安全说明](.github/SECURITY.md) 与 [数据备份与恢复](docs/zh/recovery.md)。
 
 ## 文档
 

package/docs/en/CHANGELOG.md

@@ -1,17 +1,39 @@
 <p align="right"><a href="../zh/CHANGELOG.md">中文</a> · <b>English</b></p>
 
-# Changelog
-
+# Changelog
+
+## 1.0.9 — 2026-10-11
+
+- In follow-ups, answer the new detail without repeating limitations already explained; answer a question about source or feelings directly.
+- Discuss project proposals using the details actually given, without inventing the other person's existing game mechanics or assignment. If a first bot reply misses a newly delivered passage or question, retry once for that content; empty confirmations still stop.
+- For a concrete story excerpt, describe the visible events before clarifying that the larger plot is unknown.
+- Reject duplicate JSON fields so a later `bubbles` field cannot silently replace an answer. Queued messages can see replies already delivered before their turn starts, reducing repeated acknowledgments and corrections.
+- Distinguish questions, proposals, feelings and corrections. Reviews retain the necessary original words and participants to check mistaken adaptations and unsupported apologies. When a follow-up omits a work's title, use the immediately delivered reply to that same person in the same conversation to find reading records, returning only the reading fact, not the reply's text. Select old summaries by the current topic while preserving address agreements separately.
+- Check repeated bot confirmations before they produce emotional changes. Verify new actions claimed in proactive drafts against activity records; old wishes cannot prove execution. Preserve history and readable source dates during review.
+- Retain earlier repair constraints. Keep a shortened original reply only after every check passes again. Historical evaluations exclude future memories and self-feedback, record code fingerprints, and fail explicitly when requested cases are missing.
+- Remove the unavailable OpenCode Zen Space Bunny Free and Step 5 Preview Free presets. On startup, remove their saved profiles while preserving other models and the default.
+- Add a separate Volcengine Ark Agent Plan category with its auto-router and all 14 current text model IDs/aliases. Use the dedicated `/api/plan/v3` Responses API, official context sizes and vision capabilities; exclude Coding Plan, models already being retired, and image, video, speech and embedding models.
+
+## 1.0.8 — 2026-10-10
+
+- Rework dialogue instructions and context around the current question, proposal or feeling. Old activity reports, room shorthand and self-summaries no longer dominate ordinary exchanges. Greeting images retain their immediate context and agreed forms of address remain available.
+- Allow natural recurring affection and greetings without forcing invented counts, elapsed-time reports or lifestyle advice. Complete reactions are no longer mechanically rewritten to fit a twenty-character limit.
+- Preserve the actual addressee and quoted evidence in group conversations. Later laughter does not erase a serious question, and another bot's interpretation is not the person's confirmation. Empty bot reports do not create confirmation chains or relationship growth.
+- Add an independent comprehensibility check for explanation requests; revisions and factual review retain the current question. Validation respects the configured reasoning effort.
+- Recall relevant historical work versions without denying earlier reading because recent records are incomplete or revealing unrelated private text. Exclude unrelated web material from game progress and sharing while retaining the archive.
+- Distinguish someone else's writing from her own reading promise. Waiting for a manuscript does not execute as writing or substitute another or older book. New self-expressions check actions and participants rather than turning wishes into completed experiences.
+- Update both READMEs, capability boundaries and the release badge; expand historical replay, sequential group scenarios and regression coverage. Transcripts and model reports remain local.
+
 ## 1.0.7 — 2026-10-09
-
-- Ground understanding in the current messages, supplements, speakers and quote chains before choosing a response. Corrections address the actual question instead of substituting apologies or abstract monologues.
-- Keep single topical remarks out of the enduring self's core and prevent extracted replies from becoming fixed scripts. Related recollections, cross-conversation continuity and disclosure boundaries remain available.
-- Exclude known bots from human room-style statistics and end empty bot confirmation loops. An explicit addressed stop ends the current turn; a renewed question can still receive a reply.
-- Preserve provenance and uncertainty in game-content presentation. Current activities and work fragments distinguish reference reading and model-generated material from client operation or completion.
-- Rewrite the latest rejected draft, allow requested factual repetition, and keep contradiction repairs confined to relevant questions. Conversation endings no longer receive an unrelated confusion fallback.
-- Add full-corpus review, historical replay and sequential conversation evaluation tools. Paid model checks run explicitly; private transcripts and reports stay local and are excluded from release artifacts.
-
-## 1.0.5 — 2026-10-07
+
+- Ground understanding in the current messages, supplements, speakers and quote chains before choosing a response. Corrections address the actual question instead of substituting apologies or abstract monologues.
+- Keep single topical remarks out of the enduring self's core and prevent extracted replies from becoming fixed scripts. Related recollections, cross-conversation continuity and disclosure boundaries remain available.
+- Exclude known bots from human room-style statistics and end empty bot confirmation loops. An explicit addressed stop ends the current turn; a renewed question can still receive a reply.
+- Preserve provenance and uncertainty in game-content presentation. Current activities and work fragments distinguish reference reading and model-generated material from client operation or completion.
+- Rewrite the latest rejected draft, allow requested factual repetition, and keep contradiction repairs confined to relevant questions. Conversation endings no longer receive an unrelated confusion fallback.
+- Add full-corpus review, historical replay and sequential conversation evaluation tools. Paid model checks run explicitly; private transcripts and reports stay local and are excluded from release artifacts.
+
+## 1.0.5 — 2026-10-07
 
 - Fixed bound relationships being forgotten when the person was absent from the current conversation. Chat, initiative, solitude, diaries and reviews recall the same account-based ledger by name and role.
 - Distinguished current relationship facts from past opinions and personal feelings. Historical denials and jokes remain in history; relationship-related replies are checked against current knowledge while preserving her choices about interaction and address.
@@ -25,19 +47,18 @@
 - Update and restart stages and validates the official release before stopping, saves a verified data restore point, and switches programs. Failed startup attempts restoration of the previous code and data. Source/npm installs and instance configuration remain intact; repeated clicks coalesce and CLI launches retain managed updates.
 - Added privacy, same-name identity, recovery, real installed-package switching and viewport regression checks. Archive checks verify bytes before parsing SQLite, so damaged files do not expose raw schema errors.
 
-
-## 1.0.3 — 2026-10-06
-
-- Group personas become thoughts about each place. She selectively adds, revises or lets go of impressions, wishes, preferences, questions and boundaries from local encounters, retaining reasons, sources and versions. Her overall personality remains shared; copied legacy personas stay only in history.
-- Manual update checks in system runtime settings show the installed and latest npm versions and release notes. Checks cache and coalesce requests and recover from failures; they do not install or restart.
-- Nature edit allowances come from the server. Audited, idempotent local extra opportunities preserve personality history and other instances' default limits.
-- Added source isolation, selective updates, restart persistence, failed update recovery and responsive interface checks.
-
-## 1.0.2 — 2026-10-06
-
-- Streamed full SQLite data packages with validated import previews, retained recovery points and rollback on failure.
-- Destination management sign-ins and connection settings are retained. Imported auto replies and plugin grants await review; cancelled, expired and interrupted temporary packages are reclaimed.
-
+## 1.0.3 — 2026-10-06
+
+- Group personas become thoughts about each place. She selectively adds, revises or lets go of impressions, wishes, preferences, questions and boundaries from local encounters, retaining reasons, sources and versions. Her overall personality remains shared; copied legacy personas stay only in history.
+- Manual update checks in system runtime settings show the installed and latest npm versions and release notes. Checks cache and coalesce requests and recover from failures; they do not install or restart.
+- Nature edit allowances come from the server. Audited, idempotent local extra opportunities preserve personality history and other instances' default limits.
+- Added source isolation, selective updates, restart persistence, failed update recovery and responsive interface checks.
+
+## 1.0.2 — 2026-10-06
+
+- Streamed full SQLite data packages with validated import previews, retained recovery points and rollback on failure.
+- Destination management sign-ins and connection settings are retained. Imported auto replies and plugin grants await review; cancelled, expired and interrupted temporary packages are reclaimed.
+
 ## 1.0.1 — 2026-10-05
 
 - Global npm installation runs with `luckytri`, including the server, built WebUI, guides and bundled plugin. User data remains outside the package across updates and reinstalls.

package/docs/en/guide.md

@@ -63,12 +63,14 @@ Without a model key, simulated replies use local samples and call no model. Once
 
 Open "System → Model library", click "+ Add model" and choose a preset.
 
-- For the API address enter the root of the provider's compatible endpoint. The program appends `/chat/completions` itself; do not write the full path again.
+- For the API address enter the root of the provider's compatible endpoint. The program appends `/chat/completions` or `/responses` according to the preset; do not write the full path again.
 - For the model name enter a model ID the provider accepts.
 - Leaving the API key empty keeps the saved key.
 
 A preset only fills in a common address and model name; the real models are whatever your provider's console shows. Speaking decisions and replies need the model to return a JSON object.
 
+Volcengine Ark Agent Plan and Coding Plan use separate plans, keys and endpoints. The Agent Plan preset uses its dedicated `/api/plan/v3` address and the Responses API. Enter an Agent Plan API key; do not reuse a Coding Plan key or a regular Ark inference key.
+
 After saving, click "Test this model's connection". The test carries no group chat text. Test again after changing the address, model or key.
 
 You can also stay in simulation mode and trial-chat with TA under "Nature" to see how she speaks before letting her join real QQ.

package/docs/zh/CHANGELOG.md

@@ -1,17 +1,39 @@
 <p align="right"><b>中文</b> · <a href="../en/CHANGELOG.md">English</a></p>
 
-# 版本记录
-
+# 版本记录
+
+## 1.0.9 — 2026-10-11
+
+- 连续追问只回答新问的细节，不反复重讲已经交代的限制；问来源就说来源，问感受就说感受。
+- 聊别人提出的项目时只依据原话，不擅自补出对方正在做的玩法或作业背景。机器人交来新正文或提出新问题却被初稿漏接时，按新内容重答一次；单纯重复确认仍然收住。
+- 对具体故事片段先讲清眼前发生了什么，再说明整部主线未知；不以等全文为由漏答。
+- 拒绝模型输出中的重复 JSON 字段，避免后一个 `bubbles` 静默覆盖完整答案。排队中的消息可以看到本轮开始前已送达的回复，减少重复认错与确认。
+- 区分提问、提议、感受和纠正；复核时保留必要的原话与参与者，核对新提议是否被误当成改编旧作、已经听懂的内容是否被再次认错。新问题省略作品名时，可用同一会话中刚送达给同一人的上一条回复找回阅读记录，只带回阅读事实，不带入回复正文。旧总结按当前话题召回，称呼约定独立保留。
+- 机器人之间的重复报备与换词确认在形成情感变化前核对。主动草稿声称的新行动也先核实实际记录，旧愿望不能给自己作证；复审保留历史与可读的来源日期。
+- 修订保留此前指出的约束；末尾气泡出错时，只有重新通过全部检查的完整前缀才可保留。历史评测隔离未来记忆与自我反馈，记录代码指纹，漏选指定场景时明确报错。
+- 移除已不可用的 OpenCode Zen Space Bunny Free 与 Step 5 Preview Free 预设；实例启动时自动删除对应的旧档案，保留其他模型和默认项。
+- 新增独立的火山方舟 Agent Plan 分类，提供自动路由与全部 14 个当前文本模型 ID/别名。按官方接口使用专属 `/api/plan/v3` Responses API、模型上下文与视觉能力；不混入 Coding Plan、已启动下线模型或图像、视频、语音和向量模型。
+
+## 1.0.8 — 2026-10-10
+
+- 重新整理对话提示与上下文：优先回答眼前的具体问题、提议和感受，不再让旧活动汇报、群内暗号和过去的自我总结主导普通交流。问候附图同样按当前语境处理，约定称呼仍然保留。
+- 修复普通亲近表达被重复检查退回的问题；“我也想你”、晚安等自然回应可以再次使用，无须编出次数、时间间隔或生活建议。完整的一句反应不再因二十字限制被机械改写。
+- 多人对话保留实际回应对象与引用证据，不因后面的笑声漏掉认真提问，也不把另一机器人的猜测当本人确认。没有新内容的机器人报备不再形成确认链或关系增长。
+- 增加独立的可理解性检查：对方要求解释时，答案须让提问者读懂；修订与事实复核保留当前问题，校验阶段遵循配置的推理程度。
+- 作品召回搜索相关历史版本；已有阅读可以核实，不再因近期记录缺失否认过去，也不披露无关私下正文。排除混入游戏资料的无关网页，保留原档案并阻止其成为进度证据或分享内容。
+- 区分别人的写作与自己的阅读约定；等待正文时不执行成写作，不拿无关或旧书替代。新保存的念头核对行动与参与者，避免把愿望写成已完成经历。
+- 更新中英文 README、能力边界与发布版本徽章；扩展历史回放、连续多人对话和回归测试。聊天记录与模型评测报告只留本地。
+
 ## 1.0.7 — 2026-10-09
-
-- 调整理解与表达顺序：先核对本轮原话、连续补充、说话人和引用，再决定回应。被纠正时修正具体问题，不用道歉、内心独白或抽象比喻替代答案。
-- 临时话题观点不再自动占据长期自我的核心位置；一次回复不形成固定话术习惯。相关旧想法仍可召回，跨群连续记忆、来源和私密范围保留。
-- 已知机器人不再参与人类群聊口吻统计；无新内容的机器人确认循环会收住。明确要求停止时不再一边答应闭嘴一边继续建议，新的问题仍能重新回应。
-- 修复游戏内容展示抹去来源与不确定性的错误。当前活动和作品片段带回参考阅读与材料来源，模型整理不再被展示层改写为客户端操作或通关。
-- 重写针对最新被退回的稿子；重复确认事实不会因去重而被吞掉。旧话矛盾的修复只用于相关追问，不插入无关问答。收尾、未理解问题和危机场景分别处理。
-- 增加全量会话分段审阅、历史场景回放与连续对话评测工具。调用模型的检查需显式运行，原始聊天和报告仅留本地，不随发布包分发。
-
-## 1.0.5 — 2026-10-07
+
+- 调整理解与表达顺序：先核对本轮原话、连续补充、说话人和引用，再决定回应。被纠正时修正具体问题，不用道歉、内心独白或抽象比喻替代答案。
+- 临时话题观点不再自动占据长期自我的核心位置；一次回复不形成固定话术习惯。相关旧想法仍可召回，跨群连续记忆、来源和私密范围保留。
+- 已知机器人不再参与人类群聊口吻统计；无新内容的机器人确认循环会收住。明确要求停止时不再一边答应闭嘴一边继续建议，新的问题仍能重新回应。
+- 修复游戏内容展示抹去来源与不确定性的错误。当前活动和作品片段带回参考阅读与材料来源，模型整理不再被展示层改写为客户端操作或通关。
+- 重写针对最新被退回的稿子；重复确认事实不会因去重而被吞掉。旧话矛盾的修复只用于相关追问，不插入无关问答。收尾、未理解问题和危机场景分别处理。
+- 增加全量会话分段审阅、历史场景回放与连续对话评测工具。调用模型的检查需显式运行，原始聊天和报告仅留本地，不随发布包分发。
+
+## 1.0.5 — 2026-10-07
 
 - 修复人际关系已绑定却无法在另一段会话中认出对方的问题。聊天、主动表达、独处、日记和回顾从同一份关系记录按名字、账号与称呼召回，不要求关系对象正在说话。
 - 区分当前关系、过去看法和自己的感受。旧的否认或玩笑保留在历史中，不能替代更新后的事实；关系相关回复发送前再次核对，保持自己的相处与称呼选择。
@@ -25,19 +47,18 @@
 - 检查更新新增「更新并重启」：先安装校验，再保留完整数据恢复点并切换；启动失败尝试恢复旧程序和数据。源码、npm 安装、配置与生活数据保留，重复点击合并，启动命令接续已更新程序。
 - 补充关系权限、同名对象、身份、失败恢复、真实安装切换与不同屏幕回归。校验清单先检查文件哈希，再解析数据库，损坏文件不会返回原始 SQLite 结构错误。
 
-
-## 1.0.3 — 2026-10-06
-
-- 群人格改为「在这里的想法」：她根据各处真实相处选择性新增、修改或放下印象、愿望、偏好、疑问和分寸，保留理由、来源和版本。整体人格仍统一，复制来的旧正文仅留在历史中。
-- 系统运行设置新增手动检查更新，显示当前版本、npm 最新版本及发布说明；有缓存、并发合并和失败重试，不自动安装或重启。
-- 天性修改额度由服务端统一提供，支持有记录、幂等的本地额外机会，不删除原人格版本，不改变其他实例默认限制。
-- 补充跨会话来源、选择性更新、重启持久化、更新失败恢复，以及桌面、平板和手机界面的回归检查。
-
-## 1.0.2 — 2026-10-06
-
-- 数据导入导出：流式导出完整 SQLite 数据包，导入前校验并预览；替换前保留恢复点，失败可回滚。
-- 保留目标实例的管理登录和连接设置；导入后先关闭自动回复与插件授权，供管理员重新确认。临时包支持取消、过期和重启回收。
-
+## 1.0.3 — 2026-10-06
+
+- 群人格改为「在这里的想法」：她根据各处真实相处选择性新增、修改或放下印象、愿望、偏好、疑问和分寸，保留理由、来源和版本。整体人格仍统一，复制来的旧正文仅留在历史中。
+- 系统运行设置新增手动检查更新，显示当前版本、npm 最新版本及发布说明；有缓存、并发合并和失败重试，不自动安装或重启。
+- 天性修改额度由服务端统一提供，支持有记录、幂等的本地额外机会，不删除原人格版本，不改变其他实例默认限制。
+- 补充跨会话来源、选择性更新、重启持久化、更新失败恢复，以及桌面、平板和手机界面的回归检查。
+
+## 1.0.2 — 2026-10-06
+
+- 数据导入导出：流式导出完整 SQLite 数据包，导入前校验并预览；替换前保留恢复点，失败可回滚。
+- 保留目标实例的管理登录和连接设置；导入后先关闭自动回复与插件授权，供管理员重新确认。临时包支持取消、过期和重启回收。
+
 ## 1.0.1 — 2026-10-05
 
 - 全局 npm 安装后直接运行 `luckytri`，服务端、WebUI、教程和内置插件一并安装；用户数据独立保存，更新和重装继续使用。

package/docs/zh/guide.md

@@ -63,12 +63,14 @@ LuckyTri 是「TA 的小世界」，左侧导航分三组、十个入口：
 
 打开「系统 → 模型库」，点「＋ 新增模型」选择一个预设。
 
-- API 地址填写服务商的兼容接口根路径。程序会自己拼接 `/chat/completions`，不要把完整路径再写一遍。
+- API 地址填写服务商的兼容接口根路径。程序会按预设自动拼接 `/chat/completions` 或 `/responses`，不要把完整路径再写一遍。
 - 模型名称填写服务商接受的模型 ID。
 - API Key 留空表示保留已保存的密钥。
 
 预设只填入常见地址和模型名，以服务商控制台里的实际模型为准。发言决策和回复生成需要模型返回 JSON 对象。
 
+火山方舟 Agent Plan 与 Coding Plan 使用不同套餐、密钥和接口地址。Agent Plan 预设使用专属 `/api/plan/v3` 地址和 Responses API；请填入 Agent Plan 专属 API Key，不要与 Coding Plan 或普通方舟推理 API 的密钥混用。
+
 保存后点「测试此模型连接」。测试不携带群聊原文。更换地址、模型或密钥后需要重新测试。
 
 也可以先保持模拟模式，在「天性」里和 TA 试聊，确认 TA 说话的样子后再让 TA 参加真实 QQ。

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "luckytri",
-  "version": "1.0.7",
+  "version": "1.0.9",
   "description": "让由技术诞生的她，在时间、记忆、相遇与选择中逐渐形成自己的方向",
   "license": "MIT",
   "repository": {

package/public/guide.en.html

@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8" />
     <meta name="viewport" content="width=device-width,initial-scale=1" />
-    <title>LuckyTri v1.0.7 · Getting Started</title>
+    <title>LuckyTri v1.0.9 · Getting Started</title>
     <style>
       * {
         box-sizing: border-box;
@@ -269,7 +269,7 @@
   <body>
     <header>
       <div>
-        <b>LuckyTri · Handbook</b><small>TIME · MEMORY · CHOICE / v1.0.7</small>
+        <b>LuckyTri · Handbook</b><small>TIME · MEMORY · CHOICE / v1.0.9</small>
       </div>
       <nav>
         <a href="/#setup">Back to the studio</a
@@ -497,8 +497,9 @@ luckytri
         <ul>
           <li>
             For the API address enter the root of the provider&#39;s compatible
-            endpoint. The program appends <code>/chat/completions</code> itself;
-            do not write the full path again.
+            endpoint. The program appends <code>/chat/completions</code> or
+            <code>/responses</code> according to the preset; do not write the
+            full path again.
           </li>
           <li>For the model name enter a model ID the provider accepts.</li>
           <li>Leaving the API key empty keeps the saved key.</li>
@@ -508,6 +509,13 @@ luckytri
           models are whatever your provider&#39;s console shows. Speaking
           decisions and replies need the model to return a JSON object.
         </p>
+        <p>
+          Volcengine Ark Agent Plan and Coding Plan use separate plans, keys and
+          endpoints. The Agent Plan preset uses its dedicated
+          <code>/api/plan/v3</code> address and the Responses API. Enter an
+          Agent Plan API key; do not reuse a Coding Plan key or a regular Ark
+          inference key.
+        </p>
         <p>
           After saving, click &quot;Test this model&#39;s connection&quot;. The
           test carries no group chat text. Test again after changing the
@@ -1057,7 +1065,7 @@ npm start
     </div>
     <footer>
       LuckyTri · so that experience and choice stay coherent. This guide matches
-      the v1.0.7 interface.
+      the v1.0.9 interface.
     </footer>
   </body>
 </html>

package/public/guide.html

@@ -3,7 +3,7 @@
   <head>
     <meta charset="utf-8" />
     <meta name="viewport" content="width=device-width,initial-scale=1" />
-    <title>LuckyTri v1.0.7 · 使用教程</title>
+    <title>LuckyTri v1.0.9 · 使用教程</title>
     <style>
       * {
         box-sizing: border-box;
@@ -269,7 +269,7 @@
   <body>
     <header>
       <div>
-        <b>LuckyTri · 上手手册</b><small>TIME · MEMORY · CHOICE / v1.0.7</small>
+        <b>LuckyTri · 上手手册</b><small>TIME · MEMORY · CHOICE / v1.0.9</small>
       </div>
       <nav>
         <a href="/#setup">返回管理台</a
@@ -460,8 +460,9 @@ luckytri
         <p>打开「系统 → 模型库」，点「＋ 新增模型」选择一个预设。</p>
         <ul>
           <li>
-            API 地址填写服务商的兼容接口根路径。程序会自己拼接
-            <code>/chat/completions</code>，不要把完整路径再写一遍。
+            API 地址填写服务商的兼容接口根路径。程序会按预设自动拼接
+            <code>/chat/completions</code> 或
+            <code>/responses</code>，不要把完整路径再写一遍。
           </li>
           <li>模型名称填写服务商接受的模型 ID。</li>
           <li>API Key 留空表示保留已保存的密钥。</li>
@@ -470,6 +471,12 @@ luckytri
           预设只填入常见地址和模型名，以服务商控制台里的实际模型为准。发言决策和回复生成需要模型返回
           JSON 对象。
         </p>
+        <p>
+          火山方舟 Agent Plan 与 Coding Plan 使用不同套餐、密钥和接口地址。Agent
+          Plan 预设使用专属 <code>/api/plan/v3</code> 地址和 Responses
+          API；请填入 Agent Plan 专属 API Key，不要与 Coding Plan 或普通方舟推理
+          API 的密钥混用。
+        </p>
         <p>
           保存后点「测试此模型连接」。测试不携带群聊原文。更换地址、模型或密钥后需要重新测试。
         </p>
@@ -864,6 +871,6 @@ npm start
         </p>
       </article>
     </div>
-    <footer>LuckyTri · 让经历和选择彼此连贯。教程与 v1.0.7 界面同步。</footer>
+    <footer>LuckyTri · 让经历和选择彼此连贯。教程与 v1.0.9 界面同步。</footer>
   </body>
 </html>

package/public/tutorial.en.md

@@ -61,12 +61,14 @@ Without a model key, simulated replies use local samples and call no model. Once
 
 Open "System → Model library", click "+ Add model" and choose a preset.
 
-- For the API address enter the root of the provider's compatible endpoint. The program appends `/chat/completions` itself; do not write the full path again.
+- For the API address enter the root of the provider's compatible endpoint. The program appends `/chat/completions` or `/responses` according to the preset; do not write the full path again.
 - For the model name enter a model ID the provider accepts.
 - Leaving the API key empty keeps the saved key.
 
 A preset only fills in a common address and model name; the real models are whatever your provider's console shows. Speaking decisions and replies need the model to return a JSON object.
 
+Volcengine Ark Agent Plan and Coding Plan use separate plans, keys and endpoints. The Agent Plan preset uses its dedicated `/api/plan/v3` address and the Responses API. Enter an Agent Plan API key; do not reuse a Coding Plan key or a regular Ark inference key.
+
 After saving, click "Test this model's connection". The test carries no group chat text. Test again after changing the address, model or key.
 
 You can also stay in simulation mode and trial-chat with TA under "Nature" to see how she speaks before letting her join real QQ.

package/public/tutorial.md

@@ -61,12 +61,14 @@ LuckyTri 是「TA 的小世界」，左侧导航分三组、十个入口：
 
 打开「系统 → 模型库」，点「＋ 新增模型」选择一个预设。
 
-- API 地址填写服务商的兼容接口根路径。程序会自己拼接 `/chat/completions`，不要把完整路径再写一遍。
+- API 地址填写服务商的兼容接口根路径。程序会按预设自动拼接 `/chat/completions` 或 `/responses`，不要把完整路径再写一遍。
 - 模型名称填写服务商接受的模型 ID。
 - API Key 留空表示保留已保存的密钥。
 
 预设只填入常见地址和模型名，以服务商控制台里的实际模型为准。发言决策和回复生成需要模型返回 JSON 对象。
 
+火山方舟 Agent Plan 与 Coding Plan 使用不同套餐、密钥和接口地址。Agent Plan 预设使用专属 `/api/plan/v3` 地址和 Responses API；请填入 Agent Plan 专属 API Key，不要与 Coding Plan 或普通方舟推理 API 的密钥混用。
+
 保存后点「测试此模型连接」。测试不携带群聊原文。更换地址、模型或密钥后需要重新测试。
 
 也可以先保持模拟模式，在「天性」里和 TA 试聊，确认 TA 说话的样子后再让 TA 参加真实 QQ。

package/server/core/context-builder.js

@@ -24,11 +24,30 @@ function recallTerms(text) {
 
 // Who said what to whom, up to the watermark: @, quotes, name calls and the
 // reply chains they form.
-export function perceive(repo, session, watermark, simulated, name) {
+export function perceive(
+  repo,
+  session,
+  watermark,
+  simulated,
+  name,
+  { resolved = null, sentBefore = 0 } = {},
+) {
+  // A queued message may predate the reply to the preceding batch. She has
+  // already said those words by the time this turn starts and must see them.
+  // Keep later user messages and replay futures outside the batch boundary.
+  const delivered = sentBefore
+    ? repo
+        .recentEvents(session, 8, { simulated, role: "assistant" })
+        .filter((m) => m.seq > watermark && m.time <= sentBefore)
+    : [];
+  if (resolved && !delivered.length) return resolved;
   return resolveTargets(
     [
-      ...repo.references(session, { simulated }),
-      ...repo.events(session, watermark, { simulated }),
+      ...(resolved || [
+        ...repo.references(session, { simulated }),
+        ...repo.events(session, watermark, { simulated }),
+      ]),
+      ...delivered,
     ],
     name,
     identityAliases(name, repo.store.settings().aliases || ""),

package/server/core/contribution-check.js

@@ -0,0 +1,50 @@
+import {
+  conversationGrounding,
+  recentOwnMessages,
+} from "./conversation-grounding.js";
+
+export function botExchange(snapshot, decision = {}) {
+  if (!decision || typeof decision !== "object" || Array.isArray(decision))
+    return null;
+  if (
+    snapshot.initiative ||
+    decision.act ||
+    decision.share ||
+    ["chat", "rest"].includes(decision.attention?.action)
+  )
+    return null;
+  const grounding = conversationGrounding(snapshot);
+  const current = (snapshot.messages || []).filter(
+    (m) => snapshot.batchIds?.includes(m.id) && m.role === "user",
+  );
+  if (
+    !current.length ||
+    !current.every((m) => grounding.botMessageIds.includes(m.id)) ||
+    grounding.botOnlyTail < 4
+  )
+    return null;
+  const own = recentOwnMessages(snapshot, 4);
+  if (!own.length) return null;
+  const speakers = new Set(current.map((m) => m.speaker));
+  return {
+    current: current.map(({ id, speaker, text }) => ({ id, speaker, text })),
+    previousOwn: own.map(({ id, text }) => ({ id, text })),
+    previousBots: (snapshot.messages || [])
+      .filter(
+        (m) =>
+          m.role === "user" &&
+          speakers.has(m.speaker) &&
+          !snapshot.batchIds.includes(m.id),
+      )
+      .slice(-4)
+      .map(({ id, text }) => ({ id, text })),
+  };
+}
+
+export const CONTRIBUTION_CHECK = `判断一段机器人之间的接话是否有继续说的内容。只输出JSON，不扮演任何人。
+botExchange是实际原话，reply是准备发出的话；plannedPoint只是草稿的自我描述，不能拿“接住、回应、强调、确认、收住”这些工作说明证明有内容。reply非空时只判断它实际说了什么。
+对方提出新问题、分享新感受或实际段落，可以回应；具体的感受、疑问、不同看法、小联想也算内容，不要求新知识、完整故事或重大事件。尤其创作讨论，可以喜欢或不喜欢一处实际表达，不必强迫沉默。
+但同一个边界、承诺、等待、归属或确认，换措辞、换比喻再认一遍，仍没有新意思。比如双方已经确认什么时候发由作者自己定，下一句“对，还是你决定”不用再发；只说“等稿、这笔记上、原样还你、谁也不欠、按你算”不能独自成为新内容。对方报备同一决定也不需要你再次许可。没有新内容就结束，不为了避免沉默另编一件事。
+如果reply没有新内容，再判断current里是否有这轮刚出现、且draft没有回答的具体新段落、作品交付、问题或纠正。有则shouldRepair=true，表示需要根据这轮新内容重想一次；这不是要换词确认。若current只是旧决定的重复报备、同意或收尾，shouldRepair=false。输出 {"hasContribution":true或false,"newPoint":"reply里确有的新内容，没有则空","shouldRepair":true或false,"reason":"与先前原话相比，实际增加或重复了什么"}。`;
+
+export const CONTRIBUTION_REPAIR = `上一稿被判为没有新内容。请重新读 context 和 exchange.current，判断这轮是否有还没答到的新问题、纠正、实际交付或具体片段。若有，就只回应那个新点：有人送来新作品或片段时，不只重复“我等全文/会按约定读”，先从本轮实际给出的文字里挑一处，给出具体而有限的反应；整部主线或人物动机未知时再说明未知。不要编造原文没有的情节，不必复盘整段历史。若眼前确实没有新点，可以继续沉默。仍输出完整的聊天判断 JSON。`;

package/server/core/conversation-cues.js

@@ -1,4 +1,9 @@
 import { claimedPlay } from "../mind/guard.js";
+import { readerQuestions } from "./reader-check.js";
+import {
+  recentOwnMessages,
+  routineSocialReply,
+} from "./conversation-grounding.js";
 
 // Stable message timestamps stay with history; changing clock/style cues belong at the tail.
 const clockFormats = new Map();
@@ -73,7 +78,11 @@ export function replyFocus(snapshot, decision) {
   if (
     /看不懂|没看懂|听不懂|太抽象|说人话|复读|别重复|好好说话|你在说什么|你在讲什么/.test(
       latest,
-    )
+    ) ||
+    (/^[?？]+$/.test(latest) &&
+      readerQuestions(snapshot, decision).some((q) =>
+        targets.some((m) => m.id === q.id),
+      ))
   )
     return {
       kind: "readability_repair",
@@ -185,7 +194,7 @@ export function conversationCues(
   now = Date.now(),
   timeZone,
 ) {
-  const recent = messages.filter((m) => m.role === "assistant").slice(-8);
+  const recent = recentOwnMessages({ messages, batchIds }, 8);
   const batch = messages.filter((m) => batchIds.includes(m.id));
   const previous = messages
     .filter(
@@ -207,7 +216,7 @@ export function conversationCues(
       ellipsisCount: recent.filter((m) => ellipsis.test(m.text)).length,
       recentReplies: recent.map((m) => ({ id: m.id, text: m.text })),
       instruction:
-        "这是过去说过的话，不是风格示范。保留事实，不继承复述、拖音、省略号、无意义第二句等坏习惯。短反应hh可自然重复，具体台词不要换几个字重发。",
+        "这是近期说过的话，不是风格示范。不继承模板或无意义第二句；新问候和亲近表达可以自然回应，晚安、我也想你、hh不必为避免重复而编花样。没有新意思的承诺和确认不用换词再发。",
     },
   };
 }
@@ -218,10 +227,7 @@ export function conversationalIssues(result, snapshot, decision = {}) {
     : (snapshot.messages || []).filter((m) =>
         snapshot.batchIds?.includes(m.id),
       );
-  const recent = snapshot.messages
-    .filter((m) => m.role === "assistant")
-    .slice(-8)
-    .map((m) => m.text);
+  const recent = recentOwnMessages(snapshot, 8).map((m) => m.text);
   const issues = [];
   if (
     replyFocus(snapshot, decision).kind === "readability_repair" &&
@@ -327,9 +333,22 @@ export function conversationalIssues(result, snapshot, decision = {}) {
     )
   )
     issues.push("不要为共情虚构自己同样上班或亲历；回应对方的事情即可");
-  if (texts.some(claimedPlay))
+  if (
+    texts.some(
+      (line) =>
+        claimedPlay(line) &&
+        !(
+          /通关后|通关才能|解锁|需要.{0,8}通关|二周目.{0,6}(?:设计|设定|模式)/.test(
+            line,
+          ) &&
+          !/我.{0,10}(?:已经|之前|刚|早就|确实|全)?(?:玩过|通关|打完|拿到|达成)/.test(
+            line,
+          )
+        ),
+    )
+  )
     issues.push(
-      "不要说自己玩过、通关过什么或平时玩得杂：你没有这样的经历记录。可以说知道这作、听人聊过，或者想玩；被问到玩过什么，如实说还没真的玩过",
+      "不要把游戏资料阅读说成实际操控客户端、通关或拿到成就。有真实阅读和笔记时，直接谈读到的内容、进度和感受，不能反过来否认读过或写过；只想了解的作品才说想了解，不用旧的口头夸大当经历证据",
     );
   if (
     texts.some((t) =>
@@ -341,20 +360,13 @@ export function conversationalIssues(result, snapshot, decision = {}) {
     issues.push(
       "不要为接话虚构自己有身体做过的日常经历；保留对眼前趣事的反应，不说自己也拿过、去过或做过",
     );
-  if (
-    texts.some((t) =>
-      /^.{2,22}[啊呀][，,…。]*(?:那)?(?:确实|真的|有点)/.test(t),
-    )
-  )
-    issues.push(
-      "这是复述加感叹的模板，不要只改标点或换同义词；用一句自己的态度回应，也可以很短",
-    );
   // A substantial shared beginning is a useful signal, unlike repeated brief reactions.
   const clean = (t) => t.replace(/[\s\p{P}\p{S}]/gu, "");
   for (const text of texts) {
     const t = clean(text);
     if (
       t.length >= 8 &&
+      !routineSocialReply(text, snapshot) &&
       recent.filter((r) => clean(r).startsWith(t.slice(0, 5))).length >= 2
     )
       issues.push(