dsh-human-wait 0.2.2 → 0.2.3

package/CHANGELOG.md

@@ -1,5 +1,15 @@
 # Changelog
 
+## 0.2.3 — 2026-11-15
+
+Documentation only, no behaviour change.
+
+- The opening line states the scope and the outcome (only in PTC mode; the 120-second deadline
+  pauses while DSH waits for you) instead of saying a timeout counts down.
+- The FAQ keeps only questions readers actually ask. The defensive "does it affect standard
+  sessions?" entry is gone: the scope already says PTC mode, so there is nothing to warn about.
+- Plain wording throughout, including the "it still timed out" checklist and the privacy note.
+
 ## 0.2.2 — 2026-11-15
 
 - Rewrote the README for users: when the plugin helps, what it does and does not change (a table

package/README.en.md

@@ -1,14 +1,14 @@
 # dsh-human-wait
 
-**Stops the PTC `run_code` deadline while DSH is waiting for you.**
+**PTC mode only: while DSH is waiting for you — a question, a plan review, an approval — the 120-second deadline pauses, so thinking longer no longer ends the run.**
 
-PTC mode wraps the whole program — including any question, plan review or approval raised mid-run — in one 120-second wall clock. Think a little too long and the run is already gone:
+PTC mode (the agent writes a short program with `run_code` and runs it as the task) puts one 120-second deadline around the whole program, and the questions, plan reviews and approvals raised in the middle count against it. Think for three minutes and you come back to:
 
 ```
 Error: code run failed (timeout): execution deadline reached (120000ms)
 ```
 
-and the question card is reported as **interrupted**. With this plugin, the time you spend answering is no longer charged to that budget; a runaway program is still cut off when the budget runs out.
+and the question card is reported as **interrupted**. With this plugin, the time you spend replying no longer counts against that deadline, and it waits for you up to the cap you set (24 hours by default); a runaway program is still cut off at the mark.
 
 > English | [中文](README.md)
 
@@ -45,11 +45,9 @@ A change takes effect in about 1.5 seconds, no restart.
 
 ## FAQ
 
-**It still timed out?** Check three things: the session header shows the `PTC` badge; the plugin's `enabled` is not set to false in the profile patch; the log has a line starting with `[dsh-human-wait]`. If the wrapper did not see that wait, it cannot pause for it.
+**It still timed out?** Check three things: the session header shows the `PTC` badge; the plugin is enabled; the plugin was running when that wait happened. If any of the three is missing, it cannot pause the clock for you.
 
-**The error kind became `abort`?** Expected. The plugin aborts through its own signal, so the runtime classifies it as `abort` instead of `timeout`; the text still contains `execution deadline reached`.
-
-**Does it affect standard sessions?** No. Standard sessions never had this timeout — they wait indefinitely by design.
+**The error kind became `abort`?** Expected. The plugin stops the run itself, so the type reads `abort` instead of `timeout`; the text still contains `execution deadline reached`.
 
 ## Privacy and cost
 

package/README.md

@@ -1,14 +1,14 @@
 # dsh-human-wait
 
-**PTC 模式下，DSH 在等你回答问题时，不再让执行超时继续倒数。**
+**只在 PTC 模式下起作用：DSH 等你回话的时候（回答问题、确认计划、批准操作），那条 120 秒的限时暂停，不会因为你想得久就超时。**
 
-PTC（`run_code`）把整个程序——包括中途弹出的问题、计划审批、权限批准——包在一条 120 秒的墙钟预算里。你想久一点再回答，程序就已经超时了：
+PTC 模式（让智能体用 `run_code` 写段程序去跑任务）会给整段程序一条 120 秒的限时，中途弹给你的问题、计划审批、权限批准，都算在这条限时里。你多想了三分钟，回来就看到：
 
 ```
 Error: code run failed (timeout): execution deadline reached (120000ms)
 ```
 
-问题卡还会被标成「已中断」。装上这个插件，等待你回答的那段时间不再计入预算；程序自己跑飞了，照样在预算到点时被掐断。
+问题卡还会被标成「已中断」。装上这个插件，等你回话的那段时间不再算进去；最多等到你设的上限（默认 24 小时），程序自己跑飞了照样到点就被掐断。
 
 > [English](README.en.md) | 中文
 
@@ -45,16 +45,13 @@ Error: code run failed (timeout): execution deadline reached (120000ms)
 
 ## 常见问题
 
-**还是超时了？** 确认三件事：会话头部显示 PTC 标记；插件的 `enabled` 没在 profile 补丁里被关掉；日志里有 `[dsh-human-wait]` 开头的那行说明。如果等待期间恰好插件没看到这次等待，它就不会暂停计时。
+**还是超时了？** 看三处：会话头部有 PTC 标记；插件处于启用状态；等待发生的时候插件确实在运行。三者有一个不成立，它就没法替你暂停计时。
 
-**错误类型变成 `abort` 了？** 正常。插件用自己的信号中止程序，所以 kind 从 `timeout` 变成 `abort`，提示文字里仍然有 `execution deadline reached`。
-
-**普通会话受影响吗？** 不受影响。普通会话本来就会一直等你回答，没有这个超时。
+**报错变成 `abort` 了？** 正常。插件是自己主动叫停的，所以类型标成 `abort` 而不是 `timeout`，提示文字里照样有 `execution deadline reached`。
 
 ## 隐私与开销
 
-- 只在内存里包住三个宿主服务的调用，不写文件、不联网
-- 不修改会话内容，也不改变程序本身的执行预算
+它只是在内存里接管了三处「等你回答」的等待，不写文件、不联网，也不改会话内容。卸载并重启后，DSH 原来的行为就回来了。
 
 ## 卸载
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-human-wait",
-  "version": "0.2.2",
+  "version": "0.2.3",
   "description": "Pauses the PTC run_code deadline while DSH is waiting for you to answer a question, review a plan or approve a request, so long human waits are no longer reported as `execution deadline reached (120000ms)`.",
   "license": "MIT",
   "author": {