@jspg-ai/coding-bb 0.0.1 → 0.0.2-beta.22

package/cbb/worktrees/skills/{openspec-push-worktrees → cbb-worktree-push}/scripts/commit-worktrees.js

@@ -1,6 +1,6 @@
 require('./silence-popup');
 /**
- * openspec-push-worktrees 批量 commit 所有 worktree 仓库
+ * cbb-worktree-push 批量 commit 所有 worktree 仓库
  *
  * 用法：
  *   node commit-worktrees.js <ws_root> <branch> --message "msg" [--untracked] [--per-repo "ep-foo:m1;ep-bar:m2"] [--allow-empty] [--dry-run] [--skip-repo name]
@@ -109,7 +109,7 @@ function scanWorktreeRepos(wsRoot, branch) {
     if (!e.isDirectory() || e.name.startsWith('.')) continue;
     const appWt = path.join(wtRoot, e.name);
     if (!isGitRepo(appWt)) continue;
-    repos.push({ name: e.name, wt: appWt, repo: path.join(wsRoot, '.code', e.name) });
+    repos.push({ name: e.name, wt: appWt, repo: path.join(wsRoot, '.codespace', e.name) });
   }
   return { wtRoot, repos, error: null };
 }

package/cbb/worktrees/skills/{openspec-push-worktrees → cbb-worktree-push}/scripts/find-target-worktree.js

@@ -47,7 +47,7 @@ if (cwdMatch) {
 const worktreesDir = path.join(wsRoot, '.worktrees');
 if (!fs.existsSync(worktreesDir)) {
   console.error('❌ .worktrees 目录不存在：' + worktreesDir);
-  console.error('   请先执行 openspec-init-worktree 创建 worktree');
+  console.error('   请先执行 cbb-worktree-init 创建 worktree');
   console.log('---');
   console.log('NO_WORKTREE');
   process.exit(2);
@@ -65,7 +65,7 @@ const entries = fs.readdirSync(worktreesDir, { withFileTypes: true })
 
 if (entries.length === 0) {
   console.error('❌ 未找到任何 worktree');
-  console.error('   请先执行 openspec-init-worktree 创建 worktree');
+  console.error('   请先执行 cbb-worktree-init 创建 worktree');
   console.log('---');
   console.log('NO_WORKTREE');
   process.exit(2);

package/cbb/worktrees/skills/{openspec-extend-worktree → cbb-worktree-push}/scripts/find-workspace-root.js

@@ -5,8 +5,8 @@ require('./silence-popup');
  * 唯一真源：cbb/worktrees/_shared/scripts/find-workspace-root.js
  * 由 scripts/sync-shared.js 展开到各 skill 的 scripts/ 下（init / extend / close / push）。
  *
- * 优先：git worktree list 第一行（主仓库根目录，不受 worktree 内 CONFIG.json 副本干扰）
- * 兜底：当前目录含 CONFIG.json
+ * 优先：git worktree list 第一行（主仓库根目录，不受 worktree 内 workspace-config.json 副本干扰）
+ * 兜底：当前目录含 workspace-config.json
  *
  * 退出码：
  *   0 - 定位成功，输出 WS_ROOT 绝对路径
@@ -44,19 +44,19 @@ if (worktreeList.ok) {
   }
 }
 
-// 兜底：当前目录含 CONFIG.json
+// 兜底：当前目录含 workspace-config.json
 if (!wsRoot) {
   const cwd = process.cwd();
-  if (fs.existsSync(path.join(cwd, 'CONFIG.json'))) {
+  if (fs.existsSync(path.join(cwd, 'workspace-config.json'))) {
     wsRoot = cwd;
   }
 }
 
 // 校验
-if (!wsRoot || !fs.existsSync(path.join(wsRoot, 'CONFIG.json'))) {
+if (!wsRoot || !fs.existsSync(path.join(wsRoot, 'workspace-config.json'))) {
   console.error('❌ 未找到工作空间根目录');
-  console.error('   原因：git worktree list 失败且当前目录无 CONFIG.json');
-  console.error('   请在业务工作空间根目录（由 cbb setup 初始化、包含 CONFIG.json）下执行本技能');
+  console.error('   原因：git worktree list 失败且当前目录无 workspace-config.json');
+  console.error('   请在业务工作空间根目录（由 cbb setup 初始化、包含 workspace-config.json）下执行本技能');
   process.exit(1);
 }
 

package/cbb/worktrees/skills/{openspec-push-worktrees → cbb-worktree-push}/scripts/push-core.js

@@ -12,6 +12,12 @@ require('./silence-popup');
  *   - pushSingle(repoPath, repoName, branch)  推送单个仓库并建立 upstream
  *   - collectRemoteMetadata(repoPath, branch, remote)  采集远程 commit 元信息
  *
+ * pushSingle 状态契约：
+ *   - pushed                 本次推送成功（新建分支或快进）
+ *   - skipped                远程同名分支已存在且与本地一致 → 无需推送（幂等，重跑 init 场景）
+ *   - remote-exists          远程同名分支存在但与本地不一致 → 需用户决策（附 metadata）
+ *   - failed                 推送失败，error 见错误码契约
+ *
  * 错误码契约（classifyError 输出）：
  *   - ssh-auth-failed        Permission denied (publickey)
  *   - https-auth-failed      Authentication failed
@@ -115,6 +121,18 @@ function pushSingle(repoPath, repoName, branch, opts) {
   const r = remote.out.split(/\r?\n/)[0];
   const branchEsc = escapeBranch(branch);
   const remoteEsc = '"' + String(r).replace(/\\/g, '\\\\').replace(/"/g, '\\"') + '"';
+
+  // 幂等：远程同名分支已存在且 hash 与本地完全一致 → 此前已推送，直接跳过。
+  // 让 init-worktree 可安全重跑（补齐新增应用/中断恢复），且不会重复推送或误报 remote-exists。
+  const lsRemote = tryExec('git ls-remote --heads ' + remoteEsc + ' ' + escapeBranch('refs/heads/' + branch), repoPath, execImpl);
+  if (lsRemote.ok && lsRemote.out) {
+    const remoteHash = lsRemote.out.split(/\s+/)[0];
+    const localHash = tryExec('git rev-parse --verify ' + branchEsc, repoPath, execImpl);
+    if (localHash.ok && localHash.out && localHash.out === remoteHash) {
+      return { name: repoName, status: 'skipped', upstream: r + '/' + branch, message: '远程分支与本地一致，无需推送' };
+    }
+  }
+
   const pushResult = tryExec('git push -u ' + remoteEsc + ' ' + branchEsc, repoPath, execImpl);
   if (pushResult.ok) {
     return { name: repoName, status: 'pushed', upstream: r + '/' + branch };

package/cbb/worktrees/skills/{openspec-push-worktrees → cbb-worktree-push}/scripts/push-worktrees.js

@@ -1,6 +1,6 @@
 require('./silence-popup');
 /**
- * openspec-push-worktrees 推送所有 worktree 仓库
+ * cbb-worktree-push 推送所有 worktree 仓库
  *
  * 用法：
  *   node push-worktrees.js <ws_root> <branch>
@@ -17,12 +17,12 @@ require('./silence-popup');
  *   2 - 部分或全部推送失败（AI agent 必须阻塞流程）
  *
  * 与 init-worktree/scripts/push-branches.js 的区别：
- *   - push-branches.js 推送 workspace 主目录 + .code/<app>/（创建 worktree 时使用）
+ *   - push-branches.js 推送 workspace 主目录 + .codespace/<app>/（创建 worktree 时使用）
  *   - push-worktrees.js 推送 .worktrees/worktree-<branch>/ 下所有 worktree（开发完成时使用）
  *
  * 错误码契约复用 push-core.classifyError：
- *   - pushed / remote-exists / failed(ssh-auth-failed / https-auth-failed / network-unreachable
- *     / branch-protected / no-remote / non-fast-forward / unknown)
+ *   - pushed / skipped（远程已一致）/ remote-exists / failed(ssh-auth-failed / https-auth-failed
+ *     / network-unreachable / branch-protected / no-remote / non-fast-forward / unknown)
  */
 
 const { pushSingle } = require('./push-core');
