@starwish-ai/xingyuan-dsh 0.6.5 → 0.6.7

package/CHANGELOG.md

@@ -5,6 +5,102 @@ All notable changes to this project are documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.6.7] - 2026-09-29
+
+Close the parity gap that the host's newly shipped practice rule
+(`dsh-agent-preset/skills/cordis-plugin-development/references/user-actions.md`,
+"one operation, two callers") exposes: three things you could only do on a page now have
+agent-facing equivalents over the same business layer. Model tool count 45 → 49.
+
+### Added
+- `set_wish_category_color` — set or clear a category's default color, the same write path the
+  wish page's 分类管理 panel uses (empty color key clears the override, falling back to the
+  wish's own color or the automatic hash).
+- `clear_all_memories` — clear the whole memory store. This is a locked destructive category:
+  it always confirms regardless of the write-confirmation switches, and an empty store replies
+  without asking.
+- `get_xingyuan_settings` / `update_xingyuan_settings` — read every preference, and change the
+  four non-authorization ones (memory injection limit, confirmation-card language, tab
+  visibility mode, per-tab hidden list). Writes go through the host settings form on the
+  bundle's own row and are **read back and compared**: if the host did not accept them the tool
+  fails with `pref_write_rejected` rather than reporting a change that never happened.
+- The `xingyuan` service gained `uiPrefs()` and `setPrefs(patch)` alongside `prefs()`.
+
+### Changed
+- Category-color writes moved out of `routes/api.ts` into `store.setCategoryColor`, so the page
+  action and the chat tool share one validation and one serialized read-modify-write queue.
+  Previously the route only truncated the category name, so `name: ''` persisted a ghost
+  override keyed by the empty string that could never be cleared from the UI; names are now
+  validated (`bad_category_name`) on both paths. Category existence (wishes ∪ color overrides)
+  likewise has one implementation, `store.categoryExists`.
+- Rejected preference writes never half-apply: out-of-range limits (`bad_memory_limit`), unknown
+  tab ids (`unknown_tab`) and empty patches (`missing_field`) all fail before anything is written.
+- Documentation: AGENTS.md §5.5 confirmation matrix, §6 tool list, §8 configuration table and
+  the §5.10 self-audit against the 0.2.0-rc.1 skills now record the closed gap; both READMEs
+  state the UI/chat parity.
+
+### Security
+- `update_xingyuan_settings` deliberately does **not** accept `confirmWrites` or `confirmOps`.
+  Loosening the write-confirmation policy is an authorization change and stays user-only per
+  the same official rule; a test asserts those keys are absent from the tool's parameters.
+
+## [0.6.6] - 2026-09-29
+
+Adapt to the dsh `0.2.0-rc.1` host line while keeping `0.1.7-rc.1` supported. Upgrading the
+host had made the plugin disappear completely: the compatibility gate introduced in
+0.1.7-rc.1 evaluates only the peers a package *declares*, and `^0.1.7-rc.1` does not admit
+`0.2.0-rc.1`, so dsh skipped the whole bundle — reproduced with
+`dsh --profile web --dump-config`, which printed
+`skipping profile bundle "@starwish-ai/xingyuan-dsh" … is incompatible with dsh 0.2.0-rc.1`.
+Preset, chat cards, session-view tabs, the settings page and the standalone `/xingyuan/*`
+pages all vanished; the SQLite data stayed intact.
+
+### Added
+- `test/host-baseline.test.ts` — two new gates: every supported host version line
+  (`SUPPORTED_DSH_VERSIONS`) must be admitted by **all** dsh peers under the host's own
+  predicate (`semver.satisfies(line, range, {includePrerelease: true})`), the pinned
+  devDependency must be one of those lines, and an unverified next generation
+  (`0.3.0-rc.1`) must still be refused. Widening support therefore stays a deliberate,
+  verified act instead of a silent over-promise.
+- `test/prompts.test.ts` — a gate that the reminder guide and the capabilities section
+  contain no host-version-specific assertion.
+- AGENTS.md §5.10 — self-audit against the skills shipped with 0.2.0-rc.1 (the new
+  `references/user-actions.md` "one operation, two callers" rule and the `agent-experience`
+  skill), recording three UI-only actions that still lack tool equivalents as deliberate,
+  documented deviations rather than shipping half-implementations.
+
+### Changed
+- peerDependencies: all 16 `@deepseek-ai/dsh-*` entries now admit two host lines
+  (`^0.1.7-rc.1 || ^0.2.0-rc.1`) — this is exactly what the gate reads.
+- devDependencies: host baseline moved to `0.2.0-rc.1`. `cordis 4.0.4`,
+  `cordis-plugin-loader 1.0.5` and `schemastery 3.18.4` are unchanged in that release.
+- Reminder guidance (`REMINDER_GUIDE` plus the capabilities line) no longer states a fixed
+  capability. The host rewrote its schedule subsystem in 0.2.0 — one-shot/session-local
+  timers became Host-wide durable reminders with `daily`/`weekly`/`cron`, a
+  `schedule_update` tool, its own storage domain and `every_seconds` lowered to a 60 s
+  minimum — and because this package supports both host lines, any "periodic reminders are
+  impossible" sentence would now be a false statement to users. The guide instead tells the
+  model to read the timing parameters `schedule_create` actually accepts and to answer
+  accordingly.
+- Documentation: AGENTS.md header gains the 0.2.0-rc.1 delta notes; §10 decision 7 and §11
+  are rewritten on the new schedule facts; the transcriptView note now reflects per-host
+  defaults (web defaults to `detailed` from 0.2.0, Desktop `standard`, and only `verbose`
+  avoids folding completed turns); §4's upgrade checklist gained the schedule row's changed
+  plugin shape; the troubleshooting table gained the observed symptom and its remedy.
+
+### Fixed
+- The plugin being unusable on dsh 0.2.0-rc.1. **No business-code change was required**:
+  package-by-package byte comparison between 0.1.7-rc.1 and 0.2.0-rc.1 showed that every
+  host seam this plugin touches is unchanged — session format is still v4, the v3→v4
+  migration edge still preserves ignorable plugin events (so the session-log self-repair
+  boundary stands), `retainedBy.mainView` and `projectionValues.agentPreset` are unchanged,
+  `dsh-host-webserver` / `dsh-settings` / `dsh-storage` / `dsh-storage-domain` /
+  `dsh-system-prompt` / `dsh-user-questions` / `dsh-client-ui-slots` /
+  `dsh-client-ui-renderer` / `dsh-client-store` / `dsh-session-format-catalog` and the
+  `dsh-agent-preset` implementation are byte-identical, and no changed package removed a
+  symbol this package imports. Verified with `pnpm typecheck`, `pnpm build` and the full
+  suite (25 files / 293 tests) against the new baseline.
+
 ## [0.6.5] - 2026-09-24
 
 First stable line on the dsh 0.1.7 host contract. This release re-verifies the plugin

package/README.en-US.md

@@ -16,8 +16,12 @@ XingYuan is a wish & habit-building companion, shipped as a DeepSeek Harness plu
 - **Micro-actions**: break an overwhelming goal into 3–7 tiny steps and walk through them guided
 - **Growth system**: levels Lv.1–Lv.10, streak bonuses, stat cards, 30-day bar chart
 - **Session view tabs**: Today / Wishes / Tasks / Calendar / Growth / Memory — buttons call action endpoints directly; shown only in XingYuan-preset sessions by default, switchable to always show/hide and per-tab in Settings
-- **Memory**: important memories injected into context (limit configurable), full CRUD
+- **Memory**: important memories injected into context (limit configurable), full CRUD and clear-all
 - **Charts**: 15 chart types rendered as cards
+- **Parity between UI and chat**: anything you can do on a page — check in, claim, delete, rename or
+  recolor a category, clear memories, adjust preferences — you can also ask the assistant to do,
+  through the same business layer with the same result; loosening the write-confirmation policy
+  stays user-only (Settings page) by design
 - **Safe writes**: write confirmation is per-category (create / check-in / undo / claim / edit / save memory); deletion always confirms and cannot be turned off; defaults match previous versions
 - **Theming**: light/dark follows the app theme
 
@@ -25,10 +29,12 @@ Tools are only mounted on sessions using the XingYuan preset; other sessions are
 
 ## Install
 
