code-workspace-zhuiyi 0.1.0-beta.6 → 0.1.0-beta.8

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
 
@@ -34,7 +34,6 @@ code-workspace init . \
 ```
 
 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.
-Pass `--coordination` to install the write-coordination Hooks into the selected providers' native configuration.
 
 Initialization writes only Workspace-owned state and integrations:
 
@@ -42,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 or Codex coordination is enabled, and `.claude/settings.json` when Claude coordination is enabled
+- `.codex/hooks.json` when monitoring is enabled
 
 It does not create `openspec/`, install native `/opsx` commands, or install native `openspec-*` skills.
 
@@ -51,11 +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 none --yes
-code-w extension install
-code-w extension install zhuiyi-jira-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.
@@ -64,7 +65,9 @@ Users select names, not versions; `zhuiyi-jira-mcp@0.1.0` is intentionally rejec
 
 `extension install` does not rerun core Workspace initialization. In JSON, non-TTY, or `--yes` mode, at least one extension name is required. Multiple names are installed in order with one confirmation boundary and independent transactions; any failure makes the install command fail while later extensions still run.
 
-The bundled `zhuiyi-jira-mcp` extension configures the Jira MCP service for the selected Agent tools. It does not create an `openspec/` directory or install native OpenSpec commands.
+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 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.
 
@@ -75,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
 
@@ -91,12 +94,14 @@ Claude Code users can invoke:
 /code-workspace:add-projects /absolute/path/to/project-a /absolute/path/to/project-b
 ```
 
-Codex users can invoke `$code-workspace-add-projects` with the same explicit paths. For low-level automation, prepare a complete project record and run:
+Codex users can invoke `$code-workspace-add-projects` with the same explicit paths. For low-level automation, pass complete project records through stdin:
 
 ```bash
-code-workspace project add --projects-file projects.json --yes --json
+cat projects.json | code-workspace project add --stdin --yes --json
 ```
 
+`--stdin` accepts `{ "schemaVersion": 1, "projects": [...] }` JSON with the same semantics as `--projects-file`, requires `--yes`, and fails before writing when input is empty, invalid, or larger than 1 MiB. `--stdin`, `--project-file`, `--projects-file`, and a positional path are mutually exclusive.
+
 The registry stores each project's name, real location, registered branch, type, and context. The registered branch is the Code Workspace expected state; the actual branch is observed from the selected Git worktree. Workspace never guesses a path from a conversation or automatically decides which branch is authoritative.
 
 Project registration is always stored in a separate file in the `.code-workspace` directory. Initialization uses `config-projects.yaml` by default, while `projects.ref` may name any safe regular filename in that directory:
