code-workspace-zhuiyi 0.1.0-beta.1 → 0.1.0-beta.11

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,43 +33,63 @@ 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:
 
-- `.code-workspace/config.yaml` and `.code-workspace/state.json`
+- `.code-workspace/config.yaml`, its referenced project configuration file (default: `.code-workspace/config-projects.yaml`), and `.code-workspace/state.json`
 - `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.
 
 ### Experimental built-in extensions
 
-`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:
+`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 with no extensions selected, where each choice shows its name and a short description. ESC exits without changes:
 
 ```bash
-code-w init . --extensions openspec-workspace --yes
-code-w init . --extensions none --yes
-code-w extension install
-code-w extension install openspec-workspace --yes
-code-w extension uninstall openspec-workspace --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 install code-workspace-jira-prd-analysis --yes
+codew extension install code-workspace-jira-task-breakdown --yes
+codew extension install code-workspace-issue-fix-summary --yes
+codew extension install code-workspace-guangda-coding-spec --yes
+codew extension uninstall zhuiyi-jira-mcp --yes
+codew extension uninstall code-workspace-jira-prd-analysis --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.
 
-Users select names, not versions; `openspec-workspace@1.0.0` is intentionally rejected. Code Workspace resolves the highest extension SemVer implemented against a Host-supported Extension Spec before confirmation. A new non-interactive Workspace installs no extensions unless `--extensions` is provided. Re-initializing an existing Workspace defaults to its installed extensions and upgrades them when a newer supported built-in version exists. `none` skips extension work and does not uninstall existing artifacts.
+Users select names, not versions; `zhuiyi-jira-mcp@0.1.0` is intentionally rejected. Code Workspace resolves the highest extension SemVer implemented against a Host-supported Extension Spec before confirmation. A new non-interactive Workspace installs no extensions unless `--extensions` is provided. Re-initializing an existing Workspace defaults to its installed extensions and upgrades them when a newer supported built-in version exists. `none` skips extension work and does not uninstall existing artifacts.
 
 `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 `openspec-workspace` extension installs a namespaced `code-workspace-openspec-propose` skill 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.
+
+The bundled `code-workspace-jira-prd-analysis`, `code-workspace-jira-task-breakdown`, and `code-workspace-issue-fix-summary` extensions install optional Codex and Claude Code skill files. They are independent extensions, are not installed by core `init` or `update`, and can be uninstalled separately. Install `zhuiyi-jira-mcp` separately when they need Jira access.
+
+The bundled `code-workspace-guangda-coding-spec` extension installs a Codex and Claude Code skill that applies the China Everbright Bank research, security, testing, and release rules to Guangda customer projects. It is independent of core `init` and `update`, can be uninstalled separately, and requires no MCP service.
+
+The MCP runtime packages are not copied into the Workspace. Only their configuration is stored there; a launcher prepares and caches each package on demand in the user-level Extension Store.
+
+`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.
 
-Extensions may own complete files or contribute Host-managed Codex TOML blocks and Hook fragments. Shared targets are composed and verified by Code Workspace; extensions never patch the real Workspace directly. Uninstall uses recorded installed state and does not execute extension code. Unknown changes to extension-owned files or contributions stop the operation instead of being overwritten.
+Extensions may own complete files or declare Host-managed abstract Hooks. Codex and Claude
+adaptors render those declarations into each provider's native configuration and dynamically plug
+or unplug them during extension install, upgrade, and uninstall. Shared targets are composed and
+verified by Code Workspace; extensions never patch the real Workspace directly. Uninstall uses
+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
 
