code-workspace-zhuiyi 0.1.0-beta.7 → 0.1.0-beta.9

package/README.md

@@ -13,7 +13,7 @@ Code Workspace is a local multi-project registry and safety layer for Claude Cod
 npm install -g @icebearx-ai/code-workspace
 ```
 
-The package provides `code-workspace` and the shorter alias `code-w`.
+The package provides the `code-workspace` command and the shorter `codew` alias. The legacy `code-w` alias remains available for compatibility.
 
 ## Initialize
 
@@ -33,7 +33,7 @@ code-workspace init . \
   --yes
 ```
 
-Use `--tools claude`, `--tools codex`, or `--tools none` to override the default tool selection. Codex monitoring is enabled by default when Codex is selected; use `--no-monitor` to disable it.
+Use `--tools claude`, `--tools codex`, or `--tools none` to override the default tool selection. Monitoring is not enabled implicitly; install the `monitor` extension with `--extensions monitor` or through the interactive extension picker.
 
 Initialization writes only Workspace-owned state and integrations:
 
@@ -41,7 +41,7 @@ Initialization writes only Workspace-owned state and integrations:
 - `USER_GUIDE.md`
 - `CLAUDE.md` and/or `AGENTS.md`
 - Workspace-specific commands and skills whose names start with `code-workspace-` or use the `/code-workspace` namespace
-- `.codex/hooks.json` when monitoring is enabled
+- `.codex/hooks.json` is written by the `monitor` extension when that extension is installed
 
 It does not create `openspec/`, install native `/opsx` commands, or install native `openspec-*` skills.
 
@@ -50,13 +50,13 @@ It does not create `openspec/`, install native `/opsx` commands, or install nati
 `init` can install integrations from the versioned `extensions/` repository shipped inside this npm package. Select extension names interactively, or pass a comma-separated name list non-interactively. The dedicated install command accepts one or more names; without names it opens the built-in extension multiselect, where ESC exits without changes:
 
 ```bash
-code-w init . --extensions zhuiyi-jira-mcp --yes
-code-w init . --extensions zhuiyi-opensvn-mcp --yes
-code-w init . --extensions none --yes
-code-w extension install
-code-w extension install zhuiyi-jira-mcp --yes
-code-w extension install zhuiyi-opensvn-mcp --yes
-code-w extension uninstall zhuiyi-jira-mcp --yes
+codew init . --extensions zhuiyi-jira-mcp --yes
+codew init . --extensions zhuiyi-opensvn-mcp --yes
+codew init . --extensions none --yes
+codew extension install
+codew extension install zhuiyi-jira-mcp --yes
+codew extension install zhuiyi-opensvn-mcp --yes
+codew extension uninstall zhuiyi-jira-mcp --yes
 ```
 
 The Workspace operation lock shared by init, extension install, and extension uninstall is configured in the Code Workspace project's `.env` (not in the target Workspace). `CODE_WORKSPACE_INIT_LOCK_UPDATE_MS` defaults to `5000`, and `CODE_WORKSPACE_INIT_LOCK_STALE_MS` defaults to `30000`; process environment variables take precedence. See `.env.example` for the project configuration names.
@@ -67,7 +67,7 @@ Users select names, not versions; `zhuiyi-jira-mcp@0.1.0` is intentionally rejec
 
 The bundled `zhuiyi-jira-mcp` and `zhuiyi-opensvn-mcp` extensions configure the Jira and OpenSVN MCP services for the selected Agent tools. They do not create an `openspec/` directory or install native OpenSpec commands.
 
-`zhuiyi-opensvn-mcp` accesses OpenSVN static resources through `opssvn.in.wezhuiyi.com`. Its runtime configuration requires `SVN_AUTHORIZATION` and optionally accepts `SVN_OUTPUT_DIR` and `SVN_MAX_RESOURCES`; credentials are not stored in the extension package and should be supplied through local configuration or the runtime environment.
+`zhuiyi-opensvn-mcp` accesses OpenSVN static resources through `opssvn.in.wezhuiyi.com`. Its bundled configuration sets `SVN_OUTPUT_DIR` to `.mcp-cache-opensvn`, requires `SVN_AUTHORIZATION`, and defaults `SVN_MAX_RESOURCES` to `200`; credentials are not stored in the extension package and should be supplied through local configuration or the runtime environment.
 
 Extension entries run in separate Node processes and generate files in temporary staging directories. The host rejects undeclared, missing, symbolic-link, non-file, path-escaping, conflicting, and checksum-mismatched artifacts before transactionally installing them. Per-Workspace state is stored in `.code-workspace/ext-manifest.json`. A failed extension is reported as a warning and does not roll back successful core initialization or stop later extensions; a failed upgrade restores and retains the previous installed version.
 
