dsh-working-activity 0.2.6 → 0.3.2

package/LICENSE

@@ -1,28 +1,28 @@
-BSD 3-Clause License
-
-Copyright (c) 2026, chimney (ccch1mneyyy)
-
-Redistribution and use in source and binary forms, with or without
-modification, are permitted provided that the following conditions are met:
-
-1. Redistributions of source code must retain the above copyright notice, this
-   list of conditions and the following disclaimer.
-
-2. Redistributions in binary form must reproduce the above copyright notice,
-   this list of conditions and the following disclaimer in the documentation
-   and/or other materials provided with the distribution.
-
-3. Neither the name of the copyright holder nor the names of its
-   contributors may be used to endorse or promote products derived from
-   this software without specific prior written permission.
-
-THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
-AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
-IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
-DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
-FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
-DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
-SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
-CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
-OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
-OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+BSD 3-Clause License
+
+Copyright (c) 2026, chimney (ccch1mneyyy)
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+
+1. Redistributions of source code must retain the above copyright notice, this
+   list of conditions and the following disclaimer.
+
+2. Redistributions in binary form must reproduce the above copyright notice,
+   this list of conditions and the following disclaimer in the documentation
+   and/or other materials provided with the distribution.
+
+3. Neither the name of the copyright holder nor the names of its
+   contributors may be used to endorse or promote products derived from
+   this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
+CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

package/README.i18n.yaml

@@ -1,6 +1,6 @@
-# Bilingual-pair consistency record (docs/i18n/README.md): the git blob hash of each
-# side as of the last confirmed-consistent state. Both languages carry equal authority;
-# after editing either side, bring the other along and re-record with:
-#   pnpm run verify-translation-pairing --write packages/activity/working-activity/README.md
-README.md: bf0787caac11a292882ba1a35963878e373e7db8
-README.zh.md: de09a7945dbe42c85d359fd256cdac0264d4b6cd
+# Bilingual-pair consistency record (docs/i18n/README.md): the git blob hash of each
+# side as of the last confirmed-consistent state. Both languages carry equal authority;
+# after editing either side, bring the other along and re-record with:
+#   pnpm run verify-translation-pairing --write packages/activity/working-activity/README.md
+README.md: bf0787caac11a292882ba1a35963878e373e7db8
+README.zh.md: de09a7945dbe42c85d359fd256cdac0264d4b6cd

package/README.md

