patchwarden 0.6.1 → 0.6.4

package/PatchWarden-Control-Tray.cmd

@@ -0,0 +1,11 @@
+@echo off
+setlocal
+cd /d "%~dp0"
+if /i "%~1"=="--foreground" (
+  powershell.exe -NoProfile -ExecutionPolicy Bypass -File "%~dp0scripts\control\control-center-tray.ps1" %*
+  set EXITCODE=%ERRORLEVEL%
+  endlocal & exit /b %EXITCODE%
+)
+
+start "" powershell.exe -NoProfile -ExecutionPolicy Bypass -WindowStyle Hidden -File "%~dp0scripts\control\control-center-tray.ps1" %*
+endlocal & exit /b 0

package/PatchWarden-Control.cmd

@@ -0,0 +1,6 @@
+@echo off
+setlocal
+cd /d "%~dp0"
+powershell -ExecutionPolicy Bypass -NoProfile -File "%~dp0scripts\control\start-control-center.ps1" %*
+set EXITCODE=%ERRORLEVEL%
+endlocal & exit /b %EXITCODE%

package/PatchWarden-Desktop.cmd

@@ -0,0 +1,5 @@
+@echo off
+setlocal
+cd /d "%~dp0"
+start "" powershell.exe -NoProfile -ExecutionPolicy Bypass -WindowStyle Hidden -File "%~dp0scripts\control\control-center-tray.ps1" %*
+endlocal & exit /b 0

package/PatchWarden.cmd

@@ -20,7 +20,7 @@ set "HTTPS_PROXY=%PATCHWARDEN_PROXY_URL%"
 set "ALL_PROXY=%PATCHWARDEN_PROXY_URL%"
 set "NO_PROXY=localhost,127.0.0.1,::1"
 