@@ -78,7 +78,7 @@ verified by Code Workspace; extensions never patch the real Workspace directly.
 recorded installed state and does not execute extension code. Unknown changes to extension-owned
 files or contributions stop the operation instead of being overwritten.
 
-This is fault isolation, not a malicious-code security sandbox. The experimental release trusts only extension code shipped with Code Workspace; network sources, external extension directories, dependencies, arbitrary patches, force uninstall, disable commands, and automatic extension updates through `code-w update` are not supported. The developer contract is in `docs/extensions.md`.
+This is fault isolation, not a malicious-code security sandbox. The experimental release trusts only extension code shipped with Code Workspace; network sources, external extension directories, dependencies, arbitrary patches, force uninstall, disable commands, and automatic extension updates through `codew update` are not supported. The developer contract is in `docs/extensions.md`.
 
 ## Register projects
 
@@ -185,13 +185,14 @@ code-workspace language --json
 
 ## Monitor
 
+Monitor ships as the built-in `monitor` extension. Install it into a workspace and run its dashboard through the generic extension runtime:
+
 ```bash
-code-workspace monitor --port 3211
+code-workspace extension install monitor --yes
+code-workspace ext monitor serve --port 3211
 ```
 
-The monitor binds to loopback, combines events from multiple initialized workspaces, and keeps hook reporting failure-open. Review and trust project hooks in Codex before relying on reports.
-
-## Completion
+The monitor binds to loopback, combines events from multiple initialized workspaces, and keeps hook reporting (`codew ext monitor report`) failure-open. Review and trust project hooks in Codex before relying on reports.
 
 ```bash
 code-workspace completion --shell zsh

package/README.zh-CN.md

@@ -13,7 +13,7 @@ Code Workspace 是面向 Claude Code 与 Codex 的本地多项目注册表和安
 npm install -g @icebearx-ai/code-workspace
 ```
 
-软件包提供 `code-workspace` 命令及短别名 `code-w`。
+软件包提供 `code-workspace` 命令及短别名 `codew`。为保持兼容，旧别名 `code-w` 仍然可用。
 
 ## 初始化
 
@@ -33,7 +33,7 @@ code-workspace init . \
   --yes
 ```
 
-可用 `--tools claude`、`--tools codex` 或 `--tools none` 覆盖默认工具选择。选择 Codex 时默认启用监控；可传 `--no-monitor` 关闭。
+可用 `--tools claude`、`--tools codex` 或 `--tools none` 覆盖默认工具选择。监控不会隐式启用；请通过 `--extensions monitor` 或交互式扩展选择安装 `monitor` 扩展。
 
 初始化只写入 Workspace 自有状态和集成：
 
@@ -41,7 +41,7 @@ code-workspace init . \
 - `USER_GUIDE.md`
 - `CLAUDE.md` 和/或 `AGENTS.md`
 - 名称以 `code-workspace-` 开头或使用 `/code-workspace` 命名空间的 Workspace 专用命令与 Skill
-- 启用监控时的 `.codex/hooks.json`
+- 安装 `monitor` 扩展时由扩展写入的 `.codex/hooks.json`
 
 它不会创建 `openspec/`，不会安装原生 `/opsx` 命令，也不会安装原生 `openspec-*` Skill。
 
@@ -50,13 +50,13 @@ code-workspace init . \
 `init` 可以从 npm 包内随附的版本化 `extensions/` 仓库安装集成。交互模式按扩展名多选；非交互模式传入逗号分隔的扩展名。独立安装命令接受一个或多个扩展名；不传名称时打开内置扩展多选，按 ESC 可无修改退出：
 
 ```bash