@@ -1,122 +1,122 @@
-# dsh-working-activity
-
-A live "working line" for DeepSeek Harness: the model's real-time activity — playful thinking copy, the tool actually running, elapsed time, and a turn-end summary — shown while the agent works.
-
-## What it does
-
-Folds the durable session stream (`turn/start`, `assistant/chunk`, `tool/call`, `tool/result`, `turn/end`) plus `agent/status` into one status line, refreshed on a render tick:
-
-- **Thinking**: short colloquial copy rotates every few seconds (`嗯…让我捋捋`, `盘一下盘一下`, `大脑转起来了`, deadpan `lol` / `hm` / `ok`), tiered when thinking runs long (30s / 1min / 5min), night-owl copy mixed in between 00:00–06:00 local time.
-- **Tool activity**: the running tool renders as `俏皮动词 + 参数细节 + 已耗时` (`跑个命令 npm test · 12s`); failed tools show `翻车了`-style copy in the done line.
-- **Turn summary**: on `turn/end` the line becomes `搞定 ✓ · N 工具 · 想Xs 干Ys` (thinking/tool split), with the last tool's fragment pinned for a few seconds.
-- **Minimal mode**: `phrases: false` renders plain functional labels (`思考中 · 总1m23s`, `bash npm test · 12s`).
-
-Two optional sinks, both off by default only when their seam is absent:
-
-1. **TUI prompt slot** — registers the `${activity}` template value on `ctx.tuiPrompt` when the TUI is composed. Add `${activity}` to `theme.leftPrompt` to see it next to `cwd`/`model`/`context`.
-2. **Session events** — appends log-only `activity/status` events (never surface events: the model never sees them) for Web and other UI consumers; replay ignores them.
-
-## Installation
-
-The package is a self-mounting bundle: it declares `dsh.bundle.patch`
-(`cordis.patch.yml`), so the official CLI both installs it and appends it to
-the profile's bundle layer stack:
-
-```sh
-dsh plugin --profile <profile> add dsh-working-activity
-```
-
-At boot, app-boot applies the bundle's patch list over the profile root and
-the package inserts its own `working-activity` row — no manual configuration
-required. To tune a value, override the row's config by id in the profile's
-user layer (`$DSH_HOME/profiles/<profile>/cordis.patch.yml`) instead of
-inserting a second same-id row:
-
-```yaml
-- id: working-activity
-  config:
-    publishIntervalMs: 500
-```
-
-## TUI usage
-
-Install the plugin into a profile that composes the official `dsh-tui`, then
-add the `${activity}` slot to the left prompt template in the profile's user
-layer (`$DSH_HOME/profiles/<profile>/cordis.patch.yml`):
-
-```yaml
-- id: tui
-  config:
-    theme:
-      leftPrompt: '${cwd}${git/worktree}${activity}${model}${token_meter/cache_hit_rate}${context}'
-```
-
-While a turn runs, the prompt line shows e.g. `dsh main 跑个命令 npm test · 12s deepseek-chat …`; while thinking, `嗯…让我捋捋 · 总1m23s`; after the turn, `搞定 ✓ · 4 工具 · 想12s 干11s` briefly. Without `${activity}` in the template, the plugin is inert in the TUI (the slot is unregistered values are omitted by the template renderer).
-
-## Web usage
-
-The Web client renders the live line two ways, both fed by the `activity/status` events:
-
-- The turn-level status label (`TurnStatus`, formerly the static "Deep diving...") shows the live line while a turn runs, keeping its sweep animation.
-- A working-line dock entry (`WorkingLine` on `conversation.input.dock`) renders the turn-end statistics (token/elapsed/tool summary) above the composer after a turn settles; live phases stay on the turn label.
-
-Both fall back to the previous static label while the plugin is absent, so the Web UI is unaffected by disabling it.
-
-## Configuration
-
-| Key | Type | Default | Meaning |
-|---|---|---|---|
-| `phrases` | `boolean` | `true` | Playful copy pool; `false` renders plain functional labels |
-| `publish` | `boolean` | `false` | Append `activity/status` session events for UI consumers. Off by default: appended events currently make session logs unresumable (see note below) |
-| `tickMs` | `number` | `500` | Status render tick interval (100–5000) |
-| `publishIntervalMs` | `number` | `2000` | Minimum interval between published events while the line is stable (500–30000) |
-| `detailLimit` | `number` | `40` | Max displayed detail length (paths/commands/patterns), 8–120 |
-| `customActions` | `object` | `{}` | Exact tool-name → action-copy pools, e.g. `{"my_deploy": ["部署一下", "上线中"]}` |
-| `narrate` | `boolean` | `true` | Inject the `⏵` self-narration contract into the system prompt; the line is surfaced live and stripped from the chat body |
-
-## Event contract
-
-`activity/status` is a log-only session event (merge-extensible `SessionEventMap` member, no `surfaceOp`):
-
-```ts
-{
-  phase: 'idle' | 'waiting' | 'thinking' | 'tool' | 'done'
-  line: string            // plain-text status line, no ANSI
-  label?: string          // current work label (tool action / stage)
-  detail?: string         // path / command / pattern fragment
-  phrase?: string         // current playful phrase
-  toolCount: number       // tools completed this turn
-  turnElapsedMs: number   // ms since turn start
-  phaseStartedAt: number  // epoch ms the phase started (animation anchor)
-}
-```
-
-> **Why `publish` is off by default:** `session.append()` cannot mark events ignorable, and the resume read path refuses any log containing unknown non-ignorable event types — so with `publish: true`, every session that rendered a status line fails to resume. Re-enable only for a log-replaying consumer on a harness that supports ignorable appends. The live TUI prompt line is unaffected.
-
-Publishing rules: line changes publish immediately; a stable line republishes at most every `publishIntervalMs` so a long tool's elapsed time stays live without flooding the log. All data is lossless JSON; optional fields are omitted when absent.
-
-## Export shape
-
-A function/namespace plugin: `name` / `Config` / `apply`, no default export. The state machine (`ActivityTracker`) and copy pools live in `./status` and `./phrases` (pure, clock-injected, unit-tested). The invariant companion registers under `./invariant`.
-
-## Model Experience
-
-### Prompt and tool surface
-
-Nothing. The plugin injects no prompt sections, registers no tools, and appends no surface events. `activity/status` is UI state only: it never enters derived model history, so the model cannot see its own working line.
-
-### Token effect
-
-Zero per request.
-
-### KV Cache effect
-
-No system-prompt contribution, so no cache-stability effect.
-
-## Known Limitations and Deferred Work
-
-- **Single active line**: the plugin keeps one status line per session; the TUI slot shows the most recently active session.
-- **Narration is opt-in**: the `⏵` self-narration contract (model writes a short status line at the top of each reply) is injected by default (`narrate: true`); set `narrate: false` for a purely event-derived line.
-- **No progress percentages**: DSH has no tool progress events; a long tool shows elapsed time only.
-- **No animated frames**: the TUI slot renders a static text fragment; frame animation (moon/comet/braille presets) is deferred until the prompt-slot contract supports a frame callback.
-- **Web dock entry duplicates the turn label**: the input-dock `WorkingLine` and the chat `TurnStatus` show the same snapshot; the dock entry exists for session views where the turn label is not visible.
+# dsh-working-activity
+
+A live "working line" for DeepSeek Harness: the model's real-time activity — playful thinking copy, the tool actually running, elapsed time, and a turn-end summary — shown while the agent works.
+
+## What it does
+
+Folds the durable session stream (`turn/start`, `assistant/chunk`, `tool/call`, `tool/result`, `turn/end`) plus `agent/status` into one status line, refreshed on a render tick:
+
+- **Thinking**: short colloquial copy rotates every few seconds (`嗯…让我捋捋`, `盘一下盘一下`, `大脑转起来了`, deadpan `lol` / `hm` / `ok`), tiered when thinking runs long (30s / 1min / 5min), night-owl copy mixed in between 00:00–06:00 local time.
+- **Tool activity**: the running tool renders as `俏皮动词 + 参数细节 + 已耗时` (`跑个命令 npm test · 12s`); failed tools show `翻车了`-style copy in the done line.
+- **Turn summary**: on `turn/end` the line becomes `搞定 ✓ · N 工具 · 想Xs 干Ys` (thinking/tool split), with the last tool's fragment pinned for a few seconds.
+- **Minimal mode**: `phrases: false` renders plain functional labels (`思考中 · 总1m23s`, `bash npm test · 12s`).
+
+Two optional sinks, both off by default only when their seam is absent:
+
+1. **TUI prompt slot** — registers the `${activity}` template value on `ctx.tuiPrompt` when the TUI is composed. Add `${activity}` to `theme.leftPrompt` to see it next to `cwd`/`model`/`context`.
+2. **Session events** — appends log-only `activity/status` events (never surface events: the model never sees them) for Web and other UI consumers; replay ignores them.
+
+## Installation
+
+The package is a self-mounting bundle: it declares `dsh.bundle.patch`
+(`cordis.patch.yml`), so the official CLI both installs it and appends it to
+the profile's bundle layer stack:
+
+```sh
+dsh plugin --profile <profile> add dsh-working-activity
+```
+
+At boot, app-boot applies the bundle's patch list over the profile root and
+the package inserts its own `working-activity` row — no manual configuration
+required. To tune a value, override the row's config by id in the profile's
+user layer (`$DSH_HOME/profiles/<profile>/cordis.patch.yml`) instead of
+inserting a second same-id row:
+
+```yaml
+- id: working-activity
+  config:
+    publishIntervalMs: 500
+```
+
+## TUI usage
+
+Install the plugin into a profile that composes the official `dsh-tui`, then
+add the `${activity}` slot to the left prompt template in the profile's user
+layer (`$DSH_HOME/profiles/<profile>/cordis.patch.yml`):
+
+```yaml
+- id: tui
+  config:
+    theme:
+      leftPrompt: '${cwd}${git/worktree}${activity}${model}${token_meter/cache_hit_rate}${context}'
+```
+
+While a turn runs, the prompt line shows e.g. `dsh main 跑个命令 npm test · 12s deepseek-chat …`; while thinking, `嗯…让我捋捋 · 总1m23s`; after the turn, `搞定 ✓ · 4 工具 · 想12s 干11s` briefly. Without `${activity}` in the template, the plugin is inert in the TUI (the slot is unregistered values are omitted by the template renderer).
+
+## Web usage
+
+The Web client renders the live line two ways, both fed by the `activity/status` events:
+
+- The turn-level status label (`TurnStatus`, formerly the static "Deep diving...") shows the live line while a turn runs, keeping its sweep animation.
+- A working-line dock entry (`WorkingLine` on `conversation.input.dock`) renders the turn-end statistics (token/elapsed/tool summary) above the composer after a turn settles; live phases stay on the turn label.
+
+Both fall back to the previous static label while the plugin is absent, so the Web UI is unaffected by disabling it.
+
+## Configuration
+
+| Key | Type | Default | Meaning |
+|---|---|---|---|
+| `phrases` | `boolean` | `true` | Playful copy pool; `false` renders plain functional labels |
+| `publish` | `boolean` | `false` | Append `activity/status` session events for UI consumers. Off by default: appended events currently make session logs unresumable (see note below) |
+| `tickMs` | `number` | `500` | Status render tick interval (100–5000) |
+| `publishIntervalMs` | `number` | `2000` | Minimum interval between published events while the line is stable (500–30000) |
+| `detailLimit` | `number` | `40` | Max displayed detail length (paths/commands/patterns), 8–120 |
+| `customActions` | `object` | `{}` | Exact tool-name → action-copy pools, e.g. `{"my_deploy": ["部署一下", "上线中"]}` |
+| `narrate` | `boolean` | `true` | Inject the `⏵` self-narration contract into the system prompt; the line is surfaced live and stripped from the chat body |
+
+## Event contract
+
+`activity/status` is a log-only session event (merge-extensible `SessionEventMap` member, no `surfaceOp`):
+
+```ts
+{
+  phase: 'idle' | 'waiting' | 'thinking' | 'tool' | 'done'
+  line: string            // plain-text status line, no ANSI
+  label?: string          // current work label (tool action / stage)
+  detail?: string         // path / command / pattern fragment
+  phrase?: string         // current playful phrase
+  toolCount: number       // tools completed this turn
+  turnElapsedMs: number   // ms since turn start
+  phaseStartedAt: number  // epoch ms the phase started (animation anchor)
+}
+```
+
+> **Why `publish` is off by default:** `session.append()` cannot mark events ignorable, and the resume read path refuses any log containing unknown non-ignorable event types — so with `publish: true`, every session that rendered a status line fails to resume. Re-enable only for a log-replaying consumer on a harness that supports ignorable appends. The live TUI prompt line is unaffected.
+
+Publishing rules: line changes publish immediately; a stable line republishes at most every `publishIntervalMs` so a long tool's elapsed time stays live without flooding the log. All data is lossless JSON; optional fields are omitted when absent.
+
+## Export shape
+
+A function/namespace plugin: `name` / `Config` / `apply`, no default export. The state machine (`ActivityTracker`) and copy pools live in `./status` and `./phrases` (pure, clock-injected, unit-tested). The invariant companion registers under `./invariant`.
+
+## Model Experience
+
+### Prompt and tool surface
+
+Nothing. The plugin injects no prompt sections, registers no tools, and appends no surface events. `activity/status` is UI state only: it never enters derived model history, so the model cannot see its own working line.
+
+### Token effect
+
+Zero per request.
+
+### KV Cache effect
+
+No system-prompt contribution, so no cache-stability effect.
+
+## Known Limitations and Deferred Work
+
+- **Single active line**: the plugin keeps one status line per session; the TUI slot shows the most recently active session.
+- **Narration is opt-in**: the `⏵` self-narration contract (model writes a short status line at the top of each reply) is injected by default (`narrate: true`); set `narrate: false` for a purely event-derived line.
+- **No progress percentages**: DSH has no tool progress events; a long tool shows elapsed time only.
+- **No animated frames**: the TUI slot renders a static text fragment; frame animation (moon/comet/braille presets) is deferred until the prompt-slot contract supports a frame callback.
+- **Web dock entry duplicates the turn label**: the input-dock `WorkingLine` and the chat `TurnStatus` show the same snapshot; the dock entry exists for session views where the turn label is not visible.