@@ -121,7 +126,7 @@ projects:
       Service ownership and navigation context.
 ```
 
-`projects.ref` is resolved relative to `config.yaml`. It must be one safe regular filename in the same `.code-workspace` directory; URLs, globs, absolute paths, path traversal, and inline `projects` arrays are not supported. All project commands keep their existing CLI semantics; they read and write the referenced project file. The `.code-workspace/` directory is ignored by default, so Git history for this local registry requires an explicit repository policy.
+`projects.ref` is resolved relative to `config.yaml`. It must be one safe regular filename in the same `.code-workspace` directory; URLs, globs, absolute paths, path traversal, and inline `projects` arrays are not supported. Existing project command arguments and behavior remain compatible, `project add` additionally supports `--stdin`, and project data is still read from and written to the referenced file. The `.code-workspace/` directory is ignored by default, so Git history for this local registry requires an explicit repository policy.
 
 For example, `ref: team-projects.yaml` makes the project registry `.code-workspace/team-projects.yaml`; the default remains `config-projects.yaml`.
 
@@ -168,45 +173,11 @@ AI/Agent must not directly edit this file. They may read the policy and invoke t
 
 `permissions apply` shows the complete authorization plan for the selected Agent tools, requires confirmation when changes are needed, applies and verifies the requested grants, and reports the result per tool. Agent directory access remains a user authorization. The command adds missing registered-project access but does not revoke additional directories; use `project remove` or edit the Agent settings explicitly to revoke access.
 
-## Coordinate concurrent Agent writes
-
-When trusted Codex or Claude Hooks are installed, Code Workspace keeps the coordination ledger outside the Workspace and reserves write ranges before a supported tool runs. Different files in one project can proceed after an explicit project-parallel approval; overlapping files are denied without a force override.
-
-Inspect tasks, claims, and pending recovery decisions:
-
-```bash
-code-workspace task list --json
-code-workspace task show <task-id> --json
-code-workspace task lock list --json
-code-workspace task decision show <request-id> --json
-```
-
-Resolve a pending decision only after reviewing its evidence. Planned-write commands require confirmation; automation must pass `--yes` and always retry the original Agent operation after a successful decision:
-
-```bash
-code-workspace task decision keep <request-id> --yes --json
-code-workspace task decision approve <request-id> --yes --json
-code-workspace task decision release <request-id> --yes --json
-code-workspace task decision abandon <request-id> --yes --json
-```
-
-`ACTIVE` file conflicts cannot be overridden. `UNKNOWN` reservations remain protected until the user keeps them or abandons the entire generation; a known live process blocks abandon. The mechanism covers only trusted, enabled, supported Agent Hooks and is not an OS-level sandbox for editors, shells, or external processes.
-
-Hook support matrix (schema v1):
-
-| Provider | Lifecycle events | Write events | Target handling |
-| --- | --- | --- | --- |
-| Codex | `SessionStart`, `UserPromptSubmit`, `PermissionRequest`, `Stop`, `SessionEnd` | `PreToolUse`, `PostToolUse` and available failure events | Known Edit/Write-style tools use exact files; unknown shell/tools use `PROJECT_WIDE` |
-| Claude | `SessionStart`, `UserPromptSubmit`, `PermissionRequest`, `Stop`, `StopFailure`, `SessionEnd` | `PreToolUse`, `PostToolUse`, `PostToolUseFailure` | Same normalized core decisions and scope rules as Codex |
-
-The adapters are versioned fixtures rather than a promise that future Agent releases keep identical native fields. New or unrecognized tools fail closed as possible writes; Hook enforcement does not cover bypassed or disabled Hooks, external editors, or arbitrary OS processes.
-
 ## Update and language
 
 ```bash
 code-workspace update --json
 code-workspace update --language zh-CN --json
-code-workspace update --coordination --json
 code-workspace language --json
 ```
 

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` 仍然可用。
 
 ## 初始化
 
@@ -34,7 +34,6 @@ code-workspace init . \
 ```
 
 可用 `--tools claude`、`--tools codex` 或 `--tools none` 覆盖默认工具选择。选择 Codex 时默认启用监控；可传 `--no-monitor` 关闭。
-传入 `--coordination` 可把与 Monitor 独立的写入协调 Hook 安装到选中工具的原生配置中。
 
 初始化只写入 Workspace 自有状态和集成：
 
@@ -42,7 +41,7 @@ code-workspace init . \
 - `USER_GUIDE.md`
 - `CLAUDE.md` 和/或 `AGENTS.md`
 - 名称以 `code-workspace-` 开头或使用 `/code-workspace` 命名空间的 Workspace 专用命令与 Skill
-- 启用监控或 Codex 协调时的 `.codex/hooks.json`，以及启用 Claude 协调时的 `.claude/settings.json`
+- 启用监控时的 `.codex/hooks.json`
 
 它不会创建 `openspec/`，不会安装原生 `/opsx` 命令，也不会安装原生 `openspec-*` Skill。
 
@@ -51,11 +50,13 @@ code-workspace init . \
 `init` 可以从 npm 包内随附的版本化 `extensions/` 仓库安装集成。交互模式按扩展名多选；非交互模式传入逗号分隔的扩展名。独立安装命令接受一个或多个扩展名；不传名称时打开内置扩展多选，按 ESC 可无修改退出：
 
 ```bash
