dsh-global-todo 0.3.2 → 0.4.0

package/CHANGELOG.md

@@ -7,6 +7,90 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.4.0] — 2026-10-19
+
+The first release after the plugin was listed in a community catalog. It is a reliability
+release: the features that already existed now tell the truth — a sort that honours every level,
+a page that says it was cut, a language setting that applies, and an automatic collector that can
+explain itself and survives a failed question.
+
+- **An unknown working directory is a reason not to ask.** The exemption is keyed on where a
+  conversation works; a place nobody can name cannot be checked against it, and asking there would
+  volunteer a question in a workspace somebody may well have excluded. The decision now reports
+  `unknown-dir` and stays quiet, and the panel's switch tooltip says so. The cost is a conversation
+  whose cwd the Host never reported, which the event tracker normally supplies on its first message.
+
+- **The automatic collect switch shows the last decision.** `/health` now reports the full decision
+  list, so the switch's tooltip can say *why* nothing has happened — not quiet long enough, waiting
+  for you, cooling down, retrying, or an exempt workspace — together with how many candidates are
+  waiting and how many are due.
+
+- **The automatic collect switch can explain itself.** The decision layer knew why a conversation
+  was skipped — switched off, exempt, not quiet yet, waiting for a person, cooling down — and the
+  timer threw that reason away, so `/health` could report `enabled: true` while nothing ever
+  happened and give no way to tell why. The whole decision list is reported now, with the last one,
+  the number of waiting candidates, and in-memory counters for asked / succeeded / failed / dropped.
+  The settings file also reports how it loaded (`file` / `missing` / `corrupt`): "off because
+  somebody turned it off" and "off because the file was unreadable" used to look identical.
+
+- **A failed question no longer silences a conversation.** The cooldown was booked before the ask
+  and survived a failed request, so `awaiting-human` kept that conversation quiet until a person
+  happened to speak again — one transient resume failure turned the feature off for that
+  conversation, permanently and invisibly. A failure now releases the booking and schedules a
+  bounded retry (1 / 5 / 25 minutes, three attempts) before dropping the candidate with the reason
+  recorded. The ask is bounded too: an `agents.resume` that never settles now times out after ten
+  seconds instead of leaving the global `asking` flag set and silencing every conversation.
+
+- **A priority sort that put `urgent` last.** The rank table was written when there were three
+  levels, and adding a fourth did not touch it: the comparator read `undefined` for `urgent` and
+  produced `NaN`, so `sort=priority` (and the panel's level grouping) moved P0 to the bottom.
+  Every level now has a rank, and the test names all four in order.
+
+- **The list stopped at 200 without saying so.** `/list` cut the page at a fixed limit while
+  `counts` was computed over the whole file, so a list of 350 showed "350 open" above 200 rows.
+  The reply now carries `matched` (before the cut) and `truncated`, the panel prints "showing the
+  first N of M", and `global_todo_list` tells the model the same thing instead of letting it
+  reason about a page as if it were the whole set.
+
+- **The panel described the quiet window with the cooldown number.** The hint said "quiet for
+  {n} minutes" while `{n}` was `cooldownMinutes`; the gate it describes is `idleMinutes`, and the
+  two only looked identical because both default to 30. A hint that lies once the value is
+  changed is worse than no hint.
+
+- **Switching the interface language did nothing.** `resolveLang` read `locale` / `id` / `language`
+  / `current` from the locale snapshot, but the snapshot carries `active`; the value was never
+  found and the panel always fell back to `navigator.language`. It reads `active` first now, and
+  the unused `workspaces` client dependency is gone.
+
+- **The English panel was partly Chinese.** Seventeen keys — the whole `note.*` and `completion.*`
+  groups, plus `link.missing`, `search.hint` and `detail.notes` — existed only in the Chinese
+  dictionary and silently fell back; `meta.completed` was Chinese in the English table as well.
+  Both tables now carry the same 186 keys, guarded by a test that also refuses a Chinese value in
+  the English one.
+
+- **Two empty states, one wrong.** The panel decided between "no todos yet" and "nothing in this
+  filter" by looking at the current filter, so "all" with a search term and an empty list showed
+  the wrong sentence. The decision now uses the list's real size and whether a search is active.
+
+- **Opening a row near the bottom did nothing visible.** The detail expanded below the viewport;
+  the row now scrolls into view when it opens.
+
+- **The no-literal-colours test was checking fourteen characters.** It sliced from `const CSS =`
+  to the first `.gt-root` inside the stylesheet, so it never inspected a colour. The slice now
+  runs to the end of the template, which makes the guard real — and the theme-token rule is the
+  one thing that keeps dark mode working.
+
+- **Documentation that had drifted from the tree.** Both READMEs gained the five routes they were
+  missing (`note`, `dirs`, `settings`, `assign`, `diagnostics`); `docs/DESIGN.md` records the four
+  fields and two activity kinds added since the table was written; `cordis.patch.yml` names
+  `guidance` and `browseRoot`, which a wholesale `config` override would otherwise drop;
+  `docs/ROADMAP.md` cites files and functions instead of line numbers that had moved by dozens of
+  lines.
+
+- **The contribution terms are written down.** MIT in, MIT out — no CLA, no copyright assignment —
+  so a future patch cannot quietly stay its author's property and block a license change years
+  later. The READMEs also say plainly that this is a community plugin, not a DeepSeek project.
+
 ## [0.3.2] — 2026-10-19
 
 No code change. `0.3.1` was published to npm by hand, so it carries no provenance attestation;

package/CONTRIBUTING.md

@@ -56,6 +56,20 @@ Node 22.19 or newer is all you need.
 - **No secrets, ever.** The store is local and the plugin stores no credentials. The URL
   rule that refuses `user:password@` exists for this reason — do not relax it.
 
+## Licensing of contributions
+
+The plugin is [MIT](LICENSE)-licensed, and contributions arrive under the same terms — no CLA, no
+copyright assignment. Opening a pull request is the agreement. If that is not something you can do
+(an employer owns your work, say), say so in the PR before writing much code and we will work out
+the shape of the contribution first.
+
+Why this is written down rather than assumed: without a statement, a patch stays the property of
+whoever wrote it, and one unrelated contribution would be enough to block the project from ever
+changing its license without tracking that person down. Inbound = outbound, said once, keeps that
+door closed.
+
+`Signed-off-by` is welcome but not required.
+
 ## Releasing
 
 Facts checked on 2026-10-14, so nobody has to re-derive them:

package/README.md

@@ -40,8 +40,14 @@ profile already installed, or whatever `DSH_PLAYWRIGHT` points at.
 
 ## Requirements
 
-- DeepSeek Harness `0.2.x` (developed and verified against `0.2.1-rc.2`)
+- DeepSeek Harness `0.2.x` (developed and verified against `0.2.1-rc.2`; `engines.dsh` is
+  `>=0.2.0-rc.1 <0.3.0`, and a Host outside it skips the bundle instead of warning)
 - Node.js `>= 22.19.0` (the Web profile's own requirement)
+- A **Web** client: the panel is served by the Host's web server. Headless / ACP / SDK keep the
+  agent tools but have no panel; an Electron-style desktop client (file:// + IPC) is not
+  supported yet
+- After a Host upgrade, refresh the page — the client module graph belongs to the release the
+  page booted with
 - No runtime dependencies. Nothing is imported from `@deepseek-ai/*`.
 
 ## Install
@@ -57,6 +63,10 @@ dsh plugin --profile web add /absolute/path/to/dsh-global-todo
 The plugin is a Loader row, not a hot-loaded script: **restart the host** (`dsh web`)
 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.4.0`)
+when it matters.
+
 To roll back:
 
 ```sh
@@ -224,12 +234,13 @@ fence when that service is present, and by a strict loopback check otherwise.
 
 | Method | Path | Body / query |
 |---|---|---|
-| GET | `/api/global-todo/list` | `status`, `query`, `tag`, `sort`, `limit` |
+| GET | `/api/global-todo/list` | `status`, `query`, `tag`, `sort`, `limit` — the reply carries `matched` and `truncated` when the page was cut |
+| GET | `/api/global-todo/dirs` | `path?` — list subdirectories for the panel's built-in folder picker (the shell's own picker is preferred when mounted) |
 | GET | `/api/global-todo/get` | `id` |
 | GET | `/api/global-todo/export` | — (the store's own JSON document, for backup or migration) |
 | POST | `/api/global-todo/import` | `{ doc, mode?: replace\|merge }` — `replace` is an exact round trip, `merge` updates by id and appends (what the panel sends) |
 | POST | `/api/global-todo/capture` | `{ sessionId? }` — ask the current conversation to collect its follow-ups |
-| GET | `/api/global-todo/health` | — (store location, counts, dispatch capabilities, plus **tool registration** and **whether the completion watcher attached** — both fail quietly, so both are reported — and `metrics`: dispatch success rate, agent tool calls, list growth) |
+| GET | `/api/global-todo/health` | — (store location, counts, dispatch capabilities, plus **tool registration** and **whether the completion watcher attached** — both fail quietly, so both are reported — and `metrics`: dispatch success rate, agent tool calls, list growth; `autoCollect`: why each waiting conversation was or was not asked, counters, and how the settings file loaded) |
 | POST | `/api/global-todo/create` | `{ title, description?, links?, tags?, priority?, dueAt? }` |
 | POST | `/api/global-todo/update` | `{ id, ...fields, by?: human\|agent }` |
 | POST | `/api/global-todo/status` | `{ id, status, by?: human\|agent }` |
@@ -237,6 +248,9 @@ fence when that service is present, and by a strict loopback check otherwise.
 | POST | `/api/global-todo/restore` | `{ todo }` — put a removed record back verbatim (undo) |
 | POST | `/api/global-todo/link` | `{ id, add?: [...], remove?: [value \| index] }` |
 | POST | `/api/global-todo/dispatch` | `{ id, mode?: auto\|bound\|new\|current, sessionId?, dir? }` |
+| POST | `/api/global-todo/assign` | `{ ids, items?, target?, dir? }` — hand several todos over in one call; an id that matches nothing comes back instead of being sent elsewhere |
+| POST | `/api/global-todo/settings` | `{ autoCollect?, idleMinutes?, cooldownMinutes?, exemptWorkspaces? }` — the Host-side switches behind automatic collect |
+| POST | `/api/global-todo/diagnostics` | `{ scope, status?, reason?, message?, url? }` — the panel's own error report |
 
 `by` on `/update` and `/status` says whose write this is: omitted (what the panel sends) it is
 the person at the keyboard, and a script acting for the agent says `by: 'agent'` rather than
@@ -299,8 +313,13 @@ npm run check     # parse every file, assert the shipping shape, and — when a
                   # Host's own validator
 npm test          # 100+ unit, contract and bundle tests, zero dependencies
 npm run verify    # both
+npm run check:matrix  # the running dsh against engines.dsh, then the manifest,
+                      # bundle and tool-schema contracts (no preview writes)
 ```
 
+`engines.dsh` is the one version fact that matters: a Host outside it skips the whole bundle
+instead of warning, so `check:matrix` is the smoke to run before widening the range.
+
 There is **no build step**. The host half is plain ESM under `lib/`; the client half is a
 classic script that registers itself with `window.__ModuleLoader__`, so no bundler,
 TypeScript toolchain or CI artifact is involved. `lib/client.js` edits take effect on a
@@ -342,3 +361,6 @@ Please report vulnerabilities as described in [SECURITY.md](SECURITY.md).
 ## License
 
 [MIT](LICENSE) © 2026 LUgABeEEE
+
+A community plugin, not a DeepSeek project: the `dsh` prefix marks the ecosystem it plugs into, not
+an endorsement. "DeepSeek" and "DeepSeek Harness" remain their owners' marks.

package/README.zh.md

@@ -36,8 +36,12 @@ HTML（不依赖宿主、零依赖），再以 1280×720 拍进 `docs/screenshot
 
 ## 环境要求
 
-- DeepSeek Harness `0.2.x`（按 `0.2.1-rc.2` 开发与验证）
+- DeepSeek Harness `0.2.x`（按 `0.2.1-rc.2` 开发与验证；`engines.dsh` 是 `>=0.2.0-rc.1 <0.3.0`，
+  区间外的宿主会**整层跳过**这个 bundle，不是警告）
 - Node.js `>= 22.19.0`（Web profile 本身的要求）
+- **Web 客户端**：面板由宿主的 web server 提供。headless / ACP / SDK 只有 Agent 工具、没有面板；
+  Electron 式桌面端（file:// + IPC）暂不支持
+- 宿主升级后要**刷新页面**——客户端模块图属于页面启动时那个 release
 - **零运行期依赖**，也不 import 任何 `@deepseek-ai/*` 包
 
 ## 安装
@@ -53,6 +57,9 @@ dsh plugin --profile web add /绝对路径/dsh-global-todo
 插件是宿主组合里的**一行 Loader**，不是热加载脚本：**装完要重启宿主**（`dsh web`），
 再刷新页面。侧栏会出现「待办」入口。
 
+npm 上的包才是事实来源。社区目录可能落后于 npm、或指向某个旧 release；需要确定版本时
+直接钉版本（`dsh plugin --profile web add dsh-global-todo@0.4.0`）。
+
 回滚：
 
 ```sh
@@ -129,13 +136,14 @@ dsh plugin --profile web remove dsh-global-todo
 
 | 方法 | 路径 | 参数 |
 |---|---|---|
-| GET | `/api/global-todo/list` | `status`、`query`、`tag`、`sort`、`limit` |
+| GET | `/api/global-todo/list` | `status`、`query`、`tag`、`sort`、`limit`——被截断时响应带 `matched` 与 `truncated` |
+| GET | `/api/global-todo/dirs` | `path?`——列子目录，供面板内置的目录浏览器使用（宿主自己的选择器在时会优先） |
 | GET | `/api/global-todo/get` | `id` |
 | GET | `/api/global-todo/export` | ——（存储用的那份 JSON 文档，用于备份或迁移） |
 | POST | `/api/global-todo/import` | `{ doc, mode?: replace\|merge }`——`replace` 是无损往返，`merge` 同 id 覆盖、新 id 追加（面板用的是这个） |
 | POST | `/api/global-todo/note` | `{ id, text }`（追加进展记录） |
 | POST | `/api/global-todo/capture` | `{ sessionId? }`（请当前对话把要跟进的事抓进清单） |
-| GET | `/api/global-todo/health` | —（数据位置、统计、派发能力，以及**工具注册状态**与**自动收尾观察者是否挂上**——这两种失败是静默的，所以必须能查；还有 `metrics`：派发成功率、工具调用次数、清单增长） |
+| GET | `/api/global-todo/health` | —（数据位置、统计、派发能力，以及**工具注册状态**与**自动收尾观察者是否挂上**——这两种失败是静默的，所以必须能查；还有 `metrics`：派发成功率、工具调用次数、清单增长；`autoCollect`：每个候选对话**为什么被问/没被问**、计次，以及设置文件是怎么加载进来的） |
 | POST | `/api/global-todo/create` | `{ title, description?, links?, tags?, priority?, dueAt? }` |
 | POST | `/api/global-todo/update` | `{ id, ...字段, by?: human\|agent }` |
 | POST | `/api/global-todo/status` | `{ id, status, by?: human\|agent }` |
@@ -143,6 +151,9 @@ dsh plugin --profile web remove dsh-global-todo
 | POST | `/api/global-todo/restore` | `{ todo }` —— 原样还原被删除的记录（撤销） |
 | POST | `/api/global-todo/link` | `{ id, add?: [...], remove?: [值 或 下标] }` |
 | POST | `/api/global-todo/dispatch` | `{ id, mode?: auto\|bound\|new\|current, sessionId?, dir? }` |
+| POST | `/api/global-todo/assign` | `{ ids, items?, target?, dir? }`——一次把多条交给 Agent；配不上的 id 原样报回，不擅自送到别处 |
+| POST | `/api/global-todo/settings` | `{ autoCollect?, idleMinutes?, cooldownMinutes?, exemptWorkspaces? }`——自动获取的开关与阈值 |
+| POST | `/api/global-todo/diagnostics` | `{ scope, status?, reason?, message?, url? }`——面板自己上报的错误 |
 
 `/update` 与 `/status` 的 `by` 说明这次写是谁做的：不传（面板就是这样）就是人在键盘前，
 脚本替 agent 干活时写 `by: 'agent'`，而不是被记成人的操作。传别的值是 `400`——
@@ -200,8 +211,13 @@ npm run check     # 解析全部文件、校验发布形态；本机有 DSH prof
                   # 自己的校验器逐条验证工具 schema
 npm test          # 100+ 单元/契约/bundle 测试，零依赖
 npm run verify    # 两者都跑
+npm run check:matrix  # 当前 dsh 与 engines.dsh 的实际匹配，再跑 manifest/bundle/
+                      # 工具 schema 三类契约（不写 preview）
 ```
 
+`engines.dsh` 是唯一真正决定“装不装得上”的版本事实：区间外的宿主会**整层跳过**这个
+bundle，而不是警告；所以放宽区间之前先跑 `check:matrix`。
+
 **没有构建步骤。** 宿主半区是 `lib/` 下的纯 ESM；客户端半区是一个自注册到
 `window.__ModuleLoader__` 的普通脚本——不需要打包器、不需要 TypeScript 工具链、
 CI 里也没有构建产物。改 `lib/client.js` 刷新页面即生效；改宿主半区要重启宿主。
@@ -242,3 +258,5 @@ HTTP 接口只服务本机，清单是本地文件，任何凭据都不会被存
 ## 许可
 
 [MIT](LICENSE) © 2026 LUgABeEEE
+
+社区插件，不是 DeepSeek 官方项目：包名里的 `dsh` 只表示它接入的生态，不代表任何背书；「DeepSeek」与「DeepSeek Harness」的相关权利归其所有者。

package/cordis.patch.yml

@@ -21,3 +21,9 @@
         # Reject links whose file path does not exist at write time. `false` lets
         # you attach a document before creating it.
         requireExistingFiles: true
+        # 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
+        # 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/DESIGN.md

@@ -15,7 +15,7 @@ so the file stays readable, hand-editable and diffable.
 | `title` | string | 1–200 characters, trimmed |
 | `description` | string | up to 10 000 characters, Markdown-ish plain text |
 | `status` | `open` \| `doing` \| `done` \| `cancelled` | `doing` means someone is on it |
-| `priority` | `low` \| `normal` \| `high` | three levels people actually use |
+| `priority` | `low` \| `normal` \| `high` \| `urgent` | `urgent` was added in front of the first three; `normal` stays the default |
 | `dueAt` | ISO-8601 string \| `null` | canonicalised to UTC on write |
 | `tags` | string[] | ≤ 20, each ≤ 32, de-duplicated case-insensitively |
 | `links` | `{ kind: 'url' \| 'file', value, title }[]` | documents and addresses |
@@ -25,11 +25,15 @@ so the file stays readable, hand-editable and diffable.
 | `updatedBy` | `human` \| `agent` | which side changed it last |
 | `doneAt` | epoch ms \| `null` | set on `done`, cleared on leaving `done` |
 | `sessionId` | string | the conversation this todo owns; `''` until handed off |
+| `originDir` | string | the working directory it was written from; resolves a hand-off's cwd |
+| `originSessionId` | string | the conversation that wrote it; the panel groups by this |
 | `lastDispatch` | `{ at, mode, ok, sessionId?, error? }` \| `null` | last hand-off, including its failure reason |
+| `completion` | `{ at, by, summary, sessionId, artifacts }` \| `null` | what the finishing turn said and produced; cleared on reopen |
+| `notes` | `{ at, by, text }[]` | append-only progress notes, capped at `LIMITS.notes` |
 | `activity` | `{ at, by, kind, summary? }[]` | trimmed to `activityLimit` (default 50) |
 
 The activity kinds are `created`, `updated`, `status`, `done`, `reopened`, `linked`,
-`unlinked`, `dispatched`, `dispatch-failed`.
+`unlinked`, `dispatched`, `dispatch-failed`, `noted`, `completed`.
 
 ## Storage
 
@@ -192,7 +196,9 @@ that fills itself with noise gets ignored, and then the real items get ignored t
   remembered from the conversation's own events rather than looked up when the timer runs: these
   conversations are idle most of the time, and an idle one is exactly the one the Host may have
   unloaded, where a live lookup answers `''` and the exemption would stop applying to the only
-  conversations it exists for;
+  conversations it exists for. A directory nobody can name is therefore treated as **un-askable**
+  rather than as exempt-or-allowed: the exemption cannot be checked against a place that cannot be
+  named, and the safe direction is silence (`unknown-dir`);
 - **only clean turns**: an aborted, failed or truncated turn is not a moment to ask;
 - **one question per message the person wrote**. The question is itself a message in the
   conversation, so it restarted the quiet clock, and the answer to it ended a clean turn — which
@@ -208,6 +214,27 @@ The switch lives on the Host rather than in the panel because the Host is what a
 panel may be closed when the question is due, and `/health` reports the state so the mirror can
 never drift from the thing it mirrors.
 
+### What it did is part of the feature
+
+A gate whose reason is discarded is a gate nobody can debug. The decision layer always knew why a
+conversation was skipped — off, exempt, not idle yet, awaiting a person, cooling down — but the
+timer kept only the verdict, so `/health` could say `enabled: true` while nothing ever happened and
+offer no way to tell why. The whole decision list is reported now (`autoCollect.decisions`, capped
+at twenty), along with the last decision, how many candidates are waiting, and in-memory counters
+for asked / succeeded / failed / dropped.
+
+The settings file reports how it loaded (`file` / `missing` / `corrupt`) and when. "Off" because a
+person turned it off and "off" because the file could not be read looked identical from the panel,
+and the second one is a silent failure rather than a decision.
+
+A failed question is not an answer. The booking used to survive a failed request, and
+`awaiting-human` then kept that conversation quiet until somebody happened to speak again: one
+transient resume failure switched the feature off for that conversation, permanently and
+invisibly. A failure now releases the booking, schedules a bounded retry (1 / 5 / 25 minutes,
+three attempts), and only then drops the candidate with the reason recorded. The request itself is
+bounded too: an `agents.resume` that never settles used to leave the global `asking` flag set,
+which silenced the feature for every conversation rather than the broken one.
+
 ## An action belongs where its subject is unambiguous
 
 "Collect from this chat" was a toolbar button, and in a global panel "this chat" is a guess: the

package/docs/ROADMAP.md

@@ -4,8 +4,9 @@ What could come next, ordered by value against effort. Everything here is a
 proposal, not a commitment.
 
 This file was audited against the tree: everything under **Landed** is in the code
-today, with the `file:line` that shows it. Line numbers move, so the durable part
-of a citation is the function or the label beside it.
+today, cited by the file and the function that shows it. Line numbers were removed
+after they drifted by dozens of lines: the function or the label beside a citation
+is the durable part, and a stale number is worse than none.
 
 ## Landed
 
@@ -28,80 +29,87 @@ Things that used to sit on the Next list (or in the Later table) and are facts i
 tree now.
 
 **Attachment health** — a file link is probed when the list is read, never when it is
-stored: `annotateLinks()` (`lib/service.js:347`) sets `missing: true` for a path
-that no longer resolves (`lib/service.js:360`), and both read routes apply it
-(`GET /list` `lib/routes.js:257`, `GET /get` `lib/routes.js:311`). The panel
-shows the chip on the row and in the detail (`lib/client.js:1408`,
-`lib/client.js:1678`) with the label 「文件不在了」 (`lib/client.js:209`); the render
-check asserts it (`tools/preview.mjs:572`).
+stored: `annotateLinks()` (`lib/service.js`) sets `missing: true` for a path
+that no longer resolves (`lib/service.js`), and both read routes apply it
+(`GET /list` `lib/routes.js`, `GET /get` `lib/routes.js`). The panel
+shows the chip on the row and in the detail (`lib/client.js`,
+`lib/client.js`) with the label 「文件不在了」 (`lib/client.js`); the render
+check asserts it (`tools/preview.mjs`).
 
 Still owed from the original idea: 「重新挂载」 next to a dead link, and a unit test for
 `annotateLinks` itself — today the render assertion is the only coverage.
 
-**Smarter search** — `parseQuery()` (`lib/service.js:129`) turns `tag:发布`,
-`#发布`, `level:p0` (aliases at `lib/service.js:117`), `is:…` and `has:…` into
-filters, and `matchesSyntax()` (`lib/service.js:152`) applies `is:overdue`,
+**Smarter search** — `parseQuery()` (`lib/service.js`) turns `tag:发布`,
+`#发布`, `level:p0` (aliases at `lib/service.js`), `is:…` and `has:…` into
+filters, and `matchesSyntax()` (`lib/service.js`) applies `is:overdue`,
 `is:due`, `is:active`, `has:link`, `has:note` and `is:<status>`; free text
-still has to match every word (`lib/service.js:196`). The panel advertises the syntax
-on the search box (`lib/client.js:210`, `lib/client.js:2705`) and the render check
-asserts the hint (`tools/preview.mjs:573`). Test: `test/service.test.mjs`, "the
+still has to match every word (`lib/service.js`). The panel advertises the syntax
+on the search box (`lib/client.js`) and the render check
+asserts the hint (`tools/preview.mjs`). Test: `test/service.test.mjs`, "the
 search box understands tag:, is:, has: and level: tokens".
 
 Not landed from the same idea: `before:` / `after:` date bounds.
 
-**Progress notes** — an append-only trail per todo: `addNote()` (`lib/model.js:387`),
-repaired on load by `normalizeNotes()` (`lib/model.js:361`), reached through
-`note()` (`lib/service.js:329`), `POST /note` (`lib/routes.js:423`) and the agent
-tool `global_todo_note` (`lib/tools.js:618`), and shown as 「进展记录」 in the detail
-(`lib/client.js:200`, `lib/client.js:1648`). Tests: `test/model.test.mjs:210`,
-`test/tools.test.mjs:301`, `test/routes.test.mjs:495`.
+**Progress notes** — an append-only trail per todo: `addNote()` (`lib/model.js`),
+repaired on load by `normalizeNotes()` (`lib/model.js`), reached through
+`note()` (`lib/service.js`), `POST /note` (`lib/routes.js`) and the agent
+tool `global_todo_note` (`lib/tools.js`), and shown as 「进展记录」 in the detail
+(`lib/client.js`). Tests: `test/model.test.mjs`,
+`test/tools.test.mjs`, `test/routes.test.mjs`.
 
 **JSON export and import** — `GET /export` hands back the store's own document and
-`POST /import` writes one back (`lib/routes.js:320`, `lib/routes.js:332`), through
-`exportDocument()` / `importDocument()` (`lib/service.js:536`,
-`lib/service.js:554`). `replace` is a byte-for-byte round trip; `merge` updates by
+`POST /import` writes one back (`lib/routes.js`), through
+`exportDocument()` / `importDocument()` (`lib/service.js`,
+`lib/service.js`). `replace` is a byte-for-byte round trip; `merge` updates by
 id and appends what is new. The panel has 导出 / 导入 in the header
-(`lib/client.js:2570`, `lib/client.js:2580`) and imports in merge mode on purpose: a
+(`lib/client.js`) and imports in merge mode on purpose: a
 file picked by mistake must not erase the list. Round trip: `test/transfer.test.mjs`,
 "an export imported back reproduces the list exactly".
 
 Not landed: the Markdown / TaskPaper formats this entry used to ask for, and the 1 MiB
-request cap stays (`lib/routes.js:32`), so a list exported beyond that size cannot be
+request cap stays (`lib/routes.js`), so a list exported beyond that size cannot be
 imported back through the route.
 
 **Metrics in /health** — the health reply now carries `metrics`
-(`lib/routes.js:349`): dispatch success rate, agent tool call counts, and list growth
+(`lib/routes.js`): dispatch success rate, agent tool call counts, and list growth
 (created / removed / restored / imports / noted, current size, peak), built in
 `lib/metrics.js`. The counters are in memory and reset with the Host, and the field is
 `null` when nothing mounted them — an absent metric is not a zero. Test:
 `test/metrics.test.mjs`.
 
 **Reopen, with an honest trail** — a wrongly-finished todo has a dedicated way back:
-`reopen()` (`lib/service.js:318`) does `done` / `cancelled` → `open` and refuses anything else,
-reached by the tool `global_todo_reopen` (`lib/tools.js:747`); the reason it records lands in
-the activity trail via `setStatus()` (`lib/model.js:536`, `lib/model.js:554`). Writing through
+`reopen()` (`lib/service.js`) does `done` / `cancelled` → `open` and refuses anything else,
+reached by the tool `global_todo_reopen` (`lib/tools.js`); the reason it records lands in
+the activity trail via `setStatus()` (`lib/model.js`). Writing through
 the panel's routes no longer forces a false provenance: `/update` and `/status`
-(`lib/routes.js:462`, `lib/routes.js:471`) take an explicit `by: 'agent'` and default to the
-person, and anything else is a 400 (`actorOf` at `lib/routes.js:254`). Tests:
-`test/tools.test.mjs:230`, `test/routes.test.mjs:142`.
+(`lib/routes.js`) take an explicit `by: 'agent'` and default to the
+person, and anything else is a 400 (`actorOf` at `lib/routes.js`). Tests:
+`test/tools.test.mjs`, `test/routes.test.mjs`.
 
 Not landed: the same `by` on `/create`, `/note`, `/remove` and `/link`, which still record the
 person — the agent has its own tools for those. `/restore` (the panel's undo) has no agent-facing
 equivalent at all, so nothing there can be misattributed today.
 
+**Automatic collect with a memory** — the decision layer keeps its reasons: `/health` reports
+every waiting candidate's verdict (`off`, `exempt-workspace`, `unknown-dir`, `retry-wait`,
+`awaiting-human`, `not-idle-yet`, `cooldown`), the last one, and in-memory counters for
+asked / succeeded / failed / dropped (`explainAutoCollect` in `lib/settings.js`, `autoCollectState`
+in `lib/index.js`). A failed question releases its booking and retries after 1 / 5 / 25 minutes
+(`retryDelayMs`), and an ask that never settles is bounded by a ten-second timeout. An unknown
+working directory is never asked, because the exemption cannot be checked against it.
 ### Partly landed
 
 - **Batch and multi-select** — the selection mode, its per-row markers and the batch
-  一键分配 are in (`lib/client.js:2209`, `lib/client.js:2884`, `POST /assign` at
-  `lib/routes.js:413`, `assignMany()` at `lib/dispatch.js:195`; tests
-  `test/dispatch.test.mjs:657`). Batch 完成 / 打标签 across a selection do not exist.
+  一键分配 are in (`lib/client.js`, `POST /assign` at
+  `lib/routes.js`, `assignMany()` at `lib/dispatch.js`; tests
+  `test/dispatch.test.mjs`). Batch 完成 / 打标签 across a selection do not exist.
 - **Session read-back** — `sessionAlive` is on every listed todo
-  (`lib/routes.js:259`, `lib/dispatch.js:698`). Reading what that session last said,
+  (`lib/routes.js`, `lib/dispatch.js`). 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()` at `lib/model.js:415`, 「完成记录」 at
-  `lib/client.js:1648`, the 已完成 filter and group at `lib/client.js:153`). The
+  files landed (`completeTodo()` at `lib/model.js`, 「完成记录」 at
+  `lib/client.js`, the 已完成 filter and group at `lib/client.js`). The
   cross-todo "what did the sessions finish this week, and what did they touch" view did
   not.
 
@@ -163,14 +171,14 @@ something you can review, and would be the honest way to show that a hand-off di
 
 | Idea | Note |
 |---|---|
-| Image attachments | `kind: 'image'` next to `url` / `file`. The shape is already prepared for it, but `LINK_KINDS` is still `['url', 'file']` (`lib/links.js:21`). |
-| Official `storageDomain` backend | A second store backend behind the same interface; the file stays the default because it is the feature. Today there is one backend and it says so (`kind: 'json'`, `lib/store.js:212`). |
+| Image attachments | `kind: 'image'` next to `url` / `file`. The shape is already prepared for it, but `LINK_KINDS` is still `['url', 'file']` (`lib/links.js`). |
+| Official `storageDomain` backend | A second store backend behind the same interface; the file stays the default because it is the feature. Today there is one backend and it says so (`kind: 'json'`, `lib/store.js`). |
 | Virtualised list | Only needed past a few hundred rows; measure first. Nothing in `lib/client.js` virtualises today. |
 | Drag to reorder | Manual order is meaningful to some people; it also needs a stable `position` field and a decision about how it interacts with due-date grouping. |
 | Multi-list / projects | A `list` field with one default list; deferred because "global single list" is the current identity. |
-| Archive instead of delete | Keeps history without cluttering. `POST /remove` deletes for real (`lib/routes.js:445`); only the panel's short undo brings a record back. |
+| Archive instead of delete | Keeps history without cluttering. `POST /remove` deletes for real (`lib/routes.js`); only the panel's short undo brings a record back. |
 | Cross-machine conflict notice | The file is portable (NAS, sync folder). Detect "changed underneath me" and offer a reload instead of a silent overwrite — `store.read` still trusts the file whenever it parses. |
-| Capture from outside the chat | Notifications, mail, announcements — the sources `dsh-todo-list` reads. Needs an ingest path and a policy for deduplication; `POST /capture` only asks a conversation to collect (`lib/routes.js:418`). |
+| Capture from outside the chat | Notifications, mail, announcements — the sources `dsh-todo-list` reads. Needs an ingest path and a policy for deduplication; `POST /capture` only asks a conversation to collect (`lib/routes.js`). |
 | Accessible-only sweep | Full keyboard path is close; a screen-reader pass over the panel and the group headers is still owed. |
 
 ## Explicitly not planned

package/docs/icon.svg

@@ -0,0 +1,19 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512" width="512" height="512" role="img" aria-label="Global todos">
+  <rect width="512" height="512" rx="116" fill="#0d6b5e"/>
+  <rect x="92" y="104" width="328" height="304" rx="32" fill="#f4faf8"/>
+  <g>
+    <circle cx="152" cy="184" r="23" fill="#e7f2ef"/>
+    <path d="M141 184l8 8 15-17" fill="none" stroke="#0d6b5e" stroke-width="11" stroke-linecap="round" stroke-linejoin="round"/>
+    <rect x="198" y="174" width="168" height="20" rx="10" fill="#c8d6d1"/>
+  </g>
+  <g>
+    <circle cx="152" cy="264" r="23" fill="#e7f2ef"/>
+    <path d="M141 264l8 8 15-17" fill="none" stroke="#0d6b5e" stroke-width="11" stroke-linecap="round" stroke-linejoin="round"/>
+    <rect x="198" y="254" width="132" height="20" rx="10" fill="#c8d6d1"/>
+  </g>
+  <g>
+    <circle cx="152" cy="344" r="23" fill="#f7edda"/>
+    <circle cx="152" cy="344" r="9" fill="#c98a1e"/>
+    <rect x="198" y="334" width="150" height="20" rx="10" fill="#d8e2de"/>
+  </g>
+</svg>