-code-w init . --extensions zhuiyi-jira-mcp --yes
-code-w init . --extensions zhuiyi-opensvn-mcp --yes
-code-w init . --extensions none --yes
-code-w extension install
-code-w extension install zhuiyi-jira-mcp --yes
-code-w extension install zhuiyi-opensvn-mcp --yes
-code-w extension uninstall zhuiyi-jira-mcp --yes
+codew init . --extensions zhuiyi-jira-mcp --yes
+codew init . --extensions zhuiyi-opensvn-mcp --yes
+codew init . --extensions none --yes
+codew extension install
+codew extension install zhuiyi-jira-mcp --yes
+codew extension install zhuiyi-opensvn-mcp --yes
+codew extension uninstall zhuiyi-jira-mcp --yes
 ```
 
 `init`、扩展安装和扩展卸载共享的 Workspace 操作锁配置在 Code Workspace 项目自身的 `.env` 中（不在目标 Workspace 中）。`CODE_WORKSPACE_INIT_LOCK_UPDATE_MS` 默认值为 `5000`，`CODE_WORKSPACE_INIT_LOCK_STALE_MS` 默认值为 `30000`；进程环境变量优先于 `.env`。配置项名称见 `.env.example`。
@@ -67,7 +67,7 @@ code-w extension uninstall zhuiyi-jira-mcp --yes
 
 当前随包提供的内置扩展包括 `zhuiyi-jira-mcp` 和 `zhuiyi-opensvn-mcp`，分别用于为选中的 Agent 工具配置 Jira MCP 与 OpenSVN MCP 服务；它们不会创建 `openspec/` 目录，也不会安装 OpenSpec 原生命令。
 
-`zhuiyi-opensvn-mcp` 使用 `opssvn.in.wezhuiyi.com` 访问 OpenSVN 静态资源。运行时必须在对应 Agent 配置中提供 `SVN_AUTHORIZATION`，可选配置 `SVN_OUTPUT_DIR` 和 `SVN_MAX_RESOURCES`；认证信息不会写入扩展包，应通过本地配置或运行环境注入。
+`zhuiyi-opensvn-mcp` 使用 `opssvn.in.wezhuiyi.com` 访问 OpenSVN 静态资源。内置配置将 `SVN_OUTPUT_DIR` 设为 `.mcp-cache-opensvn`，运行时必须提供 `SVN_AUTHORIZATION`，`SVN_MAX_RESOURCES` 默认为 `200`；认证信息不会写入扩展包，应通过本地配置或运行环境注入。
 
 扩展入口在独立 Node 进程中运行，只向临时 staging 目录生成文件。Host 会在事务安装前拒绝未声明、缺失、符号链接、非文件、路径逃逸、目标冲突和 hash 不匹配的制品。Workspace 状态存放在 `.code-workspace/ext-manifest.json`。扩展失败以 warning 报告，不回滚已成功的核心初始化，也不阻止后续扩展；升级失败会恢复并保留旧的已安装版本。
 
@@ -76,7 +76,7 @@ code-w extension uninstall zhuiyi-jira-mcp --yes
 Workspace 合成和验证，扩展不会直接 patch 真实 Workspace。卸载只使用已安装状态，不执行
 扩展代码；扩展所有的文件或贡献存在未知修改时会拒绝覆盖或删除。
 
-这是故障隔离，不是恶意代码安全沙箱。试验版本只信任随 Code Workspace 发布的扩展代码；暂不支持网络源、外部扩展目录、扩展依赖、任意 patch、强制卸载、禁用命令，也不会通过 `code-w update` 自动更新扩展。开发契约见 `docs/extensions.zh-CN.md`。
+这是故障隔离，不是恶意代码安全沙箱。试验版本只信任随 Code Workspace 发布的扩展代码；暂不支持网络源、外部扩展目录、扩展依赖、任意 patch、强制卸载、禁用命令，也不会通过 `codew update` 自动更新扩展。开发契约见 `docs/extensions.zh-CN.md`。
 
 ## 注册项目
 
@@ -183,11 +183,14 @@ code-workspace language --json
 
 ## 监控
 
+监控以内置 `monitor` 扩展的形式提供。先在 Workspace 中安装扩展，再通过通用扩展运行时启动面板：
+
 ```bash