-code-w init . --extensions zhuiyi-jira-mcp --yes
-code-w init . --extensions none --yes
-code-w extension install
-code-w extension install zhuiyi-jira-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`。
@@ -64,7 +65,9 @@ code-w extension uninstall zhuiyi-jira-mcp --yes
 
 `extension install` 不会重新执行 Workspace 核心初始化。在 JSON、非 TTY 或 `--yes` 模式下，必须至少提供一个扩展名。多个名称按顺序安装，只确认一次且各自使用独立事务；任一扩展失败会使安装命令失败，但后续扩展仍会继续执行。
 
-当前随包提供的内置扩展是 `zhuiyi-jira-mcp`，用于为选中的 Agent 工具配置 Jira MCP 服务；它不会创建 `openspec/` 目录，也不会安装 OpenSpec 原生命令。
+当前随包提供的内置扩展包括 `zhuiyi-jira-mcp` 和 `zhuiyi-opensvn-mcp`，分别用于为选中的 Agent 工具配置 Jira MCP 与 OpenSVN MCP 服务；它们不会创建 `openspec/` 目录，也不会安装 OpenSpec 原生命令。
+
+`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 报告，不回滚已成功的核心初始化，也不阻止后续扩展；升级失败会恢复并保留旧的已安装版本。
 
@@ -73,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`。
 
 ## 注册项目
 
@@ -89,12 +92,14 @@ Claude Code 用户可显式调用：
 /code-workspace:add-projects /absolute/path/to/project-a /absolute/path/to/project-b
 ```
 
-Codex 用户可对相同的显式路径调用 `$code-workspace-add-projects`。底层自动化可准备完整项目记录，然后运行：
+Codex 用户可对相同的显式路径调用 `$code-workspace-add-projects`。底层自动化可通过 stdin 一次传入完整项目记录：
 
 ```bash
-code-workspace project add --projects-file projects.json --yes --json
+cat projects.json | code-workspace project add --stdin --yes --json
 ```
 
+`--stdin` 接受 `{ "schemaVersion": 1, "projects": [...] }` 形式且与 `--projects-file` 相同语义的 JSON，必须与 `--yes` 一起使用，并在输入为空、无效或超过 1 MiB 时于写入前失败。`--stdin`、`--project-file`、`--projects-file` 与位置路径只能选择一个。
+
 注册表保存项目名称、真实路径、注册分支、类型和上下文。注册分支是 Code Workspace 的期望状态，实际分支是从选中 Git worktree 观测到的状态。Workspace 不会根据对话猜测路径，也不会自动判断哪一侧分支更权威。
 
 项目注册配置始终独立保存于 `.code-workspace` 目录下的单独文件。初始化默认使用 `config-projects.yaml`，但 `projects.ref` 可以引用该目录下任意安全的普通文件名：