-> Requires DeepSeek Harness `0.1.7-rc.1` (peer dependencies — including the host's
-> client-half packages — are pinned to that release; 0.1.7 rewrote the settings
-> subsystem, so on older hosts this plugin's client half does not activate at all,
-> and since rc.1 dsh refuses to load a bundle whose peer range does not match.
+> Requires DeepSeek Harness `0.1.7-rc.1` **or** `0.2.0-rc.1` (peer dependencies admit both
+> version lines, including the host's client-half packages; 0.1.7 rewrote the settings
+> subsystem, so on older hosts this plugin's client half does not activate at all, and
+> since rc.1 dsh refuses to load a whole bundle whose peer range does not match — this
+> package's "every supported line is admitted" claim is locked by a test). Scheduled
+> reminder capabilities differ between the two host versions and are not hardcoded here.
 > Check the upgrade notes in [AGENTS.md](./AGENTS.md) before bumping dsh).
 
 ```sh
@@ -55,8 +61,8 @@ that directory — copy the profile file too if you want them on a new machine.
 | Coach style | Gentle / humorous / strict |
 | User profile | Nickname, occupation, interests |
 | Write confirmation | Master switch + per-category toggles (create / check-in / undo / claim / edit / save memory); deletion always confirms and cannot be turned off |
-| Memory injection limit | Max memories injected per turn |
-| Tab visibility | Three modes (follow session / always show / always hide) plus per-tab toggles; defaults to follow session |
+| Memory injection limit | Max memories injected per turn (also settable by saying "use 20 memories" in chat) |
+| Tab visibility | Three modes (follow session / always show / always hide) plus per-tab toggles; defaults to follow session. These four non-authorization preferences are also adjustable in chat |
 | Confirm card language | Language of the in-chat confirmation card (Chinese / English; the platform does not expose UI language to plugins, defaults to Chinese) |
 
 ## Development

package/README.md

@@ -18,8 +18,11 @@
 - **成长体系**：等级 Lv.1–Lv.10、连续加成、统计卡与近 30 天柱状图
 - **会话视图页**：今日 / 愿望 / 任务 / 日历 / 成长 / 记忆 六个标签页，页面按钮直连动作接口；
   默认仅星愿预设的会话显示，可在设置里切换「始终显示 / 始终隐藏」并按标签勾选
-- **记忆**：重要记忆自动注入上下文（上限可配），支持增删改查
+- **记忆**：重要记忆自动注入上下文（上限可配），支持增删改查与一键清空
 - **图表**：15 种统计图表自动渲染为卡片
+- **页面与对话同权**：页面上能做的（打卡 / 领取 / 删除 / 分类改名与配色 / 清空记忆 /
+  调整偏好）都能直接在对话里说，走同一份业务收口，结果与回显一致；
+  放宽安全策略的开关（写操作二次确认）例外，只能由本人在设置页改
 - **安全确认**：写操作二次确认按类目细化（创建 / 打卡 / 取消打卡 / 领取 / 修改 / 保存记忆），删除始终确认不可关闭；默认与此前版本一致
 - **主题适配**：深浅色跟随应用主题
 
@@ -27,9 +30,10 @@
 
 ## 安装
 
-> 需要 DeepSeek Harness `0.1.7-rc.1`（peer 依赖按该版本锁定，含 client 半侧的宿主包；
-> 0.1.7 重写了设置子系统，更早的宿主上本插件的 client 半侧不会激活，且 rc.1 起
-> dsh 会按 peer 范围**拒绝加载**不兼容的插件包。升级 dsh 前先核对 [AGENTS.md](./AGENTS.md)
+> 需要 DeepSeek Harness `0.1.7-rc.1` 或 `0.2.0-rc.1`（peer 依赖同时 admit 这两条版本线，
+> 含 client 半侧的宿主包；0.1.7 重写了设置子系统，更早的宿主上本插件的 client 半侧不会激活；
+> rc.1 起 dsh 会按 peer 范围**整包拒绝加载**不匹配的插件，本包的「每条线都放行」由测试锁死。
+> 两版宿主的定时提醒能力不同，插件不把能力写死。升级 dsh 前先核对 [AGENTS.md](./AGENTS.md)
 > 的升级要点）。
 
 ```sh
@@ -58,8 +62,8 @@ dsh plugin --profile web add @starwish-ai/xingyuan-dsh
 | 教练风格 | 温柔 / 幽默 / 严格 |
 | 用户画像 | 昵称、职业、兴趣 |
 | 写操作二次确认 | 总开关 + 六个类目明细（创建 / 打卡 / 取消打卡 / 领取 / 修改 / 保存记忆）是否确认；删除始终确认、不可关闭 |
-| 记忆注入上限 | 每次注入上下文的记忆条数上限 |
-| 标签页显示 | 三态模式（跟随会话 / 始终显示 / 始终隐藏）+ 六个标签逐个勾选；默认跟随会话 |
+| 记忆注入上限 | 每次注入上下文的记忆条数上限（也可在对话里直接说「设成 20 条」） |
+| 标签页显示 | 三态模式（跟随会话 / 始终显示 / 始终隐藏）+ 六个标签逐个勾选；默认跟随会话（后四项偏好均可在对话里调整） |
 | 确认卡语言 | 对话中确认卡的显示语言（中文 / English；平台不向插件暴露界面语言，默认中文） |
 
 ## 开发

package/lib/domain.js

@@ -8,6 +8,7 @@
 import { randomUUID } from 'node:crypto';
 import { domainTable, defineDomain } from '@deepseek-ai/dsh-storage-domain';
 import { z } from 'zod';
+import { TAB_VISIBILITY_DEFAULTS } from './tab-policy.js';
 export const DOMAIN_VERSION = 1;
 /** 教练风格。 */
 export const COACH_STYLES = ['gentle', 'strict', 'humorous'];
@@ -155,12 +156,24 @@ function guardDomain(domain) {
         close: () => domain.close(),
     };
 }