-code-workspace monitor --port 3211
+code-workspace extension install monitor --yes
+code-workspace ext monitor serve --port 3211
 ```
 
-监控服务仅绑定 loopback，可汇总多个已初始化工作区的事件；hook 上报失败不会阻断 Agent。依赖监控前，请在 Codex 中检查并信任项目 hook。
+监控服务仅绑定 loopback，可汇总多个已初始化工作区的事件；hook 上报（`codew ext monitor report`）失败不会阻断 Agent。依赖监控前，请在 Codex 中检查并信任项目 hook。
 
 ## 命令补全
 

package/artifacts/manifest.json

@@ -1,6 +1,6 @@
 {
   "schemaVersion": 2,
-  "releaseVersion": "0.1.0-beta.7",
+  "releaseVersion": "0.1.0-beta.9",
   "requirements": {
     "node": ">=20.19.0"
   },
@@ -13,13 +13,13 @@
       "id": "workspace-user-guide-en-US",
       "kind": "asset",
       "path": "templates/user-guide/en-US.md",
-      "sha256": "a05c1611df919bcb05843d703a5a08c9d7e312c7dd69d1ac198f8bcfc266ec67"
+      "sha256": "a91d45e4fc11b4f3eb3c651a4fcee6d981b0d076d93063e0480c5c3e377ea5d2"
     },
     {
       "id": "workspace-user-guide-zh-CN",
       "kind": "asset",
       "path": "templates/user-guide/zh-CN.md",
-      "sha256": "b4fb6dee108832c02fc09e179c051678406d486f341b3174aa5e57b4053d740a"
+      "sha256": "43bfd67f0725c4834cf33bb7ab96cbe090db6f4373f0b58d01276db293cb9598"
     }
   ],
   "managedFiles": [
@@ -49,7 +49,7 @@
       "allowMissing": true,
       "desired": {
         "source": "templates/agents/WORKSPACE_GUARD.md.template",
-        "sha256": "6510cce83138fad46330d2c175506e56e9c98d5086195a699eafc7cc74163bf3"
+        "sha256": "bddb8e2ee25b7a63614b4297453e5803d2740fc475d97f5d8489dbaf17380c2c"
       },
       "render": {
         "variables": [
@@ -72,7 +72,7 @@
       "allowMissing": true,
       "desired": {
         "source": "templates/agents/WORKSPACE_GUARD.md.template",
-        "sha256": "6510cce83138fad46330d2c175506e56e9c98d5086195a699eafc7cc74163bf3"
+        "sha256": "bddb8e2ee25b7a63614b4297453e5803d2740fc475d97f5d8489dbaf17380c2c"
       },
       "render": {
         "variables": [
@@ -86,24 +86,6 @@
         "kind": "template"
       }
     },
-    {
-      "id": "workspace-codex-monitor-hooks",
-      "target": ".codex/hooks.json",
-      "tools": [
-        "codex"
-      ],
-      "capabilities": [
-        "monitor"
-      ],
-      "allowMissing": true,
-      "desired": {
-        "source": "templates/codex/hooks.json",
-        "sha256": "64d68809a2681b11d4b50bee3ca711fa8f5ea0a297c2281e5c7f8937e968e22e"
-      },
-      "provenance": {
-        "kind": "template"
-      }
-    },
     {
       "id": "workspace-claude-add-projects-command",
       "target": ".claude/commands/code-workspace/add-projects.md",
@@ -158,7 +140,7 @@
       "allowMissing": true,
       "desired": {
         "source": "templates/agents/skills/code-workspace-resolve-branch/SKILL.md",
-        "sha256": "d09b0e1847f5b39e6409ba3ac43f26fa5829a15690a3e216576e51535fb6b161"
+        "sha256": "df8c65fbadf917b7247bbd1f40144da8c904a95f2b3ee905a4d2d6176e0a5f1b"
       },
       "provenance": {
         "kind": "template"
@@ -173,7 +155,7 @@
       "allowMissing": true,
       "desired": {
         "source": "templates/agents/skills/code-workspace-resolve-branch/SKILL.md",
-        "sha256": "d09b0e1847f5b39e6409ba3ac43f26fa5829a15690a3e216576e51535fb6b161"
+        "sha256": "df8c65fbadf917b7247bbd1f40144da8c904a95f2b3ee905a4d2d6176e0a5f1b"
       },
       "provenance": {
         "kind": "template"

package/artifacts/templates/agents/WORKSPACE_GUARD.md.template

@@ -9,13 +9,13 @@ The registry is authoritative for project identity, ownership, location, and the
 If the user explicitly names a registered project, resolve it directly:
 
 ```bash
-code-w project show "<project.name>" --json
+codew project show "<project.name>" --json
 ```
 
 Only when project ownership cannot be determined, list registry metadata:
 
 ```bash
-code-w project list --json
+codew project list --json
 ```
 
 Use `name`, `type`, and `context` only to identify relevant candidates and ask the user to choose. Do not inspect candidate repositories while selecting.
@@ -33,27 +33,26 @@ Meta, help, or workspace-tool maintenance tasks that do not depend on registered
 Before reading or modifying selected project code, run:
 
 ```bash
-code-w project verify "<project.name>" --json
+codew project verify "<project.name>" --json
 ```
 
 For several explicitly selected projects, use:
 
 ```bash