package/README.zh.md

@@ -1,113 +1,113 @@
-# @deepseek-ai/dsh-working-activity
-
-[English](README.md) | 中文
-
-为 DeepSeek Harness 打造的一条实时 "工作状态行"：模型的实时活动——俏皮思考文案、真正在跑的工具、已耗时、收尾摘要——在 agent 干活时展示出来。
-
-## 功能
-
-把持久会话流（`turn/start`、`assistant/chunk`、`tool/call`、`tool/result`、`turn/end`）和 `agent/status` 折叠成一条状态行，按渲染 tick 刷新：
-
-- **思考中**：每隔几秒轮换一句短俏皮文案（`嗯…让我捋捋`、`盘一下盘一下`、`大脑转起来了`，穿插面无表情的 `lol` / `hm` / `ok`）；想久了自动分档（30 秒 / 1 分钟 / 5 分钟）；本地时间 00:00–06:00 混入深夜专属文案。
-- **工具活动**：正在运行的工具渲染为 `俏皮动词 + 参数细节 + 已耗时`（`跑个命令 npm test · 12s`）；失败工具在收尾行显示 `翻车了` 风格文案。
-- **收尾摘要**：`turn/end` 后状态行变为 `搞定 ✓ · N 工具 · 想Xs 干Ys`（思考/干活耗时拆分），并短暂钉住最后一个工具的片段。
-- **极简模式**：`phrases: false` 时渲染朴素功能标签（`思考中 · 总1m23s`、`bash npm test · 12s`）。
-
-两个可选出口，只有对应接缝存在时才会生效：
-
-1. **TUI prompt 槽位** —— TUI 组合存在时，在 `ctx.tuiPrompt` 上注册 `${activity}` 模板值。把 `${activity}` 加进 `theme.leftPrompt` 即可在 `cwd`/`model`/`context` 旁边看到它。
-2. **会话事件** —— 追加只记日志的 `activity/status` 事件（绝不是 surface 事件：模型永远看不到），供 Web 与其他 UI 消费；回放时忽略它们。
-
-## 安装
-
-```yaml
-# cordis.yml
-plugins:
-  - id: working-activity
-    name: '@deepseek-ai/dsh-working-activity'
-```
-
-## TUI 用法
-
-与 `dsh-tui` 一起启用插件，并把槽位加进左侧 prompt 模板：
-
-```yaml
-plugins:
-  - id: tui
-    name: '@deepseek-ai/dsh-tui'
-    config:
-      theme:
-        leftPrompt: '${cwd}${git/worktree}${activity}${model}${token_meter/cache_hit_rate}${context}'
-  - id: working-activity
-    name: '@deepseek-ai/dsh-working-activity'
-```
-
-一轮进行中时，提示行显示例如 `dsh main 跑个命令 npm test · 12s deepseek-chat …`；思考时显示 `嗯…让我捋捋 · 总1m23s`；收尾后短暂显示 `搞定 ✓ · 4 工具 · 想12s 干11s`。模板里没有 `${activity}` 时，插件在 TUI 中不产生任何效果（槽位未注册的值会被模板渲染器省略）。
-
-## Web 用法
-
-Web 客户端通过 `activity/status` 事件以两种方式渲染实时状态行：
-
-- 回合级状态标签（`TurnStatus`，原先是静态的 "Deep diving..."）：回合进行中显示实时状态行，保留原有的流光扫过特效。
-- 输入区上方的状态行条目（`WorkingLine`，挂在 `conversation.input.dock`）：回合结束后渲染收工统计（token/耗时/工具摘要）；活动阶段只在轮辑标签上显示。
-
-插件缺席时两者都回退到原来的静态标签，禁用插件不影响 Web UI。
-
-## 配置
-
-| 键 | 类型 | 默认值 | 含义 |
-|---|---|---|---|
-| `phrases` | `boolean` | `true` | 俏皮文案池；`false` 渲染朴素功能标签 |
-| `publish` | `boolean` | `false` | 为 UI 消费者追加 `activity/status` 会话事件。默认关闭：追加的事件目前会导致会话日志无法 resume（见下方说明） |
-| `tickMs` | `number` | `500` | 状态渲染 tick 间隔（50–5000） |
-| `publishIntervalMs` | `number` | `2000` | 状态行稳定时两次发布事件的最小间隔（500–30000） |
-| `detailLimit` | `number` | `40` | 详情最大展示长度（路径/命令/模式），8–120 |
-| `customActions` | `object` | `{}` | 工具名精确匹配 → 动作文案池，如 `{"my_deploy": ["部署一下", "上线中"]}` |
-| `narrate` | `boolean` | `true` | 向 system prompt 注入 `⏵` 自述约定；该行实时展示并从聊天正文中过滤 |
-
-## 事件契约
-
-`activity/status` 是只记日志的会话事件（merge 可扩展的 `SessionEventMap` 成员，无 `surfaceOp`）：
-
-```ts
-{
-  phase: 'idle' | 'waiting' | 'thinking' | 'tool' | 'done'
-  line: string            // 纯文本状态行，无 ANSI
-  label?: string          // 当前工作标签（工具动作/阶段）
-  detail?: string         // 路径 / 命令 / 模式片段
-  phrase?: string         // 当前俏皮文案
-  toolCount: number       // 本轮已完成的工具数
-  turnElapsedMs: number   // 距本轮开始毫秒数
-  phaseStartedAt: number  // 相位开始的 epoch 毫秒（动画锚点）
-}
-```
-
-> **为什么 `publish` 默认关闭：** `session.append()` 无法把事件标记为 ignorable，而 resume 的读取路径会拒绝包含未知且不可忽略事件类型的日志——开启 `publish` 后，凡是显示过状态行的会话都会 resume 失败。仅在日志重放消费者、且 harness 支持 ignorable append 时再打开。TUI 实时状态行不受影响。
-
-发布规则：状态行变化立即发布；稳定行最多每 `publishIntervalMs` 重发一次，让长工具的已耗时保持实时而不刷爆日志。所有数据都是无损 JSON；可选字段缺省时省略。
-
-## 导出形状
-
-函数/命名空间插件：`name` / `Config` / `apply`，无默认导出。状态机（`ActivityTracker`）与文案池在 `./status` 和 `./phrases`（纯逻辑、时钟注入、有单测）。不变量伴生插件在 `./invariant` 注册。
-
-## Model Experience
-
-### 提示词与工具面
-
-没有。插件不注入任何提示词段、不注册任何工具、不追加任何 surface 事件。`activity/status` 只是 UI 状态：永不进入派生模型历史，模型看不到自己的工作状态行。
-
-### Token 影响
-
-每次请求为零。
-
-### KV 缓存影响
-
-不贡献 system prompt，因此无缓存稳定性影响。
-
-## Known Limitations and Deferred Work
-
-- **单条活跃状态行**：插件按会话维护一条状态行；TUI 槽位显示最近活跃会话。
-- **自述可选**：`⏵` 模型自述约定（每次回复顶部写一行短状态文案）默认注入（`narrate: true`）；设 `narrate: false` 则只由事件推导。
-- **无进度百分比**：DSH 没有工具进度事件；长工具只显示已耗时。
-- **无动画帧**：TUI 槽位渲染静态文本片段；帧动画（moon/comet/braille 预设）要等 prompt 槽位契约支持帧回调后再做。
-- **Web 双入口重复显示**：输入区 `WorkingLine` 与聊天区 `TurnStatus` 显示同一快照；dock 条目用于回合标签不可见的会话视图。
+# @deepseek-ai/dsh-working-activity
+
+[English](README.md) | 中文
+
+为 DeepSeek Harness 打造的一条实时 "工作状态行"：模型的实时活动——俏皮思考文案、真正在跑的工具、已耗时、收尾摘要——在 agent 干活时展示出来。
+
+## 功能
+
+把持久会话流（`turn/start`、`assistant/chunk`、`tool/call`、`tool/result`、`turn/end`）和 `agent/status` 折叠成一条状态行，按渲染 tick 刷新：
+
+- **思考中**：每隔几秒轮换一句短俏皮文案（`嗯…让我捋捋`、`盘一下盘一下`、`大脑转起来了`，穿插面无表情的 `lol` / `hm` / `ok`）；想久了自动分档（30 秒 / 1 分钟 / 5 分钟）；本地时间 00:00–06:00 混入深夜专属文案。
+- **工具活动**：正在运行的工具渲染为 `俏皮动词 + 参数细节 + 已耗时`（`跑个命令 npm test · 12s`）；失败工具在收尾行显示 `翻车了` 风格文案。
+- **收尾摘要**：`turn/end` 后状态行变为 `搞定 ✓ · N 工具 · 想Xs 干Ys`（思考/干活耗时拆分），并短暂钉住最后一个工具的片段。
+- **极简模式**：`phrases: false` 时渲染朴素功能标签（`思考中 · 总1m23s`、`bash npm test · 12s`）。
+
+两个可选出口，只有对应接缝存在时才会生效：
+
+1. **TUI prompt 槽位** —— TUI 组合存在时，在 `ctx.tuiPrompt` 上注册 `${activity}` 模板值。把 `${activity}` 加进 `theme.leftPrompt` 即可在 `cwd`/`model`/`context` 旁边看到它。
+2. **会话事件** —— 追加只记日志的 `activity/status` 事件（绝不是 surface 事件：模型永远看不到），供 Web 与其他 UI 消费；回放时忽略它们。
+
+## 安装
+
+```yaml
+# cordis.yml
+plugins:
+  - id: working-activity
+    name: '@deepseek-ai/dsh-working-activity'
+```
+
+## TUI 用法
+
+与 `dsh-tui` 一起启用插件，并把槽位加进左侧 prompt 模板：
+
+```yaml
+plugins:
+  - id: tui
+    name: '@deepseek-ai/dsh-tui'
+    config:
+      theme:
+        leftPrompt: '${cwd}${git/worktree}${activity}${model}${token_meter/cache_hit_rate}${context}'
+  - id: working-activity
+    name: '@deepseek-ai/dsh-working-activity'
+```
+
+一轮进行中时，提示行显示例如 `dsh main 跑个命令 npm test · 12s deepseek-chat …`；思考时显示 `嗯…让我捋捋 · 总1m23s`；收尾后短暂显示 `搞定 ✓ · 4 工具 · 想12s 干11s`。模板里没有 `${activity}` 时，插件在 TUI 中不产生任何效果（槽位未注册的值会被模板渲染器省略）。
+
+## Web 用法
+
+Web 客户端通过 `activity/status` 事件以两种方式渲染实时状态行：
+
+- 回合级状态标签（`TurnStatus`，原先是静态的 "Deep diving..."）：回合进行中显示实时状态行，保留原有的流光扫过特效。
+- 输入区上方的状态行条目（`WorkingLine`，挂在 `conversation.input.dock`）：回合结束后渲染收工统计（token/耗时/工具摘要）；活动阶段只在轮辑标签上显示。
+
+插件缺席时两者都回退到原来的静态标签，禁用插件不影响 Web UI。
+
+## 配置
+
+| 键 | 类型 | 默认值 | 含义 |
+|---|---|---|---|
+| `phrases` | `boolean` | `true` | 俏皮文案池；`false` 渲染朴素功能标签 |
+| `publish` | `boolean` | `false` | 为 UI 消费者追加 `activity/status` 会话事件。默认关闭：追加的事件目前会导致会话日志无法 resume（见下方说明） |
+| `tickMs` | `number` | `500` | 状态渲染 tick 间隔（50–5000） |
+| `publishIntervalMs` | `number` | `2000` | 状态行稳定时两次发布事件的最小间隔（500–30000） |
+| `detailLimit` | `number` | `40` | 详情最大展示长度（路径/命令/模式），8–120 |
+| `customActions` | `object` | `{}` | 工具名精确匹配 → 动作文案池，如 `{"my_deploy": ["部署一下", "上线中"]}` |
+| `narrate` | `boolean` | `true` | 向 system prompt 注入 `⏵` 自述约定；该行实时展示并从聊天正文中过滤 |
+
+## 事件契约
+
+`activity/status` 是只记日志的会话事件（merge 可扩展的 `SessionEventMap` 成员，无 `surfaceOp`）：
+
+```ts
+{
+  phase: 'idle' | 'waiting' | 'thinking' | 'tool' | 'done'
+  line: string            // 纯文本状态行，无 ANSI
+  label?: string          // 当前工作标签（工具动作/阶段）
+  detail?: string         // 路径 / 命令 / 模式片段
+  phrase?: string         // 当前俏皮文案
+  toolCount: number       // 本轮已完成的工具数
+  turnElapsedMs: number   // 距本轮开始毫秒数
+  phaseStartedAt: number  // 相位开始的 epoch 毫秒（动画锚点）
+}
+```
+
+> **为什么 `publish` 默认关闭：** `session.append()` 无法把事件标记为 ignorable，而 resume 的读取路径会拒绝包含未知且不可忽略事件类型的日志——开启 `publish` 后，凡是显示过状态行的会话都会 resume 失败。仅在日志重放消费者、且 harness 支持 ignorable append 时再打开。TUI 实时状态行不受影响。
+
+发布规则：状态行变化立即发布；稳定行最多每 `publishIntervalMs` 重发一次，让长工具的已耗时保持实时而不刷爆日志。所有数据都是无损 JSON；可选字段缺省时省略。
+
+## 导出形状
+
+函数/命名空间插件：`name` / `Config` / `apply`，无默认导出。状态机（`ActivityTracker`）与文案池在 `./status` 和 `./phrases`（纯逻辑、时钟注入、有单测）。不变量伴生插件在 `./invariant` 注册。
+
+## Model Experience
+
+### 提示词与工具面
+
+没有。插件不注入任何提示词段、不注册任何工具、不追加任何 surface 事件。`activity/status` 只是 UI 状态：永不进入派生模型历史，模型看不到自己的工作状态行。
+
+### Token 影响
+
+每次请求为零。
+
+### KV 缓存影响
+
+不贡献 system prompt，因此无缓存稳定性影响。
+
+## Known Limitations and Deferred Work
+
+- **单条活跃状态行**：插件按会话维护一条状态行；TUI 槽位显示最近活跃会话。
+- **自述可选**：`⏵` 模型自述约定（每次回复顶部写一行短状态文案）默认注入（`narrate: true`）；设 `narrate: false` 则只由事件推导。
+- **无进度百分比**：DSH 没有工具进度事件；长工具只显示已耗时。
+- **无动画帧**：TUI 槽位渲染静态文本片段；帧动画（moon/comet/braille 预设）要等 prompt 槽位契约支持帧回调后再做。
+- **Web 双入口重复显示**：输入区 `WorkingLine` 与聊天区 `TurnStatus` 显示同一快照；dock 条目用于回合标签不可见的会话视图。