-/** 由已打开领域构造服务句柄（bundle 入口组装用）。 */
-export function makeXingyuanStore(domain, readPrefs) {
+/**
+ * 由已打开领域构造服务句柄（bundle 入口组装用）。
+ *
+ * 后两个参数默认「读缺省 / 写即抛」：单测与探针桩只需领域读写，偏好写入缺席时
+ * 必须响亮失败而不是静默成功——否则「工具说改好了」就没有反证渠道了。
+ */
+export function makeXingyuanStore(domain, readPrefs, readUiPrefs = () => ({
+    tabVisibilityMode: TAB_VISIBILITY_DEFAULTS.tabVisibilityMode,
+    hiddenTabs: [...TAB_VISIBILITY_DEFAULTS.hiddenTabs],
+}), writePrefs = async () => {
+    throw new Error('偏好写入未接线：本服务句柄未绑定宿主 settings 表单');
+}) {
     return {
         spec: xingyuanDomainSpec,
         domain: guardDomain(domain),
         prefs: readPrefs,
+        uiPrefs: readUiPrefs,
+        setPrefs: writePrefs,
         newId: () => randomUUID(),
         checkinKey: (taskId, date) => `${taskId}|${date}`,
     };

package/lib/index.js

@@ -1,7 +1,9 @@
 import z from '@deepseek-ai/schemastery';
 import { storageBackendServiceKey } from '@deepseek-ai/dsh-storage';
 import { makeXingyuanStore, xingyuanDomainSpec } from './domain.js';
+import { SETTINGS_ENTRY_ID } from './pref-policy.js';
 import { PrefSettingsFields, readPrefSettings } from './pref-settings.js';
+import { normalizeHiddenTabs } from './tab-policy.js';
 import { registerXingyuanRoutes } from './routes/index.js';
 import { repairSessionLogs } from './session-log-repair.js';
 import { sweepOrphans } from './consistency-sweep.js';
@@ -48,11 +50,28 @@ export async function apply(ctx, config) {
             await domain.close();
     });
     // 偏好读取 thunk：每次调用现取 volatile 引用的当前值。它由领域服务持有，
-    // preset 层经 ctx.xingyuan.prefs() 读取。偏好挂在常驻主行上，故不存在
+    // preset 层经 ctx.xingyuan.prefs() / .uiPrefs() 读取。偏好挂在常驻主行上，故不存在
     // 「整页可见而数据缺席」的时序问题（来龙去脉见 src/pref-settings.ts 头注）。
     const readPrefs = () => readPrefSettings(config);
-    // 本插件自带「设置 → 星愿」整页，关掉宿主对这一行的自动生成页
-    ctx.inject(['settings'], (inv) => inv.effect(() => inv.settings.configure({ auto: false }, ctx.fiber)));
+    const readUiPrefs = () => ({
+        tabVisibilityMode: config.tabVisibilityMode.get(),
+        hiddenTabs: normalizeHiddenTabs(config.hiddenTabs.get()),
+    });
+    // 本插件自带「设置 → 星愿」整页，关掉宿主对这一行的自动生成页；
+    // 同一处捕获 settings 表单引用供对话侧写偏好使用（ctx.inject 的回调在后续微任务才跑，
+    // 故只能在回调里取值、在调用时判空——异步间隙访问 ctx.* 会命中 inactive context）。
+    let settingsForms;
+    ctx.inject(['settings'], (inv) => {
+        settingsForms = inv.settings;
+        inv.effect(() => inv.settings.configure({ auto: false }, ctx.fiber));
+    });
+    // 偏好唯一写路径：宿主按行 id 把 volatile 字段落到 profile 补丁（与设置页 configForms
+    // 同一个表单实例、同一份存储）。这里不做校验也不承诺成功——调用方须读回比对（§5.8）。
+    const writePrefs = async (patch) => {
+        if (settingsForms === undefined)
+            throw new Error('settings 表单未就绪，无法写入偏好');
+        await settingsForms.update(SETTINGS_ENTRY_ID, patch);
+    };
     // 领域打开后才 provide：注入方（preset 子树）由 cordis inject 语义等待本行
     // 激活完成，早于 provide 的读侧会拿到 undefined
     const opened = await storageDomain.open(xingyuanDomainSpec);
@@ -61,7 +80,7 @@ export async function apply(ctx, config) {
         return;
     }
     domain = opened;
-    ctx.provide('xingyuan', makeXingyuanStore(opened, readPrefs));
+    ctx.provide('xingyuan', makeXingyuanStore(opened, readPrefs, readUiPrefs, writePrefs));
     // 路由注册经 ctx.effect 挂载：register 返回的 disposer 在卸载/HMR 时注销 /xingyuan
     // 前缀——否则重激活会因重复 (kind,path) 抛错，旧 handler 还会服务已关闭的领域
     ctx.effect(() => registerXingyuanRoutes(webServer, ctx.xingyuan, config));

package/lib/preset/prompts.js

@@ -34,8 +34,8 @@ const CAPABILITIES = `# 能力范围
 - 图表统计（内部工具 generate_chart）：打卡趋势、完成率、状态分布、愿望分类、打卡排行、愿望进度、打卡日历等 15 种
 - 成长统计：get_growth_stats 查询等级/经验/连续打卡/达成数量
 - 数据汇总（内部工具 batch_query_user_data）：一次性获取全部愿望/任务数据
-- 用户配置：教练风格、用户画像
-- 定时提醒：一次性提醒（schedule_create）；周期提醒暂不支持，用今日待办概览兜底
+- 用户配置：教练风格、用户画像、偏好读取与调整（写操作确认策略除外，只能用户本人在设置页改）
+- 定时提醒：宿主原生 schedule_* 工具，一次性与周期能力随宿主版本，判定见「定时提醒指南」
 
 ## 界面入口（主动告知用户）
 会话顶部有视图标签页，无需通过对话即可直接查看与操作：
@@ -115,7 +115,7 @@ const PATTERNS = `# 处理模式
 适用场景：用户删除内容（删除任务、删除愿望、删除记忆）
 处理步骤：
 1. 向用户复述要删除的对象（名称+影响范围），不自行询问确认（删除始终由系统弹卡确认）
-2. 执行删除（delete_task/delete_wish/batch_delete_tasks/delete_memory）→ 系统确认卡确认后自动执行
+2. 执行删除（delete_task/delete_wish/batch_delete_tasks/delete_memory/clear_all_memories）→ 系统确认卡确认后自动执行
 3. 确认删除结果，按"标准回复模板-删除"生成回复
 
 示例：
@@ -352,6 +352,7 @@ const MEMORY_GUIDE = `# 记忆操作指南
 - 用户要求修改已保存的信息 → update_memory
 - 用户询问之前提到的信息 → search_memory / get_memory / get_all_memories
 - 用户要求删除已保存的信息 → delete_memory（不可恢复，会弹系统确认）
+- 用户要求把记住的信息**全部**清掉 → clear_all_memories（同样弹确认；先看清条数再动手）
 - 不确定键名时 → search_memory
 
 ## 常用键名参考
@@ -367,10 +368,15 @@ const CONFIG_GUIDE = `# 用户配置指南
 - 用户设置/修改教练风格 → update_coach_style（免确认直接执行）
 - 用户询问画像信息 → get_profile
 - 用户完善画像（昵称/职业/兴趣等） → update_profile（免确认直接执行）
+- 用户问「现在是怎么设置的/注入多少条记忆/标签页只显示星愿吗」 → get_xingyuan_settings
+- 用户要求调整记忆注入条数、确认卡语言、标签页显隐 → update_xingyuan_settings（免确认，只传被点名的项）
+- 用户要求关掉或放宽「写操作二次确认」 → **不代改**：这是安全策略，只能由用户本人在「设置 → 星愿 → 写操作确认」里改，说明入口后停下
 
 ## 注意事项
 - 教练风格（温柔/严格/幽默）影响后续所有回复的语气与措辞，修改后一句话告知用户当前风格
-- 画像信息优先从用户对话中提取，已提供的信息不重复询问`;
+- 画像信息优先从用户对话中提取，已提供的信息不重复询问
+- 偏好改动即时生效、无需重启；回复按工具回包报**实际生效值**，越界或未知取值会被直接拒绝，此时如实转述可选区间而不是猜
+- 用户把标签页全部隐藏后又想找回：入口在「设置 → 星愿 → 标签页显示」（页面上的开关始终可达）`;
 const CHART_GUIDE = `# 图表展示指南（均为内部能力，通过 generate_chart 生成）
 
 ## 选型速查（chartKey 必须精确一致，选错会得到错误图表）
@@ -410,18 +416,20 @@ const CHART_GUIDE = `# 图表展示指南（均为内部能力，通过 generate
 - 图表卡自动渲染；文字回复聚焦结论（趋势/占比/排行）与建议，基于工具返回 subtitle 与数据要点概括，不得只说"已生成图表"`;
 const REMINDER_GUIDE = `# 定时提醒指南
 
-## 能力边界（务必如实告知）
-- 支持**一次性提醒**：原生 schedule_create 工具，参数 prompt（提醒内容）+ at（RFC3339 绝对时间，如 2026-08-25T15:00:00+08:00）
-- **不支持**每天/每周/每月等周期提醒——定时器仅一次性触发且仅在当前会话存活期间送达。
-  用户要周期提醒时，说明限制并引导替代方案：「我会在每次对话开始给你今日待打卡概览，也可以随时问“今天有什么任务”」
+## 能力判定（先看参数，别凭记忆断言）
+提醒走宿主原生 schedule_* 工具，能做什么随宿主版本不同。**动手前看 schedule_create 本次实际接受的参数**：
+- 有 daily / weekly / cron / every_seconds → 周期提醒可以做，直接设（weekly 的 weekdays 用 ISO 序号：周一 1 …… 周日 7；这些参数还各自要本地时刻与时区，时区给 IANA 名如 Asia/Shanghai）
+- 只有 at / after_seconds → 本环境只支持一次性提醒。如实说明并给替代方案：「我会在每次对话开始给你今日待打卡概览，也可以随时问“今天有什么任务”」
+两种情况都只填用户要的**那一种**时间参数；参数表里标了必填的其余字段（如标题）一并填满。
 
 ## 何时使用
-- 「明天下午3点提醒我开会」「10分钟后提醒我喝水」→ schedule_create（prompt 写清提醒正文，at 用绝对时间）
+- 「明天下午3点提醒我开会」「10分钟后提醒我喝水」→ schedule_create（提醒正文写清，绝对时间或「延后多少秒」二选一）
+- 「每天早上9点提醒我打卡」「每周一三五提醒我锻炼」→ 参数支持时按 daily / weekly 设；不支持时退化为一次性提醒，并说明周期做不到
 
 ## 注意事项
-- 口语时间须换算为绝对时间并在复述中明确（如"好的，明天下午3点（2026-08-26 15:00）我会提醒你"）
-- 会话结束后提醒不再触达；跨会话的任务触达依赖今日页与开场概览
-- 查看已设提醒 → schedule_list；取消 → schedule_delete（均为本环境原生工具，ID 取列表真实值）`;
+- 口语时间须换算并在复述里说全（时间、内容、是否重复三样，如"好的，明天下午3点（2026-08-26 15:00）我会提醒你开会"）
+- 提醒的存活范围与送达次数由宿主决定，不得向用户承诺「关掉会话也不会丢」或「一定只送达一次」
+- 查看已设提醒 → schedule_list；取消 → schedule_delete；改时间或正文 → schedule_update（本环境没有该工具时删除后重建）；ID 一律取列表真实值`;
 const STYLE_TONES = {
     gentle: '当前教练风格：温柔型——暖心鼓励为主，肯定每一点进步，建议措辞柔和。',
     strict: '当前教练风格：严格型——直接鞭策、少客套，明确指出拖延与差距，督促立即行动。',

package/lib/preset/tools.js

@@ -4,11 +4,13 @@ import { CATEGORY_COLOR_KEYS } from '../category-color.js';
 import { addDays, calculateOpportunityDates, findFirstUncheckedOpportunityDate, todayIso } from '../opportunity.js';
 import { confirmAction } from './hitl.js';
 import { unclaimedNoteLine } from './prompts.js';
+import { CONFIRM_LANGS, CONFIRM_OPS, MEMORY_LIMIT_MAX, MEMORY_LIMIT_MIN } from '../pref-policy.js';
+import { TAB_IDS, TAB_VISIBILITY_MODES } from '../tab-policy.js';
 import { buildChart, CHART_KEYS } from './charts.js';
 import { growthSummary } from '../growth.js';
 import { MICRO_STEPS_MAX, MICRO_STEPS_MIN, completeMicroStep, restartMicroAction, startMicroAction } from '../micro.js';
 import { removeTaskCompletely, removeWishCompletely } from '../cascade.js';
-import { allMemories, anchorOf, cancelCheckIn, checkinCountIndex, checkedDatesOf, claimTask, createTask, createWish, CYCLE_LABELS, CYCLE_LABELS_EN, deleteMemory, freshTask, freshWish, freshWishes, freshWishesWithTasks, isClaimed, mutateGlobal, performCheckIn, planForDay, planForRange, renameCategory, saveMemory, searchMemories, updateProfileGlobal, updateTask, updateWish, ToolError, validateCategoryName, validateEstimatedDate, validateTaskName, validateWishTitle, } from '../store.js';
+import { allMemories, anchorOf, cancelCheckIn, categoryExists, checkinCountIndex, checkedDatesOf, claimTask, clearMemories, createTask, createWish, CYCLE_LABELS, CYCLE_LABELS_EN, deleteMemory, freshTask, freshWish, freshWishes, freshWishesWithTasks, isClaimed, mutateGlobal, performCheckIn, planForDay, planForRange, renameCategory, saveMemory, searchMemories, setCategoryColor, updateProfileGlobal, updateTask, updateWish, ToolError, validateCategoryName, validateColorKey, validateEstimatedDate, validateTaskName, validateWishTitle, } from '../store.js';
 export const inject = ['tools', 'xingyuan', 'userQuestions'];
 const STATUS_LABELS = {
     pending: '待领取',
@@ -245,6 +247,21 @@ const CANCEL_CHECKIN_NOTE = '无需事先询问用户，直接调用即可；结
 /** 分类颜色白名单（schema enum 与展示色共用同一事实源）。 */
 const COLOR_KEY_ENUM = CATEGORY_COLOR_KEYS;
 const COLOR_KEY_NOTE = `可选值：${CATEGORY_COLOR_KEYS.join('/')}（不传则按分类名自动配色）`;
+/** 确认类目的中文标签（工具回包呈现用；键集由类型系统强制与 CONFIRM_OPS 对齐）。 */
+const CONFIRM_OP_LABELS = {
+    create: '创建',
+    checkin: '打卡',
+    cancelCheckin: '取消打卡',
+    claim: '领取',
+    update: '修改',
+    memorySave: '记忆保存',
+};
+/** 标签页显隐三态的说法（与设置页同口径，回包不出现内部词）。 */
+const TAB_MODE_LABELS = {
+    follow: '仅星愿会话显示',
+    show: '任何会话都显示',
+    hide: '任何会话都不显示',
+};
 /**
  * 写操作确认门闩（分层模型见 AGENTS.md §10 决策 8）：
  * 总开关关闭 → 可配类目一律不弹（一键静音）；开启 → 按类目明细决定。
@@ -559,11 +576,8 @@ export function registerTools(ctx, config) {
         timeoutMs: 600_000,
         async execute(args, exec) {
             // 校验先于确认：分类不存在（无同名愿望且无颜色覆盖）直接报错，不让用户白确认
-            // 一次。存在性 = 愿望 ∪ 覆盖键（覆盖迁移与愿望是否存在解耦，见 store.ts
-            // renameCategory 注释），纯覆盖分类的改名同样合法、如实报告 0 个愿望。
-            const exists = [...store.domain.table('wishes').entries()].some(([, w]) => w.categoryName === args.oldName)
-                || store.domain.global.get().categoryColors?.[args.oldName] !== undefined;
-            if (!exists)
+            // 一次。存在性口径与配色工具共用 store.categoryExists（纯覆盖分类也是合法对象）。
+            if (!categoryExists(store, args.oldName))
                 throw new ToolError(`分类「${args.oldName}」不存在`);
             // 新名口径先于确认：store.renameCategory 逐条落库，非法新名会在中途被写路径闸门
             // 拒掉，留下「部分愿望已改名、颜色覆盖键未迁移」的半改状态且无回滚
@@ -581,6 +595,38 @@ export function registerTools(ctx, config) {
                 : `已将分类「${args.oldName}」改名为「${args.newName}」，该分类下没有愿望。`;
         },
     }));
+    ctx.tools.register(defineTool({
+        name: 'set_wish_category_color',
+        description: '设置分类颜色。何时使用：用户要求给某个愿望分类换颜色（如「把学习分类改成蓝色」），或要求恢复自动配色时调用。与愿望页「分类管理」面板同一写路径：改的是**分类默认色**，该分类下没有单独指定颜色的愿望都会跟着变。分类名不确定时先调 list_wish_categories；色键不确定时先调 list_wish_category_color_keys（22 选 1）。',
+        parameters: {
+            categoryName: { type: 'string', required: true, description: '分类名称，须与现有分类完全一致（区分大小写）。2-6个中文字符' },
+            colorKey: { type: 'string', required: true, description: `颜色标识，取值见 list_wish_category_color_keys（如 blue）。${CLEARABLE_NOTE}示例：blue` },
+        },
+        output: TEXT_OUTPUT,
+        timeoutMs: 600_000,
+        async execute(args, exec) {
+            // 校验与存在性判定都在写之前：分类不存在时不让用户白确认一次，
+            // 非法色键同样先过一遍口径（store 内还会校验，两半侧同源不另写规则）
+            if (!categoryExists(store, args.categoryName))
+                throw new ToolError(`分类「${args.categoryName}」不存在`);
+            if (args.colorKey.trim() !== '')
+                validateColorKey(args.colorKey);
+            if (confirmGate(config, 'update')) {
+                const clearing = args.colorKey.trim() === '';
+                const approved = await confirmAction(ctx, exec, bi(clearing
+                    ? `确定清除分类「${args.categoryName}」的颜色设置，恢复自动配色吗？`
+                    : `确定把分类「${args.categoryName}」的颜色设为「${args.colorKey}」吗？该分类下未单独指定颜色的愿望都会跟着变。`, clearing
+                    ? `Clear the color of category “${args.categoryName}” and fall back to automatic coloring?`
+                    : `Set category “${args.categoryName}” to color “${args.colorKey}”? Wishes in it without an explicit color will follow.`));
+                if (!approved)
+                    return '已取消颜色设置。';
+            }
+            const applied = await setCategoryColor(store, args.categoryName, args.colorKey);
+            return applied === null
+                ? `已清除分类「${args.categoryName}」的颜色设置，恢复自动配色。`
+                : `已把分类「${args.categoryName}」的颜色设为 ${applied}。`;
+        },
+    }));
     ctx.tools.register(defineTool({
         name: 'delete_wish',
         description: `删除愿望。何时使用：删除单个愿望及其关联的所有任务时调用，适用于愿望已完成、取消或误创建的场景。${DELETE_NOTE}回复时向用户说明影响范围。`,
@@ -1221,6 +1267,24 @@ export function registerTools(ctx, config) {
             return `已删除：「${args.key}」`;
         },
     }));
+    ctx.tools.register(defineTool({
+        name: 'clear_all_memories',
+        description: `【清空全部用户信息】使用场景：用户明确要求把已保存的记忆**全部**删掉（如"把你记住我的都删了""清空记忆"）时使用。只删单条请改用 delete_memory。${DELETE_NOTE}条数不确定时先用 get_all_memories 看一眼。`,
+        parameters: {},
+        output: TEXT_OUTPUT,
+        timeoutMs: 600_000,
+        async execute(_args, exec) {
+            const count = allMemories(store).length;
+            if (count === 0)
+                return '当前没有已保存的信息，无需清空。';
+            // 删除类目为锁定项：不受 confirmWrites / confirmOps 影响，始终确认（ADR-0001）
+            const approved = await confirmAction(ctx, exec, bi(`确定清空全部 ${count} 条已保存的信息吗？清空后不可恢复，之后我只能重新认识你。`, `Clear all ${count} saved memories? This cannot be undone — I'll have to learn about you again.`));
+            if (!approved)
+                return '已取消清空。';
+            const cleared = await clearMemories(store);
+            return `已清空 ${cleared} 条信息。`;
+        },
+    }));
     // ===== 用户配置（教练风格/画像，免确认）=====
     ctx.tools.register(defineTool({
         name: 'get_coach_config',
@@ -1281,6 +1345,91 @@ export function registerTools(ctx, config) {
             return '已更新用户画像。';
         },
     }));
+    ctx.tools.register(defineTool({
+        name: 'get_xingyuan_settings',
+        description: '读取星愿偏好设置。何时使用：用户问「现在是怎么设置的」「记忆注入多少条」「确认卡是中文还是英文」「标签页是不是只在星愿会话显示」，或在改设置前要先看当前值时使用。返回写操作确认策略（只读）、记忆注入上限、确认卡语言与标签页显隐。',
+        parameters: {},
+        output: TEXT_OUTPUT,
+        isConcurrencySafe: () => true,
+        async execute() {
+            const prefs = store.prefs();
+            const ui = store.uiPrefs();
+            const on = CONFIRM_OPS.filter((key) => prefs.confirmOps[key]).map((key) => CONFIRM_OP_LABELS[key]);
+            return [
+                `写操作确认：${prefs.confirmWrites ? '开' : '关（仅删除类仍始终确认）'}`,
+                prefs.confirmWrites ? `　需确认的类目：${on.length > 0 ? on.join('、') : '无'}` : undefined,
+                `　删除（愿望/任务/记忆、含批量与清空）：始终确认，不可关闭`,
+                `记忆注入上限：${prefs.memoryInjectLimit} 条`,
+                `确认卡语言：${prefs.confirmLang}`,
+                `标签页显示：${TAB_MODE_LABELS[ui.tabVisibilityMode]}${ui.hiddenTabs.length > 0 ? `；已勾掉：${ui.hiddenTabs.join('、')}` : ''}`,
+            ].filter((line) => line !== undefined).join('\n');
+        },
+    }));
+    ctx.tools.register(defineTool({
+        name: 'update_xingyuan_settings',
+        description: '修改星愿偏好设置（部分更新：只传用户明确提到的项，未提及不传）。可改四项：memoryInjectLimit（记忆注入条数上限）、confirmLang（对话确认卡语言）、tabVisibilityMode（会话视图标签页显隐）、hiddenTabs（勾掉哪几页）。**写操作确认策略 confirmWrites / confirmOps 不在其中**——那是放宽安全策略，只能由用户本人在「设置 → 星愿」里改，本工具不接受也不提供绕过。何时使用：用户明确要求调整上述偏好（如「以后注入的记忆少一点，设成 20 条」「标签页一直显示」）。改完把新值如实回给用户。',
+        parameters: {
+            memoryInjectLimit: { type: 'integer', description: `每次对话自动注入上下文的记忆条数，${MEMORY_LIMIT_MIN}-${MEMORY_LIMIT_MAX} 的整数。越界直接拒绝、不会静默夹取，请如实告知用户可填区间` },
+            confirmLang: { type: 'string', enum: CONFIRM_LANGS, description: '对话内确认卡的语言：zh 中文 / en 英文。宿主不向插件暴露界面语言，此项独立选择' },
+            tabVisibilityMode: { type: 'string', enum: TAB_VISIBILITY_MODES, description: '会话视图标签页显隐：follow 仅星愿预设的会话显示（默认）/ show 任何会话都显示 / hide 任何会话都不显示' },
+            hiddenTabs: { type: 'array', items: { type: 'string' }, description: `在「显示」前提下被单独勾掉的标签 id，取值 ${TAB_IDS.join(' / ')}；传空数组表示六页全显示，不传则保持现状。未知 id 直接拒绝。注意 hide 或勾掉当前正看着的页面时，界面会自动回到 Chat，需在回复里提示用户` },
+        },
+        output: TEXT_OUTPUT,
+        async execute(args) {
+            const patch = {};
+            if (args.memoryInjectLimit !== undefined) {
+                const limit = args.memoryInjectLimit;
+                if (limit < MEMORY_LIMIT_MIN || limit > MEMORY_LIMIT_MAX) {
+                    throw new ToolError(`记忆注入上限须为 ${MEMORY_LIMIT_MIN}-${MEMORY_LIMIT_MAX} 的整数（收到 ${limit}）`, 'bad_memory_limit', { limit });
+                }
+                patch.memoryInjectLimit = limit;
+            }
+            if (args.confirmLang !== undefined)
+                patch.confirmLang = args.confirmLang;
+            if (args.tabVisibilityMode !== undefined)
+                patch.tabVisibilityMode = args.tabVisibilityMode;
+            if (args.hiddenTabs !== undefined) {
+                const unknown = args.hiddenTabs.filter((tab) => !TAB_IDS.includes(tab));
+                if (unknown.length > 0) {
+                    throw new ToolError(`未知标签 id：${unknown.join('、')}；可选值为 ${TAB_IDS.join(' / ')}`, 'unknown_tab', { tabs: unknown });
+                }
+                patch.hiddenTabs = args.hiddenTabs;
+            }
+            if (Object.keys(patch).length === 0) {
+                throw new ToolError('没有要修改的偏好项：至少传一个字段（可先调 get_xingyuan_settings 看当前值）', 'missing_field');
+            }
+            await store.setPrefs(patch);
+            // 写后读回比对：宿主可能拒绝（行缺席 / 字段非 volatile / 表单不可写），
+            // 而「工具说改好了、实际没改」是比报错更糟的结果
+            const prefs = store.prefs();
+            const ui = store.uiPrefs();
+            const mismatch = [];
+            if (patch.memoryInjectLimit !== undefined && prefs.memoryInjectLimit !== patch.memoryInjectLimit) {
+                mismatch.push(`memoryInjectLimit=${prefs.memoryInjectLimit}`);
+            }
+            if (patch.confirmLang !== undefined && prefs.confirmLang !== patch.confirmLang) {
+                mismatch.push(`confirmLang=${prefs.confirmLang}`);
+            }
+            if (patch.tabVisibilityMode !== undefined && ui.tabVisibilityMode !== patch.tabVisibilityMode) {
+                mismatch.push(`tabVisibilityMode=${ui.tabVisibilityMode}`);
+            }
+            if (patch.hiddenTabs !== undefined) {
+                const wanted = [...new Set(patch.hiddenTabs)].sort().join(',');
+                if (ui.hiddenTabs.slice().sort().join(',') !== wanted)
+                    mismatch.push(`hiddenTabs=${ui.hiddenTabs.join(',')}`);
+            }
+            if (mismatch.length > 0) {
+                throw new ToolError(`偏好写入未被宿主接受，当前值未变（${mismatch.join('；')}）。请到「设置 → 星愿」检查该行是否可写`, 'pref_write_rejected', { mismatch });
+            }
+            return [
+                patch.memoryInjectLimit !== undefined ? `记忆注入上限：${prefs.memoryInjectLimit} 条` : undefined,
+                patch.confirmLang !== undefined ? `确认卡语言：${prefs.confirmLang}` : undefined,
+                patch.tabVisibilityMode !== undefined || patch.hiddenTabs !== undefined
+                    ? `标签页显示：${TAB_MODE_LABELS[ui.tabVisibilityMode]}${ui.hiddenTabs.length > 0 ? `；已勾掉：${ui.hiddenTabs.join('、')}` : ''}`
+                    : undefined,
+            ].filter((line) => line !== undefined).join('；') + '。（已生效，无需重启）';
+        },
+    }));
     // ===== 图表（内部）=====
     ctx.tools.register(defineTool({
         name: 'generate_chart',
@@ -1457,7 +1606,7 @@ export function registerTools(ctx, config) {
             const done = result.state.steps.filter((s) => s.completed).length;
             const skipped = result.state.steps.filter((s) => s.skipped).length;
             if (result.finished) {
-                return `「${task.name}」微行动全部完成（完成 ${done} 步、跳过 ${skipped} 步）🎉 计划走完了——现在可以打卡这个任务，告诉我或去「今日」页点打卡都行。`;
+                return `「${task.name}」微行动全部完成（完成 ${done} 步、跳过 ${skipped} 步）。\n🎉 计划走完了——现在可以打卡这个任务，告诉我或去「今日」页点打卡都行。`;
             }
             const next = result.state.steps.find((s) => s.stepNumber === result.state.currentStepNumber);
             return `第 ${args.stepNumber} 步已${args.action === 'complete' ? '完成 ✓' : '跳过 ↷'}（${done}/${result.state.steps.length} 完成）。下一步 第 ${result.state.currentStepNumber} 步：${next?.instruction ?? ''}`;

package/lib/routes/api.js

@@ -1,8 +1,7 @@
-import { allMemories, anchorOf, checkedDatesOf, checkinCountIndex, clearMemories, createTask, createWish, cancelCheckIn, claimTask, deleteMemory, freshTask, freshWish, freshWishes, isClaimed, monthRange, performCheckIn, planForDay, planForRange, renameCategory, saveMemory, searchMemories, updateProfileGlobal, updateTask, validateCategoryName, validateColorKey, } from '../store.js';
+import { allMemories, anchorOf, checkedDatesOf, checkinCountIndex, clearMemories, createTask, createWish, cancelCheckIn, claimTask, deleteMemory, freshTask, freshWish, freshWishes, isClaimed, monthRange, performCheckIn, planForDay, planForRange, renameCategory, saveMemory, searchMemories, setCategoryColor, updateProfileGlobal, updateTask, validateCategoryName, } from '../store.js';
 import { addDays, calculateOpportunityDates, findFirstUncheckedOpportunityDate, isIsoDate, todayIso } from '../opportunity.js';
 import { LEVEL_CONFIGS, growthSummary } from '../growth.js';
 import { getMicroAction } from '../micro.js';
-import { mutateGlobal } from '../store.js';
 import { removeTaskCompletely, removeWishCompletely } from '../cascade.js';
 import { ActionError, HttpError } from './errors.js';
 const MEMORY_CATEGORIES = ['personal', 'preference', 'habit', 'event', 'other'];
@@ -531,17 +530,6 @@ async function actionUpdateTask(deps, body) {
     return { ok: true, task: taskView(store, task) };
 }
 // ===== 分类管理 =====
-async function setCategoryOverride(deps, name, colorKey) {
-    // 读-改-写整体进串行队列：并发改不同分类颜色互不覆盖
-    await mutateGlobal(deps.store, (global) => {
-        const overrides = { ...(global.categoryColors ?? {}) };
-        if (colorKey === null)
-            delete overrides[name];
-        else
-            overrides[name] = colorKey;
-        return { ...global, categoryColors: Object.keys(overrides).length > 0 ? overrides : undefined };
-    });
-}
 async function actionCategoryRename(deps, body) {
     requireFields(body, ['oldName', 'newName']);
     const oldName = clampStr(body.oldName, 6);
@@ -554,10 +542,9 @@ async function actionCategoryRename(deps, body) {
 }
 async function actionCategoryColor(deps, body) {
     requireFields(body, ['name']);
-    const name = clampStr(body.name, 6);
-    // colorKey 为空串 = 清除覆盖（跟随愿望显式色/哈希兜底）
-    const rawColor = typeof body.colorKey === 'string' && body.colorKey !== '' ? validateColorKey(body.colorKey) : null;
-    const colorKey = rawColor ?? null;
-    await setCategoryOverride(deps, name, colorKey);
-    return { ok: true, name, colorKey };
+    const rawColor = typeof body.colorKey === 'string' ? body.colorKey : null;
+    // 与对话侧 set_wish_category_color 同一写路径（store 收口）：空白色键 = 清除覆盖，
+    // 分类名与色键的校验也在那一处，两半侧不再各写一份口径
+    const colorKey = await setCategoryColor(deps.store, clampStr(body.name, 6), rawColor);
+    return { ok: true, name: clampStr(body.name, 6), colorKey };
 }

package/lib/store.js

@@ -655,7 +655,39 @@ export async function renameCategory(store, oldName, newName) {
     });
     return renamed;
 }
-/** 记忆全量（新→旧）。 */
+/**
+ * 分类是否存在：同名愿望 ∪ 颜色覆盖键。改名与配色两条路径共用这一口径——
+ * 「零愿望但设过色」的纯覆盖分类在页面分类面板里是合法对象，工具面不得当它不存在。
+ */
+export function categoryExists(store, name) {
+    for (const [, wish] of store.domain.table('wishes').entries()) {
+        if (wish.categoryName === name)
+            return true;
+    }
+    return store.domain.global.get().categoryColors?.[name] !== undefined;
+}
+/**
+ * 设置或清除分类颜色覆盖（页面 `category-color` 动作与 `set_wish_category_color`
+ * 工具的唯一写路径）。`colorKey` 为 null 或空白 = 清除覆盖，恢复跟随愿望显式色/哈希兜底。
+ * 分类名与色键都在此处过一遍口径：页面历史上靠 clamp 兜着，空串会写出一个键为 ''
+ * 的幽灵覆盖，从此在分类面板里阴魂不散。读-改-写整体进串行队列，并发改不同分类互不覆盖。
+ *
+ * @returns 生效的色键（null = 已清除），供调用方如实回显。
+ */
+export async function setCategoryColor(store, name, colorKey) {
+    const category = validateCategoryName(name);
+    const trimmed = colorKey?.trim() ?? '';
+    const color = trimmed === '' ? null : validateColorKey(trimmed);
+    await mutateGlobal(store, (global) => {
+        const overrides = { ...(global.categoryColors ?? {}) };
+        if (color === null)
+            delete overrides[category];
+        else
+            overrides[category] = color;
+        return { ...global, categoryColors: Object.keys(overrides).length > 0 ? overrides : undefined };
+    });
+    return color;
+}
 export function allMemories(store) {
     const list = [];
     for (const [, memory] of store.domain.table('memories').entries())

package/lib/tab-policy.js

@@ -12,6 +12,8 @@
  */
 /** 六个会话视图标签的稳定业务名（与 slot entry id 的 xy- 前缀解耦，配置文件里可读）。 */
 export const TAB_IDS = ['today', 'wishes', 'tasks', 'calendar', 'growth', 'memory'];
+/** 显隐模式取值（主行 Config 的 schema 枚举、设置页选项与工具参数三方同源）。 */
+export const TAB_VISIBILITY_MODES = ['follow', 'show', 'hide'];
 /**
  * 星愿 preset 身份：宿主会话投影值 `agentPreset` 的取值，与 bundle 补丁里
  * `preset-xingyuan` 声明行的 `config.id` 是同一串纯字符串（对拍见 test/preset-declaration.test.ts）。

package/lib/types/domain.d.ts

@@ -1,6 +1,6 @@
 import { type Domain, type DomainTableSpec } from '@deepseek-ai/dsh-storage-domain';
 import { z } from 'zod';
-import type { PrefSettings } from './pref-policy.js';
+import type { PrefPatch, PrefSettings, UiSettings } from './pref-policy.js';
 export declare const DOMAIN_VERSION = 1;
 /** 教练风格。 */
 export declare const COACH_STYLES: readonly ["gentle", "strict", "humorous"];
@@ -101,6 +101,15 @@ export interface XingyuanStore {
     readonly domain: Domain<typeof xingyuanDomainSpec>;
     /** 对话偏好：bundle 主行 volatile Config 的当前解析值（非领域数据），每次调用现取。 */
     prefs(): PrefSettings;
+    /** 界面偏好（标签页显隐）的当前解析值，同样每次现取。 */
+    uiPrefs(): UiSettings;
+    /**
+     * 偏好写入的唯一路径（bundle 主行经宿主 settings 表单落到 profile 补丁）。
+     * 调用方（对话工具）负责参数校验；本方法只负责落盘，**不承诺成功**——
+     * 宿主可能拒绝（行缺席 / 非 volatile 字段 / 无写权限），调用方须再读
+     * {@link prefs} / {@link uiPrefs} 比对，未生效即如实报错，不得静默当作改成了。
+     */
+    setPrefs(patch: PrefPatch): Promise<void>;
     newId(): string;
     checkinKey(taskId: string, date: string): string;
 }
@@ -119,6 +128,11 @@ export declare class RecordInvalidError extends Error {
     readonly code = "invalid_record";
     constructor(message: string);
 }
-/** 由已打开领域构造服务句柄（bundle 入口组装用）。 */
-export declare function makeXingyuanStore(domain: Domain<typeof xingyuanDomainSpec>, readPrefs: () => PrefSettings): XingyuanStore;
+/**
+ * 由已打开领域构造服务句柄（bundle 入口组装用）。
+ *
+ * 后两个参数默认「读缺省 / 写即抛」：单测与探针桩只需领域读写，偏好写入缺席时
+ * 必须响亮失败而不是静默成功——否则「工具说改好了」就没有反证渠道了。
+ */
+export declare function makeXingyuanStore(domain: Domain<typeof xingyuanDomainSpec>, readPrefs: () => PrefSettings, readUiPrefs?: () => UiSettings, writePrefs?: (patch: PrefPatch) => Promise<void>): XingyuanStore;
 export {};

package/lib/types/pref-policy.d.ts

@@ -20,7 +20,7 @@
  *   locale 服务是浏览器专属 seam，工具执行期读不到；故确认卡语言只能由用户在此
  *   显式选择，不能自动跟随界面语言。
  */
-import type { TabVisibilityMode } from './tab-policy.js';
+import type { TabId, TabVisibilityMode } from './tab-policy.js';
 /**
  * 偏好落在哪一条 profile 行上：dsh 0.1.7 起「可编辑设置 = 该行的 Config schema 里
  * 标了 `.volatile()` 的字段」，客户端经 `ctx.configForms.get(SETTINGS_ENTRY_ID)` 读写，
@@ -81,6 +81,29 @@ export interface PrefSettings {
 export declare const PREF_DEFAULTS: PrefSettings;
 /** 脏值容错：非 zh/en 一律回落 zh（与 tab-policy 的显隐脏值容错同口径）。 */
 export declare function normalizeConfirmLang(value: unknown): ConfirmLang;
+/**
+ * 界面偏好的当前解析值（标签页显隐）。与 {@link PrefSettings} 同挂主行 volatile 字段，
+ * 分两组只为让「对话侧读什么」在类型上如实；脏值收敛走 tab-policy.normalizeHiddenTabs。
+ */
+export interface UiSettings {
+    /** 三态：follow 仅星愿会话显示 / show 所有会话显示 / hide 全部隐藏。 */
+    tabVisibilityMode: TabVisibilityMode;
+    /** 在「显示」前提下被勾掉的单个标签（空 = 六个全显示）。 */
+    hiddenTabs: TabId[];
+}
+/**
+ * 偏好写入的合法载荷（对话 + 界面两组里**可由对话侧发起**的那几项）。
+ *
+ * 刻意不含 `confirmWrites` / `confirmOps`：它们是「放宽安全策略」的开关，按宿主官方
+ * 实践（dsh-agent-preset skills/references/user-actions.md：授予或确认权限的动作保持
+ * 用户专属）只能由用户在设置页亲自改，工具面不接受、也不提供绕过路径。
+ */
+export interface PrefPatch {
+    memoryInjectLimit?: number;
+    confirmLang?: ConfirmLang;
+    tabVisibilityMode?: TabVisibilityMode;
+    hiddenTabs?: readonly string[];
+}
 /**
  * 解析「记忆注入上限」输入：非整数、非数字、空串一律返回 undefined（拒绝）；
  * 越界值夹取到 [MIN,MAX] 且 clamped 置 true（调用方据此给出行内提示并回显）。

package/lib/types/preset/prompts.d.ts

@@ -1,7 +1,7 @@
 /**
  * 提示词移植：PromptTemplateManager 全量段落 → dsh systemPrompt 分节注册。
  * 渠道适配：无微信版（Web 图表卡自动渲染）；emitUiCardsBlock 移除（工具成功即发事件）；
- * 提醒指南按 harness schedule 能力如实改写（仅一次性）。
+ * 提醒指南对宿主能力保持中立（宿主 schedule 的一次性/周期口径随版本变，判定交给工具参数）。
  */
 import type { Context } from '@deepseek-ai/cordis';
 import type { XingyuanStore } from '../domain.js';

package/lib/types/preset/tools.d.ts

@@ -7,8 +7,8 @@
  * - 写确认：总开关（confirmWrites）开启时按类目明细（confirmOps）弹卡——创建/打卡/取消打卡
  *   默认确认，领取/修改/记忆保存默认免确认但可在设置开启；删除（含批量）始终确认；教练风格与画像免确认；
  * - 业务事实：写操作成功即发 xingyuan/* 会话事件驱动卡片（可回放）；
- * - 周期提醒：harness schedule 仅一次性触发，原生 schedule_create 直接可用，
- *   差异在提示词指南中如实告知，不另造包装工具。
+ * - 提醒：不自造包装工具，直接用宿主原生 schedule_*；其能力随宿主版本而不同，
+ *   判定与如实告知的口径集中在提示词的「定时提醒指南」，本层不断言能力边界。
  */
 import type { Context } from '@deepseek-ai/cordis';
 import type { XingyuanStore } from '../domain.js';

package/lib/types/store.d.ts

@@ -162,7 +162,20 @@ export declare function planForDay(store: XingyuanStore, date: string): DayPlan;
  * （分类管理面板允许存在零愿望的纯覆盖分类）。
  */
 export declare function renameCategory(store: XingyuanStore, oldName: string, newName: string): Promise<Wish[]>;
-/** 记忆全量（新→旧）。 */
+/**
+ * 分类是否存在：同名愿望 ∪ 颜色覆盖键。改名与配色两条路径共用这一口径——
+ * 「零愿望但设过色」的纯覆盖分类在页面分类面板里是合法对象，工具面不得当它不存在。
+ */
+export declare function categoryExists(store: XingyuanStore, name: string): boolean;
+/**
+ * 设置或清除分类颜色覆盖（页面 `category-color` 动作与 `set_wish_category_color`
+ * 工具的唯一写路径）。`colorKey` 为 null 或空白 = 清除覆盖，恢复跟随愿望显式色/哈希兜底。
+ * 分类名与色键都在此处过一遍口径：页面历史上靠 clamp 兜着，空串会写出一个键为 ''
+ * 的幽灵覆盖，从此在分类面板里阴魂不散。读-改-写整体进串行队列，并发改不同分类互不覆盖。
+ *
+ * @returns 生效的色键（null = 已清除），供调用方如实回显。
+ */
+export declare function setCategoryColor(store: XingyuanStore, name: string, colorKey: string | null): Promise<string | null>;
 export declare function allMemories(store: XingyuanStore): MemoryRecord[];
 /** 记忆存取。 */
 export declare function saveMemory(store: XingyuanStore, key: string, value: string, category: MemoryRecord['category'], importance: MemoryRecord['importance']): Promise<void>;

package/lib/types/tab-policy.d.ts

@@ -13,8 +13,10 @@
 /** 六个会话视图标签的稳定业务名（与 slot entry id 的 xy- 前缀解耦，配置文件里可读）。 */
 export declare const TAB_IDS: readonly ["today", "wishes", "tasks", "calendar", "growth", "memory"];
 export type TabId = (typeof TAB_IDS)[number];
+/** 显隐模式取值（主行 Config 的 schema 枚举、设置页选项与工具参数三方同源）。 */
+export declare const TAB_VISIBILITY_MODES: readonly ["follow", "show", "hide"];
 /** 显隐模式：跟随会话 / 始终显示 / 始终隐藏。 */
-export type TabVisibilityMode = 'follow' | 'show' | 'hide';
+export type TabVisibilityMode = typeof TAB_VISIBILITY_MODES[number];
 /**
  * 会话列表快照里星愿要读的最小事实面——按「本插件用到什么」收窄，不是宿主类型的复刻：
  * 宿主增删其它字段都不影响本视图，代价是**我们读的字段被撤除时编译期不会报错**

package/lib/types/ui-settings.d.ts

@@ -13,8 +13,8 @@
  */
 import z from '@deepseek-ai/schemastery';
 /**
- * 界面偏好字段表。schemastery 无 z.enum，枚举用 const+union 表达；
- * 默认值与 tab-policy 的 TAB_VISIBILITY_DEFAULTS 同源（测试对拍）。
+ * 界面偏好字段表。schemastery 无 z.enum，枚举用 const+union 表达（与 pref-settings
+ * 的 confirmLang 同形）；默认值与 tab-policy 的 TAB_VISIBILITY_DEFAULTS 同源（测试对拍）。
  */
 export declare const UiSettingsFields: {
     /** 显隐三态：follow 星愿会话才显示 / show 任何会话都显示 / hide 任何会话不显示。 */

package/lib/ui-settings.js

@@ -12,18 +12,15 @@
  * 它们出现在 host Config 里只是为了让宿主把它们投影成表单。
  */
 import z from '@deepseek-ai/schemastery';
-import { TAB_VISIBILITY_DEFAULTS } from './tab-policy.js';
+import { TAB_VISIBILITY_DEFAULTS, TAB_VISIBILITY_MODES } from './tab-policy.js';
 /**
- * 界面偏好字段表。schemastery 无 z.enum，枚举用 const+union 表达；
- * 默认值与 tab-policy 的 TAB_VISIBILITY_DEFAULTS 同源（测试对拍）。
+ * 界面偏好字段表。schemastery 无 z.enum，枚举用 const+union 表达（与 pref-settings
+ * 的 confirmLang 同形）；默认值与 tab-policy 的 TAB_VISIBILITY_DEFAULTS 同源（测试对拍）。
  */
 export const UiSettingsFields = {
     /** 显隐三态：follow 星愿会话才显示 / show 任何会话都显示 / hide 任何会话不显示。 */
-    tabVisibilityMode: z.union([
-        z.const('follow'),
-        z.const('show'),
-        z.const('hide'),
-    ]).default(TAB_VISIBILITY_DEFAULTS.tabVisibilityMode).volatile(),
+    tabVisibilityMode: z.union(TAB_VISIBILITY_MODES.map((mode) => z.const(mode)))
+        .default(TAB_VISIBILITY_DEFAULTS.tabVisibilityMode).volatile(),
     /**
      * 在「显示」前提下被勾掉的单个标签（空数组 = 六个全显示；脏值容错忽略）。
      *

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@starwish-ai/xingyuan-dsh",
-  "version": "0.6.5",
+  "version": "0.6.7",
   "description": "星愿 XingYuan for DeepSeek Harness: 对话创建愿望/任务、机会日打卡、微行动、记忆与图表的 Agent Preset 组合包",
   "type": "module",
   "license": "MIT",
@@ -97,22 +97,22 @@
   },
   "peerDependencies": {
     "@deepseek-ai/cordis": "^4.0.4",
-    "@deepseek-ai/dsh-agent-preset": "^0.1.7-rc.1",
-    "@deepseek-ai/dsh-api-session-controller": "^0.1.7-rc.1",
-    "@deepseek-ai/dsh-client-locale": "^0.1.7-rc.1",
-    "@deepseek-ai/dsh-client-ui-chat": "^0.1.7-rc.1",
-    "@deepseek-ai/dsh-client-ui-conversation": "^0.1.7-rc.1",
-    "@deepseek-ai/dsh-client-ui-settings": "^0.1.7-rc.1",
-    "@deepseek-ai/dsh-client-ui-settings-plugins": "^0.1.7-rc.1",
-    "@deepseek-ai/dsh-host-webserver": "^0.1.7-rc.1",
-    "@deepseek-ai/dsh-schedule": "^0.1.7-rc.1",
-    "@deepseek-ai/dsh-session": "^0.1.7-rc.1",
-    "@deepseek-ai/dsh-settings": "^0.1.7-rc.1",
-    "@deepseek-ai/dsh-storage": "^0.1.7-rc.1",
-    "@deepseek-ai/dsh-storage-domain": "^0.1.7-rc.1",
-    "@deepseek-ai/dsh-system-prompt": "^0.1.7-rc.1",
-    "@deepseek-ai/dsh-tools": "^0.1.7-rc.1",
-    "@deepseek-ai/dsh-user-questions": "^0.1.7-rc.1",
+    "@deepseek-ai/dsh-agent-preset": "^0.1.7-rc.1 || ^0.2.0-rc.1",
+    "@deepseek-ai/dsh-api-session-controller": "^0.1.7-rc.1 || ^0.2.0-rc.1",
+    "@deepseek-ai/dsh-client-locale": "^0.1.7-rc.1 || ^0.2.0-rc.1",
+    "@deepseek-ai/dsh-client-ui-chat": "^0.1.7-rc.1 || ^0.2.0-rc.1",
+    "@deepseek-ai/dsh-client-ui-conversation": "^0.1.7-rc.1 || ^0.2.0-rc.1",
+    "@deepseek-ai/dsh-client-ui-settings": "^0.1.7-rc.1 || ^0.2.0-rc.1",
+    "@deepseek-ai/dsh-client-ui-settings-plugins": "^0.1.7-rc.1 || ^0.2.0-rc.1",
+    "@deepseek-ai/dsh-host-webserver": "^0.1.7-rc.1 || ^0.2.0-rc.1",
+    "@deepseek-ai/dsh-schedule": "^0.1.7-rc.1 || ^0.2.0-rc.1",
+    "@deepseek-ai/dsh-session": "^0.1.7-rc.1 || ^0.2.0-rc.1",
+    "@deepseek-ai/dsh-settings": "^0.1.7-rc.1 || ^0.2.0-rc.1",
+    "@deepseek-ai/dsh-storage": "^0.1.7-rc.1 || ^0.2.0-rc.1",
+    "@deepseek-ai/dsh-storage-domain": "^0.1.7-rc.1 || ^0.2.0-rc.1",
+    "@deepseek-ai/dsh-system-prompt": "^0.1.7-rc.1 || ^0.2.0-rc.1",
+    "@deepseek-ai/dsh-tools": "^0.1.7-rc.1 || ^0.2.0-rc.1",
+    "@deepseek-ai/dsh-user-questions": "^0.1.7-rc.1 || ^0.2.0-rc.1",
     "@deepseek-ai/schemastery": "*",
     "react": "^18.2.0",
     "zod": "^4.4.3"
@@ -150,30 +150,30 @@
     "@deepseek-ai/cordis": "4.0.4",
     "@deepseek-ai/cordis-plugin-include": "1.0.9",
     "@deepseek-ai/cordis-plugin-loader": "1.0.5",
-    "@deepseek-ai/dsh-agent": "0.1.7-rc.1",
-    "@deepseek-ai/dsh-agent-preset": "0.1.7-rc.1",
-    "@deepseek-ai/dsh-api-remotes": "0.1.7-rc.1",
-    "@deepseek-ai/dsh-api-session-controller": "0.1.7-rc.1",
-    "@deepseek-ai/dsh-attachment": "0.1.7-rc.1",
-    "@deepseek-ai/dsh-client-locale": "0.1.7-rc.1",
-    "@deepseek-ai/dsh-client-store": "0.1.7-rc.1",
-    "@deepseek-ai/dsh-client-ui-chat": "0.1.7-rc.1",
-    "@deepseek-ai/dsh-client-ui-conversation": "0.1.7-rc.1",
-    "@deepseek-ai/dsh-client-ui-renderer": "0.1.7-rc.1",
-    "@deepseek-ai/dsh-client-ui-settings": "0.1.7-rc.1",
-    "@deepseek-ai/dsh-client-ui-settings-plugins": "0.1.7-rc.1",
-    "@deepseek-ai/dsh-client-ui-slots": "0.1.7-rc.1",
-    "@deepseek-ai/dsh-host-webserver": "0.1.7-rc.1",
-    "@deepseek-ai/dsh-llm": "0.1.7-rc.1",
-    "@deepseek-ai/dsh-schedule": "0.1.7-rc.1",
-    "@deepseek-ai/dsh-session": "0.1.7-rc.1",
-    "@deepseek-ai/dsh-session-format-catalog": "0.1.7-rc.1",
-    "@deepseek-ai/dsh-settings": "0.1.7-rc.1",
-    "@deepseek-ai/dsh-storage": "0.1.7-rc.1",
-    "@deepseek-ai/dsh-storage-domain": "0.1.7-rc.1",
-    "@deepseek-ai/dsh-system-prompt": "0.1.7-rc.1",
-    "@deepseek-ai/dsh-tools": "0.1.7-rc.1",
-    "@deepseek-ai/dsh-user-questions": "0.1.7-rc.1",
+    "@deepseek-ai/dsh-agent": "0.2.0-rc.1",
+    "@deepseek-ai/dsh-agent-preset": "0.2.0-rc.1",
+    "@deepseek-ai/dsh-api-remotes": "0.2.0-rc.1",
+    "@deepseek-ai/dsh-api-session-controller": "0.2.0-rc.1",
+    "@deepseek-ai/dsh-attachment": "0.2.0-rc.1",
+    "@deepseek-ai/dsh-client-locale": "0.2.0-rc.1",
+    "@deepseek-ai/dsh-client-store": "0.2.0-rc.1",
+    "@deepseek-ai/dsh-client-ui-chat": "0.2.0-rc.1",
+    "@deepseek-ai/dsh-client-ui-conversation": "0.2.0-rc.1",
+    "@deepseek-ai/dsh-client-ui-renderer": "0.2.0-rc.1",
+    "@deepseek-ai/dsh-client-ui-settings": "0.2.0-rc.1",
+    "@deepseek-ai/dsh-client-ui-settings-plugins": "0.2.0-rc.1",
+    "@deepseek-ai/dsh-client-ui-slots": "0.2.0-rc.1",
+    "@deepseek-ai/dsh-host-webserver": "0.2.0-rc.1",
+    "@deepseek-ai/dsh-llm": "0.2.0-rc.1",
+    "@deepseek-ai/dsh-schedule": "0.2.0-rc.1",
+    "@deepseek-ai/dsh-session": "0.2.0-rc.1",
+    "@deepseek-ai/dsh-session-format-catalog": "0.2.0-rc.1",
+    "@deepseek-ai/dsh-settings": "0.2.0-rc.1",
+    "@deepseek-ai/dsh-storage": "0.2.0-rc.1",
+    "@deepseek-ai/dsh-storage-domain": "0.2.0-rc.1",
+    "@deepseek-ai/dsh-system-prompt": "0.2.0-rc.1",
+    "@deepseek-ai/dsh-tools": "0.2.0-rc.1",
+    "@deepseek-ai/dsh-user-questions": "0.2.0-rc.1",
     "@deepseek-ai/schemastery": "3.18.4",
     "@types/js-yaml": "^4.0.9",
     "@types/node": "^24.0.0",