-code-w project verify "<project-a>" "<project-b>" --json
+codew project verify "<project-a>" "<project-b>" --json
 ```
 
 - For one project, continue only when the targeted result has `ok: true`. For a multi-project result, evaluate every ordered project result independently: continue passed projects and keep failed projects paused even when the top-level `ok` is false.
 - On `PROJECT_BRANCH_MISMATCH`, pause affected project work and invoke the installed `code-workspace-resolve-branch` Skill. The Skill may combine mismatches from the explicitly selected scope into one concise question; do not choose a branch direction yourself.
-- For any other failure, report the targeted diagnostics and wait for user direction for the affected project; a failure in one batch result does not block unrelated successful selected projects. Do not escalate to full-workspace validation.
-- The branch Skill completes after `project branch verify` confirms alignment; it does not own overall project readiness. After its handoff, discard branch-dependent context and rerun targeted `project verify` for the successfully reconciled projects before resuming work.
-- If that overall verification fails for a non-branch reason, keep the affected project paused and handle the project-level diagnostic here without treating the branch Skill as failed. If a new `PROJECT_BRANCH_MISMATCH` appears because the branch drifted again, re-enter the Skill. Do not list or verify unrelated projects.
+- For any other failure, report the targeted diagnostics and wait for user direction for the affected project; a failure in one batch result does not block unrelated successful selected projects. Do not escalate to full-workspace validation. Do not list or verify unrelated projects.
+- The branch Skill completes after `project branch verify` confirms alignment; it does not own overall project readiness. After its handoff, proceed directly to `project branch update-latest` without rerunning targeted `project verify`. If update-latest reports a new `PROJECT_BRANCH_MISMATCH`, re-enter the Skill using the new CLI observation.
 - After branch verification succeeds—including projects whose branches were already aligned—run `project branch update-latest` for the selected projects:
 
 ```bash
-code-w project branch update-latest "<project-a>" "<project-b>" --json
+codew project branch update-latest "<project-a>" "<project-b>" --json
 ```
 
-  Pass each selected project name as a separate argument; for a single project, pass only that project name. Evaluate each project result independently, including when the batch-level `ok` is `false`: continue only for projects whose individual result has `ok: true`, and treat `disabled` and `already-latest` as successful skips. If an update fails, keep that project paused and do not run ad-hoc `fetch`, `pull`, `reset`, `stash`, or `rebase` commands. For each successful or skipped project, discard pre-update context and rerun targeted `project verify` before starting project work.
+  Pass each selected project name as a separate argument; for a single project, pass only that project name. Evaluate each project result independently, including when the batch-level `ok` is `false`: continue only for projects whose individual result has `ok: true`, and treat `disabled` and `already-latest` as successful skips. If an update fails, keep that project paused and do not run ad-hoc `fetch`, `pull`, `reset`, `stash`, or `rebase` commands. Do not rerun targeted `project verify` after update-latest. For each `fastForwarded: true` result, discard pre-update context and re-read the project files and instructions before starting project work; `disabled` and `already-latest` results may continue with the existing context.
 
 ## Workspace Write Boundary
 
@@ -63,7 +62,7 @@ The AI/Agent MUST NOT directly create, edit, move, or delete Workspace-owned fil
 - `.codex/config.toml`
 - `CLAUDE.md`, `AGENTS.md`, or other managed workspace files
 
-AI/Agent registry changes must use an approved `code-w` command. Users may manually edit `.code-workspace/config.yaml` and are responsible for the resulting configuration; AI/Agent must not imitate that edit with a script or direct file write. The CLI owns confirmation, concurrency checks, persistence or safe external effects, postconditions, rollback/compensation, and structured output. This boundary does not prevent user-requested production-code changes inside the selected external `project.location`.
+AI/Agent registry changes must use an approved `codew` command. Users may manually edit `.code-workspace/config.yaml` and are responsible for the resulting configuration; AI/Agent must not imitate that edit with a script or direct file write. The CLI owns confirmation, concurrency checks, persistence or safe external effects, postconditions, rollback/compensation, and structured output. This boundary does not prevent user-requested production-code changes inside the selected external `project.location`.
 
 ## Responsibilities
 

package/artifacts/templates/agents/skills/code-workspace-resolve-branch/SKILL.md

@@ -12,7 +12,7 @@ Resolve only the already selected registered project or projects. This Skill own
 Run one command from the Workspace for all selected projects whose targeted verification reported `PROJECT_BRANCH_MISMATCH`. Pass each project name as a separate argument; do not join names with commas:
 
 ```bash