@@ -119,7 +124,7 @@ projects:
       服务职责和代码导航上下文。
 ```
 
-`projects.ref` 相对于 `config.yaml` 解析，必须是同一 `.code-workspace` 目录下的安全普通文件名。不支持 URL、glob、绝对路径、路径逃逸或内联 `projects` 数组。所有项目 CLI 的语义保持不变，只是改为读取和写入引用文件。`.code-workspace/` 默认被忽略；如需 Git 历史，需要显式制定仓库策略。
+`projects.ref` 相对于 `config.yaml` 解析，必须是同一 `.code-workspace` 目录下的安全普通文件名。不支持 URL、glob、绝对路径、路径逃逸或内联 `projects` 数组。项目命令的现有参数和行为保持兼容，`project add` 额外支持 `--stdin`；项目数据仍只读取和写入引用文件。`.code-workspace/` 默认被忽略；如需 Git 历史，需要显式制定仓库策略。
 
 例如，`ref: team-projects.yaml` 会将项目注册表放在 `.code-workspace/team-projects.yaml`；默认名称仍为 `config-projects.yaml`。
 
@@ -166,45 +171,11 @@ AI/Agent 不得直接编辑该文件；可以读取策略并调用已注册的 C
 
 `permissions apply` 会展示选中 Agent 工具的完整授权计划，在需要修改时要求确认，实施并验证请求的授权，并按工具报告结果。Agent 目录访问仍属于用户授权。该命令只补齐已注册项目缺失的访问权限，不撤销额外目录；如需撤销，请使用 `project remove` 或显式编辑 Agent 设置。
 
-## 协调并行 Agent 写入
-
-安装并信任 Codex 或 Claude 协调 Hook 后，Code Workspace 会把协调台账保存在 Workspace 外部，并在受支持工具真正运行前预约写入范围。同一项目写不同文件时，经过一次明确的项目并行确认即可继续；范围重叠时强制拒绝，不提供强制覆盖。
-
-查询任务、范围 claim 和待处理裁决：
-
-```bash
-code-workspace task list --json
-code-workspace task show <task-id> --json
-code-workspace task lock list --json
-code-workspace task decision show <request-id> --json
-```
-
-查看证据后再处理裁决。写入型命令需要确认；自动化场景必须传 `--yes`，裁决成功后始终重新执行原 Agent 操作：
-
-```bash
-code-workspace task decision keep <request-id> --yes --json
-code-workspace task decision approve <request-id> --yes --json
-code-workspace task decision release <request-id> --yes --json
-code-workspace task decision abandon <request-id> --yes --json
-```
-
-`ACTIVE` 文件冲突不能覆盖。`UNKNOWN` reservation 必须由用户选择保留，或放弃整个 generation；已知旧进程仍存活时不能 abandon。该机制只覆盖已信任、已启用且受支持的 Agent Hook，不是编辑器、Shell 或外部进程的 OS 级沙箱。
-
-Hook 支持矩阵（schema v1）：
-
-| Provider | 生命周期事件 | 写入事件 | 目标处理 |
-| --- | --- | --- | --- |
-| Codex | `SessionStart`、`UserPromptSubmit`、`PermissionRequest`、`Stop`、`SessionEnd` | `PreToolUse`、`PostToolUse` 及可用失败事件 | 已知 Edit/Write 类工具使用 exact 文件；未知 Shell/工具使用 `PROJECT_WIDE` |
-| Claude | `SessionStart`、`UserPromptSubmit`、`PermissionRequest`、`Stop`、`StopFailure`、`SessionEnd` | `PreToolUse`、`PostToolUse`、`PostToolUseFailure` | 与 Codex 使用相同的归一化核心决策和范围规则 |
-
-适配器通过版本化 fixture 固化输入，而不是承诺未来 Agent 版本保持相同原生字段。新增或无法识别的工具按可能写入处理并 fail closed；Hook 强制范围不包含被绕过或禁用的 Hook、外部编辑器或任意 OS 进程。
-
 ## 更新与语言
 
 ```bash
 code-workspace update --json
 code-workspace update --language en-US --json