-set "SCRIPTS_DIR=%~dp0scripts"
+set "SCRIPTS_DIR=%~dp0scripts\control"
 set "MANAGER=%SCRIPTS_DIR%\manage-patchwarden.ps1"
 
 if not exist "%MANAGER%" (

package/README.en.md

@@ -8,16 +8,19 @@
 [![Node.js](https://img.shields.io/badge/Node.js-%3E%3D18-339933.svg)](https://nodejs.org/)
 [![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE)
 
-Current stable release: **v0.6.0**. See the
-[release notes](docs/release-v0.6.0.md),
+Current stable release: **v0.6.4**. See the
+[release notes](docs/release-v0.6.4.md),
 [migration guide](docs/migration-from-safe-bifrost.md), and
-[GitHub Release](https://github.com/jiezeng2004-design/PatchWarden/releases/tag/v0.6.0).
+[GitHub Release](https://github.com/jiezeng2004-design/PatchWarden/releases/tag/v0.6.4).
 
-PatchWarden is a security-focused MCP bridge for local coding agents.
-ChatGPT, Codex, OpenCode, or another MCP client can plan and review work;
+PatchWarden is a local-first MCP safety and verification layer for AI coding
+agents, with workspace confinement, command allowlists, scope-violation
+detection, and auditable task evidence.
+
+ChatGPT, Codex, OpenCode, or another MCP client can plan and review work.
 PatchWarden stores that plan as a workspace-scoped task, lets a preconfigured
-local agent execute it, and returns results, diffs, and independent
-verification evidence.
+local agent execute it, and returns results, diffs, artifact manifests, and
+independent verification evidence.
 
 ![PatchWarden ChatGPT connector demo](docs/assets/patchwarden-chatgpt-demo.svg)
 
@@ -30,6 +33,8 @@ verification evidence.
 ## Contents
 
 - [What PatchWarden solves](#what-patchwarden-solves)
+- [How PatchWarden differs](#how-patchwarden-differs)
+- [Evidence example](#evidence-example)
 - [Runtime architecture](#runtime-architecture)
 - [Requirements](#requirements)
 - [Five-minute quick start](#five-minute-quick-start)
@@ -77,6 +82,83 @@ PatchWarden is not designed for:
 - Managing an entire drive, home directory, or directory full of private data.
 - Unattended commits, pushes, releases, or production changes.
 
+## How PatchWarden differs
+
+PatchWarden sits between an MCP client and local coding tools. It is not a
+replacement for every adjacent layer:
+
+| Layer | Primary job | PatchWarden's role |
+| --- | --- | --- |
+| Sandbox | Isolate a process or filesystem at runtime. | Add task-level policy, evidence, verification, and review records around local agent work. |
+| Coding agent | Edit code and run local tools. | Launch only preconfigured agents with trusted argument templates and bounded repositories. |
+| Generic MCP server | Expose tools to an MCP client. | Expose a constrained task workflow instead of a broad shell or arbitrary filesystem access. |
+
+The first reusable capability to evaluate independently is:
+
+> Artifact manifest + verified completion evidence
+
+This capability is intentionally small: a task can finish with structured
+status, changed-file groups, release-artifact metadata, verification records,
+and scope-violation evidence in JSON. Other projects can inspect or adapt that
+evidence model without adopting PatchWarden's full runtime.
+
+## Evidence example
+
+A completed task writes bounded, reviewable artifacts under
+`.patchwarden/tasks/<task_id>/`. The high-signal files are:
+
+- `result.json` - final status, verification status, changed-file groups, and warnings.
+- `artifact_manifest.json` - generated artifacts with size, type, and SHA-256.
+- `verify.json` - exact verification commands and exit codes.
+- `diff.patch` - complete source diff when Git evidence is available.
+- `rollback_scope_violation_plan.md` - review plan when a task changes files outside `repo_path`.
+
+Example compact evidence:
+
+```json
+{
+  "task_id": "task_20260625_010513_ad59bb",
+  "status": "done",
+  "verify_status": "passed",
+  "changed_file_groups": {
+    "source_changes": 2,
+    "docs_changes": 1,
+    "config_changes": 0,
+    "test_changes": 1,
+    "release_artifacts": 1,
+    "runtime_generated_files": 0
+  },
+  "artifact_status": "collected",
+  "artifact_manifest": {
+    "artifacts": [
+      {
+        "path": "release/app.zip",
+        "type": "zip",
+        "size": 467725,
+        "sha256": "03731a12990718325d3cb9ecdc9dbc899fc840e8ef6e2de3e810577999b5f864"
+      }
+    ]
+  },
+  "new_out_of_scope_changes": []
+}
+```
+
+
+A scope violation remains explicit:
+
+```json
+{
+  "status": "failed_scope_violation",
+  "verify_status": "failed",
+  "new_out_of_scope_changes": [
+    {
+      "path": "external/external-renamed.txt",
+      "change": "modified"
+    }
+  ]
+}
+```
+
 ## Runtime architecture
 
 ```text
@@ -184,7 +266,7 @@ execution still requires a separate Watcher.
 New-Item -ItemType Directory .\patchwarden-runtime
 Set-Location .\patchwarden-runtime
 npm.cmd init -y
-npm.cmd install patchwarden@0.6.0
+npm.cmd install patchwarden@0.6.4
 Copy-Item .\node_modules\patchwarden\examples\config.example.json .\patchwarden.config.json
 $env:PATCHWARDEN_CONFIG = (Resolve-Path .\patchwarden.config.json)
 node .\node_modules\patchwarden\dist\runner\watch.js
@@ -193,7 +275,7 @@ node .\node_modules\patchwarden\dist\runner\watch.js
 An MCP client can launch:
 
 ```text
-npx.cmd -y patchwarden@0.6.0
+npx.cmd -y patchwarden@0.6.4
 ```
 
 Pin the version in important environments instead of using `latest`
@@ -352,7 +434,7 @@ Pinned npm configuration:
 ```toml
 [mcp_servers.patchwarden]
 command = "npx.cmd"
-args = ["-y", "patchwarden@0.6.0"]
+args = ["-y", "patchwarden@0.6.4"]
 
 [mcp_servers.patchwarden.env]
 PATCHWARDEN_CONFIG = "D:\\path\\to\\patchwarden.config.json"
@@ -412,7 +494,7 @@ PatchWarden.cmd start core
 The launcher:
 
 - Builds `dist/index.js` if it is missing.
-- Verifies v0.6.0, the fixed 16-tool `chatgpt_core` catalog, and its schema
+- Verifies v0.6.4, the fixed 17-tool `chatgpt_core` catalog, and its schema
   manifest.
 - Reads or prompts for the Tunnel ID.
 - Reads or prompts for the runtime API key.
@@ -446,7 +528,7 @@ the expanded tunnel examples.
 
 ### Launcher default
 
-`scripts/start-patchwarden-tunnel.ps1` first reads `HTTPS_PROXY` from the
+`scripts/control/start-patchwarden-tunnel.ps1` first reads `HTTPS_PROXY` from the
 current process. If it is absent, the launcher defaults to:
 
 ```text
@@ -606,6 +688,7 @@ mean the task is wrong.
 | `result.md` | Human-readable execution report. |
 | `result.json` | Structured result, paths, changes, warnings, and next steps. |
 | `diff.patch` | Complete task change evidence. |
+| `artifact_manifest.json` | Generated artifact paths, types, sizes, and SHA-256 hashes. |
 | `file-stats.json` | Per-file addition and deletion statistics. |
 | `verify.json` | Structured record for every independent verification command. |
 | `verify.log` | Human-readable independent verification output. |
@@ -695,8 +778,11 @@ available from PowerShell:
 .\PatchWarden.cmd restart all
 .\PatchWarden.cmd status all
 .\PatchWarden.cmd kill all
+.\Stop-PatchWarden.cmd
 ```
 
+For daily desktop use, start with `PatchWarden-Desktop.cmd`; it starts the tray and keeps Control Center available without opening extra browser windows. Use `PatchWarden-Control-Tray.cmd --foreground` only for tray debugging, `PatchWarden-Control.cmd` for the full local Web dashboard, and `Stop-PatchWarden.cmd` for one-click shutdown of Core/Direct, Control Center, and the tray.
+
 The old single-purpose launchers remain under `scripts/launchers/` as a
 compatibility layer. Personal launchers live under `.local/launchers/` and
 remain excluded from Git and release packages. `stop` and `restart` correlate
@@ -768,7 +854,7 @@ terminate unrelated PatchWarden, OpenCode, or Codex instances.
 | --- | --- | --- |
 | Tunnel connection keeps timing out | No proxy is listening on default port 7892 | Find the real HTTP/Mixed port, set `HTTPS_PROXY`, and start from the same terminal. |
 | Logs show 403 and `unsupported_country_region_territory` | Unsupported proxy exit region | Switch exit region and restart the tunnel. |
-| `list_workspace` only shows `tunnel-client.exe` | MCP started in the wrong directory or did not receive the config path | Use `scripts/patchwarden-mcp-stdio.cmd`. |
+| `list_workspace` only shows `tunnel-client.exe` | MCP started in the wrong directory or did not receive the config path | Use `scripts/mcp/patchwarden-mcp-stdio.cmd`. |
 | MCP is connected, but tasks do not run | Watcher is missing or stale | Start `npm.cmd run watch` and inspect `health_check`. |
 | `Agent command not found` | Agent is not on PATH, or Codex Desktop was mistaken for the CLI | Run `where.exe` and use the real CLI path in `agents.command`. |
 | Verification command is rejected | It does not exactly match the allowlist | Add the exact command to `allowedTestCommands`. |
@@ -845,13 +931,13 @@ names.
 
 ## MCP tools and profiles
 
-`chatgpt_core` is the fixed 16-tool profile used by the ChatGPT tunnel:
+`chatgpt_core` is the fixed 17-tool profile used by the ChatGPT tunnel:
 
 `health_check`, `list_agents`, `list_workspace`,
 `read_workspace_file`, `save_plan`, `create_task`,
 `wait_for_task`, `get_task_summary`, `get_diff`, `get_result`,
 `get_result_json`, `get_test_log`, `get_task_status`, `list_tasks`,
-`cancel_task`, and `audit_task`.
+`cancel_task`, `audit_task`, and `safe_status`.
 
 `get_task_summary` keeps the backward-compatible `standard` view by default.
 ChatGPT should request `view: "compact"` first; terminal `wait_for_task`
@@ -871,7 +957,7 @@ to `full`.
 
 ### ChatGPT Direct mode
 
-Direct mode exposes nine guarded tools so ChatGPT can create an editing
+Direct mode exposes ten guarded tools so ChatGPT can create an editing
 session, read and search source files, apply hash-bound JSON patches, run
 exactly allowlisted verification commands, finalize the evidence, and audit
 the result without a local execution agent.
@@ -895,7 +981,7 @@ On first use, provide the `tunnel-client.exe` path and a Tunnel ID dedicated
 to the Direct Connector. The launcher uses the `patchwarden-direct` profile,
 stores runtime state under `%LOCALAPPDATA%\patchwarden\runtime-direct`, skips
 the Watcher, and retains the existing DPAPI credential handling. In a fresh
-ChatGPT conversation, `health_check` should report `chatgpt_direct`, nine
+ChatGPT conversation, `health_check` should report `chatgpt_direct`, ten
 tools, and `direct_profile_enabled=true`.
 
 ## Security boundaries and local data
@@ -931,7 +1017,7 @@ Start with a dedicated test workspace and a repository you can recover.
 Upgrade a pinned npm installation:
 
 ```powershell
-npm.cmd install patchwarden@0.6.0
+npm.cmd install patchwarden@0.6.4
 ```
 
 Upgrade a source checkout:
@@ -997,6 +1083,8 @@ and release-asset checksums independently.
 
 ## Related documentation
 
+- [v0.6.4 release notes](docs/release-v0.6.4.md)
+- [v0.6.1 release notes](docs/release-v0.6.1.md)
 - [v0.6.0 release notes](docs/release-v0.6.0.md)
 - [ChatGPT usage guide](docs/chatgpt-usage.md)
 - [Migration guide](docs/migration-from-safe-bifrost.md)

package/README.md

@@ -8,16 +8,20 @@
 [![Node.js](https://img.shields.io/badge/Node.js-%3E%3D18-339933.svg)](https://nodejs.org/)
 [![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE)
 
-当前稳定版本：**v0.6.1**。查看
-[发布说明](docs/release-v0.6.1.md)、
+当前稳定版本：**v0.6.4**。查看
+[发布说明](docs/release-v0.6.4.md)、
 [迁移指南](docs/migration-from-safe-bifrost.md)和
-[GitHub Release](https://github.com/jiezeng2004-design/PatchWarden/releases/tag/v0.6.1)。
+[GitHub Release](https://github.com/jiezeng2004-design/PatchWarden/releases/tag/v0.6.4)。
 
 PatchWarden 是一个面向本地编程 Agent 的安全 MCP 桥接器。上游的
 ChatGPT、Codex、OpenCode 或其他 MCP 客户端负责规划与验收，
 PatchWarden 负责把计划保存成工作区内任务，再由预先配置的本地 Agent
 执行，并返回结果、代码差异和独立测试记录。
 
+统一英文定位：
+
+> PatchWarden is a local-first MCP safety and verification layer for AI coding agents, with workspace confinement, command allowlists, scope-violation detection, and auditable task evidence.
+
 ![PatchWarden ChatGPT connector demo](docs/assets/patchwarden-chatgpt-demo.svg)
 
 > [!IMPORTANT]
@@ -96,6 +100,7 @@ ChatGPT / Codex / OpenCode / 其他 MCP 客户端
        MCP 客户端读取、审计、人工验收
 ```
 
+
 一次完整运行通常包含三个角色：
 
 1. **MCP Server**：由 Codex、OpenCode 或 Tunnel 启动。
@@ -175,7 +180,7 @@ npm 包适合让 MCP 客户端通过固定版本启动 PatchWarden。为了执
 New-Item -ItemType Directory .\patchwarden-runtime
 Set-Location .\patchwarden-runtime
 npm.cmd init -y
-npm.cmd install patchwarden@0.6.0
+npm.cmd install patchwarden@0.6.4
 Copy-Item .\node_modules\patchwarden\examples\config.example.json .\patchwarden.config.json
 $env:PATCHWARDEN_CONFIG = (Resolve-Path .\patchwarden.config.json)
 node .\node_modules\patchwarden\dist\runner\watch.js
@@ -184,7 +189,7 @@ node .\node_modules\patchwarden\dist\runner\watch.js
 MCP 客户端可以使用：
 
 ```text
-npx.cmd -y patchwarden@0.6.0
+npx.cmd -y patchwarden@0.6.4
 ```
 
 建议固定版本号，不要在重要环境中无条件使用 `latest`。
@@ -337,7 +342,7 @@ npm.cmd run watch
 ```toml
 [mcp_servers.patchwarden]
 command = "npx.cmd"
-args = ["-y", "patchwarden@0.6.0"]
+args = ["-y", "patchwarden@0.6.4"]
 
 [mcp_servers.patchwarden.env]
 PATCHWARDEN_CONFIG = "D:\\path\\to\\patchwarden.config.json"
@@ -426,7 +431,7 @@ ChatGPT Connector 创建时：
 
 ### 一键脚本的默认值
 
-`scripts/start-patchwarden-tunnel.ps1` 优先读取当前进程的
+`scripts/control/start-patchwarden-tunnel.ps1` 优先读取当前进程的
 `HTTPS_PROXY`。如果没有设置，它会默认使用：
 
 ```text
@@ -568,6 +573,7 @@ ChatGPT 任务应优先选择前三个守护模板：只读诊断使用 `inspect
 | `result.md` | 人类可读的执行报告。 |
 | `result.json` | 结构化结果、路径、变更、警告和后续建议。 |
 | `diff.patch` | 完整任务差异证据。 |
+| `artifact_manifest.json` | 构建或发布产物的路径、类型、大小与 SHA-256。 |
 | `file-stats.json` | 文件级增删统计。 |
 | `verify.json` | 每条独立验证命令的结构化记录。 |
 | `verify.log` | 独立验证的可读日志。 |
@@ -653,8 +659,11 @@ Direct 两种模式的启动、停止、重启与状态。也可以在 PowerShel
 .\PatchWarden.cmd restart all
 .\PatchWarden.cmd status all
 .\PatchWarden.cmd kill all
+.\Stop-PatchWarden.cmd
 ```
 
+日常桌面入口：`PatchWarden-Desktop.cmd` 启动托盘并确保 Control Center 可用，不自动打开额外浏览器窗口。只有调试托盘时才使用 `PatchWarden-Control-Tray.cmd --foreground`；需要完整 Web 控制台时打开 `PatchWarden-Control.cmd`；需要一键收尾时使用 `Stop-PatchWarden.cmd` 关闭 Core/Direct、Control Center 和托盘。
+
 旧的单用途入口保留在 `scripts/launchers/` 作为兼容层；个人入口位于
 `.local/launchers/`，并继续被 Git 和发布包排除。`stop` / `restart` 会同时检查
 运行状态、精确的 Tunnel Profile、项目启动器和进程树，因此可以清理同一 Profile
@@ -726,13 +735,13 @@ Core Agent 和 Direct 可以**同时运行**，使用不同的 `tunnel-client` p
 **Core 启动示例：**
 
 ```cmd
-powershell.exe -NoProfile -ExecutionPolicy Bypass -File "%CD%\scripts\start-patchwarden-tunnel.ps1" -ToolProfile chatgpt_core -Profile patchwarden -HealthListenAddr 127.0.0.1:8080
+powershell.exe -NoProfile -ExecutionPolicy Bypass -File "%CD%\scripts\control\start-patchwarden-tunnel.ps1" -ToolProfile chatgpt_core -Profile patchwarden -HealthListenAddr 127.0.0.1:8080
 ```
 
 **Direct 启动示例：**
 
 ```cmd
-powershell.exe -NoProfile -ExecutionPolicy Bypass -File "%CD%\scripts\start-patchwarden-tunnel.ps1" -ToolProfile chatgpt_direct -Profile patchwarden-direct -HealthListenAddr 127.0.0.1:8081 -SkipWatcher
+powershell.exe -NoProfile -ExecutionPolicy Bypass -File "%CD%\scripts\control\start-patchwarden-tunnel.ps1" -ToolProfile chatgpt_direct -Profile patchwarden-direct -HealthListenAddr 127.0.0.1:8081 -SkipWatcher
 ```
 
 如果使用 `.local\launchers\` 下的个人启动器，也需要同步追加对应
@@ -751,7 +760,7 @@ powershell.exe -NoProfile -ExecutionPolicy Bypass -File "%CD%\scripts\start-patc
 | --- | --- | --- |
 | Tunnel 一直连接超时 | 默认 7892 没有代理服务 | 确认实际 HTTP/Mixed 端口，设置 `HTTPS_PROXY` 后从同一窗口启动。 |
 | 日志出现 403 和 `unsupported_country_region_territory` | 代理出口区域不受支持 | 切换出口区域，再重启 Tunnel。 |
-| `list_workspace` 只看到 `tunnel-client.exe` | MCP 从错误目录启动或没收到配置路径 | 使用 `scripts/patchwarden-mcp-stdio.cmd`。 |
+| `list_workspace` 只看到 `tunnel-client.exe` | MCP 从错误目录启动或没收到配置路径 | 使用 `scripts/mcp/patchwarden-mcp-stdio.cmd`。 |
 | MCP 显示 connected，但任务不执行 | Watcher 没启动或心跳过期 | 启动 `npm.cmd run watch`，再看 `health_check`。 |
 | `Agent command not found` | Agent 不在 PATH，或 Codex Desktop 被误当成 CLI | 运行 `where.exe`，必要时在 `agents.command` 写真实 CLI 路径。 |
 | 验证命令被拒绝 | 与白名单不是逐字一致 | 把确切命令加入 `allowedTestCommands`，不要扩大成任意 Shell。 |
@@ -828,19 +837,19 @@ PatchWarden v0.4.0 不自动读取旧 CLI、旧环境变量、旧 Header、旧
 
 ## MCP 工具与 Profile
 
-`chatgpt_core` 是固定的 16 工具 Profile，适合 ChatGPT Tunnel：
+`chatgpt_core` 是固定的 17 工具 Profile，适合 ChatGPT Tunnel：
 
 `health_check`、`list_agents`、`list_workspace`、
 `read_workspace_file`、`save_plan`、`create_task`、
 `wait_for_task`、`get_task_summary`、`get_diff`、`get_result`、
 `get_result_json`、`get_test_log`、`get_task_status`、`list_tasks`、
-`cancel_task`、`audit_task`。
+`cancel_task`、`audit_task`、`safe_status`。
 
 `get_task_summary` 默认保留兼容的 `standard` 视图；ChatGPT 应优先使用
 `view: "compact"`，终态 `wait_for_task` 也只内嵌 compact 验收证据。
 
-`full` 在 `chatgpt_core` 基础上额外提供 6 个管理工具，合计 22 个核心
-工具；启用 Direct 后再追加 6 个 Direct 工具，共 28 个工具（22 + 6）：
+`full` 提供完整 30 工具本地开发目录，包含核心工具、管理工具和 Direct
+工具。除 `chatgpt_core` 外，常用额外管理工具包括：
 
 - `get_plan`
 - `kill_task`
@@ -849,15 +858,15 @@ PatchWarden v0.4.0 不自动读取旧 CLI、旧环境变量、旧 Header、旧
 - `get_task_stdout_tail`
 - `get_task_log_tail`
 
-`chatgpt_direct` 是 v0.6.0 新增的 Direct 直接开发 Profile，包含 9 个工具：
+`chatgpt_direct` 是 v0.6.0 新增的 Direct 直接开发 Profile，v0.6.4 包含 10 个工具：
 
 `health_check`、`list_workspace`、`create_direct_session`、
 `search_workspace`、`read_workspace_file`、`apply_patch`、
-`run_verification`、`finalize_direct_session`、`audit_session`。
+`run_verification`、`finalize_direct_session`、`audit_session`、`sync_file`。
 
 `chatgpt_direct` 默认关闭，需要通过 `enableDirectProfile: true` 或
 `PATCHWARDEN_TOOL_PROFILE=chatgpt_direct` 显式启用。`chatgpt_core` 保持
-16 工具不变。
+17 工具不变。
 
 Tunnel 包装脚本会强制使用 `chatgpt_core`；普通本地开发默认使用 `full`。
 
@@ -912,7 +921,7 @@ Tunnel ID。启动器使用 `patchwarden-direct` Profile、独立的
 Tunnel API Key 仍通过现有 Windows DPAPI 缓存处理，不会写入仓库。
 
 连接 ChatGPT 后新建对话并先调用 `health_check`。预期
-`tool_profile=chatgpt_direct`、`tool_count=9`、
+`tool_profile=chatgpt_direct`、`tool_count=10`、
 `direct_profile_enabled=true`。已有对话可能缓存旧工具清单，需要重新连接
 Connector 后再新建对话。
 
@@ -975,7 +984,7 @@ PatchWarden 能降低误操作风险，但不能替代人工审查。第一次
 升级 npm 固定版本：
 
 ```powershell
-npm.cmd install patchwarden@0.6.0
+npm.cmd install patchwarden@0.6.4
 ```
 
 源码升级：
@@ -1040,6 +1049,8 @@ Release 和发布资产校验值。
 
 ## 相关文档
 
+- [v0.6.4 发布说明](docs/release-v0.6.4.md)
+- [v0.6.1 发布说明](docs/release-v0.6.1.md)
 - [v0.6.0 发布说明](docs/release-v0.6.0.md)
 - [ChatGPT 调用规范](docs/chatgpt-usage.md)
 - [旧版本迁移指南](docs/migration-from-safe-bifrost.md)

package/Restart-PatchWarden-Control.cmd

@@ -0,0 +1,6 @@
+@echo off
+setlocal
+cd /d "%~dp0"
+powershell -ExecutionPolicy Bypass -NoProfile -File "%~dp0scripts\control\restart-control-center.ps1" %*
+set EXITCODE=%ERRORLEVEL%
+endlocal & exit /b %EXITCODE%

package/Stop-PatchWarden.cmd

@@ -0,0 +1,11 @@
+@echo off
+setlocal
+cd /d "%~dp0"
+powershell -ExecutionPolicy Bypass -NoProfile -File "%~dp0scripts\control\stop-patchwarden.ps1" %*
+set EXITCODE=%ERRORLEVEL%
+if not "%EXITCODE%"=="0" (
+  echo.
+  echo PatchWarden stop exited with code %EXITCODE%.
+  pause
+)
+endlocal & exit /b %EXITCODE%

package/dist/controlCenter.d.ts

@@ -0,0 +1,14 @@
+#!/usr/bin/env node
+/**
+ * PatchWarden Control Center — local HTTP dashboard service.
+ *
+ * Binds to 127.0.0.1 only. Serves the static UI from `ui/` and exposes a set
+ * of fault-tolerant JSON APIs for inspecting runtime state and driving
+ * `scripts/control/manage-patchwarden.ps1` for process lifecycle.
+ *
+ * Run: node dist/controlCenter.js
+ *   or: npm run start:control
+ *
+ * Port override: PATCHWARDEN_CONTROL_PORT=<n>  or  --port <n>
+ */
+export {};