-code-w project branch inspect "<project-a>" "<project-b>" --json
+codew project branch inspect "<project-a>" "<project-b>" --json
 ```
 
 For one project, require the existing standard envelope whose `data` contains all of: `project.name`, `project.location`, `registeredBranch`, `actualBranch`, `matches`, `worktreeClean`, `registeredBranchExists`, and `remoteBranchCandidates`. For several projects, read the ordered `data.results`; each successful result contains those facts in its `data`, while failed results are explained by the top-level diagnostics. Do not infer or independently inspect missing values.
@@ -67,8 +67,8 @@ Ask rules:
 
 ## Apply valid choices through the CLI
 
-- Group every project that selected choice 1 into one `code-w project branch use-registered "<project-a>" "<project-b>" --allow-remote --yes --json` invocation. Include only projects for which choice 1 is available. `--allow-remote` is harmless for projects whose local registered branch already exists and permits creation only from an existing unique remote-tracking branch.
-- Group every project that selected choice 2 into one `code-w project branch accept-actual "<project-a>" "<project-b>" --yes --json` invocation.
+- Group every project that selected choice 1 into one `codew project branch use-registered "<project-a>" "<project-b>" --allow-remote --yes --json` invocation. Include only projects for which choice 1 is available. `--allow-remote` is harmless for projects whose local registered branch already exists and permits creation only from an existing unique remote-tracking branch.
+- Group every project that selected choice 2 into one `codew project branch accept-actual "<project-a>" "<project-b>" --yes --json` invocation.
 - For choice 3, keep that project paused until the user confirms manual resolution is complete. Do not reuse any pre-resolution branch facts.
 
 If the registered branch is absent both locally and from remote-tracking refs, do not add `--remote` automatically. Tell the user that an explicit direct CLI invocation such as `project branch use-registered <name> --remote origin --yes --json` is required to authorize network fetch.
@@ -80,7 +80,7 @@ After all choices are valid and complete, run each non-empty automatic direction
 After both automatic direction groups finish, collect projects whose operations succeeded or skipped together with projects that were already matching during inspection, discard their cached branch-dependent context, and run one branch-only verification. After the user confirms one or more manual resolutions, verify those confirmed projects the same way:
 
 ```bash
-code-w project branch verify "<project-a>" "<project-b>" --json
+codew project branch verify "<project-a>" "<project-b>" --json
 ```
 
 Use each result independently. A successful result means branch reconciliation is complete and branch alignment has been verified for that project; a failed result remains unresolved. Complete all independent automatic operations and branch verification before giving one consolidated report of inspected failures, successful changes, skips, branch-verification failures, and projects awaiting manual handling.

package/artifacts/templates/user-guide/en-US.md

@@ -24,8 +24,8 @@ Upgrade the global package, update the current workspace's managed files, then v
 
 ```bash
 npm install -g @icebearx-ai/code-workspace@latest
-code-w update
-code-w doctor
+codew update
+codew doctor
 ```
 
 `update` refreshes managed instructions, Workspace skills, hooks, and this guide. It stops if a managed file contains unknown local changes. Review the file first; use `--force` only when replacing those changes is intentional.
@@ -35,24 +35,25 @@ code-w doctor
 Choose the Workspace language during initialization, or pass it explicitly:
 
 ```bash
-code-w init --language en-US
-code-w language
+codew init --language en-US
+codew language
 ```
 
 The selected preference is stored at `workspace.language` in `.code-workspace/config.yaml`. Change an initialized workspace with:
 
 ```bash
-code-w update --language en-US
+codew update --language en-US
 ```
 
 This also switches this managed guide. Existing project context is not translated.
 
 ## Use the Agent monitor
 
-Start one global monitor for all workspaces:
+Monitoring ships as the built-in `monitor` extension. Install it in a workspace and start one global monitor for all workspaces:
 
 ```bash
-code-w monitor
+codew extension install monitor --yes
+codew ext monitor
 ```
 
 Open the printed local URL. The dashboard shows workspaces, execution state, pending approvals, completed turns, and live signals. Monitor language is selected on the page and is independent of `workspace.language`.
@@ -60,26 +61,26 @@ Open the printed local URL. The dashboard shows workspaces, execution state, pen
 Use another port when necessary:
 
 ```bash
-code-w monitor --port 8080
+codew ext monitor serve --port 8080
 ```
 
-Each participating workspace must use the same URL in `.code-workspace/config.yaml`. After initialization, review and trust the project hooks with `/hooks` in Codex.
+The extension reports to the URL recorded in `.code-workspace/monitor-reporting.json`. After installation, review and trust the project hooks with `/hooks` in Codex.
 
 ## Practical commands
 
 ```bash
 # Check installation and workspace health
-code-w doctor
+codew doctor
 
 # Update all managed files
-code-w update
+codew update
 
 # Apply Agent project directory authorization
-code-w permissions apply --yes
+codew permissions apply --yes
 
 # Validate local projects
-code-w project verify
-code-w project verify <project-name>
+codew project verify
+codew project verify <project-name>
 ```
 
 Directory access is authorized by the user. Code Workspace shows the requested changes, applies and verifies them, and reports the result. `permissions apply` grants missing registered-project access without revoking additional directories. Ordinary `update` does not change authorization.

package/artifacts/templates/user-guide/zh-CN.md

@@ -24,8 +24,8 @@ Claude Code：
 
 ```bash
 npm install -g @icebearx-ai/code-workspace@latest
