[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M757B0K71GC1934VY0MD13SC":3,"skill-same:01M757B0K71GC1934VY0MD13SC":62},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M757B0K71GC1934VY0MD13SC","su-archive",null,"在 review 通过后固化完成证据、风险和后续建议。","SeemSeam\u002Fagent-roles-spec","SeemSeam","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F29205273?v=4","01M7572MDYPSM30Y29C9HRMGK7","01M7572MEGCX02T16BHYV9PBVK",19,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FSeemSeam\u002Fagent-roles-spec\u002Fblob\u002Fmain\u002Froles\u002Fsu-ccb\u002Fskills\u002Fsu-archive\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: su-archive\ndescription: 在 review 通过后固化完成证据、风险和后续建议。\nmetadata:\n  short-description: CCB 归档入口\n---\n\n# \u002Fccb:su-archive\n\n## 1. 指令意图说明\n\n`\u002Fccb:su-archive` 用于把已通过 review 的任务沉淀成可追溯历史。归档不是“结束任务”四个字，而是写清完成内容、证据、未覆盖项、风险和后续建议。\n\n## 2. 节点集声明\n\n主要进入：\n\n| 节点 | Manifest |\n|---|---|\n| 归档 | `references\u002Fkernel\u002Fnodes\u002Farchive.node.md` |\n\n如果 review 未通过，必须回到 `references\u002Fkernel\u002Fnodes\u002Freview.node.md`，不得普通归档。\n\n## 3. 触发约定\n\n```text\n\u002Fccb:su-archive task_id=\u003CsubtaskId>\n\u002Fccb:su-archive requirement_id=\u003CrequirementId>\n\u002Fccb:su-archive --reopen requirement_id=\u003CrequirementId>\n\u002Fccb:su-archive 当前已通过 review 的任务\n```\n\n可带 `risk_accepted=true`，但只有用户明确授权带风险归档时才可使用。\n\n`task_id` 是子任务归档入口；`requirement_id` 是需求级手动归档入口，用于把已\n`merged` 的 per-需求 worktree 清理并把 requirement finalize 为 `delivered`。\n`--reopen` 是显式返工入口，用于把 `merged` worktree 解冻回 `ready`，复用同一实施分支继续改。\n\n## 4. Plugin 独立运行约定\n\n归档记录直接写入 plugin 域文件：\n\n1. `docs\u002F05_经验沉淀\u002F`（需要沉淀经验时）\n2. `docs\u002F03_开发计划\u002F*开发任务.md`\n3. `docs\u002F.ccb\u002Fevents\u002Fjournal.jsonl`\n\n子任务归档不得调用 worktree merge\u002Fcleanup。归档子任务时，只写该 dev_task 终态和归档记录：\n\n```js\nawait writeTaskState({\n  projectRoot,\n  taskId,\n  title,\n  patch: {\n    status: \"done\",\n    current_node: \"archive\",\n    node_substate: \"archived\",\n    review_status: \"passed\"\n  },\n  updatedBy: \"ai_session\"\n});\n```\n\n归档必须以 `docs\u002F03_开发计划\u002F` 的 dev_task 文档为任务真相；`status\u002Fcurrent_node\u002Fnode_substate\u002Freview_status` 只能通过受治理写入更新。\n\n归档子任务后，如果该子任务可能是 requirement 最后一个待归档项，只能做 requirement-wide\n终态判断并调用 `mergeRequirementWorktree()` 进入 `merged` 预览暂停；不得 cleanup 或声明\n`delivered`。需求交付状态必须等用户执行需求级手动归档。\n\n需求级手动归档入口（`\u002Fccb:su-archive requirement_id=\u003Cid>`）必须按顺序执行：\n\n1. 读取 requirement md 和 `docs\u002F.ccb\u002Fworktrees\u002F\u003Cid>.json`，确认 requirement 未\n   `cancelled\u002Fdeferred` 且 worktree runtime aggregate 为 `merged`；若 runtime aggregate 已是 `archived` 且\n   requirement 仍未 `delivered`，进入 finalize-only recovery。\n2. runtime aggregate 为 `merged` 时调用 `cleanupRequirementWorktree({ projectRoot, requirementId,\n   codeWorkspace })`。cleanup 按 implementation spaces 声明序逐空间执行；若返回\n   `status: \"escalated\"`，保留已成功 archived 的空间事实并停止，不得 finalize。仅\n   `aggregate=merged`、`aggregate=escalated && last_error.op==\"cleanup\"` 或已 `archived`\n   可进入 cleanup。\n3. cleanup 成功后重新读取 requirement md 当前 hash，再通过 `applyCapabilityOutcome()` 声明\n   delivered；必须使用 `dev_task_requirement_terminal` evidence 和\n   `requirement_finalize_expected_hash` guard。\n4. 若 cleanup 已成功但 finalize 因 CAS\u002Fhash 等失败，后续重入必须识别\n   `aggregate=archived + requirement 仍非 delivered`，跳过 cleanup，执行 finalize-only recovery。\n\n示例：\n\n```js\nimport { readFile } from \"node:fs\u002Fpromises\";\nimport { cleanupRequirementWorktree, reopenRequirementWorktree } from \"..\u002F..\u002Flib\u002Fworktree\u002Findex.mjs\";\nimport { applyCapabilityOutcome } from \"..\u002F..\u002Flib\u002Fcapability-outcome\u002Findex.mjs\";\nimport { hashContent } from \"..\u002F..\u002Flib\u002Fruntime\u002Findex.mjs\";\n\nconst cleanup = await cleanupRequirementWorktree({\n  projectRoot,\n  requirementId,\n  codeWorkspace\n});\nif (cleanup.status === \"escalated\") return cleanup;\n\nconst requirementContent = await readFile(requirementMarkdownPath, \"utf8\");\nconst requirementMarkdownHash = hashContent(requirementContent);\nawait applyCapabilityOutcome({\n  projectRoot,\n  capabilityId: \"requirement.finalize\",\n  outcomeType: \"delivered\",\n  subjectRef: {\n    subject_type: \"requirement\",\n    subject_id: requirementId,\n    canonical_path: requirementMarkdownPath,\n    base_hash: requirementMarkdownHash\n  },\n  expectedHash: requirementMarkdownHash,\n  evidence: [{\n    kind: \"C\",\n    ref: `dev-task-requirement:${requirementId}`,\n    check_id: \"dev_task_requirement_terminal\",\n    params: { requirement_id: requirementId }\n  }]\n});\n```\n\n如果全需求 dev_task 未终态、review 未通过、hash 已变、需求已 cancelled\u002Fdeferred 或 AI 判断仍有\n必须处理事项，不得声明 delivered；输出拒绝原因。\n\nreopen 入口（`\u002Fccb:su-archive --reopen requirement_id=\u003Cid>`）只处理 `merged→ready`：\n\n```js\nawait reopenRequirementWorktree({\n  projectRoot,\n  requirementId,\n  codeWorkspace\n});\n```\n\n`reopenRequirementWorktree` 不改 git 内容；它仅允许 `aggregate=merged`，并校验全部\nimplementation spaces 的 worktree+分支仍存在且 clean（单空间即 worktree+分支仍存在且 worktree clean）。任一空间失败时 all-or-nothing\n返回 `status: \"escalated\"`、保留 runtime 不写并报告原因；成功后全部空间回到 `ready`，\nassociations 重置为 pending，requirement 保持非 delivered，后续返工继续复用实施分支。\n\n不得调用 Console 业务写入接口改业务状态。Console 只负责展示归档投影。\n\n归档 \u002F merge \u002F finalize \u002F reopen 写完 canonical 后，**best-effort 主动触发一次 Console 投影刷新**（本地 Console 在跑时 `POST \u002Fapi\u002Fprojects\u002F\u003CprojectId>\u002Fscan`），并校验投影（子任务 `current_node\u002Fstatus`、需求 `status`、worktree runtime status）与 canonical 一致，不要只依赖 watcher 异步跟上（WSL2 会漏文件事件）；Console 不可达或投影不一致时，告知用户需手动 scan。Console UI 当前不是手动归档能力的唯一真相源。\n\n## 5. 强协商与 sc 要求\n\n归档前必须：\n\n1. 确认 review pass 或用户授权带风险归档。\n2. 使用 archive 节点推荐 sc 指令，或说明替代方式。\n3. 找 Codex 检查归档完整性。\n4. 写 4 锚点反思。\n5. 明确是否有敏感信息、后续任务或公开风险。\n\n## 6. 用户可见输出\n\n输出归档路径、完成摘要、验证证据、未覆盖风险、后续建议和是否继续下一个 DeliveryUnit。\n","# \u002Fccb:su-archive\n\n## 1. 指令意图说明\n\n`\u002Fccb:su-archive` 用于把已通过 review 的任务沉淀成可追溯历史。归档不是“结束任务”四个字，而是写清完成内容、证据、未覆盖项、风险和后续建议。\n\n## 2. 节点集声明\n\n主要进入：\n\n| 节点 | Manifest |\n|---|---|\n| 归档 | `references\u002Fkernel\u002Fnodes\u002Farchive.node.md` |\n\n如果 review 未通过，必须回到 `references\u002Fkernel\u002Fnodes\u002Freview.node.md`，不得普通归档。\n\n## 3. 触发约定\n\n```text\n\u002Fccb:su-archive task_id=\u003CsubtaskId>\n\u002Fccb:su-archive requirement_id=\u003CrequirementId>\n\u002Fccb:su-archive --reopen requirement_id=\u003CrequirementId>\n\u002Fccb:su-archive 当前已通过 review 的任务\n```\n\n可带 `risk_accepted=true`，但只有用户明确授权带风险归档时才可使用。\n\n`task_id` 是子任务归档入口；`requirement_id` 是需求级手动归档入口，用于把已\n`merged` 的 per-需求 worktree 清理并把 requirement finalize 为 `delivered`。\n`--reopen` 是显式返工入口，用于把 `merged` worktree 解冻回 `ready`，复用同一实施分支继续改。\n\n## 4. Plugin 独立运行约定\n\n归档记录直接写入 plugin 域文件：\n\n1. `docs\u002F05_经验沉淀\u002F`（需要沉淀经验时）\n2. `docs\u002F03_开发计划\u002F*开发任务.md`\n3. `docs\u002F.ccb\u002Fevents\u002Fjournal.jsonl`\n\n子任务归档不得调用 worktree merge\u002Fcleanup。归档子任务时，只写该 dev_task 终态和归档记录：\n\n```js\nawait writeTaskState({\n  projectRoot,\n  taskId,\n  title,\n  patch: {\n    status: \"done\",\n    current_node: \"archive\",\n    node_substate: \"archived\",\n    review_status: \"passed\"\n  },\n  updatedBy: \"ai_session\"\n});\n```\n\n归档必须以 `docs\u002F03_开发计划\u002F` 的 dev_task 文档为任务真相；`status\u002Fcurrent_node\u002Fnode_substate\u002Freview_status` 只能通过受治理写入更新。\n\n归档子任务后，如果该子任务可能是 requirement 最后一个待归档项，只能做 requirement-wide\n终态判断并调用 `mergeRequirementWorktree()` 进入 `merged` 预览暂停；不得 cleanup 或声明\n`delivered`。需求交付状态必须等用户执行需求级手动归档。\n\n需求级手动归档入口（`\u002Fccb:su-archive requirement_id=\u003Cid>`）必须按顺序执行：\n\n1. 读取 requirement md 和 `docs\u002F.ccb\u002Fworktrees\u002F\u003Cid>.json`，确认 requirement 未\n   `cancelled\u002Fdeferred` 且 worktree runtime aggregate 为 `merged`；若 runtime aggregate 已是 `archived` 且\n   requirement 仍未 `delivered`，进入 finalize-only recovery。\n2. runtime aggregate 为 `merged` 时调用 `cleanupRequirementWorktree({ projectRoot, requirementId,\n   codeWorkspace })`。cleanup 按 implementation spaces 声明序逐空间执行；若返回\n   `status: \"escalated\"`，保留已成功 archived 的空间事实并停止，不得 finalize。仅\n   `aggregate=merged`、`aggregate=escalated && last_error.op==\"cleanup\"` 或已 `archived`\n   可进入 cleanup。\n3. cleanup 成功后重新读取 requirement md 当前 hash，再通过 `applyCapabilityOutcome()` 声明\n   delivered；必须使用 `dev_task_requirement_terminal` evidence 和\n   `requirement_finalize_expected_hash` guard。\n4. 若 cleanup 已成功但 finalize 因 CAS\u002Fhash 等失败，后续重入必须识别\n   `aggregate=archived + requirement 仍非 delivered`，跳过 cleanup，执行 finalize-only recovery。\n\n示例：\n\n```js\nimport { readFile } from \"node:fs\u002Fpromises\";\nimport { cleanupRequirementWorktree, reopenRequirementWorktree } from \"..\u002F..\u002Flib\u002Fworktree\u002Findex.mjs\";\nimport { applyCapabilityOutcome } from \"..\u002F..\u002Flib\u002Fcapability-outcome\u002Findex.mjs\";\nimport { hashContent } from \"..\u002F..\u002Flib\u002Fruntime\u002Findex.mjs\";\n\nconst cleanup = await cleanupRequirementWorktree({\n  projectRoot,\n  requirementId,\n  codeWorkspace\n});\nif (cleanup.status === \"escalated\") return cleanup;\n\nconst requirementContent = await readFile(requirementMarkdownPath, \"utf8\");\nconst requirementMarkdownHash = hashContent(requirementContent);\nawait applyCapabilityOutcome({\n  projectRoot,\n  capabilityId: \"requirement.finalize\",\n  outcomeType: \"delivered\",\n  subjectRef: {\n    subject_type: \"requirement\",\n    subject_id: requirementId,\n    canonical_path: requirementMarkdownPath,\n    base_hash: requirementMarkdownHash\n  },\n  expectedHash: requirementMarkdownHash,\n  evidence: [{\n    kind: \"C\",\n    ref: `dev-task-requirement:${requirementId}`,\n    check_id: \"dev_task_requirement_terminal\",\n    params: { requirement_id: requirementId }\n  }]\n});\n```\n\n如果全需求 dev_task 未终态、review 未通过、hash 已变、需求已 cancelled\u002Fdeferred 或 AI 判断仍有\n必须处理事项，不得声明 delivered；输出拒绝原因。\n\nreopen 入口（`\u002Fccb:su-archive --reopen requirement_id=\u003Cid>`）只处理 `merged→ready`：\n\n```js\nawait reopenRequirementWorktree({\n  projectRoot,\n  requirementId,\n  codeWorkspace\n});\n```\n\n`reopenRequirementWorktree` 不改 git 内容；它仅允许 `aggregate=merged`，并校验全部\nimplementation spaces 的 worktree+分支仍存在且 clean（单空间即 worktree+分支仍存在且 worktree clean）。任一空间失败时 all-or-nothing\n返回 `status: \"escalated\"`、保留 runtime 不写并报告原因；成功后全部空间回到 `ready`，\nassociations 重置为 pending，requirement 保持非 delivered，后续返工继续复用实施分支。\n\n不得调用 Console 业务写入接口改业务状态。Console 只负责展示归档投影。\n\n归档 \u002F merge \u002F finalize \u002F reopen 写完 canonical 后，**best-effort 主动触发一次 Console 投影刷新**（本地 Console 在跑时 `POST \u002Fapi\u002Fprojects\u002F\u003CprojectId>\u002Fscan`），并校验投影（子任务 `current_node\u002Fstatus`、需求 `status`、worktree runtime status）与 canonical 一致，不要只依赖 watcher 异步跟上（WSL2 会漏文件事件）；Console 不可达或投影不一致时，告知用户需手动 scan。Console UI 当前不是手动归档能力的唯一真相源。\n\n## 5. 强协商与 sc 要求\n\n归档前必须：\n\n1. 确认 review pass 或用户授权带风险归档。\n2. 使用 archive 节点推荐 sc 指令，或说明替代方式。\n3. 找 Codex 检查归档完整性。\n4. 写 4 锚点反思。\n5. 明确是否有敏感信息、后续任务或公开风险。\n\n## 6. 用户可见输出\n\n输出归档路径、完成摘要、验证证据、未覆盖风险、后续建议和是否继续下一个 DeliveryUnit。\n",{"name":5,"metadata":23,"description":7},{"short-description":24},"CCB 归档入口","main","d07398b0a36ffa994efd970a554dd9596932ed5c","roles\u002Fsu-ccb\u002Fskills\u002Fsu-archive",2,"https:\u002F\u002Fgithub.com\u002FSeemSeam\u002Fagent-roles-spec","https:\u002F\u002Fgithub.com\u002FSeemSeam","2026-08-14 10:00:06",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add SeemSeam\u002Fagent-roles-spec --skill su-archive",{"tool":38,"command":39},"bunx","bunx skills add SeemSeam\u002Fagent-roles-spec --skill su-archive",{"tool":41,"command":42},"pnpm","pnpm dlx skills add SeemSeam\u002Fagent-roles-spec --skill su-archive","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSeemSeam\u002Fagent-roles-spec\u002Fblob\u002Fmain\u002Froles\u002Fsu-ccb\u002Fskills\u002Fsu-archive\u002FSKILL.md",true,[46,52,58],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"__tests__\u002Fsu-archive-skill.test.mjs","SCRIPT","脚本",1274,"https:\u002F\u002Fgithub.com\u002FSeemSeam\u002Fagent-roles-spec\u002Fblob\u002Fmain\u002Froles\u002Fsu-ccb\u002Fskills\u002Fsu-archive\u002F__tests__\u002Fsu-archive-skill.test.mjs",{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Farchive-flow.md","REFERENCE","参考文档",1377,"https:\u002F\u002Fgithub.com\u002FSeemSeam\u002Fagent-roles-spec\u002Fblob\u002Fmain\u002Froles\u002Fsu-ccb\u002Fskills\u002Fsu-archive\u002Freferences\u002Farchive-flow.md",{"path":59,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Fsc-integration.md",503,"https:\u002F\u002Fgithub.com\u002FSeemSeam\u002Fagent-roles-spec\u002Fblob\u002Fmain\u002Froles\u002Fsu-ccb\u002Fskills\u002Fsu-archive\u002Freferences\u002Fsc-integration.md",[63,69,76,83,90,97],{"skillNo":64,"name":65,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":18},"01M757C4HNYHR92Z3MDGPW9JSA","example-skill","https:\u002F\u002Fgithub.com\u002FSeemSeam\u002Fagent-roles-spec\u002Fblob\u002Fmain\u002Ftemplates\u002Frole-with-skills\u002Fskills\u002Fexample-skill\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":18},"01M757C2B2YT62JBH98CG1BKWG","su-status","从 docs 人读真相源与 .ccb 协调件读取当前项目、Requirement 或子任务状态。","https:\u002F\u002Fgithub.com\u002FSeemSeam\u002Fagent-roles-spec\u002Fblob\u002Fmain\u002Froles\u002Fsu-ccb\u002Fskills\u002Fsu-status\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":18},"01M757C0DVFT88AFBXN1PFXH9D","su-revise-breakdown","根据用户反馈重写 Requirement breakdown draft。","https:\u002F\u002Fgithub.com\u002FSeemSeam\u002Fagent-roles-spec\u002Fblob\u002Fmain\u002Froles\u002Fsu-ccb\u002Fskills\u002Fsu-revise-breakdown\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":18},"01M757BY5XVMPKEK118D782PRM","su-review","审查执行回执、diff 和验证证据，决定通过、返工、replan 或升级用户。","https:\u002F\u002Fgithub.com\u002FSeemSeam\u002Fagent-roles-spec\u002Fblob\u002Fmain\u002Froles\u002Fsu-ccb\u002Fskills\u002Fsu-review\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":18},"01M757BW1R61F61X7JJF2SSJET","su-resume","从 docs 人读真相源与 .ccb 协调件恢复 paused\u002Fdeferred\u002Fin-progress 主体的上下文。","https:\u002F\u002Fgithub.com\u002FSeemSeam\u002Fagent-roles-spec\u002Fblob\u002Fmain\u002Froles\u002Fsu-ccb\u002Fskills\u002Fsu-resume\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":18},"01M757BTEAFRRXA9DY3KBRTRNY","su-reconcile","AI-native 自检 docs 人读真相源、.ccb 协调件与 Console 投影漂移，并按审批结果执行修复。","https:\u002F\u002Fgithub.com\u002FSeemSeam\u002Fagent-roles-spec\u002Fblob\u002Fmain\u002Froles\u002Fsu-ccb\u002Fskills\u002Fsu-reconcile\u002FSKILL.md",[],[]]