-code-workspace update --coordination --json
 code-workspace language --json
 ```
 

package/artifacts/manifest.json

@@ -1,6 +1,6 @@
 {
   "schemaVersion": 2,
-  "releaseVersion": "0.1.0-beta.6",
+  "releaseVersion": "0.1.0-beta.8",
   "requirements": {
     "node": ">=20.19.0"
   },
@@ -13,26 +13,15 @@
       "id": "workspace-user-guide-en-US",
       "kind": "asset",
       "path": "templates/user-guide/en-US.md",
-      "sha256": "d6e3f59fc86262c4e71d2320fb2fba21394d7b4f099ef465fdec765d0b6c7754"
+      "sha256": "919217e7d7a1c59775f13803a1bf7645b48c01ba53bbb2cea9d666022c7ce7fc"
     },
     {
       "id": "workspace-user-guide-zh-CN",
       "kind": "asset",
       "path": "templates/user-guide/zh-CN.md",
-      "sha256": "4dc207305a3975ab7272addedf3bc2930054e860c2b0b2b6e0e102f4457f5cc0"
+      "sha256": "c41dd91cfeef475b48785f19253e1213fe14b3208b12c9dfd3e7aa7dad13a4a7"
     }
   ],
-  "coordinationArtifacts": {
-    "schemaVersion": 1,
-    "sources": [
-      { "id": "task-coordination-codex-hooks", "path": "templates/codex/task-coordination-hooks.json", "sha256": "68fcefa83f75294fd270713e07eb3ea3f266e63dc9d2be4ba77fe8af7596742f" },
-      { "id": "task-coordination-claude-settings", "path": "templates/claude/task-coordination-settings.json", "sha256": "4faedcc67a78c8e7e61e44dc34571e55d0d3a2ce1ce7aa636222e1813505ca29" }
-    ],
-    "managedFiles": [
-      { "id": "task-coordination-codex-hooks", "target": ".codex/task-coordination-hooks.json", "tool": "codex" },
-      { "id": "task-coordination-claude-settings", "target": ".claude/task-coordination-settings.json", "tool": "claude" }
-    ]
-  },
   "managedFiles": [
     {
       "id": "workspace-user-guide",
@@ -60,7 +49,7 @@
       "allowMissing": true,
       "desired": {
         "source": "templates/agents/WORKSPACE_GUARD.md.template",
-        "sha256": "6510cce83138fad46330d2c175506e56e9c98d5086195a699eafc7cc74163bf3"
+        "sha256": "bddb8e2ee25b7a63614b4297453e5803d2740fc475d97f5d8489dbaf17380c2c"
       },
       "render": {
         "variables": [
@@ -83,7 +72,7 @@
       "allowMissing": true,
       "desired": {
         "source": "templates/agents/WORKSPACE_GUARD.md.template",
-        "sha256": "6510cce83138fad46330d2c175506e56e9c98d5086195a699eafc7cc74163bf3"
+        "sha256": "bddb8e2ee25b7a63614b4297453e5803d2740fc475d97f5d8489dbaf17380c2c"
       },
       "render": {
         "variables": [
@@ -109,7 +98,7 @@
       "allowMissing": true,
       "desired": {
         "source": "templates/codex/hooks.json",
-        "sha256": "64d68809a2681b11d4b50bee3ca711fa8f5ea0a297c2281e5c7f8937e968e22e"
+        "sha256": "ecba346e0ce73d931802615dd798b952f1d0afabef3c67d7d1ee21f81b133b46"
       },
       "provenance": {
         "kind": "template"
@@ -124,7 +113,7 @@
       "allowMissing": true,
       "desired": {
         "source": "templates/claude/commands/code-workspace/add-projects.md",
-        "sha256": "7cd5a47c88185d276c0c4c38e18577e009e5e6d4ed99062554ff116b7e8d1812"
+        "sha256": "177fbebf35383e1499c274007a2c577a7cd2f727407bcd0a0ca0511f4666dd6e"
       },
       "provenance": {
         "kind": "template"
@@ -139,7 +128,7 @@
       "allowMissing": true,
       "desired": {
         "source": "templates/codex/skills/code-workspace-add-projects/SKILL.md",
-        "sha256": "f95847b00c93c2dd287247e226fecd6953286064dfde99b8ede830d181ef276f"
+        "sha256": "1b3a10870bd748244d85945b9a2562b7b30a8792bcd6163d8d53ed73cd9ef619"
       },
       "provenance": {
         "kind": "template"
@@ -154,7 +143,7 @@
       "allowMissing": true,
       "desired": {
         "source": "templates/codex/skills/code-workspace-add-projects/SKILL.md",
-        "sha256": "f95847b00c93c2dd287247e226fecd6953286064dfde99b8ede830d181ef276f"
+        "sha256": "1b3a10870bd748244d85945b9a2562b7b30a8792bcd6163d8d53ed73cd9ef619"
       },
       "provenance": {
         "kind": "template"
@@ -169,7 +158,7 @@
       "allowMissing": true,
       "desired": {
         "source": "templates/agents/skills/code-workspace-resolve-branch/SKILL.md",
-        "sha256": "d09b0e1847f5b39e6409ba3ac43f26fa5829a15690a3e216576e51535fb6b161"
+        "sha256": "df8c65fbadf917b7247bbd1f40144da8c904a95f2b3ee905a4d2d6176e0a5f1b"
       },
       "provenance": {
         "kind": "template"
@@ -184,7 +173,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/claude/commands/code-workspace/add-projects.md

@@ -1,5 +1,5 @@
 ---
-description: When explicitly invoked with one or more project paths, inspect Git worktrees read-only, generate concise project context, register the completed local records, and apply Agent directory authorization.
+description: When explicitly invoked with one or more project paths, inspect Git worktrees read-only, generate concise AI project context, register the completed records in one stdin transaction, and apply Agent directory authorization.
 argument-hint: "<project path> [additional project paths]"
 ---
 
@@ -7,17 +7,59 @@ Run this workflow only when the user explicitly invokes `/code-workspace:add-pro
 
 Expected invocation: `/code-workspace:add-projects /absolute/path/to/project-a /absolute/path/to/project-b`
 