-code-w update
-code-w doctor
+codew update
+codew doctor
 ```
 
 `update` 会更新托管指令、Workspace 技能、Hook 和本指南。如果托管文件包含未知的本地修改，更新会停止。请先检查文件；只有明确要覆盖这些修改时才使用 `--force`。
@@ -35,24 +35,25 @@ code-w doctor
 初始化时可选择 Workspace 语言，也可以显式指定：
 
 ```bash
-code-w init --language zh-CN
-code-w language
+codew init --language zh-CN
+codew language
 ```
 
 所选偏好保存在 `.code-workspace/config.yaml` 的 `workspace.language`。已有工作区可通过以下命令切换语言：
 
 ```bash
-code-w update --language zh-CN
+codew update --language zh-CN
 ```
 
 该操作也会切换本托管指南。已有项目 context 不会自动翻译。
 
 ## 使用 Agent Monitor
 
-为所有工作区启动一个全局 Monitor：
+监控以内置 `monitor` 扩展的形式提供。先在 Workspace 中安装扩展，再为所有工作区启动一个全局 Monitor：
 
 ```bash
-code-w monitor
+codew extension install monitor --yes
+codew ext monitor
 ```
 
 打开命令输出的本地地址。面板会显示工作区、执行状态、待授权请求、已完成轮次和实时信号。Monitor 语言在页面中单独选择，与 `workspace.language` 相互独立。
@@ -60,26 +61,26 @@ code-w monitor
 必要时可使用其他端口：
 
 ```bash
-code-w monitor --port 8080
+codew ext monitor serve --port 8080
 ```
 
-所有参与监控的工作区都必须在 `.code-workspace/config.yaml` 中使用相同 URL。初始化后，请在 Codex 中使用 `/hooks` 检查并信任项目 Hook。
+扩展会向 `.code-workspace/monitor-reporting.json` 中记录的 URL 上报。安装后，请在 Codex 中使用 `/hooks` 检查并信任项目 Hook。
 
 ## 实用命令
 
 ```bash
 # 检查安装和工作区健康状态
-code-w doctor
+codew doctor
 
 # 更新所有托管文件
-code-w update
+codew update
 
 # 应用 Agent 项目目录授权
-code-w permissions apply --yes
+codew permissions apply --yes
 
 # 校验本地项目