package/cordis.patch.yml

@@ -1,19 +1,19 @@
-# dsh-working-activity bundle patch: mount the plugin itself into the
-# profile composition tree.
-#
-# `dsh plugin --profile <name> add dsh-working-activity` auto-initializes the
-# profile (first layer @deepseek-ai/dsh-base), pnpm-installs this package into
-# the profile, and the CLI's reconcile step appends it to the profile's
-# dsh.profile.bundles because this package.json declares `dsh.bundle.patch`.
-# At boot, app-boot applies every bundle's patch list in bundle order over the
-# empty root; this insert list is what actually mounts the working-activity
-# row — no manual configuration is needed.
-#
-# All row config stays at schema defaults (phrases/publish/tickMs/
-# publishIntervalMs/detailLimit/customActions/narrate). To tune a value (for
-# dsh-cc, set publishIntervalMs to 500), override this row's config by id in
-# the profile's own cordis.patch.yml user layer — do NOT insert a second
-# same-id row.
-- insert:
-    - id: working-activity
-      name: 'dsh-working-activity'
+# dsh-working-activity bundle patch: mount the plugin itself into the
+# profile composition tree.
+#
+# `dsh plugin --profile <name> add dsh-working-activity` auto-initializes the
+# profile (first layer @deepseek-ai/dsh-base), pnpm-installs this package into
+# the profile, and the CLI's reconcile step appends it to the profile's
+# dsh.profile.bundles because this package.json declares `dsh.bundle.patch`.
+# At boot, app-boot applies every bundle's patch list in bundle order over the
+# empty root; this insert list is what actually mounts the working-activity
+# row — no manual configuration is needed.
+#
+# All row config stays at schema defaults (phrases/publish/tickMs/
+# publishIntervalMs/detailLimit/customActions/narrate). To tune a value (for
+# dsh-cc, set publishIntervalMs to 500), override this row's config by id in
+# the profile's own cordis.patch.yml user layer — do NOT insert a second
+# same-id row.
+- insert:
+    - id: working-activity
+      name: 'dsh-working-activity'