@@ -82,7 +82,7 @@ function scanWorktreeRepos(wsRoot, branch) {
     if (e.name.startsWith('.')) continue;
     const appWt = path.join(wtRoot, e.name);
     if (!isGitRepo(appWt)) continue;
-    repos.push({ name: e.name, wt: appWt, repo: path.join(wsRoot, '.code', e.name) });
+    repos.push({ name: e.name, wt: appWt, repo: path.join(wsRoot, '.codespace', e.name) });
   }
   return { wtRoot, repos, error: null };
 }
@@ -139,6 +139,8 @@ function main() {
   for (const r of results) {
     if (r.status === 'pushed') {
       console.log('✅ ' + r.name + ': 已推送 ' + r.upstream);
+    } else if (r.status === 'skipped') {
+      console.log('⏭️  ' + r.name + ': 远程分支与本地一致，跳过推送');
     } else if (r.status === 'remote-exists') {
       console.log('⚠️  ' + r.name + ': 远程分支已存在（需用户决策）');
     } else {

package/config/workspace-config.sample.json

@@ -0,0 +1,18 @@
+{
+    "_comment": "AI 开发工作空间配置样例（请勿修改本文件，复制为工作空间根目录的 workspace-config.json 后编辑使用）。apps 数组中每个对象需包含：name（应用名，同时作为 .codespace/ 子目录名）、repo（Git 仓库地址，支持 SSH 或 HTTPS）、side（仓库类型，'front' 表示前端工程，'back' 表示后端工程）；可选 desc（该应用的职责描述，便于人与 AI 理解应用分工）。",
+    "apps":
+    [
+        {
+            "name": "ep-user-auth-app",
+            "repo": "git@code.example.com:team/ep-user-auth-app.git",
+            "side": "back",
+            "desc": "用户认证与授权服务：登录注册、Token 签发与校验、权限模型"
+        },
+        {
+            "name": "ep-user-web",
+            "repo": "git@code.example.com:team/ep-user-web.git",
+            "side": "front",
+            "desc": "用户中心前端：登录注册页、账号与个人信息管理界面"
+        }
+    ]
+}

package/config/workspaces.json

@@ -2,14 +2,19 @@
   "_comment": "业务空间与 GitLab 仓库映射表，由本项目维护者配置。执行 `cbb setup` 时会列出本表中的所有业务空间让用户选择，并在当前目录自动检测/拉取对应仓库，再继续安装本项目的现有能力。name 用于显示，可含中文；repo 为 `git clone` 命令接受的地址，支持 SSH（git@host:path）与 HTTPS（https://host/path）两种形式；businessLine 用于业务归类（如：直采、增值、KA 等），便于后续按业务线筛选或分组展示。",
   "workspaces": [
     {
-      "name": "直采AI开发工作空间",
-      "repo": "git@code.amh-group.com:yzg/ymm-ka-ai-workspace.git",
-      "businessLine": "TMS"
+      "name": "江苏一港通openapi平台-AI开发工作空间",
+      "repo": "http://git.portjs.cn/jspg-ai/ai-workspace/jsygt-openapi-aiws.git",
+      "businessLine": "jsygt"
     },
     {
-      "name": "ETC业务AI开发工作空间",
-      "repo": "git@code.amh-group.com:etc/etc-ai-workspace.git",
-      "businessLine": "TMS"
+      "name": "扬州港智能安防项目-AI开发工作空间",
+      "repo": "http://git.portjs.cn/jspg-ai/ai-workspace/yzg-ai-security-aiws.git",
+      "businessLine": "yzg-ai"
+    },
+    {
+      "name": "江苏港口集团数据-AI开发工作空间",
+      "repo": "http://git.portjs.cn/jspg-ai/ai-workspace/jspg-data-labeling-aiws.git",
+      "businessLine": "yzg-ai"
     }
   ]
 }

package/openspec/.version

@@ -1,6 +1,6 @@
-{
-  "sha": "9d4e5974e5c0d9a09b9c6c1e1eb0975e80ec4461",
-  "branch": "main",
-  "repo": "Fission-AI/OpenSpec",
-  "updatedAt": "2026-09-12T00:00:00.000Z"
-}
+{
+  "sha": "9d4e5974e5c0d9a09b9c6c1e1eb0975e80ec4461",
+  "branch": "main",
+  "repo": "Fission-AI/OpenSpec",
+  "updatedAt": "2026-09-12T00:00:00.000Z"
+}

package/openspec/commands/apply.md

@@ -1,9 +1,9 @@
----
-name: "OPSX: Apply"
-description: Implement tasks from an OpenSpec change (Experimental)
-category: Workflow
-tags: [workflow, artifacts, experimental]
----
+---
+name: "OPSX: Apply"
+description: Implement tasks from an OpenSpec change (Experimental)
+category: Workflow
+tags: [workflow, artifacts, experimental]
+---
 Implement tasks from an OpenSpec change.
 
 **Store selection:** If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run `openspec store list --json` to discover registered store ids, then pass `--store <id>` on the commands that read or write specs and changes (`new change`, `status`, `instructions`, `list`, `show`, `validate`, `archive`, `doctor`, `context`). Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local `openspec/` root.
@@ -179,4 +179,4 @@ What would you like to do?
 This skill supports the "actions on a change" model:
 
 - **Can be invoked anytime**: Before all artifacts are done (if tasks exist), after partial implementation, interleaved with other actions
-- **Allows artifact updates**: If implementation reveals design issues, suggest updating artifacts - not phase-locked, work fluidly
+- **Allows artifact updates**: If implementation reveals design issues, suggest updating artifacts - not phase-locked, work fluidly

package/openspec/commands/archive.md

@@ -1,9 +1,9 @@
----
-name: "OPSX: Archive"
-description: Archive a completed change in the experimental workflow
-category: Workflow
-tags: [workflow, archive, experimental]
----
+---
+name: "OPSX: Archive"
+description: Archive a completed change in the experimental workflow
+category: Workflow
+tags: [workflow, archive, experimental]
+---
 Archive a completed change in the experimental workflow.
 
 **Store selection:** If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run `openspec store list --json` to discover registered store ids, then pass `--store <id>` on the commands that read or write specs and changes (`new change`, `status`, `instructions`, `list`, `show`, `validate`, `archive`, `doctor`, `context`). Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local `openspec/` root.
@@ -220,4 +220,4 @@ Target archive directory already exists.
 - Consider every guidance entry and explain any inapplicable or conflicting advice
 - Existing CLI checks, resolved paths, prompts, and command contracts are unchanged
 - Artifact rules constrain only the specs being written and are never operation guidance
-- Never copy runtime context, operation guidance, or artifact-rule text verbatim into output files
+- Never copy runtime context, operation guidance, or artifact-rule text verbatim into output files

package/openspec/commands/bulk-archive.md

@@ -1,9 +1,9 @@
----
-name: "OPSX: Bulk Archive"
-description: Archive multiple completed changes at once
-category: Workflow
-tags: [workflow, archive, experimental, bulk]
----
+---
+name: "OPSX: Bulk Archive"
+description: Archive multiple completed changes at once
+category: Workflow
+tags: [workflow, archive, experimental, bulk]
+---
 Archive multiple completed changes in a single operation.
 
 This skill allows you to batch-archive changes, handling spec conflicts intelligently by checking the codebase to determine what's actually implemented.
@@ -331,4 +331,4 @@ No active changes found. Create a new change to get started.
 - Operation guidance remains advisory; consider every entry and explain rejected advice
 - Keep runtime inputs, conflict analysis, CLI-derived values, and artifact rules separate
 - Artifact rules constrain only written specs
-- Never copy runtime input or artifact-rule text verbatim into output files
+- Never copy runtime input or artifact-rule text verbatim into output files

package/openspec/commands/continue.md

@@ -1,9 +1,9 @@
----
-name: "OPSX: Continue"
-description: Continue working on a change - create the next artifact (Experimental)
-category: Workflow
-tags: [workflow, artifacts, experimental]
----
+---
+name: "OPSX: Continue"
+description: Continue working on a change - create the next artifact (Experimental)
+category: Workflow
+tags: [workflow, artifacts, experimental]
+---
 Continue working on a change by creating the next artifact.
 
 **Store selection:** If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run `openspec store list --json` to discover registered store ids, then pass `--store <id>` on the commands that read or write specs and changes (`new change`, `status`, `instructions`, `list`, `show`, `validate`, `archive`, `doctor`, `context`). Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local `openspec/` root.
@@ -109,4 +109,4 @@ If the `instruction` field directs you to use a specific skill or command to cre
 - Use the schema's artifact sequence, don't assume specific artifact names
 - **IMPORTANT**: `context` and `rules` are constraints for YOU, not content for the file
   - Do NOT copy `<context>`, `<rules>`, `<project_context>` blocks into the artifact
-  - These guide what you write, but should never appear in the output
+  - These guide what you write, but should never appear in the output

package/openspec/commands/explore.md

@@ -1,9 +1,9 @@
----
-name: "OPSX: Explore"
-description: Enter explore mode - think through ideas, investigate problems, clarify requirements
-category: Workflow
-tags: [workflow, explore, experimental, thinking]
----
+---
+name: "OPSX: Explore"
+description: Enter explore mode - think through ideas, investigate problems, clarify requirements
+category: Workflow
+tags: [workflow, explore, experimental, thinking]
+---
 Enter explore mode. Think deeply. Visualize freely. Follow the conversation wherever it goes.
 
 **IMPORTANT: Explore mode is for thinking, not implementing.** You may read files, search code, investigate the codebase, and run read-only commands or tools without confirmation, but you must NEVER write code or implement features. If the user asks you to implement something, remind them to exit explore mode first and create a change proposal. You MAY create or update OpenSpec change artifacts (proposals, designs, specs) within a confirmed scope—that's capturing thinking, not implementing. Answering design or clarifying questions is never consent to write. Before the first write-capable action, name the artifacts or files you would change and what you would do, ask a direct yes/no question, and wait for the user's confirmation in a separate message. Confirmation covers only the scope you described; ask again before expanding it. For a new change, scaffold it first as described below.
@@ -203,4 +203,4 @@ When things crystallize, you might offer a summary - but it's optional. Sometime
 - **Don't manually scaffold changes** - Never create a new change directory under `openspec/changes/` by hand. Always use `openspec new change "<name>"` (with `--store <id>` when applicable) so required metadata such as `.openspec.yaml` is created before writing artifacts.
 - **Do visualize** - A good diagram is worth many paragraphs
 - **Do explore the codebase** - Ground discussions in reality
-- **Do question assumptions** - Including the user's and your own
+- **Do question assumptions** - Including the user's and your own

package/openspec/commands/ff.md

@@ -1,9 +1,9 @@
----
-name: "OPSX: Fast Forward"
-description: Create a change and generate all artifacts needed for implementation in one go
-category: Workflow
-tags: [workflow, artifacts, experimental]
----
+---
+name: "OPSX: Fast Forward"
+description: Create a change and generate all artifacts needed for implementation in one go
+category: Workflow
+tags: [workflow, artifacts, experimental]
+---
 Fast-forward through artifact creation - generate everything needed to start implementation.
 
 **Store selection:** If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run `openspec store list --json` to discover registered store ids, then pass `--store <id>` on the commands that read or write specs and changes (`new change`, `status`, `instructions`, `list`, `show`, `validate`, `archive`, `doctor`, `context`). Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local `openspec/` root.
@@ -108,4 +108,4 @@ After completing all artifacts, summarize:
 - Always read dependency artifacts before creating a new one - re-read from disk, not from conversation memory (files may have changed since you last saw them)
 - If context is critically unclear, ask the user - but prefer making reasonable decisions to keep momentum
 - If a change with that name already exists, ask if user wants to continue it or create a new one
-- Verify each artifact file exists after writing before proceeding to next
+- Verify each artifact file exists after writing before proceeding to next

package/openspec/commands/new.md

@@ -1,9 +1,9 @@
----
-name: "OPSX: New"
-description: Start a new change using the experimental artifact workflow (OPSX)
-category: Workflow
-tags: [workflow, artifacts, experimental]
----
+---
+name: "OPSX: New"
+description: Start a new change using the experimental artifact workflow (OPSX)
+category: Workflow
+tags: [workflow, artifacts, experimental]
+---
 Start a new change using the experimental artifact-driven approach.
 
 **Store selection:** If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run `openspec store list --json` to discover registered store ids, then pass `--store <id>` on the commands that read or write specs and changes (`new change`, `status`, `instructions`, `list`, `show`, `validate`, `archive`, `doctor`, `context`). Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local `openspec/` root.
@@ -67,4 +67,4 @@ After completing the steps, summarize:
 - Do NOT advance beyond showing the first artifact template
 - If the name is invalid (not kebab-case), ask for a valid name
 - If a change with that name already exists, suggest using `/opsx:continue` instead
-- Pass --schema if using a non-default workflow
+- Pass --schema if using a non-default workflow

package/openspec/commands/onboard.md

@@ -1,9 +1,9 @@
----
-name: "OPSX: Onboard"
-description: Guided onboarding - walk through a complete OpenSpec workflow cycle with narration
-category: Workflow
-tags: [workflow, onboarding, tutorial, learning]
----
+---
+name: "OPSX: Onboard"
+description: Guided onboarding - walk through a complete OpenSpec workflow cycle with narration
+category: Workflow
+tags: [workflow, onboarding, tutorial, learning]
+---
 Guide the user through their first complete OpenSpec workflow cycle. This is a teaching experience—you'll do real work in their codebase while explaining each step.
 
 **Store selection:** If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run `openspec store list --json` to discover registered store ids, then pass `--store <id>` on the commands that read or write specs and changes (`new change`, `status`, `instructions`, `list`, `show`, `validate`, `archive`, `doctor`, `context`). Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local `openspec/` root.
@@ -552,4 +552,4 @@ Exit gracefully.
 - **Pause for acknowledgment** at marked points, but don't over-pause
 - **Handle exits gracefully**—never pressure the user to continue
 - **Use real codebase tasks**—don't simulate or use fake examples
-- **Adjust scope gently**—guide toward smaller tasks but respect user choice
+- **Adjust scope gently**—guide toward smaller tasks but respect user choice

package/openspec/commands/propose.md

@@ -1,9 +1,9 @@
----
-name: "OPSX: Propose"
-description: Propose a new change - create it and generate all artifacts in one step
-category: Workflow
-tags: [workflow, artifacts, experimental]
----
+---
+name: "OPSX: Propose"
+description: Propose a new change - create it and generate all artifacts in one step
+category: Workflow
+tags: [workflow, artifacts, experimental]
+---
 Propose a new change - create the change and generate all artifacts in one step.
 
 **Planning boundary**: This workflow creates planning artifacts only. The user request that selected or triggered this workflow authorizes planning only, even if it asks to build or fix something. Do not edit project code. After the planning artifacts are complete, stop. Do not start implementation in the same response, even if the initial request asks for it. Wait for a new user request after the artifacts are presented; then start the apply workflow.
@@ -154,4 +154,4 @@ After completing all artifacts, summarize:
 - Always read dependency artifacts before creating a new one - re-read from disk, not from conversation memory (files may have changed since you last saw them)
 - Ask about ambiguities that would materially change scope, externally observable behavior, compatibility, or acceptance criteria; for minor details, make reasonable assumptions and record them
 - If a change with that name already exists, ask if user wants to continue it or create a new one
-- Verify each artifact file exists after writing before proceeding to next
+- Verify each artifact file exists after writing before proceeding to next

package/openspec/commands/sync.md

@@ -1,9 +1,9 @@
----
-name: "OPSX: Sync"
-description: Sync delta specs from a change to main specs
-category: Workflow
-tags: [workflow, specs, experimental]
----
+---
+name: "OPSX: Sync"
+description: Sync delta specs from a change to main specs
+category: Workflow
+tags: [workflow, specs, experimental]
+---
 Sync delta specs from a change to main specs.
 
 This is an **agent-driven** operation - you will read delta specs and directly edit main specs to apply the changes. This allows intelligent merging (e.g., adding a scenario without copying the entire requirement).
@@ -253,4 +253,4 @@ Main specs are now updated. The change remains active - archive when implementat
 - Honor a caller-supplied subset of `existingOutputPaths`; never widen it back to the full list
 - Fetch specs instructions once for direct sync, or reuse the archive-supplied snapshot inline
 - Stop before every main-spec write on a non-zero or invalid JSON specs-instruction response
-- Artifact rules constrain only the specs being written and are never copied into output files
+- Artifact rules constrain only the specs being written and are never copied into output files

package/openspec/commands/update.md

@@ -1,9 +1,9 @@
----
-name: "OPSX: Update"
-description: 
-category: Workflow
-tags: [workflow, artifacts, experimental]
----
+---
+name: "OPSX: Update"
+description: 
+category: Workflow
+tags: [workflow, artifacts, experimental]
+---
 Revise a change's existing planning artifacts and keep them coherent. Never edit code.
 
 **Store selection:** If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run `openspec store list --json` to discover registered store ids, then pass `--store <id>` on the commands that read or write specs and changes (`new change`, `status`, `instructions`, `list`, `show`, `validate`, `archive`, `doctor`, `context`). Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local `openspec/` root.
@@ -82,4 +82,4 @@ After each invocation, show:
 - Edit only the concrete files in `existingOutputPaths`; never write to a glob `resolvedOutputPath`.
 - Do not advance the build frontier: no new artifacts, no new files under glob artifacts - that is `/opsx:continue`'s job.
 - Confirm every edit with the user before writing.
-- If the request changes the change's *intent* rather than refining it, first verify whether the optional `/opsx:new` workflow is available. If it is, recommend starting fresh with `/opsx:new` (the "Update vs. Start Fresh" heuristic). If it is unavailable, ask for a distinct unused change name and recommend `openspec new change "<new-change-name>"` instead.
+- If the request changes the change's *intent* rather than refining it, first verify whether the optional `/opsx:new` workflow is available. If it is, recommend starting fresh with `/opsx:new` (the "Update vs. Start Fresh" heuristic). If it is unavailable, ask for a distinct unused change name and recommend `openspec new change "<new-change-name>"` instead.

package/openspec/commands/verify.md

@@ -1,9 +1,9 @@
----
-name: "OPSX: Verify"
-description: Verify implementation matches change artifacts before archiving
-category: Workflow
-tags: [workflow, verify, experimental]
----
+---
+name: "OPSX: Verify"
+description: Verify implementation matches change artifacts before archiving
+category: Workflow
+tags: [workflow, verify, experimental]
+---
 Verify that an implementation matches the change artifacts (specs, tasks, design).
 
 **Store selection:** If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run `openspec store list --json` to discover registered store ids, then pass `--store <id>` on the commands that read or write specs and changes (`new change`, `status`, `instructions`, `list`, `show`, `validate`, `archive`, `doctor`, `context`). Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local `openspec/` root.
@@ -166,4 +166,4 @@ Use clear markdown with:
 - Grouped lists for issues (CRITICAL/WARNING/SUGGESTION)
 - Code references in format: `file.ts:123`
 - Specific, actionable recommendations
-- No vague suggestions like "consider reviewing"
+- No vague suggestions like "consider reviewing"