-code-w project verify
-code-w project verify <project-name>
+codew project verify
+codew project verify <project-name>
 ```
 
 目录访问由用户授权。Code Workspace 负责展示请求的变更、实施并验证变更，以及报告结果。`permissions apply` 只补齐已注册项目缺失的授权，不撤销额外目录。普通 `update` 不会改变授权。

package/bin/code-workspace.js

@@ -1,10 +1,11 @@
 #!/usr/bin/env node
 
 const { main } = require("../src/cli");
+const { hostJsonRequested } = require("../src/cli/parser");
 const { renderResult } = require("../src/cli/renderer");
 const { failure } = require("../src/cli/result");
 
-const json = process.argv.some((arg) => arg === "--json" || arg.startsWith("--json="));
+const json = hostJsonRequested(process.argv);
 
 main(process.argv)
   .then((result) => renderResult(result, { json }))

package/docs/extension-architecture.zh-CN.md

@@ -93,6 +93,12 @@ extensions/<extension-id>/<version>/
 
 Host 明确声明自己支持的 Extension Spec 版本集合，只有 manifest 的 `extensionSpecVersion` 属于该集合时才会执行扩展。静态 manifest 用于发现、规划、冲突预检和用户确认。它不描述扩展业务实现，不包含需要由 Host 理解的下载 URL、npm 包信息或归档格式。
 
+manifest 还可以声明独立的 `runtime` 入口。Runtime Host 只负责按 Store 中的精确版本校验
+入口、创建最小 context、管理 oneshot 或 service 进程生命周期；扩展 ID 后的参数由扩展自行
+解释。`workspace` runtime 依赖当前 Workspace activation，`global` runtime 不依赖全局
+Workspace，也不因此获得任意 Workspace 路径或凭证。Runtime 子进程与初始化子进程一样属于
+可信代码执行，不是安全沙箱。
+
 入口可能继续读取扩展包内的辅助代码、模板和私有元数据，因此仅校验 `init.js` 不能冻结完整执行输入。Host 在规划时还需要计算整个扩展版本目录的规范摘要，并在执行前重新验证，以防 manifest、入口、辅助代码或模板在计划确认后发生变化。
 
 ### 4.5 初始化入口
@@ -175,13 +181,23 @@ installed manifest 是 Host 持久化的最终安装事实，保存在 Workspace
 - 卸载前验证文件未发生未知修改；
 - 验证成功后删除该文件。
 
-### 6.2 独占目录
+### 6.2 种子文件（seeded）
+
+`seeded` 是 `file` 的一种特殊所有权：Host 只在目标文件缺失时写入扩展提供的默认内容（种子），之后把该文件视为用户所有。Host 负责：
+
+- 首次安装且目标缺失时写入默认内容；
+- 升级时永不覆盖已存在的用户内容，也不做漂移检查；
+- 卸载时直接删除该文件，即使内容已被用户修改。
+
+该能力用于「随扩展安装、之后归用户拥有」的本地配置文件（例如 monitor 的上报地址与开关）。
+
+### 6.3 独占目录
 
 一个扩展独占一个 Workspace 相对目录目标。它用于安装包含多个文件的运行时，例如预构建的 Jira MCP 包。
 
 Host 将目录视为一个制品，使用规范化目录摘要检测漂移，并通过 staging、备份和 rename 完成可恢复提交。目录摘要算法必须固定路径规则、排序、文件类型和文件内容计算方式。
 
-### 6.3 共享文本块
+### 6.4 共享文本块
 
 扩展提供一个文本片段，Host 使用稳定的扩展 id 和输出 id 标记，将其合成到声明的共享文本目标中。
 
@@ -194,7 +210,7 @@ Host 负责：
 
 该能力覆盖当前 Codex TOML 配置需求，但协议不包含 Codex 或 MCP 业务字段。
 
-### 6.4 JSON 对象成员
+### 6.5 JSON 对象成员
 
 扩展提供一个 JSON 值，并在静态 manifest 中声明目标文件和唯一成员位置。Host 只拥有该成员，不拥有整个 JSON 文件。
 
@@ -208,7 +224,7 @@ Host 负责：
 
 该能力覆盖 `.mcp.json` 中单个 MCP server 的需求，但核心不验证 server 的 Jira 业务含义。
 
-### 6.5 暂不增加的输出
+### 6.6 暂不增加的输出
 
 基础版不增加 `remote-archive` 之类的下载型制品。下载和解压是扩展准备候选目录的实现过程，不是 Host 的安装制品语义。
 
@@ -371,6 +387,7 @@ node init.js --context <context-file> --output <staging-directory> --result <res
 
 - 独占目标同时只能由一个扩展拥有。
 - 共享目标由 Host 管理多个局部 contribution 的所有权。
+- 种子文件目标在首次安装后视为用户所有，升级不覆盖、卸载删除、不参与漂移检查。
 - 静态 manifest 是安装意图，不是已安装事实。
 - 初始化结果是扩展声明，不是可信事实。
 - installed manifest 是 Host 验证后的事实来源。

package/extensions/monitor/1.0.0/assets/i18n-icon.svg

@@ -0,0 +1 @@
+<svg xmlns="http://www.w3.org/2000/svg" aria-hidden="true" focusable="false" viewBox="0 0 24 24" class="vt-locales-btn-icon" data-v-6229553e=""><path d="M0 0h24v24H0z" fill="none"></path><path d=" M12.87 15.07l-2.54-2.51.03-.03c1.74-1.94 2.98-4.17 3.71-6.53H17V4h-7V2H8v2H1v1.99h11.17C11.5 7.92 10.44 9.75 9 11.35 8.07 10.32 7.3 9.19 6.69 8h-2c.73 1.63 1.73 3.17 2.98 4.56l-5.09 5.02L4 19l5-5 3.11 3.11.76-2.04zM18.5 10h-2L12 22h2l1.12-3h4.75L21 22h2l-4.5-12zm-2.62 7l1.62-4.33L19.12 17h-3.24z " class="css-c4d79v"></path></svg>

package/extensions/monitor/1.0.0/assets/logo-vector.svg

@@ -0,0 +1,30 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<svg xmlns="http://www.w3.org/2000/svg"
+     width="1254" height="1254" viewBox="0 0 1254 1254"
+     role="img" aria-label="Geometric teal-blue logo">
+  <defs>
+    <linearGradient id="logoGradient" x1="320" y1="175" x2="860" y2="1080" gradientUnits="userSpaceOnUse">
+      <stop offset="0" stop-color="#19AEB8"/>
+      <stop offset="0.48" stop-color="#087DA5"/>
+      <stop offset="1" stop-color="#07528C"/>
+    </linearGradient>
+  </defs>
+
+  <g fill="none"
+     stroke="url(#logoGradient)"
+     stroke-width="118"
+     stroke-linecap="butt"
+     stroke-linejoin="round">
+    <path d="M 794 289
+             L 630 184
+             L 291 394
+             L 291 786
+             L 630 1020
+             L 973 786
+             L 973 393
+             L 914 354"/>
+    <path d="M 850 386
+             L 617 526
+             L 617 850"/>
+  </g>
+</svg>