dsh-global-todo 0.13.1 → 0.14.0

package/CHANGELOG.md

@@ -1,3 +1,40 @@
+## [0.14.0] — 2026-10-22
+
+Choose how much surface a deployment pays for.
+
+- **`config.toolGroups`: `all` (10 tools, default), `core` (6 — the list itself) or `none`.**
+  The ten tool schemas cost about **2k tokens per turn**; a deployment that only wants the panel
+  should not pay for a collaboration surface it never asks an agent to use. An unrecognised value
+  is reported and treated as `all`, so a typo cannot silently remove tools.
+- **The guidance section follows the tools.** With `core`/`none` the model is no longer told to
+  call `global_todo_capture`, which would be a call that cannot exist; `none` injects no guidance
+  at all.
+- **`/health` reports `modules`** (`toolGroups`, `registered`, `capture`), and the panel hides the
+  "collect from this conversation" entries when the capture tool is off instead of offering a
+  button that 404s. An older host with no `modules` field is assumed fully on.
+- **Deferred, on purpose**: splitting the package into several Loader rows (one row per module),
+  which the harness does support — `dsh.bundle.patch` may list files and a row may name a package
+  subpath. It buys Plugins-page cards for a user base of three stars; the config key buys the same
+  context saving today. `modules` in `/health` is the protocol that split would need, so it is in
+  place before anyone needs it.
+
+## [0.13.2] — 2026-10-22
+
+Four gaps the Windows sweep found in the new weight/settings surface (#5).
+
+- **`null` is a bad settings body, not zero.** `Number(null) === 0`, so `{captureMinWeight: null}`
+  answered 200, stored 0 and turned the whole capture gate off — while `{autoCollect: null}` was
+  correctly 400. Every numeric field now refuses `null` with a message saying to omit the field.
+- **The weight threshold is two decimals or a bad request.** `{captureMinWeight: 0.345}` used to be
+  rounded to 0.35 and stored, the same silent adjustment a fractional minute is rejected for.
+- **A deadline must be a real date.** `normalizeDue` was a bare `Date.parse`, so `"2026"` became
+  January 1st and `"October 2026"` an implementation-defined, timezone-dependent day. Input is now
+  a date, a date with time, or a date with time and zone — and `2026-02-31` is refused instead of
+  rolling over to March. The capture scorer reuses the same rule, so a garbage deadline can no
+  longer earn the +0.2 bonus that carried weak candidates past the gate.
+- **A blank step is refused, not dropped.** `steps: ['']` was silently discarded while the caller
+  believed it was stored, and the scorer still gave it +0.15 for "already broken into steps".
+
 ## [0.13.1] — 2026-10-22
 
 The sort orders are total orders now, which is what CI caught.

package/README.md

@@ -184,7 +184,7 @@ The plugin is a Loader row, not a hot-loaded script: **restart the host** (`dsh
 after installing, then refresh the page. A "待办 / Todos" entry appears in the sidebar.
 
 The npm package is the source of truth. A community catalog can lag behind it or point at an
-older release; pin the version you want (`dsh plugin --profile web add dsh-global-todo@0.12.4`)
+older release; pin the version you want (`dsh plugin --profile web add dsh-global-todo@0.13.1`)
 when it matters.
 
 **Hand-copied a directory instead?** Check it before wondering why the plugins page looks wrong:
@@ -434,6 +434,7 @@ topic feeds we have not verified, is [docs/DISTRIBUTION.md](docs/DISTRIBUTION.md
     storePath: /home/me/notes/global-todos.json   # a synced or versioned folder
     dispatchDir: /home/me/projects/thing          # default cwd for a new session
     requireExistingFiles: true                    # refuse a document that is not there yet
+    toolGroups: all                               # all (10 tools) | core (6: the list itself) | none
 ```
 
 The file is the artifact: plain JSON, one record per todo, written through a temp file and
@@ -473,8 +474,11 @@ and [docs/ROADMAP.md](docs/ROADMAP.md) for what could come next.
 npm run check     # parse every file, assert the shipping shape, and — when a DSH
                   # profile is present — validate every tool schema against the
                   # Host's own validator
-npm test          # 257 unit, contract and bundle tests, zero dependencies
-npm run verify    # both
+npm test              # unit, contract and bundle tests, zero dependencies
+npm run verify        # static checks + tests
+npm run check:contracts  # the cross-field matrix a reviewer re-tests by hand:
+                      # one invalid value, one answer, whichever field it lands on
+npm run check:windows    # the same idea on a real filesystem (Windows in CI)
 npm run check:matrix  # the running dsh against engines.dsh, then the manifest,
                       # bundle and tool-schema contracts (no preview writes)
 ```

package/README.zh.md

@@ -174,7 +174,7 @@ npx dsh-global-todo-doctor "$HOME/.dsh/plugins-local/全局待办插件"
 `Plugin metadata … ENOENT … \locale`。
 
 npm 上的包才是事实来源。社区目录可能落后于 npm、或指向某个旧 release；需要确定版本时
-直接钉版本（`dsh plugin --profile web add dsh-global-todo@0.10.0`）。
+直接钉版本（`dsh plugin --profile web add dsh-global-todo@0.13.1`）。
 
 回滚：
 
@@ -317,6 +317,7 @@ dsh plugin --profile web remove dsh-global-todo
     storePath: /home/me/notes/global-todos.json   # 放进同步盘或版本库
     dispatchDir: /home/me/projects/thing          # 新会话的默认工作目录
     requireExistingFiles: true                    # 文件还不存在就先不让挂
+    toolGroups: all                               # all（10 个工具）| core（6 个：只操作清单）| none
 ```
 
 **文件本身就是产物**：纯 JSON、一条记录一个待办，写入走「临时文件 + rename」，

package/cordis.patch.yml

@@ -24,6 +24,13 @@
         # Inject the short usage guidance into every turn. `false` leaves the tools
         # available but stops asking the model to record things on its own.
         guidance: true
+        # Which Agent tools this deployment registers. The ten schemas cost roughly
+        # 2k tokens per turn, so a deployment that only wants the panel can shed them:
+        #   all   10 tools (default)
+        #   core  6 tools: add / list / get / update / note / done
+        #   none  no tools; the guidance section is skipped too
+        # An unrecognised value is reported and treated as `all`.
+        toolGroups: all
         # Starting point for the panel's built-in folder browser when the shell has
         # no native picker. Empty = home directory, then the Host's cwd.
         browseRoot: ''

package/docs/DISTRIBUTION.md

@@ -15,10 +15,10 @@ of trusting this table.
 
 | Registry | Form | What it gives you | Verified state |
 |---|---|---|---|
-| **npm** | the package | the install path | `dsh-global-todo@0.12.10` |
+| **npm** | the package | the install path | `dsh-global-todo@0.13.1` |
 | **1024 Store** ([deepseek1024.com](https://deepseek1024.com)) · [repo](https://github.com/imsai-sh/awesome-deepseek-harness-plugins) | catalog entry, merged [#654](https://github.com/imsai-sh/awesome-deepseek-harness-plugins/pull/654) | searchable, has a public API | 🟡 entry live, but its install line still resolves to `github:LUgABeEEE/dsh-global-todo` — their npm enrichment has not caught up. Install works either way. |
 | **dsh.pub** · [page](https://dsh.pub/en/plugins/dsh-global-todo/) | published page + `dshpub` CLI | `npx dshpub add LUgABeEEE/dsh-global-todo` | ✅ page live, pinned to a commit |
-| **DSH-Plugins-Marketplace** ([bradeGithub](https://github.com/bradeGithub/DSH-Plugins-Marketplace)) | `registry.json`, collected from the `dsh-plugin` topic | one-click install inside DSH | ✅ `v0.12.x`, risk tier `safe` |
+| **DSH-Plugins-Marketplace** ([bradeGithub](https://github.com/bradeGithub/DSH-Plugins-Marketplace)) | `registry.json`, collected from the `dsh-plugin` topic | one-click install inside DSH | ✅ `v0.13.x`, risk tier `safe` |
 | **awesome-dsh-plugin** ([19.7k★](https://github.com/awesome-dsh-plugin/awesome-dsh-plugin)) | one YAML per plugin | the largest directory | ✅ merged [#7498](https://github.com/awesome-dsh-plugin/awesome-dsh-plugin/pull/7498) |
 | **walkinglabs/awesome-deepseek-harness-plugins** | README entry (source-verified list) | review-backed listing | ✅ merged [#114](https://github.com/walkinglabs/awesome-deepseek-harness-plugins/pull/114) |
 

package/docs/ROADMAP.md

@@ -15,14 +15,29 @@ is the durable part, and a stale number is worse than none.
 - Global list, one JSON file, atomic writes, one write path for both writers.
 - Creation time on every entry, immutable and shown everywhere.
 - Attachments as references: any number of documents and addresses per todo.
-- Nine `global_todo_*` tools — `add`, `capture`, `list`, `get`, `update`, `link`, `note`,
-  `done`, `remove`; `reopen` joined them later (below). What `/health` reports as
+- Ten `global_todo_*` tools — `add`, `capture`, `list`, `get`, `update`, `link`, `note`,
+  `done`, `remove`, and `reopen`, which followed in 0.3. What `/health` reports as
   `tools.registered` is the list as it stands, and panel and tools share the same validation.
 - Four hand-off modes, with success **and failure** recorded on the record.
 - Restore/undo for a delete, keyboard shortcuts, editable detail panel.
 - Proactive capture: `global_todo_capture` for batches, plus guidance that says when the
   agent should record something itself and when it must not.
 
+### Landed in 0.6
+
+The panel became one column with one type scale, and every conditional state got a baseline.
+
+- **The layout is a column, not a wrapping row** (`0.6.0`); the header wraps its actions, the
+  toolbar is two semantic rows, and the directory / handoff / browse controls sit behind a single
+  Context toggle. Five type sizes, one 28px control height, a 340px settings inspector instead of
+  an in-flow block.
+- **The settings panel was rebuilt as an inspector** (`0.6.4`): title row, three labelled groups,
+  help text under every field, a pinned save row, and About showing the data file and version.
+- **Every conditional state has an image** (`0.6.3`, `0.6.8`): empty list, filter with no match,
+  inbox, due reminder, selection, settings. `npm run screenshots` photographs them from the same
+  `SCENARIOS` table the static preview renders, and `npm run check:render` asserts each state's
+  marker, so a blank picture fails CI instead of shipping.
+
 ### Landed since 0.1
 
 Things that used to sit on the Next list (or in the Later table) and are facts in the
@@ -133,14 +148,13 @@ reminder) photographed into `docs/screenshots/` by `npm run screenshots`, and
 `npm run check:render` asserting each state's marker.
 ### Partly landed
 
-- **Session read-back** — `sessionAlive` is on every listed todo (`sessionAlive` in
-  `lib/dispatch.js`, surfaced by `GET /list`). Reading what that session last said, and
-  linking to it, is not: `lib/completion.js` reads `assistant/message` only to close a todo
-  this plugin dispatched, and stores one summary in its completion record.
-- **What the agents produced** — the per-todo record with a summary and the changed files landed
-  (`completeTodo()` in `lib/model.js`, 「完成记录」 in `lib/client.js`, the 已完成 filter and
-  group). The cross-todo "what did the sessions finish this week, and what did they touch" view
-  did not.
+- ~~**Session read-back**~~ — landed: `GET /session?id=` returns `alive`, `dir` and the last
+  assistant `tail` (`lib/routes.js`, `sessionTails` in `lib/index.js`), and the detail panel shows
+  that line (`lib/client.js`). It stays cheap and failure-tolerant: a conversation this process
+  has not seen speak answers `null`, which is the normal case for an old hand-off.
+- ~~**What the agents produced**~~ — landed: `GET /report?days=7` aggregates completion records
+  into finished items, conversations, touched files and the review backlog (`lib/report.js`), and
+  the panel shows it from `⋯ → 本周报告`.
 - **Attachment health** — a dead file link is flagged on read, but there is no 「重新挂载」 next
   to it (`relink` does not exist anywhere in `lib/`), and `annotateLinks()` has no unit test:
   today the render assertion in `tools/preview.mjs` is the only coverage.
@@ -162,17 +176,12 @@ plan. `normalizeSteps()` in `lib/model.js`, `dispatchPrompt()` in `lib/service.j
 What is left of the original idea: making a step addressable on its own (a tool that ticks step 3
 without resending the array) — not worth a tenth tool today.
 
-### 2. Session read-back — makes hand-off stop being fire-and-forget
-
-`sessionAlive` says a bound conversation still exists. Next: one line of its latest
-assistant message plus a link to open it.
+### 2. ~~Session read-back~~ — landed in 0.12
 
-- Today: `lib/completion.js` reads `assistant/message` only to close a todo this plugin
-  dispatched; nothing exposes it to the panel.
-- Effort: medium, and it must stay cheap and failure-tolerant: a missing or huge message is
-  a normal case, not an error.
-- Why second: the panel currently cannot answer "did the thing I handed over get anywhere",
-  which is the question people actually ask.
+`GET /session?id=` answers `alive`, `dir` and the last assistant `tail`, and the detail panel
+shows that line instead of a bare "still alive" flag. `lib/completion.js` keeps the tail it
+already reads for its own closing logic; a conversation this process has not seen speak answers
+`null`, which is a normal case rather than an error.
 
 ### 3. ~~Markdown import and export~~ — landed in 0.10.0
 

package/lib/client.js

@@ -3089,6 +3089,9 @@ button.gt-chip[data-on="1"] { color: var(--dsw-alias-label-primary); border-colo
 
       // The two toggles belong with the other "how this panel behaves" controls, not in
       // the title row.
+      // Absent modules (an older host) means everything is on; a switched-off capture tool
+      // means the group action would ask for a tool that cannot exist.
+      const captureOn = state.health?.modules?.capture !== false
       const settingsOn = state.health?.settings?.autoCollect === true
       // The Host already knows why it stayed quiet; the switch's tooltip is the cheapest
       // place to show it, and "nothing ever happens" stops being a mystery.
@@ -4789,7 +4792,7 @@ button.gt-chip[data-on="1"] { color: var(--dsw-alias-label-primary); border-colo
                             )
                           : null,
                         [
-                          group.sessionId === undefined
+                          group.sessionId === undefined || !captureOn
                             ? null
                             : {
                                 key: 'capture',
@@ -4810,7 +4813,7 @@ button.gt-chip[data-on="1"] { color: var(--dsw-alias-label-primary); border-colo
                           : h(Menu, {
                               label: t('group.actions'),
                               items: [
-                                group.sessionId === undefined
+                                group.sessionId === undefined || !captureOn
                                   ? null
                                   : {
                                       key: 'capture',

package/lib/index.js

@@ -34,10 +34,10 @@ import { LIMITS } from './model.js'
 import { ROUTE_BASE, createRoutes } from './routes.js'
 import { createService } from './service.js'
 import { createStore, resolveStorePath } from './store.js'
-import { createTools } from './tools.js'
+import { createTools, normalizeToolGroups, selectTools } from './tools.js'
 
 /** Must equal `package.json`'s version; `npm run check` enforces that. */
-export const VERSION = '0.13.1'
+export const VERSION = '0.14.0'
 
 /** Plugin id. Also the Loader row id in `cordis.patch.yml`. */
 export const name = 'dsh-global-todo'
@@ -49,6 +49,15 @@ export const DEFAULTS = Object.freeze({
   activityLimit: LIMITS.activity,
   requireExistingFiles: true,
   guidance: true,
+  /**
+   * Which agent tools this deployment registers: `all` (10), `core` (6, the list
+   * itself) or `none`.
+   *
+   * The schemas cost about 2k tokens per turn; a deployment that only wants the
+   * panel should not pay for the collaboration surface. An unrecognised value is
+   * reported and treated as `all`, because a typo must not silently remove tools.
+   */
+  toolGroups: 'all',
   // Starting point for the built-in folder browser when the shell has no picker.
   // Documented here because a patch override replaces `config` wholesale and has
   // to restate every key it wants to keep.
@@ -65,6 +74,24 @@ export const DEFAULTS = Object.freeze({
  *
  * Kept short on purpose: it is injected on every turn.
  */
+/**
+ * The guidance section for a tool-group mode: no tools, no instructions.
+ *
+ * Telling the model to use `global_todo_capture` when that tool was switched off
+ * is worse than saying nothing — it produces a call that cannot exist.
+ *
+ * @param {string} mode
+ * @returns {string} an empty string when nothing is registered
+ */
+export function guidanceFor(mode) {
+  const wanted = normalizeToolGroups(mode)
+  if (wanted === 'none') return ''
+  if (wanted === 'all') return GUIDANCE
+  return GUIDANCE.split('\n')
+    .filter((line) => !line.includes('global_todo_capture') && !line.includes('抓一下待办'))
+    .join('\n')
+}
+
 const GUIDANCE = [
   '【全局待办】一份跨会话、跨工作区、人和你共用的待办清单（`global_todo_*` 工具）。它和内置 `todo_write` 不是一回事：那个是你这个会话的计划，这份属于用户、跨会话保留。',
   '',
@@ -503,8 +530,15 @@ export function apply(ctx, config) {
     toolCtx.effect(() => {
       try {
         const definitions = createTools(service, { metrics, settings })
-        const disposers = definitions.map((definition) => toolCtx.tools.register(definition))
-        toolState.registered = definitions.map((definition) => definition.name)
+        const mode = normalizeToolGroups(resolved.toolGroups)
+        if (resolved.toolGroups !== mode) {
+          // A typo in `config.toolGroups` must be visible, not silently `all`.
+          logger?.warn?.(`dsh-global-todo: 未知的 toolGroups=${String(resolved.toolGroups)}，按 all 处理`)
+        }
+        const selected = selectTools(definitions, mode)
+        const disposers = selected.map((definition) => toolCtx.tools.register(definition))
+        toolState.registered = selected.map((definition) => definition.name)
+        toolState.mode = mode
         toolState.error = null
         toolCtx.logger?.info?.(`dsh-global-todo: 注册了 ${definitions.length} 个 Agent 工具`)
         return () => {
@@ -555,6 +589,13 @@ export function apply(ctx, config) {
         autoCollect: autoCollectState,
         reminders: reminderState,
         version: VERSION,
+        // What this deployment actually exposes, for the panel to hide absent entries and
+        // for a check to tell "switched off" apart from "failed to register".
+        modulesInfo: () => ({
+          toolGroups: normalizeToolGroups(resolved.toolGroups),
+          registered: toolState.registered.slice(),
+          capture: toolState.registered.includes('global_todo_capture'),
+        }),
         // What is on disk, which after an upgrade is not what this process is running.
         // The panel talks to a tree that changed under it; /health is where that is visible.
         diskVersion,
@@ -573,13 +614,14 @@ export function apply(ctx, config) {
     }, 'dsh-global-todo: web routes')
   })
 
-  if (resolved.guidance !== false) {
+  const guidanceText = guidanceFor(resolved.toolGroups)
+  if (resolved.guidance !== false && guidanceText !== '') {
     ctx.inject(['systemPrompt'], (promptCtx) => {
       try {
         const dispose = promptCtx.systemPrompt.section({
           name: 'dsh-global-todo:guidance',
           order: 3040,
-          text: GUIDANCE,
+          text: guidanceText,
         })
         return () => {
           try {

package/lib/model.js

@@ -108,6 +108,52 @@ function normalizeText(value, field, max, code) {
   return text
 }
 
+/**
+ * @param {unknown} value
+ * @returns {string | null} canonical ISO-8601 (UTC) or null
+ */
+/**
+ * The shapes a deadline may take: a date, or a date with time, optionally zoned.
+ *
+ * The old implementation was a bare `Date.parse`, which accepts `"2026"` (January 1st,
+ * invented), `"October 2026"` (implementation-defined, timezone-dependent) and anything
+ * else the engine happens to recognise. A deadline that silently becomes New Year's Day
+ * is worse than a rejected one.
+ */
+const DUE_SHAPE = /^(\d{4})-(\d{2})-(\d{2})(?:[T ](\d{2}):(\d{2})(?::(\d{2})(?:\.(\d{1,3}))?)?(Z|[+-]\d{2}:\d{2})?)?$/
+
+/**
+ * @param {unknown} value
+ * @returns {{ ok: true, iso: string } | { ok: false, reason: string }}
+ */
+export function parseDueText(value) {
+  if (typeof value !== 'string') return { ok: false, reason: '不是字符串' }
+  const text = value.trim()
+  const match = DUE_SHAPE.exec(text)
+  if (match === null) return { ok: false, reason: '只接受 2026-10-20 / 2026-10-20T10:00 / 带时区三种写法' }
+  const year = Number(match[1])
+  const month = Number(match[2])
+  const day = Number(match[3])
+  if (month < 1 || month > 12) return { ok: false, reason: '月份不合法' }
+  if (day < 1 || day > new Date(Date.UTC(year, month, 0)).getUTCDate()) return { ok: false, reason: '日期不合法' }
+  if (match[4] !== undefined && (Number(match[4]) > 23 || Number(match[5]) > 59 || Number(match[6] ?? 0) > 59)) {
+    return { ok: false, reason: '时间不合法' }
+  }
+  // A zone-less value keeps its usual meaning (local time, as the panel's datetime picker
+  // produces); only the accepted shapes were narrowed.
+  const parsed = Date.parse(text)
+  if (Number.isNaN(parsed)) return { ok: false, reason: '无法解析' }
+  return { ok: true, iso: new Date(parsed).toISOString() }
+}
+
+/**
+ * @param {unknown} value
+ * @returns {boolean} whether this value would be accepted as a deadline
+ */
+export function isValidDue(value) {
+  return typeof value === 'string' && value.trim() !== '' && parseDueText(value).ok === true
+}
+
 /**
  * @param {unknown} value
  * @returns {string | null} canonical ISO-8601 (UTC) or null
@@ -115,13 +161,12 @@ function normalizeText(value, field, max, code) {
 export function normalizeDue(value) {
   if (value === undefined || value === null || value === '') return null
   if (typeof value !== 'string') throw new TodoError('invalid-due', '截止时间必须是 ISO-8601 字符串')
-  const text = value.trim()
-  if (text === '') return null
-  const parsed = Date.parse(text)
-  if (Number.isNaN(parsed)) {
-    throw new TodoError('invalid-due', `无法解析截止时间：${value}（用 ISO-8601，例如 2026-10-20T10:00 或 2026-10-20）`)
+  if (value.trim() === '') return null
+  const verdict = parseDueText(value)
+  if (verdict.ok !== true) {
+    throw new TodoError('invalid-due', `无法解析截止时间：${value}（${verdict.reason}；例如 2026-10-20 或 2026-10-20T10:00）`)
   }
-  return new Date(parsed).toISOString()
+  return verdict.iso
 }
 
 /**
@@ -722,8 +767,11 @@ export function normalizeSteps(value) {
       if (text.length > LIMITS.step) {
         throw new TodoError('invalid-steps', `每一步最多 ${LIMITS.step} 字，收到 ${text.length} 字`)
       }
-      // A blank line in a textarea is a typo, not a step.
-      if (text !== '') out.push({ text, done: false })
+      // A blank step used to be dropped on the floor while the caller believed it was
+      // stored — and it earned the capture weight bonus for "already broken into steps".
+      // The panel already filters empty lines, so this only catches a caller that meant it.
+      if (text === '') throw new TodoError('invalid-steps', '步骤不能为空')
+      out.push({ text, done: false })
       continue
     }
     if (item === null || typeof item !== 'object' || Array.isArray(item)) {
@@ -733,7 +781,7 @@ export function normalizeSteps(value) {
     if (text.length > LIMITS.step) {
       throw new TodoError('invalid-steps', `每一步最多 ${LIMITS.step} 字，收到 ${text.length} 字`)
     }
-    if (text === '') continue
+    if (text === '') throw new TodoError('invalid-steps', '步骤不能为空')
     out.push({ text, done: item.done === true })
   }
   return out

package/lib/routes.js

@@ -438,6 +438,10 @@ export function createRoutes(deps) {
         // Tool registration is the surface that fails quietly, so it is reported
         // rather than assumed.
         tools: deps.tools ?? { registered: [], error: null },
+        // Which optional surfaces this deployment has. The panel hides entries it cannot
+        // call, and a check can tell "switched off" (mode/registered) from "failed"
+        // (tools.error above). Absent on an older host → assume everything is on.
+        modules: deps.modulesInfo?.() ?? { toolGroups: 'all', registered: [], capture: true },
         // Automatic completion is the other surface that can fail quietly: if the
         // session watcher did not attach, the only symptom would be todos that
         // never finish themselves.
@@ -796,10 +800,21 @@ function assertSettingsRange(body) {
   }
   for (const [field, [low, high, whole]] of Object.entries(ranges)) {
     const value = body[field]
-    if (value === undefined || value === null) continue
+    if (value === undefined) continue
+    // `null` used to fall through to the clamp: `Number(null) === 0`, so a null weight
+    // became 0 and turned the whole capture gate off while answering 200. A field that is
+    // present but null is a bad body, like every other non-number here.
+    if (value === null) {
+      throw new TodoError('invalid-body', `${field} 不能是 null；要恢复默认就从请求里省略它`)
+    }
     if (typeof value !== 'number' || !Number.isFinite(value)) {
       throw new TodoError('invalid-body', `${field} 必须是数字（${low}–${high}）`)
     }
+    // The weight is a two-decimal number by contract; storing 0.345 as 0.35 is the same
+    // silent adjustment that a fractional minute is rejected for.
+    if (field === 'captureMinWeight' && Math.round(value * 100) / 100 !== value) {
+      throw new TodoError('invalid-body', 'captureMinWeight 最多两位小数，收到 ' + String(value))
+    }
     // normalizeSettings only accepts integers for the minute fields and otherwise falls back
     // to the default — a silently ignored 30.5 is the same trap as a silent clamp.
     if (whole === true && !Number.isInteger(value)) {

package/lib/tools.js

@@ -325,6 +325,40 @@ function originOf(exec) {
  * @param {{ now?: () => number, metrics?: object }} [options]
  * @returns {object[]} definitions for `ctx.tools.register`
  */
+/**
+ * Which tools a deployment gets. `core` is the list itself; `all` adds the
+ * collaboration surface (batch capture, attachments, delete, reopen).
+ *
+ * The ten tool schemas are about 2k tokens per turn, which is real money for a
+ * deployment that only wants a todo list and never asks an agent to touch it.
+ * A config value is enough to shed that; splitting the package into several
+ * Loader rows is the heavier option, deferred until adoption asks for it.
+ */
+export const TOOL_GROUPS = Object.freeze({
+  core: Object.freeze(['global_todo_add', 'global_todo_list', 'global_todo_get', 'global_todo_update', 'global_todo_note', 'global_todo_done']),
+  advanced: Object.freeze(['global_todo_capture', 'global_todo_link', 'global_todo_remove', 'global_todo_reopen']),
+})
+
+/**
+ * @param {string} value
+ * @returns {'all' | 'core' | 'none'} one of the supported modes
+ */
+export function normalizeToolGroups(value) {
+  return value === 'core' || value === 'none' || value === 'all' ? value : 'all'
+}
+
+/**
+ * @param {{ name: string }[]} definitions
+ * @param {'all' | 'core' | 'none'} mode
+ * @returns {{ name: string }[]} the subset this mode registers
+ */
+export function selectTools(definitions, mode) {
+  const wanted = normalizeToolGroups(mode)
+  if (wanted === 'none') return []
+  if (wanted === 'all') return definitions
+  return definitions.filter((definition) => TOOL_GROUPS.core.includes(definition.name))
+}
+
 export function createTools(service, options = {}) {
   const now = options.now ?? (() => Date.now())
   // Read lazily: the settings object is created before the tools and its value can change

package/lib/weight.js

@@ -13,6 +13,8 @@
  * @module dsh-global-todo/weight
  */
 
+import { isValidDue } from './model.js'
+
 /** A phrase that reads like a commitment rather than an observation. */
 const COMMITMENT = ['记得', '别忘', '回头', '下周', '明天', '后天', '截止', 'deadline', '要交', '待确认', '等回复', '跟进', '安排', '发我', '确认一下', '记得要', '别忘了']
 
@@ -46,10 +48,15 @@ export function scoreItem(item, options = {}) {
   else if (length >= 3) add('specific', 0.05, '标题偏短')
   else add('tiny', -0.15, '标题几乎没有信息')
 
-  const due = typeof item.dueAt === 'string' && Number.isFinite(Date.parse(item.dueAt))
+  // The same validity rule create() applies: a date the store would reject must not earn
+  // the deadline bonus here, or a garbage dueAt could carry a weak candidate past the gate.
+  const due = isValidDue(item.dueAt)
   if (due) add('due', 0.2, '有可解析的截止时间')
 
-  if (Array.isArray(item.steps) && item.steps.length > 0) add('steps', 0.15, '已经拆成步骤')
+  const stepTexts = Array.isArray(item.steps)
+    ? item.steps.map((step) => (typeof step === 'string' ? step : step !== null && typeof step === 'object' ? step.text : ''))
+    : []
+  if (stepTexts.some((text) => typeof text === 'string' && text.trim() !== '')) add('steps', 0.15, '已经拆成步骤')
   if (Array.isArray(item.links) && item.links.length > 0) add('links', 0.1, '挂了文档或地址')
   if (typeof item.evidence === 'string' && item.evidence.trim() !== '') add('evidence', 0.1, '引用了原话')
   if (item.priority === 'urgent') add('priority', 0.15, '标了 P0')

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-global-todo",
-  "version": "0.13.1",
+  "version": "0.14.0",
   "icon": "./docs/icon.svg",
   "description": "Cross-session todo list for DeepSeek Harness: one JSON file a person and an agent both write to, with step plans that ship as a numbered hand-off, session read-back, and a human confirmation before an agent's \"done\" counts.",
   "type": "module",
@@ -73,6 +73,7 @@
     "check": "node scripts/check.mjs",
     "doctor": "node tools/doctor.mjs",
     "check:windows": "node tools/windows-check.mjs",
+    "check:contracts": "node tools/contracts-check.mjs",
     "notify": "node tools/notify.mjs",
     "test": "node --test \"test/**/*.test.mjs\"",
     "verify": "npm run check && npm run check:render && npm test",