@@ -85,14 +105,42 @@ 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:
+
+```yaml
+# .code-workspace/config.yaml
+projects:
+  ref: config-projects.yaml
+```
+
+The referenced file uses this format:
+
+```yaml
+# .code-workspace/config-projects.yaml
+schemaVersion: 1
+projects:
+  - name: payments
+    location: /absolute/path/to/payments
+    branch: main
+    type: backend
+    context: |-
+      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. 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`.
+
 ## Daily commands
 
 ```bash
@@ -117,11 +165,18 @@ The two reconciliation directions are deliberately separate:
 
 Both commands detect plan drift and verify postconditions. `project branch update-latest` is the separate, opt-in path for projects with `updateLatest: true`; it only fetches the configured upstream and fast-forwards a clean matching branch. Code Workspace never creates or downloads a branch and never performs stash, reset, rebase, non-fast-forward merge, production-code edits, or conflict resolution.
 
-Users may manually set the optional project policy in `.code-workspace/config.yaml`:
+Users may manually set the optional project policy in the file named by `projects.ref` (default: `.code-workspace/config-projects.yaml`):
 
 ```yaml
+# .code-workspace/config-projects.yaml
+schemaVersion: 1
 projects:
   - name: payments
+    location: /absolute/path/to/payments
+    branch: main
+    type: backend
+    context: |-
+      Service ownership and navigation context.
     updateLatest: true
 ```
 
@@ -141,13 +196,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,43 +33,61 @@ code-workspace init . \
   --yes
 ```
 
-可用 `--tools claude`、`--tools codex` 或 `--tools none` 覆盖默认工具选择。选择 Codex 时默认启用监控；可传 `--no-monitor` 关闭。
+可用 `--tools claude`、`--tools codex` 或 `--tools none` 覆盖默认工具选择。监控不会隐式启用；请通过 `--extensions monitor` 或交互式扩展选择安装 `monitor` 扩展。
 
 初始化只写入 Workspace 自有状态和集成：
 
-- `.code-workspace/config.yaml` 与 `.code-workspace/state.json`
+- `.code-workspace/config.yaml`、其引用的项目配置文件（默认：`.code-workspace/config-projects.yaml`）与 `.code-workspace/state.json`
 - `USER_GUIDE.md`
 - `CLAUDE.md` 和/或 `AGENTS.md`
 - 名称以 `code-workspace-` 开头或使用 `/code-workspace` 命名空间的 Workspace 专用命令与 Skill
-- 启用监控时的 `.codex/hooks.json`
+- 安装 `monitor` 扩展时由扩展写入的 `.codex/hooks.json`
 
 它不会创建 `openspec/`，不会安装原生 `/opsx` 命令，也不会安装原生 `openspec-*` Skill。
 
 ### 试验性内置扩展
 
-`init` 可以从 npm 包内随附的版本化 `extensions/` 仓库安装集成。交互模式按扩展名多选；非交互模式传入逗号分隔的扩展名。独立安装命令接受一个或多个扩展名；不传名称时打开内置扩展多选，按 ESC 可无修改退出：
+`init` 可以从 npm 包内随附的版本化 `extensions/` 仓库安装集成。交互模式按扩展名多选；非交互模式传入逗号分隔的扩展名。独立安装命令接受一个或多个扩展名；不传名称时打开内置扩展多选，每个选项显示名称和简短描述，且默认不勾选任何扩展，按 ESC 可无修改退出：
 
 ```bash
-code-w init . --extensions openspec-workspace --yes
-code-w init . --extensions none --yes
-code-w extension install
-code-w extension install openspec-workspace --yes
-code-w extension uninstall openspec-workspace --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 install code-workspace-jira-prd-analysis --yes
+codew extension install code-workspace-jira-task-breakdown --yes
+codew extension install code-workspace-issue-fix-summary --yes
+codew extension install code-workspace-guangda-coding-spec --yes
+codew extension uninstall zhuiyi-jira-mcp --yes
+codew extension uninstall code-workspace-jira-prd-analysis --yes
 ```
 
 `init`、扩展安装和扩展卸载共享的 Workspace 操作锁配置在 Code Workspace 项目自身的 `.env` 中（不在目标 Workspace 中）。`CODE_WORKSPACE_INIT_LOCK_UPDATE_MS` 默认值为 `5000`，`CODE_WORKSPACE_INIT_LOCK_STALE_MS` 默认值为 `30000`；进程环境变量优先于 `.env`。配置项名称见 `.env.example`。
 