package/lib/client.js

@@ -6,7 +6,7 @@ window.__ModuleLoader__.load({
 		Object.defineProperty(exports, Symbol.toStringTag, { value: "Module" });
 		let react_jsx_runtime = require("react/jsx-runtime");
 		//#region \0dsh-css:src/client/WorkingLine.module.css.mjs
-		const css = ".KySvIG_line{box-sizing:border-box;width:100%;max-width:var(--dsh-composer-card-max-width);font-family:var(--dsw-font-family);color:var(--dsw-alias-label-secondary);align-items:center;gap:8px;margin:0 auto;padding:4px 16px 0;font-size:13px;line-height:18px;display:flex}.KySvIG_marker{background:var(--dsw-alias-label-tertiary);border-radius:50%;flex:none;width:7px;height:7px;animation:1.6s ease-in-out infinite KySvIG_working-pulse}.KySvIG_line[data-activity-phase=done] .KySvIG_marker{background:var(--dsw-alias-state-business-primary);animation:none}.KySvIG_line[data-activity-phase=tool] .KySvIG_marker{background:var(--dsw-alias-state-business-primary)}.KySvIG_line[data-activity-phase=waiting] .KySvIG_marker{background:var(--dsw-alias-label-tertiary);opacity:.6}.KySvIG_text{text-overflow:ellipsis;white-space:nowrap;overflow:hidden}.KySvIG_tools{background:var(--dsw-alias-surface-tertiary);min-width:18px;color:var(--dsw-alias-label-secondary);text-align:center;border-radius:9px;flex:none;padding:0 5px;font-size:11px;line-height:18px}@keyframes KySvIG_working-pulse{0%,to{opacity:1}50%{opacity:.35}}";
+		const css = ".TG_uoa_line{box-sizing:border-box;width:100%;max-width:var(--dsh-composer-card-max-width);font-family:var(--dsw-font-family);color:var(--dsw-alias-label-secondary);align-items:center;gap:8px;margin:0 auto;padding:4px 16px 0;font-size:13px;line-height:18px;display:flex}.TG_uoa_marker{background:var(--dsw-alias-label-tertiary);border-radius:50%;flex:none;width:7px;height:7px;animation:1.6s ease-in-out infinite TG_uoa_working-pulse}.TG_uoa_line[data-activity-phase=done] .TG_uoa_marker{background:var(--dsw-alias-state-business-primary);animation:none}.TG_uoa_line[data-activity-phase=tool] .TG_uoa_marker{background:var(--dsw-alias-state-business-primary)}.TG_uoa_line[data-activity-phase=waiting] .TG_uoa_marker{background:var(--dsw-alias-label-tertiary);opacity:.6}.TG_uoa_text{text-overflow:ellipsis;white-space:nowrap;overflow:hidden}.TG_uoa_tools{background:var(--dsw-alias-surface-tertiary);min-width:18px;color:var(--dsw-alias-label-secondary);text-align:center;border-radius:9px;flex:none;padding:0 5px;font-size:11px;line-height:18px}@keyframes TG_uoa_working-pulse{0%,to{opacity:1}50%{opacity:.35}}";
 		const tagId = "dsh-working-activity/WorkingLine.module.css";
 		if (typeof document !== "undefined" && document.querySelector("style[data-plugin-css=" + JSON.stringify(tagId) + "]") === null) {
 			const tag = document.createElement("style");
@@ -16,11 +16,11 @@ window.__ModuleLoader__.load({
 			document.head.appendChild(tag);
 		}
 		var WorkingLine_module_css_default = {
-			"working-pulse": "KySvIG_working-pulse",
-			"text": "KySvIG_text",
-			"marker": "KySvIG_marker",
-			"tools": "KySvIG_tools",
-			"line": "KySvIG_line"
+			"working-pulse": "TG_uoa_working-pulse",
+			"tools": "TG_uoa_tools",
+			"line": "TG_uoa_line",
+			"text": "TG_uoa_text",
+			"marker": "TG_uoa_marker"
 		};
 		//#endregion
 		//#region src/client/WorkingLine.tsx