xxachangxx
a4878656e2
* 修复 Pi 恢复子任务的状态和对话跟踪
关联 #9200。
改动：
- 仅在 action:resume 确认成功启动新的 single async run 后登记独立子任务条目，按新 run ID 和 asyncDir 跟踪状态，拒绝失败及管理调用产生的假条目。
- 将对话去重从文件级调整为子任务条目与文件组合，支持恢复运行复用 session JSONL，避免旧通知结束新运行。
- 扩展原适配器回归测试，并附脱敏的命令输出、真实工具结果和 macOS Electron 截图，未改 UI、协议或共享生命周期。
实际验证：
- 原适配器下恢复条目回归为 RED；恢复旧文件级去重后共享对话回归为 RED。
- 基线 d46ee6558c 上 npm run build:server、npm run format、npm run typecheck、npm run lint、git diff --check 均成功。
- 在 packages/server 执行 npx vitest run src/server/agent/providers/pi/extensions/pi-subagents/index.test.ts --bail=1，21/21 通过。
- 已在此前 0.15.3 开发版中，通过真实 macOS Electron、Pi 1.5.0、pi-subagents 0.86.0 验证 A→B→C 恢复、运行条目和对话、完成状态、归档保留运行任务、失败恢复不产生假条目；普通启动走 CLI/API，恢复通过真实 composer。截图不是 0.15.4 发布包验收。
- 同步后适配器与测试文件字节和第三方锁定依赖均未变，复用独立代码评审与上述桌面证据。公开材料已做隐私扫描。
- 未执行全量测试（仓库禁止本地全量执行）、CI、其他平台或发布安装包验证；短暂重复 Shell 文案原因未定位，不宣称本次修复。
回滚：
- 本提交仍为 HEAD 时执行 git revert HEAD；否则先用 git log --oneline --grep='修复 Pi 恢复子任务的状态和对话跟踪' 确认本提交哈希，再 git revert <确认的哈希>，不要重置或覆盖其他修改。
- 回滚后重跑该适配器测试并执行 npm run build:server；若需要部署回滚产物，另行安排服务切换，禁止未经授权重启正在使用的 Paseo daemon。
- 本提交仅改源码、测试和 QA 证据，无数据迁移；回滚不应删除已有 Pi 会话或异步目录。独立 QA 服务不由本提交启停。
* 补强 Pi 恢复对话的新消息与实时回放断言
回应 PR #9261 的 Greptile P2 评论 discussion_r4521416122。
改动：
- 只修改 pi-subagents/index.test.ts，按子任务 ID 提取 assistant_message 文本，精确检查 C 的历史与本轮内容。
- 观察 C reader 初始读取后再追加消息，在写入终态前验证新消息实时到达且 C 仍运行，避免只靠完成时刷新通过。
- 回放精确校验三条预期消息、顺序与 resume-c 归属，保留旧通知隔离、完成状态和 bg_wait 断言。
- 不修改生产实现、历史 QA 证据或普通启动行为。
实际验证：
- 临时在测试观察回调中丢弃 C 本轮消息：定向测试 exit 1，只有 Attempt b 的历史不能通过初始断言。
- 临时只丢弃 C 后追加消息：定向测试 exit 1，缺少 Attempt c follow-up 的断言在写入完成状态前失败。
- 两次故障注入已移除；最终在 packages/server 执行 npx vitest run src/server/agent/providers/pi/extensions/pi-subagents/index.test.ts --bail=1，21/21 通过。
- npm run format、npm run typecheck、npm run lint 和 git diff --check 均通过；全仓 lint 为 0 warnings / 0 errors。
- LSP 推断项目模式仅报告未修改旧测试行的两处 results 类型警告；项目正式 typecheck 通过。
- 未运行全量测试、远端 CI 或重复桌面验收。本次只有测试变更，复用原产品评审和真实桌面验证，不将临时故障注入当作生产缺陷。
回滚：
- 本提交仍为 HEAD 时执行 git revert HEAD；否则用 git log --oneline --grep='补强 Pi 恢复对话的新消息与实时回放断言' 确认哈希后 git revert <该哈希>。
- 回滚后重跑上述适配器测试；这只撤销测试增强，不应回滚先前 #9200 产品修复，也无需重启 daemon 或删除任何会话数据。
Pi resumed subagents — #9200
Scope and provenance
An AI agent ran this QA through Playwright/CDP attached to the real macOS Electron renderer, using an isolated desktop-managed daemon. The user authorized the run; this is not a claim that the user personally operated the UI. No production daemon, installed package, or daily host configuration was changed.
Desktop evidence was captured on the modified 0.15.3 development checkout at base e260f93cc7b6098f6b175bd0e5c7eb24d3f03cf4, with Electron 44.2.0, Pi 1.5.0, and installed pi-subagents 0.86.0. The final branch was subsequently fast-forwarded to d46ee6558c043f9fb377d20f05ff662ce27a31f6 (0.15.4). The adapter and test file stayed byte-for-byte identical. The lockfile changes only workspace version references; third-party dependency entries did not change. Server declarations were rebuilt and the checks below passed on the final base. These screenshots are not a 0.15.4 release-package test.
Before and automated checks
Issue #9200 reports ordinary async spawn appearing in the track while successive successful resumes disappear. The original adapter rejects any action and requires top-level agent/task, which a resume does not supply. A separate file-only transcript deduplication also prevents a new attempt row from following Pi's reused session file.
Captured command output contains:
- RED on the original adapter: a successful resume returns no descriptor instead of a running row.
- RED on the intermediate implementation with old file-only deduplication: the next resumed row gets no transcript.
- Final 21/21 tests passing, including consecutive resumes with a real shared temporary JSONL, polling, notice/replay routing, late old-notice isolation,
bg_wait, failed/management calls, missing launch identity, and the task alias. Existing spawn fixtures still pass. - Full
npm run format,npm run typecheck,npm run lint, andgit diff --checkpassing after the base update.
Only the specific adapter test file was run, not the full suite. CI has not been run. There is no old-desktop before screenshot; the reported failure and the two actual RED runs are the before evidence.
Real desktop steps and observations
- Built server/app dependencies and launched the existing desktop dev runner with a separate home, Electron userData, Pi configuration/session directory, and async root. The final endpoints were loopback-only: daemon 6768, Metro 8082, and CDP 9223. The renderer's desktop bridge confirmed its own managed daemon/home/server identity. Only the existing pi-subagents extension and a marker-only test agent were enabled; child tasks used
sleep/printf, not workspace edits. - Created a Pi parent through the normal Paseo CLI/API, asking it to call
subagent({agent:"qa-marker", task, async:true}). This produced A. The model first enabled the subagent tool, then performed the ordinary spawn. This step was not submitted through the composer. - Used the real Electron composer to ask Pi for
subagent({action:"resume", id:A, message}), then resumed B the same way to produce C. No top-levelagent,task, orasyncwas supplied to these resume calls. All three finished with their requested markers. - Opened the provider-owned track while C ran: it showed
1 working, the follow-up description, andqa-marker. Opening that row showed the reused child conversation and the current Shell call. Each resume had a new run/async directory, while all attempts reused the same session JSONL. - While C was still running, clicked Archive finished subagents. Completed A/B rows disappeared, while C remained visible as
1 working. - Submitted a nonexistent resume ID through the composer. Pi returned an error and the parent reported “not found”; no new row or async run appeared.
- The first B screenshot was taken after B finished because screenshot capture waited for fonts. It is not offered as running-state proof. A supplementary real resume from A, B_OBSERVE, was captured as
1 workingand opened successfully. It also finished. The final track contained exactly the four successful runs, not a fifth phantom from the failed resume.
The selected real tool arguments/results, final statuses, and four completion notices preserve the test UUIDs. B's revivedFrom is A; C's is B. This file contains selected fields from persisted Pi entries/status files, not synthesized launch details. The dialogue DOM excerpt records opening a resumed child. Test-root paths are replaced with <QA_ROOT> and the encoded workspace directory with <QA_WORKSPACE>; no auth or models configuration is included.
Screenshots
Unmodified captures, except for the explicitly described dialogue crop. They contain only isolated test prompts, test UUIDs, and app UI; no account, credentials, or user-home paths.
C running in the native provider-owned track:
After archiving finished rows, C remains running:
Opened C conversation, current Shell call and parent link: this is an unaltered crop of the bottom 880×245 pixels of the real child-pane capture, omitting the long temporary session path above it. No state was redrawn.
Final four completed rows, with the failed resume reported above:
Coverage and limits
| Surface | Tested |
|---|---|
| macOS Electron development desktop | Yes — real renderer, composer, track, child pane, archive-finished action |
| Pi RPC / Paseo WebSocket / daemon | Yes — real provider calls and persisted tool results/notices |
| Standalone browser web | No |
| iOS / Android | No |
| Windows / Linux desktop | No |
| Packaged release / CI | No |
Each resumed attempt intentionally gets its own row and reads the whole reused child transcript, including earlier history; it does not slice history by attempt. Old-notice isolation is also covered by the automated regression and the earlier real-notice host replay, rather than forcing a delayed notification in the desktop run.
Short-lived duplicate Shell text was observed in the streaming child pane; its cause was not established and it is not claimed fixed here. The earlier direct-SDK smoke's turn-end persistence error did not recur through this normal RPC run. All four test runners exited, the parent settled idle, and the temporary workspace stayed empty. No claims are made about old workflow issues or daemon-restart global adoption.