-用户只选择扩展名，不能选择版本；`openspec-workspace@1.0.0` 会被明确拒绝。Code Workspace 在确认前，从 Host 明确支持的 Extension Spec 实现中解析最高扩展 SemVer。新 Workspace 非交互初始化时，未传 `--extensions` 就不安装扩展；已有 Workspace 重新初始化时，默认选择已安装扩展，并在存在更高受支持内置版本时升级。`none` 只跳过本次扩展初始化，不会卸载已有制品。
+用户只选择扩展名，不能选择版本；`zhuiyi-jira-mcp@0.1.0` 会被明确拒绝。Code Workspace 在确认前，从 Host 明确支持的 Extension Spec 实现中解析最高扩展 SemVer。新 Workspace 非交互初始化时，未传 `--extensions` 就不安装扩展；已有 Workspace 重新初始化时，默认选择已安装扩展，并在存在更高受支持内置版本时升级。`none` 只跳过本次扩展初始化，不会卸载已有制品。
 
 `extension install` 不会重新执行 Workspace 核心初始化。在 JSON、非 TTY 或 `--yes` 模式下，必须至少提供一个扩展名。多个名称按顺序安装，只确认一次且各自使用独立事务；任一扩展失败会使安装命令失败，但后续扩展仍会继续执行。
 
-内置 `openspec-workspace` 扩展会为选中的 Agent 工具安装命名空间为 `code-workspace-openspec-propose` 的 Skill；它不会创建 `openspec/` 目录，也不会安装 OpenSpec 原生命令。
+当前随包提供的内置扩展包括 `zhuiyi-jira-mcp` 和 `zhuiyi-opensvn-mcp`，分别用于为选中的 Agent 工具配置 Jira MCP 与 OpenSVN MCP 服务；它们不会创建 `openspec/` 目录，也不会安装 OpenSpec 原生命令。
+
+随包还提供 `code-workspace-jira-prd-analysis`、`code-workspace-jira-task-breakdown` 和 `code-workspace-issue-fix-summary` 三个 Skill 扩展，用于安装可选的 Codex 与 Claude Code Skill 文件。它们不随核心 `init` 或 `update` 安装，可以独立安装和卸载；需要 Jira 访问时另行安装 `zhuiyi-jira-mcp`。
+
+随包还提供 `code-workspace-guangda-coding-spec` Skill 扩展，用于在光大客户项目按风险域落实研发、安全、测试与投产规范。它同样不随核心 `init` 或 `update` 安装，可以独立安装和卸载，且不依赖任何 MCP 服务。
+
+两个 MCP 的运行包不会复制到 Workspace；Workspace 只保存 MCP 配置，运行包由用户级 Extension Store 中的 launcher 按需缓存。
+
+`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 报告，不回滚已成功的核心初始化，也不阻止后续扩展；升级失败会恢复并保留旧的已安装版本。
 
-扩展可以独占完整文件，也可以贡献由 Host 管理的 Codex TOML 配置块和 Hook 片段。共享目标由 Code Workspace 合成和验证；扩展不会直接 patch 真实 Workspace。卸载只使用已安装状态，不执行扩展代码；扩展所有的文件或贡献存在未知修改时会拒绝覆盖或删除。
+扩展可以独占完整文件，也可以声明由 Host 管理的抽象 Hook。Host 通过 Codex/Claude adaptor
+把声明转换为各自的原生配置，并在扩展安装、升级和卸载时动态插拔；共享目标由 Code
+Workspace 合成和验证，扩展不会直接 patch 真实 Workspace。卸载只使用已安装状态，不执行
+扩展代码；扩展所有的文件或贡献存在未知修改时会拒绝覆盖或删除。
 
-这是故障隔离，不是恶意代码安全沙箱。试验版本只信任随 Code Workspace 发布的扩展代码；暂不支持网络源、外部扩展目录、扩展依赖、任意 patch、强制卸载、禁用命令，也不会通过 `code-w update` 自动更新扩展。开发契约见 `docs/extensions.zh-CN.md`。
+这是故障隔离，不是恶意代码安全沙箱。试验版本只信任随 Code Workspace 发布的扩展代码；暂不支持网络源、外部扩展目录、扩展依赖、任意 patch、强制卸载、禁用命令，也不会通过 `codew update` 自动更新扩展。开发契约见 `docs/extensions.zh-CN.md`。
 
 ## 注册项目
 
@@ -85,14 +103,42 @@ 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` 可以引用该目录下任意安全的普通文件名：
+
+```yaml
+# .code-workspace/config.yaml
+projects:
+  ref: config-projects.yaml
+```
+
+引用文件使用以下格式：
+
+```yaml
+# .code-workspace/config-projects.yaml
+schemaVersion: 1
+projects:
+  - name: payments
+    location: /absolute/path/to/payments
+    branch: main
+    type: backend
+    context: |-
+      服务职责和代码导航上下文。
+```
+
+`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`。
+
 ## 日常命令
 
 ```bash
@@ -117,11 +163,18 @@ code-workspace doctor --json
 
 两条命令都会检查计划漂移并验证后置条件。`project branch update-latest` 是独立的显式配置路径：仅当项目 `updateLatest: true` 时，才对干净且分支一致的 worktree fetch upstream 并 fast-forward。Code Workspace 不会创建或下载分支，也不会执行 stash、reset、rebase、非 fast-forward merge、生产代码编辑或冲突处理。
 
-用户可以手动在 `.code-workspace/config.yaml` 中设置项目策略：
+用户可以手动在 `projects.ref` 指定的文件（默认：`.code-workspace/config-projects.yaml`）中设置项目策略：
 
 ```yaml