-Before inspecting projects, run `code-workspace language --json` once. Require the standard envelope fields `schemaVersion`, `ok`, `command`, `data`, and `diagnostics`, then use `data.language` and the labels in `data.projectContext` for every generated project context in this invocation.
+## Collect evidence once
 
-For each supplied path:
+Use one read-only terminal invocation for `code-workspace language --json` and every supplied path. Inspect each path independently and continue after a path-specific failure:
 
-1. Run `code-workspace project inspect "<path>" --json`. Treat only its location, branch, manifest-file list, README-file list, and top-level entry list as CLI-verified facts.
-2. Inspect the repository read-only. Read only what is needed to understand it, starting with README files, root manifests, and relevant entry points or module directories. Do not modify the project repository.
-3. Produce a complete project record with `name`, canonical `location`, current `branch`, a concise semantic `type`, and `context`.
-4. Generate `context` as concise, stable project navigation for an AI that has not read the repository. Use exactly four semantic lines in this order: `responsibility`, `technologyStack`, `codeLocations`, and `projectBoundary`. Prefix each line with the corresponding label returned in `data.projectContext`; do not translate or replace those labels yourself. Write descriptions in the returned workspace `data.language`. Keep project names, paths, branches, technology names, identifiers, and code symbols unchanged. Prefer 150-400 Chinese characters or comparable English length. Do not include exhaustive dependencies, volatile command details, filler, or unsupported guesses.
+```bash
+code-workspace language --json
+for path in "<path-a>" "<path-b>"; do
+  printf '\n__PROJECT__ %s\n' "$path"
+  output="$(code-workspace project inspect "$path" --json)"
+  status=$?
+  printf '%s\n' "$output"
+  printf '__STATUS__ %s\n' "$status"
+done
+```
 
-Present all completed records for confirmation. After confirmation, write them to a temporary JSON document with `schemaVersion: 1` and a non-empty `projects` array, then run `code-workspace project add --projects-file <temporary-json-file> --yes --json` followed by `code-workspace project verify --json`.
+Require the standard envelope fields `schemaVersion`, `ok`, `command`, `data`, and `diagnostics`. Use `data.language` and the labels in `data.projectContext` for every generated project context in this invocation. If the language command fails, stop: the workspace language contract is unavailable.
 
