DispatchDock v0.1.4

改动 / Changes

• 回到会话时可以查任务结果。 新增 --wait [记录名]：会话关掉后再回来，任务还在跑就接着等，已经结束就立刻返回结果。只读，不会重新派发。
  Check a task after coming back. New --wait [run name]: after reopening a session, it keeps waiting if the task is still running, or returns the result right away if it has finished. Read-only; it never dispatches again.
• 托管提示用接手软件的名字。 其他监控软件按文件协议接手托管时，提示里写的是它自己的名字，不再一律写 DispatchDock。
  Managed-mode messages name the app that took over. When another monitor takes over a task through the file protocol, the message uses its name instead of always saying DispatchDock.
• codex-dispatch：Codex 结束后，看汇报、diff 和验收产物；汇报说测试已通过的不再重跑，只抽查。
  codex-dispatch: after Codex finishes, review the report, the diff and the acceptance artifacts; tests the report says passed are spot-checked, not rerun.
• dual-role-workflow：减少过度验证。测试只给共享核心写，一次性的生产任务不新写测试；验收产物以截图、渲染短片、试听文件、可点的预览为主，不另建测试体系；设计负责人改完审美部分看一眼产物就提交。生成的工程角色文档写明完整测试只在改了共享核心时最后跑一次、只做任务说明里列出的验证；设计角色文档多一节"验收怎么写"。
  dual-role-workflow: less over-verification. Tests are written only for the shared core, not for one-off production tasks; acceptance relies on screenshots, short renders, audio samples and clickable previews rather than a separate test suite; the design lead commits aesthetic tweaks after a look at the output. The generated engineering role doc runs the full suite only once, at the end, when the shared core changed, and does only the checks the task spec lists; the design role doc gains a "how to write acceptance" section.

装了软件的：在"连接"页更新技能。只装技能的：用新的压缩包重新运行 node installer/install.mjs。两种都会先备份。
App users: update the skills on the Connections page. Skills-only users: rerun node installer/install.mjs from the new zip. Both back up first.

SHA-256

3d11ba21bb2aeb6f26ee11f89b2fe197a1ac849a048ca6b69de3ff79f9244a50  DispatchDock-Setup-0.1.4-x64.exe
2b766c8b72686ebf8a95dbf59103e74dc3f6c42debf2a732e4e431fb21cc2cf0  dispatchdock-skills-0.1.4.zip