+# .code-workspace/config-projects.yaml
+schemaVersion: 1
 projects:
   - name: payments
+    location: /absolute/path/to/payments
+    branch: main
+    type: backend
+    context: |-
+      服务职责和代码导航上下文。
     updateLatest: true
 ```
 
@@ -141,11 +194,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.1",
+  "releaseVersion": "0.1.0-beta.11",
   "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": "d6e3f59fc86262c4e71d2320fb2fba21394d7b4f099ef465fdec765d0b6c7754"
+      "sha256": "29101b634cfe38dbb31d47754984a07b472d2bef83b295f609a390ad01eb7ee6"
     },
     {
       "id": "workspace-user-guide-zh-CN",
       "kind": "asset",
       "path": "templates/user-guide/zh-CN.md",
-      "sha256": "4dc207305a3975ab7272addedf3bc2930054e860c2b0b2b6e0e102f4457f5cc0"
+      "sha256": "105730f83450f8be44bdf69b6c25b782fd218215695e34b0dd204aa3fb6f61a5"
     }
   ],
   "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": [
@@ -87,63 +87,60 @@
       }
     },
     {
-      "id": "workspace-codex-monitor-hooks",
-      "target": ".codex/hooks.json",
+      "id": "workspace-claude-add-projects-command",
+      "target": ".claude/commands/code-workspace/add-projects.md",
       "tools": [
-        "codex"
-      ],
-      "capabilities": [
-        "monitor"
+        "claude"
       ],
       "allowMissing": true,
       "desired": {
-        "source": "templates/codex/hooks.json",
-        "sha256": "64d68809a2681b11d4b50bee3ca711fa8f5ea0a297c2281e5c7f8937e968e22e"
+        "source": "templates/claude/commands/code-workspace/add-projects.md",
+        "sha256": "177fbebf35383e1499c274007a2c577a7cd2f727407bcd0a0ca0511f4666dd6e"
       },
       "provenance": {
         "kind": "template"
       }
     },
     {
-      "id": "workspace-claude-add-projects-command",
-      "target": ".claude/commands/code-workspace/add-projects.md",
+      "id": "workspace-claude-add-projects-skill",
+      "target": ".claude/skills/code-workspace-add-projects/SKILL.md",
       "tools": [
         "claude"
       ],
       "allowMissing": true,
       "desired": {
-        "source": "templates/claude/commands/code-workspace/add-projects.md",
-        "sha256": "7cd5a47c88185d276c0c4c38e18577e009e5e6d4ed99062554ff116b7e8d1812"
+        "source": "templates/codex/skills/code-workspace-add-projects/SKILL.md",
+        "sha256": "1b3a10870bd748244d85945b9a2562b7b30a8792bcd6163d8d53ed73cd9ef619"
       },
       "provenance": {
         "kind": "template"
       }
     },
     {
-      "id": "workspace-claude-add-projects-skill",
-      "target": ".claude/skills/code-workspace-add-projects/SKILL.md",
+      "id": "workspace-codex-add-projects-skill",
+      "target": ".codex/skills/code-workspace-add-projects/SKILL.md",
       "tools": [
-        "claude"
+        "codex"
       ],
       "allowMissing": true,
       "desired": {
         "source": "templates/codex/skills/code-workspace-add-projects/SKILL.md",
-        "sha256": "f95847b00c93c2dd287247e226fecd6953286064dfde99b8ede830d181ef276f"
+        "sha256": "1b3a10870bd748244d85945b9a2562b7b30a8792bcd6163d8d53ed73cd9ef619"
       },
       "provenance": {
         "kind": "template"
       }
     },
     {
-      "id": "workspace-codex-add-projects-skill",
-      "target": ".codex/skills/code-workspace-add-projects/SKILL.md",
+      "id": "workspace-codex-add-projects-openai",
+      "target": ".codex/skills/code-workspace-add-projects/agents/openai.yaml",
       "tools": [
         "codex"
       ],
       "allowMissing": true,
       "desired": {
-        "source": "templates/codex/skills/code-workspace-add-projects/SKILL.md",
-        "sha256": "f95847b00c93c2dd287247e226fecd6953286064dfde99b8ede830d181ef276f"
+        "source": "templates/codex/skills/code-workspace-add-projects/agents/openai.yaml",
+        "sha256": "5aab2f33feb64c6d9d2da4125afebbd484cbd2cbb522d4faf47821ec2ef4d85a"
       },
       "provenance": {
         "kind": "template"
@@ -158,7 +155,7 @@
       "allowMissing": true,
       "desired": {
         "source": "templates/agents/skills/code-workspace-resolve-branch/SKILL.md",
-        "sha256": "d09b0e1847f5b39e6409ba3ac43f26fa5829a15690a3e216576e51535fb6b161"
+        "sha256": "df8c65fbadf917b7247bbd1f40144da8c904a95f2b3ee905a4d2d6176e0a5f1b"
       },
       "provenance": {
         "kind": "template"
@@ -173,7 +170,22 @@
       "allowMissing": true,
       "desired": {
         "source": "templates/agents/skills/code-workspace-resolve-branch/SKILL.md",
-        "sha256": "d09b0e1847f5b39e6409ba3ac43f26fa5829a15690a3e216576e51535fb6b161"
+        "sha256": "df8c65fbadf917b7247bbd1f40144da8c904a95f2b3ee905a4d2d6176e0a5f1b"
+      },
+      "provenance": {
+        "kind": "template"
+      }
+    },
+    {
+      "id": "workspace-codex-resolve-branch-openai",
+      "target": ".codex/skills/code-workspace-resolve-branch/agents/openai.yaml",
+      "tools": [
+        "codex"
+      ],
+      "allowMissing": true,
+      "desired": {
+        "source": "templates/agents/skills/code-workspace-resolve-branch/agents/openai.yaml",
+        "sha256": "66d111bbc40ac800cec568479ddd608eea9899ce53d1e660c30ef3c619c7c5a4"
       },
       "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/agents/skills/code-workspace-resolve-branch/agents/openai.yaml

@@ -0,0 +1,6 @@
+interface:
+  display_name: "Code Workspace Resolve Branches"
+  short_description: "解决分支不匹配问题(被动触发)"
+  default_prompt: "Use $code-workspace-resolve-branch to reconcile the selected projects' branch mismatch."
+policy:
+  allow_implicit_invocation: false