-Do not hand-edit `.code-workspace/config.yaml` or permission files. Completion requires successful registration, authorization application, and project verification.
+For each inspection:
+
+- When `ok` is true, treat only `data.project.location`, `data.project.branch`, and `data.project.facts` as CLI-verified facts, then inspect the repository read-only.
+- When `ok` is false, retain the path, diagnostic code, message, and remediation. Do not inspect that repository or create a project record for it.
+- Continue collecting the remaining paths. Do not stop at the first failed project.
+
+## Prepare records
+
+For each valid inspection, read only what is needed to understand the repository, starting with README files, root manifests, and relevant entry points or module directories. Do not modify the project repository.
+
+Produce a complete project record with `name`, canonical `location`, current `branch`, a concise semantic `type`, and `context`.
+
+Generate `context` as concise, stable project navigation for an AI that has not read the repository. Use exactly four semantic lines in this order: `responsibility`, `technologyStack`, `codeLocations`, and `projectBoundary`. Prefix each line with the corresponding label returned in `data.projectContext`; do not translate or replace those labels yourself. Write descriptions in the returned workspace `data.language`. Keep project names, paths, branches, technology names, identifiers, and code symbols unchanged. Prefer 150-400 Chinese characters or comparable English length. Do not include exhaustive dependencies, volatile command details, filler, or unsupported guesses.
+
+## Confirm once
+
+Present all valid records and every failed path together. If any path failed, state clearly that only the valid records will be written and do not treat the failed paths as ignored without user confirmation. Ask for one decision:
+
+- add the valid records;
+- correct and retry failed paths;
+- cancel.
+
+If there are no valid records, stop without writing.
+
+## Register through stdin
+
+After confirmation, serialize one JSON document with `schemaVersion: 1` and a non-empty `projects` array containing only the confirmed valid records. Send it to `code-workspace project add` over stdin:
+
+```bash
+code-workspace project add --stdin --yes --json
+```
+
+Use the runtime's native stdin channel when available. Do not create a temporary JSON file and do not place the JSON document in command arguments. If a shell heredoc is the only available transport, use a unique, unpredictable, quoted delimiter and pass the serialized JSON unchanged.
+
+Completion requires `ok: true`, the expected registered projects, and every applicable permission result to report `verified: true`. `project add` performs the existing configuration and authorization postcondition verification inside its transaction. Do not run `code-workspace project verify --json` by default; run it only when the user explicitly asks for an independent final check.
+
+Do not hand-edit `.code-workspace/config.yaml` or permission files.
 
 $ARGUMENTS

package/artifacts/templates/codex/hooks.json

@@ -6,7 +6,7 @@
         "hooks": [
           {
             "type": "command",
-            "command": "code-w monitor report",
+            "command": "codew monitor report",
             "timeout": 1
           }
         ]
@@ -18,7 +18,7 @@
         "hooks": [
           {
             "type": "command",
-            "command": "code-w monitor report",
+            "command": "codew monitor report",
             "timeout": 1
           }
         ]
@@ -30,7 +30,7 @@
         "hooks": [
           {
             "type": "command",
-            "command": "code-w monitor report",
+            "command": "codew monitor report",
             "timeout": 1
           }
         ]
@@ -42,7 +42,7 @@
         "hooks": [
           {
             "type": "command",
-            "command": "code-w monitor report",
+            "command": "codew monitor report",
             "timeout": 1
           }
         ]
@@ -54,7 +54,7 @@
         "hooks": [
           {
             "type": "command",
-            "command": "code-w monitor report",
+            "command": "codew monitor report",
             "timeout": 1
           }
         ]
@@ -65,7 +65,7 @@
         "hooks": [
           {
             "type": "command",
-            "command": "code-w monitor report",
+            "command": "codew monitor report",
             "timeout": 1
           }
         ]
@@ -76,7 +76,7 @@
         "hooks": [
           {
             "type": "command",
-            "command": "code-w monitor report",
+            "command": "codew monitor report",
             "timeout": 1
           }
         ]