flow-comet 1.7.0 → 1.8.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (78) hide show
  1. package/.flow-comet/skills/flow-comet/INSTALLED_VERSION +1 -1
  2. package/.flow-comet/skills/flow-comet/SKILL.md +16 -14
  3. package/.flow-comet/skills/flow-comet/reference/commit-discipline.md +1 -1
  4. package/.flow-comet/skills/flow-comet/reference/decision-points.md +5 -5
  5. package/.flow-comet/skills/flow-comet/reference/dirty-worktree.md +1 -1
  6. package/.flow-comet/skills/flow-comet/reference/entry-detail.md +9 -9
  7. package/.flow-comet/skills/flow-comet/reference/fix-loop.md +4 -4
  8. package/.flow-comet/skills/flow-comet/reference/init-detection.md +1 -1
  9. package/.flow-comet/skills/flow-comet/reference/platform-facts.md +2 -2
  10. package/.flow-comet/skills/flow-comet/reference/post-archive-handoff.md +264 -0
  11. package/.flow-comet/skills/flow-comet/reference/recovery.md +1 -1
  12. package/.flow-comet/skills/flow-comet/reference/replan.md +1 -1
  13. package/.flow-comet/skills/flow-comet/scripts/comet-check.mjs +1 -0
  14. package/.flow-comet/skills/flow-comet/scripts/comet-hook-guard.mjs +270 -30
  15. package/.flow-comet/skills/flow-comet/scripts/items/a.mjs +25 -8
  16. package/.flow-comet/skills/flow-comet/scripts/items/b.mjs +41 -38
  17. package/.flow-comet/skills/flow-comet/scripts/items/c.mjs +11 -9
  18. package/.flow-comet/skills/flow-comet/scripts/items/e.mjs +2 -2
  19. package/.flow-comet/skills/flow-comet/scripts/items/f.mjs +1 -1
  20. package/.flow-comet/skills/flow-comet/scripts/items/h.mjs +112 -53
  21. package/.flow-comet/skills/flow-comet/scripts/items/k.mjs +357 -3
  22. package/.flow-comet/skills/flow-comet/scripts/items/l.mjs +24 -1
  23. package/.flow-comet/skills/flow-comet/scripts/items/m.mjs +2 -2
  24. package/.flow-comet/skills/flow-comet/scripts/items/n.mjs +9 -10
  25. package/.flow-comet/skills/flow-comet/scripts/lib/ac-coverage.mjs +8 -8
  26. package/.flow-comet/skills/flow-comet/scripts/lib/fix-loop-node.mjs +4 -15
  27. package/.flow-comet/skills/flow-comet/scripts/lib/guard-evidence-gates.mjs +79 -107
  28. package/.flow-comet/skills/flow-comet/scripts/lib/guard-gates.mjs +183 -232
  29. package/.flow-comet/skills/flow-comet/scripts/lib/guard-routing.mjs +91 -14
  30. package/.flow-comet/skills/flow-comet/scripts/lib/guard-template-fidelity.mjs +20 -32
  31. package/.flow-comet/skills/flow-comet/scripts/lib/guard-uidesign.mjs +10 -19
  32. package/.flow-comet/skills/flow-comet/scripts/lib/state-commands-admin.mjs +27 -17
  33. package/.flow-comet/skills/flow-comet/scripts/lib/state-commands-flow.mjs +240 -87
  34. package/.flow-comet/skills/flow-comet/scripts/lib/state-commands-recovery.mjs +15 -22
  35. package/.flow-comet/skills/flow-comet/scripts/lib/state-determine.mjs +11 -4
  36. package/.flow-comet/skills/flow-comet/scripts/lib/state-io.mjs +192 -24
  37. package/.flow-comet/skills/flow-comet/scripts/lib/state-skillmarkers.mjs +55 -44
  38. package/.flow-comet/skills/flow-comet/scripts/lib/system-fixtures.mjs +2 -4
  39. package/.flow-comet/skills/flow-comet/scripts/lib/test-assertions.mjs +0 -3
  40. package/.flow-comet/skills/flow-comet/scripts/lib/test-fixtures.mjs +191 -17
  41. package/.flow-comet/skills/flow-comet/scripts/lib/test-helpers.mjs +3 -0
  42. package/.flow-comet/skills/flow-comet/scripts/lib/text-anchor-checks.mjs +23 -5
  43. package/.flow-comet/skills/flow-comet/scripts/lib/wave-projection.mjs +10 -11
  44. package/.flow-comet/skills/flow-comet/scripts/protocol-utils.mjs +40 -3
  45. package/.flow-comet/skills/flow-comet/scripts/route-node.mjs +12 -5
  46. package/.flow-comet/skills/flow-comet/scripts/scenarios/a.mjs +193 -111
  47. package/.flow-comet/skills/flow-comet/scripts/scenarios/b.mjs +314 -57
  48. package/.flow-comet/skills/flow-comet/scripts/scenarios/c.mjs +311 -216
  49. package/.flow-comet/skills/flow-comet/scripts/scenarios/d.mjs +33 -62
  50. package/.flow-comet/skills/flow-comet/scripts/scenarios/e.mjs +188 -91
  51. package/.flow-comet/skills/flow-comet/scripts/scenarios/f.mjs +94 -37
  52. package/.flow-comet/skills/flow-comet/scripts/scenarios/g.mjs +36 -27
  53. package/.flow-comet/skills/flow-comet/scripts/scenarios/h.mjs +285 -9
  54. package/.flow-comet/skills/flow-comet/scripts/scenarios/i.mjs +2 -6
  55. package/.flow-comet/skills/flow-comet/scripts/scenarios/j.mjs +5 -15
  56. package/.flow-comet/skills/flow-comet/scripts/scenarios/k.mjs +6 -5
  57. package/.flow-comet/skills/flow-comet/scripts/scenarios/l.mjs +40 -36
  58. package/.flow-comet/skills/flow-comet/scripts/scenarios/m.mjs +2 -2
  59. package/.flow-comet/skills/flow-comet/scripts/scenarios/n.mjs +346 -25
  60. package/.flow-comet/skills/flow-comet/scripts/state-schema.mjs +0 -2
  61. package/.flow-comet/skills/flow-comet/scripts/workflow-handoff.mjs +41 -54
  62. package/.flow-comet/skills/flow-comet-archive/SKILL.md +33 -11
  63. package/.flow-comet/skills/flow-comet-change/SKILL.md +1 -1
  64. package/.flow-comet/skills/flow-comet-design/SKILL.md +5 -3
  65. package/.flow-comet/skills/flow-comet-dev/SKILL.md +2 -2
  66. package/.flow-comet/skills/flow-comet-execute/SKILL.md +11 -11
  67. package/.flow-comet/skills/flow-comet-integration/SKILL.md +10 -4
  68. package/.flow-comet/skills/flow-comet-plan/GUIDANCE.md +1 -1
  69. package/.flow-comet/skills/flow-comet-plan/SKILL.md +8 -8
  70. package/.flow-comet/skills/flow-comet-review/SKILL.md +8 -8
  71. package/.flow-comet/skills/flow-comet-subagent-execute/GUIDANCE.md +1 -1
  72. package/.flow-comet/skills/flow-comet-subagent-execute/SKILL.md +14 -14
  73. package/.flow-comet/skills/flow-comet-task/SKILL.md +3 -2
  74. package/.flow-comet/skills/flow-comet-ui-design/SKILL.md +2 -2
  75. package/.flow-comet/skills/flow-comet-verify/SKILL.md +1 -1
  76. package/README.md +2 -2
  77. package/package.json +1 -1
  78. package/scripts/dsh-bridge.mjs +238 -21
@@ -4,7 +4,7 @@
4
4
  // Return Contract、subagent-execute 摘要与多趟完成
5
5
  // 判定、required-skill / schema / 产物 存在性门禁——即「完成声明必须有证据与产物」这一族判据。
6
6
  //
7
- // 分级沿用既有语义:新 change(init 标记)强制 BLOCKED + 恢复指引,旧 change 渐进 WARN 不阻断。
7
+ // 判级:单一判级——违反即 BLOCKED + 恢复指引(新旧双轨已退役,同一形态不再有渐进 WARN 侧)。
8
8
 
9
9
  import { promises as fs } from 'fs';
10
10
  import path from 'path';
@@ -26,14 +26,15 @@ import {
26
26
  } from '../protocol-utils.mjs';
27
27
  import { runRoot, packageRoot, fileExists, statePath, writeJson, protocolPath } from './guard-state-io.mjs';
28
28
  import {
29
+ archiveDirNameNotice,
29
30
  eligibleParallelBlocks,
30
31
  inFlightHandoffRequests,
31
32
  isArchivedChange,
32
- isNewChange,
33
33
  missingAugmentationChecks,
34
34
  missingRequiredArtifacts,
35
35
  missingRequiredSchemaEvidence,
36
36
  missingRequiredSkillChecks,
37
+ recoveryActionText,
37
38
  taskDependsOn,
38
39
  verifySummaries,
39
40
  } from './guard-routing.mjs';
@@ -85,7 +86,7 @@ export function runDirectOverrideGate({ node, state }) {
85
86
 
86
87
  // 验证隔离「同一时刻只有一个写者」出口校验——读 state.evidence['subagent-execute'].handoffRequests:
87
88
  // 存在条目且**至少一个无对应 handoffResult** ⇒ 在飞委托(写者未收工,跑全量判据会被未提交中间态
88
- // 污染):新 change BLOCKED(含恢复指引「待写入者收工后重跑 / 已作废则撤回」)/ 旧 change WARN 渐进;
89
+ // 污染):一律 BLOCKED(含恢复指引「待写入者收工后重跑 / 已作废则撤回」);
89
90
  // 全部有对应 result ⇒ 放行;已撤回(withdrawnAt + withdrawnBy 齐备)的 request 不构成在飞委托 ⇒
90
91
  // 放行;无该证据对象 ⇒ 零输出。落点 = 出口校验流(与其余 violations / WARN 同风格,不新增独立命令
91
92
  // 面);判据经 inFlightHandoffRequests 单处求值(与 Return Contract 的 result 侧契约校验正交,不
@@ -96,12 +97,9 @@ export function runInFlightHandoffGate({ node, state }) {
96
97
  if (inFlight.length > 0) {
97
98
  const inFlightDetail = '存在在飞委托(handoffRequests 有 request 无对应 handoffResult): '
98
99
  + inFlight.join(', ') + '——验证隔离要求同一时刻只有一个写者(写者未收工)';
99
- if (isNewChange(state)) {
100
- console.error('BLOCKED: ' + inFlightDetail);
101
- console.error('恢复: 待写入者收工后重跑——子代理回传后用 workflow-handoff.mjs result <task-id> <Return Contract> 记录结果再重试 exit;若该委托已作废(零提交复验失败 / 写边界被拒后遗弃),用 workflow-handoff.mjs withdraw <task-id> --by <来源> [--reason <原因>] 撤回后再重试 exit(撤回留痕 withdrawnAt/withdrawnBy,已撤回 = 终态,历史不删)');
102
- process.exit(1);
103
- }
104
- console.error('WARN: ' + inFlightDetail + '(旧 change 渐进不阻断;待写入者收工后重跑全量判据;已作废的委托可用 workflow-handoff.mjs withdraw <task-id> --by <来源> 撤回)');
100
+ console.error('BLOCKED: ' + inFlightDetail);
101
+ console.error('恢复: 待写入者收工后重跑——子代理回传后用 workflow-handoff.mjs result <task-id> <Return Contract> 记录结果再重试 exit;若该委托已作废(零提交复验失败 / 写边界被拒后遗弃),用 workflow-handoff.mjs withdraw <task-id> --by <来源> [--reason <原因>] 撤回后再重试 exit(撤回留痕 withdrawnAt/withdrawnBy,已撤回 = 终态,历史不删)');
102
+ process.exit(1);
105
103
  }
106
104
  }
107
105
 
@@ -152,9 +150,8 @@ function mentionsLessonsId(body, id) {
152
150
  return new RegExp('(^|[^0-9])' + escaped + '(?![0-9])', 'iu').test(body);
153
151
  }
154
152
 
155
- // 每份 SUMMARY 的两条判据 → 问题描述数组(分级由调用方按 isNewChange 决定:新 change BLOCKED /
156
- // 旧 change WARN——C10 无例外)。TASK.md 或 .specs/LESSONS.md 缺席时对应输入为空:段在场判据照常,
157
- // 命中计算自然为空集(无条目可命中)。
153
+ // 每份 SUMMARY 的两条判据 → 问题描述数组(命中即由调用方计入 violations → BLOCKED)。
154
+ // TASK.md 或 .specs/LESSONS.md 缺席时对应输入为空:段在场判据照常,命中计算自然为空集(无条目可命中)。
158
155
  async function lessonsScanProblems(changeDir, summaryFiles) {
159
156
  if (summaryFiles.length === 0) return [];
160
157
  const rule = await lessonsScanRule();
@@ -240,59 +237,37 @@ export async function runSummarySectionsGate({ node, state }) {
240
237
  const method = methodSection === null ? null
241
238
  : /brooks.?review|cache.?brooks|builtin.?quickcheck/i.exec(methodSection);
242
239
  if (!method) {
243
- // 过渡规则:旧格式 SUMMARY 无 ## 自检方法 段——若全文已声明 brooks-review/cache-brooks/
244
- // builtin(旧模板行为),WARN 兼容不 BLOCKED;无任何自检声明才 BLOCKED
240
+ // 旧格式 SUMMARY 无 ## 自检方法 段——若全文已声明 brooks-review/cache-brooks/builtin
241
+ // (旧模板行为)按「段缺席」计入 violations(标题必须在场);无任何自检声明同样 BLOCKED。
245
242
  if (/brooks.?review|cache.?brooks|builtin.?quickcheck/i.test(content)) {
246
- if (isNewChange(state)) {
247
- violations.push(f + ' 缺 ## 自检方法 段(新 change 强制声明自检方法)');
248
- } else {
249
- console.error('BROOKS-LINT WARN: ' + f + ' 缺 ## 自检方法 段(旧格式),6 维自查已声明自检方法——兼容通过,建议补全');
250
- }
243
+ violations.push(f + ' 缺 ## 自检方法 段(须声明自检方法)');
251
244
  } else {
252
245
  violations.push(f + ' 缺 ## 自检方法 字段(必须声明 brooks-review 或 builtin-quickcheck)');
253
246
  }
254
247
  } else if (/builtin/i.test(method[0])) {
255
248
  // builtin 降级两级校验——① 必须声明不可用原因;② 必须含缓存尝试证据(已尝试 Read 插件缓存
256
249
  // 协议文件手动执行仍不可行——两级降级路径第 2 级;防「未尝试读缓存」的偷懒降级)。关键词
257
- // 声明级校验(设计边界:不做语义判断);缺失 → 新 change BLOCKED / 旧 SUMMARY WARN 渐进
250
+ // 声明级校验(设计边界:不做语义判断);缺失 → BLOCKED
258
251
  if (!/brooks-lint 不可用|插件不可用|unavailable|N\/A/i.test(content)) {
259
- if (isNewChange(state)) {
260
- console.error('BLOCKED: SUMMARY 使用 builtin-quickcheck 未声明 brooks-lint 不可用原因(新 change 强制);恢复: 在 ## 自检方法 段补原因(声明级校验——须含关键词: brooks-lint 不可用 / 插件不可用 / unavailable / N/A,如「brooks-lint 不可用(Skill 仅返回占位,插件执行体未加载)」)');
261
- process.exit(1);
262
- }
263
- console.error('BROOKS-LINT WARN: ' + f + ' 使用 builtin-quickcheck 但未声明 brooks-lint 不可用原因');
252
+ console.error('BLOCKED: SUMMARY 使用 builtin-quickcheck 未声明 brooks-lint 不可用原因;恢复: 在 ## 自检方法 段补原因(声明级校验——须含关键词: brooks-lint 不可用 / 插件不可用 / unavailable / N/A,如「brooks-lint 不可用(Skill 仅返回占位,插件执行体未加载)」)');
253
+ process.exit(1);
264
254
  } else if (!/插件缓存|缓存协议|协议文件|plugins\/cache/i.test(content)) {
265
- if (isNewChange(state)) {
266
- console.error('BLOCKED: SUMMARY 使用 builtin-quickcheck 未声明缓存尝试证据(新 change 强制先 Read 插件缓存协议文件);恢复: 在 ## 自检方法 段声明缓存尝试(须含关键词: 插件缓存 / 缓存协议 / 协议文件 / plugins/cache,如「已 Read 插件缓存协议文件(~/.claude/plugins/cache/...)手动执行仍不可行」)');
267
- process.exit(1);
268
- }
269
- console.error('BROOKS-LINT WARN: ' + f + ' 使用 builtin-quickcheck 但未声明缓存尝试证据(应先 Read 插件缓存协议文件手动执行完整 brooks 流程)');
255
+ console.error('BLOCKED: SUMMARY 使用 builtin-quickcheck 未声明缓存尝试证据(须先 Read 插件缓存协议文件);恢复: 在 ## 自检方法 段声明缓存尝试(须含关键词: 插件缓存 / 缓存协议 / 协议文件 / plugins/cache,如「已 Read 插件缓存协议文件(~/.claude/plugins/cache/...)手动执行仍不可行」)');
256
+ process.exit(1);
270
257
  }
271
258
  }
272
259
  if (sixDimBody !== null && !/brooks.?review|cache.?brooks/i.test(sixDimBody)) {
273
- if (isNewChange(state)) {
274
- console.error('BLOCKED: SUMMARY 的 6 维自查未声明使用 /brooks-review(新 change 强制声明自检方法);恢复: 在 6 维自查段声明 /brooks-review 或理由');
275
- process.exit(1);
276
- }
277
- console.error('BROOKS-LINT WARN: ' + f + ' 的 6 维自查未声明使用 /brooks-review(可能使用了内置快查)');
260
+ console.error('BLOCKED: SUMMARY 的 6 维自查未声明使用 /brooks-review;恢复: 在 6 维自查段声明 /brooks-review 或理由');
261
+ process.exit(1);
278
262
  }
279
263
  } catch {}
280
264
  }
281
- // LESSONS 扫描(AC-18):每份 SUMMARY 的扫描段在场 + 命中条目逐条回应。分级沿用既有语义——
282
- // 新 change BLOCKED / 旧 change WARN(C10 无例外)。
265
+ // LESSONS 扫描(AC-18):每份 SUMMARY 的扫描段在场 + 命中条目逐条回应;缺失即计入 violations。
283
266
  const lessonsProblems = await lessonsScanProblems(changeDir, summaryFiles);
284
- if (lessonsProblems.length > 0) {
285
- if (isNewChange(state)) {
286
- violations.push(...lessonsProblems);
287
- } else {
288
- for (const problem of lessonsProblems) {
289
- console.error('LESSONS SCAN WARN: ' + problem + '(旧 change 渐进,不阻断;新 change 将强制)');
290
- }
291
- }
292
- }
267
+ if (lessonsProblems.length > 0) violations.push(...lessonsProblems);
293
268
  if (violations.length > 0) {
294
269
  console.error('BLOCKED: SUMMARY 关键段校验失败: ' + violations.join('; '));
295
- if (lessonsProblems.length > 0 && isNewChange(state)) {
270
+ if (lessonsProblems.length > 0) {
296
271
  console.error('恢复: 按 flow-kit/templates/SUMMARY.md 在 ## 自检方法 之后补 ## LESSONS 扫描 段,并逐条写出命中条目编号与差异声明(无命中写「无 active 条目命中」);命中来源 = TASK.md 该任务 write_files 的路径段 × .specs/LESSONS.md 条目的关键词行');
297
272
  }
298
273
  process.exit(1);
@@ -344,23 +319,23 @@ export async function runExecuteExitGate({ protocol, node, state, emptyExitAppro
344
319
  && taskDependsOn(blockById.get(t.id) || '').every(d => doneIds.has(d)));
345
320
  if (serialRunnable.length > 0) {
346
321
  console.error('BLOCKED: execute 出口仍有串行 pending 任务: ' + serialRunnable.map(t => t.id).join(', ')
347
- + '——空退出豁免不适用于存在未完成可运行串行任务的情况(先完成该串行任务,或修正任务标记)'
348
- + ';无可执行的常规恢复动作时,可用 workflow-state.mjs advance 渡过结构性死结(逃生口:使用后本节点须重新 entry 并重做交付记录);常规缺产物/缺证据情形不适用');
322
+ + '——空退出豁免不适用于存在未完成可运行串行任务的情况(先完成该串行任务,或修正任务标记)');
323
+ // 恢复动作按目录在哪分两种说法(唯一分叉在 guard-routing 的 recoveryActionText):活动态给
324
+ // advance 逃生口;目录已搬进归档时那一步走不通(advance 的产物推导读活动路径),只给可执行的
325
+ // 那一步——把目录移回活动位置。
326
+ console.error('恢复: ' + recoveryActionText(state.activeChange,
327
+ '无可执行的常规恢复动作时,可用 workflow-state.mjs advance 渡过结构性死结(逃生口:使用后本节点须重新 entry 并重做交付记录);常规缺产物/缺证据情形不适用'));
349
328
  process.exit(1);
350
329
  }
351
330
 
352
- // done 任务 ↔ SUMMARY 完整性:done 任务 ↔ <id>-SUMMARY.md 存在(WARN 渐进不 BLOCK——防旧
353
- // change 卡死;结构级校验与 TASK 签名同源:任务完成声明须有对应产物)。新 change(enter 机制
354
- // 激活)升级为 BLOCKED——执行遗漏(声称完成但无产物)不静默进归档;旧 change 保持渐进。
331
+ // done 任务 ↔ SUMMARY 完整性:done 任务 ↔ <id>-SUMMARY.md 存在(结构级校验与 TASK 签名同源:
332
+ // 任务完成声明须有对应产物)。缺失即 BLOCKED——执行遗漏(声称完成但无产物)不静默进归档。
355
333
  const ki8ChangeDir = path.join(runRoot, '.specs', state.activeChange ?? '');
356
334
  for (const tid of tasks.filter(t => t.status === 'done').map(t => t.id)) {
357
335
  if (!(await fileExists(path.join(ki8ChangeDir, tid + '-SUMMARY.md')))) {
358
- if (isNewChange(state)) {
359
- console.error('BLOCKED: done 任务 ' + tid + ' 缺少 ' + tid + '-SUMMARY.md——execute 产物不完整(新 change 强制任务完成须有对应 SUMMARY;旧 change 渐进 WARN)');
360
- console.error('恢复: 补写 ' + tid + '-SUMMARY.md 后重试 exit;任务完成后补产物即可');
361
- process.exit(1);
362
- }
363
- console.error('WARN: done 任务 ' + tid + ' 缺少 ' + tid + '-SUMMARY.md——execute 产物不完整(任务完成须有对应 SUMMARY)');
336
+ console.error('BLOCKED: done 任务 ' + tid + ' 缺少 ' + tid + '-SUMMARY.md——execute 产物不完整(任务完成须有对应 SUMMARY)');
337
+ console.error('恢复: 补写 ' + tid + '-SUMMARY.md 后重试 exit;任务完成后补产物即可');
338
+ process.exit(1);
364
339
  }
365
340
  }
366
341
 
@@ -401,14 +376,10 @@ export async function runExecuteExitGate({ protocol, node, state, emptyExitAppro
401
376
  && (state.executionMode ?? 'subagent') !== 'direct'
402
377
  && !takeoverApproved
403
378
  && ki10ProtocolHasSubagent) {
404
- if (isNewChange(state)) {
405
- console.error('BLOCKED: TASK 有 parallel done 任务(' + ki10ParallelDone.join(', ')
406
- + ')但 subagent-execute 节点未 exit——新 change 强制 [P] 任务由 subagent-execute 节点委托');
407
- console.error('恢复: 经 subagent-execute 节点完成委托后再 exit;或说明越权委托原因');
408
- process.exit(1);
409
- }
410
- console.error('WARN: TASK 有 parallel done 任务(' + ki10ParallelDone.join(', ')
411
- + ')但 subagent-execute 节点未 exit——疑似 execute 阶段越权委托,[P] 任务应由 subagent-execute 节点委托');
379
+ console.error('BLOCKED: TASK 有 parallel done 任务(' + ki10ParallelDone.join(', ')
380
+ + ')但 subagent-execute 节点未 exit——[P] 任务须由 subagent-execute 节点委托(execute 阶段越权委托)');
381
+ console.error('恢复: 经 subagent-execute 节点完成委托后再 exit;或说明越权委托原因');
382
+ process.exit(1);
412
383
  }
413
384
  } catch {}
414
385
  return { exempt };
@@ -421,10 +392,9 @@ export async function runExecuteExitGate({ protocol, node, state, emptyExitAppro
421
392
  // 可判对象;未验证既不冒充通过也不冒充失败)。这是本出口唯一还会放行的「判不了」;
422
393
  // ② **工件内容不可判**——**change 自己的载体文件被删**(REQUIREMENT.md / TEST.md 不在)与承载段 /
423
394
  // 清单读不出(REQUIREMENT 定位不到验收准则段 / TEST.md 定位不到第 1 轮段 / 没有 AC 编号 /
424
- // 第 1 轮整段 N/A 而没有 1.1 矩阵)同属这一支 → 不是「判过且通过」:新 change BLOCKED / 旧
425
- // change WARN(WARN 行因此进入既有 WARN COUNT)——删文件、删段都不能换到放行。
426
- // · 真判过且缺覆盖:verify 出口新 change BLOCKED(点名缺失编号 + 「在 1.1 矩阵补行」的恢复指引)/
427
- // 旧 change WARN 渐进。
395
+ // 第 1 轮整段 N/A 而没有 1.1 矩阵)同属这一支 → 不是「判过且通过」:BLOCKED——删文件、
396
+ // 删段都不能换到放行。
397
+ // · 真判过且缺覆盖:verify 出口 BLOCKED(点名缺失编号 + 「在 1.1 矩阵补行」的恢复指引)。
428
398
  // · review 出口:一条汇总 WARN(列缺失编号),不阻断、不影响退出码——review 出口今天不要求
429
399
  // TEST.md,权威判定在 verify 出口;两支「判不了」都不打印(不制造噪音)。
430
400
  // 归档 change 与 verify 出口的既有豁免同源(历史归档不重判)。
@@ -439,23 +409,20 @@ export async function runAcCoverageGate({ node, state }) {
439
409
  }
440
410
  if (coverage.unjudgeable !== null) {
441
411
  if (node.id === 'review') return;
442
- const blocking = isNewChange(state);
443
- for (const line of acCoverageUnjudgeableLines({ coverage, level: blocking ? 'BLOCKED' : 'WARN' })) {
412
+ for (const line of acCoverageUnjudgeableLines({ coverage, level: 'BLOCKED' })) {
444
413
  console.error(line);
445
414
  }
446
- if (blocking) process.exit(1);
447
- return;
415
+ process.exit(1);
448
416
  }
449
417
  if (coverage.missing.length === 0) return;
450
418
  if (node.id === 'review') {
451
419
  console.error(acCoverageSummaryLine({ coverage }));
452
420
  return;
453
421
  }
454
- const blocking = isNewChange(state);
455
- for (const line of acCoverageReportLines({ coverage, level: blocking ? 'BLOCKED' : 'WARN' })) {
422
+ for (const line of acCoverageReportLines({ coverage, level: 'BLOCKED' })) {
456
423
  console.error(line);
457
424
  }
458
- if (blocking) process.exit(1);
425
+ process.exit(1);
459
426
  }
460
427
 
461
428
  // verify 出口必须真实跑命令(严格版)——历史归档 change 豁免(过渡规则)。命令来源三级:TEST.md 的
@@ -487,14 +454,10 @@ export async function runVerifyExitGate({ protocol, node, state }) {
487
454
  && (state.executionMode ?? 'subagent') !== 'direct'
488
455
  && !ki9TakeoverApproved
489
456
  && ki9ProtocolHasSubagent) {
490
- if (isNewChange(state)) {
491
- console.error('BLOCKED: TASK 有 parallel done 任务(' + ki9ParallelDone.join(', ')
492
- + ')但 subagent-execute 节点未 exit——新 change 强制(verify 兜底拦截)');
493
- console.error('恢复: 经 subagent-execute 节点完成委托后再 exit;或说明越权委托原因');
494
- process.exit(1);
495
- }
496
- console.error('WARN: TASK 有 parallel done 任务(' + ki9ParallelDone.join(', ')
497
- + ')但 subagent-execute 节点未 exit——疑似越权委托(execute 出口未拦截,verify 兜底提示)');
457
+ console.error('BLOCKED: TASK 有 parallel done 任务(' + ki9ParallelDone.join(', ')
458
+ + ')但 subagent-execute 节点未 exit——[P] 任务须由 subagent-execute 节点委托(verify 兜底拦截)');
459
+ console.error('恢复: 经 subagent-execute 节点完成委托后再 exit;或说明越权委托原因');
460
+ process.exit(1);
498
461
  }
499
462
  } catch {}
500
463
  const { spawnSync } = await import('child_process');
@@ -588,13 +551,9 @@ export function runReturnContractGate({ node, state }) {
588
551
  const noCommitTask = !!(taskReq && taskReq.noCommit === true);
589
552
  if (!r.commitHash && !noCommitTask) violations.push(taskId + ' 缺 commitHash');
590
553
  if (!r.greenEvidence || !r.greenEvidence.command) violations.push(taskId + ' 缺 greenEvidence');
591
- // redEvidence 缺失警告(过渡期不阻断)——新 change(enter 机制激活)升级为 BLOCKED(TDD RED 证据强制)
554
+ // redEvidence 缺失 = 违反 TDD RED 证据要求(BLOCKED)
592
555
  if (r && !r.redEvidence) {
593
- if (isNewChange(state)) {
594
- violations.push(taskId + ' 缺 redEvidence(新 change 强制 TDD RED 证据;旧 change 渐进 WARN)');
595
- } else {
596
- console.error('HANDOFF WARN: ' + taskId + ' 缺 redEvidence(可能未执行 TDD RED 阶段)');
597
- }
556
+ violations.push(taskId + ' 缺 redEvidence(须回传 TDD RED 证据)');
598
557
  }
599
558
  // completedChecks 严格校验(无旧 change 豁免)
600
559
  if (requiredChecks.length > 0) {
@@ -607,7 +566,7 @@ export function runReturnContractGate({ node, state }) {
607
566
  }
608
567
  if (violations.length > 0) {
609
568
  console.error('BLOCKED: Return Contract 校验失败: ' + violations.join('; '));
610
- console.error('恢复: 子代理回传完整契约(含缺失字段)后用 workflow-handoff.mjs result 重录——新 change 强制 TDD RED/GREEN 证据与 completedChecks;注意:若已记录 greenEvidence 而缺 redEvidence,时序防护会拦截事后补录(防掩盖缺 RED)——确认子代理真实执行过 TDD RED 且证据在对应 SUMMARY 中时,用 workflow-state.mjs record subagent-execute 合并写入真实 redEvidence(证据可溯源),或重新委托任务获取完整契约');
569
+ console.error('恢复: 子代理回传完整契约(含缺失字段)后用 workflow-handoff.mjs result 重录——本判据强制 TDD RED/GREEN 证据与 completedChecks;注意:若已记录 greenEvidence 而缺 redEvidence,时序防护会拦截事后补录(防掩盖缺 RED)——确认子代理真实执行过 TDD RED 且证据在对应 SUMMARY 中时,用 workflow-state.mjs record subagent-execute 合并写入真实 redEvidence(证据可溯源),或重新委托任务获取完整契约');
611
570
  process.exit(1);
612
571
  }
613
572
  }
@@ -625,12 +584,9 @@ export async function runSubagentSummaryGate({ node, state }) {
625
584
  const saDir = path.join(runRoot, '.specs', state.activeChange ?? '');
626
585
  for (const t of saTasks.filter(t => t.status === 'done')) {
627
586
  if (!(await fileExists(path.join(saDir, t.id + '-SUMMARY.md')))) {
628
- if (isNewChange(state)) {
629
- console.error('BLOCKED: done 任务 ' + t.id + ' 缺少 ' + t.id + '-SUMMARY.md——subagent-execute 产物不完整(新 change 强制任务完成须有对应 SUMMARY;旧 change 渐进 WARN)');
630
- console.error('恢复: 补写 ' + t.id + '-SUMMARY.md 后重试 exit;任务完成后补产物即可');
631
- process.exit(1);
632
- }
633
- console.error('WARN: done 任务 ' + t.id + ' 缺少 ' + t.id + '-SUMMARY.md——subagent-execute 产物不完整(任务完成须有对应 SUMMARY)');
587
+ console.error('BLOCKED: done 任务 ' + t.id + ' 缺少 ' + t.id + '-SUMMARY.md——subagent-execute 产物不完整(任务完成须有对应 SUMMARY)');
588
+ console.error('恢复: 补写 ' + t.id + '-SUMMARY.md' + ' 后重试 exit;任务完成后补产物即可');
589
+ process.exit(1);
634
590
  }
635
591
  }
636
592
  } catch {}
@@ -717,8 +673,9 @@ async function nodeSkillDeclared(nodeId, changeName) {
717
673
 
718
674
  // 守卫族的命令运行上下文(形状与状态命令族的 commandContext 相同):脚本目录由本模块位置推导,
719
675
  // 运行根 / 包根 / 协议路径取守卫运行上下文——协议路径是本次 guard 实际解析到的那一份(含 state 绑定),
720
- // 命令自带的协议上下文因此与本次运行一致。
721
- function declarationContext() {
676
+ // 命令自带的协议上下文因此与本次运行一致。导出给同族门禁(guard-gates)取用:守卫侧的命令装配
677
+ // 只有这一份上下文,各模块自行推一份必然在「架构化路径 / 协议绑定」上分叉。
678
+ export function guardCommandContext() {
722
679
  return { scriptsDir, runRoot, packageRoot, protocolPath };
723
680
  }
724
681
 
@@ -750,7 +707,7 @@ export async function declarationSkillNames(node, state) {
750
707
  //
751
708
  // 返回命令条目 { skill, command }(命令文本的构造在 state-explain,本函数只决定「哪些技能」)。
752
709
  function skillLoadDeclarationCommands({ node, skills, frontend }) {
753
- return declarationCommands({ node, skills, frontend, context: declarationContext() });
710
+ return declarationCommands({ node, skills, frontend, context: guardCommandContext() });
754
711
  }
755
712
 
756
713
  export async function nodeSkillLoadCommands({ node, state }) {
@@ -764,7 +721,7 @@ export async function nodeSkillLoadCommands({ node, state }) {
764
721
  // 单个技能的声明命令(入口 --prompt 冲突的兜底:标记声明的技能不在本节点目标集里时,仍要给一条
765
722
  // 覆写该标记的命令)。与上面同一装配,不另拼一份文本。
766
723
  export function guardDeclarationCommand({ node, skill, frontend = false }) {
767
- return declarationCommand({ node, skill, frontend, context: declarationContext() });
724
+ return declarationCommand({ node, skill, frontend, context: guardCommandContext() });
768
725
  }
769
726
 
770
727
  // record 命令与「这条命令怎么执行」的说明分行给出(两处恢复段共用):命令单独成行才是可整行照抄的
@@ -773,17 +730,24 @@ export function guardDeclarationCommand({ node, skill, frontend = false }) {
773
730
  const RECORD_RETRY_NOTE = '说明: bash / PowerShell 可直接执行;cmd.exe 请把单引号换成双引号,'
774
731
  + '并转义载荷里原有的双引号';
775
732
 
776
- function recordRecoveryCommand(node, completedChecks = []) {
777
- const payload = { summary: '<本节点完成摘要>' };
778
- if (completedChecks.length > 0) payload.completedChecks = completedChecks;
733
+ // 任意节点 + 任意载荷的 record 命令(命令文本的唯一装配:脚本路径平台化 + 整条加引号 + 协议上下文)。
734
+ // 缺证据恢复段、门控补证据段、归档提名的补录命令三处都从这里取——各自拼一段,就只有在其中一条上
735
+ // 补得到协议上下文/引号形态,另外两条照抄即失败。
736
+ export function nodeRecordCommand(nodeId, payload) {
779
737
  return scriptCommand({
780
738
  scriptsDir,
781
739
  runRoot,
782
740
  script: 'workflow-state.mjs',
783
- args: ['record', node.id, "'" + JSON.stringify(payload) + "'", ...protocolContextArgs(declarationContext())],
741
+ args: ['record', nodeId, "'" + JSON.stringify(payload) + "'", ...protocolContextArgs(guardCommandContext())],
784
742
  });
785
743
  }
786
744
 
745
+ function recordRecoveryCommand(node, completedChecks = []) {
746
+ const payload = { summary: '<本节点完成摘要>' };
747
+ if (completedChecks.length > 0) payload.completedChecks = completedChecks;
748
+ return nodeRecordCommand(node.id, payload);
749
+ }
750
+
787
751
  // 「补证据」恢复段(单一实现):两个门禁点打印同一段——缺 Output Schema 字段
788
752
  // (runEvidenceCompletionGate)与完全没有证据对象(guard-gates 的 requireNodeEvidence)。两处说的
789
753
  // 是同一件事(节点已完成、证据不在),各自拼一份必然分叉:一条带协议上下文与前置声明步骤、另一条
@@ -836,7 +800,7 @@ export async function runEvidenceCompletionGate({ protocol, node, state, evidenc
836
800
  for (const binding of node.requiredSkillCalls ?? []) {
837
801
  const check = 'required-skill:' + node.id + '.' + binding.skill;
838
802
  const applicabilityGated = applicabilityGatedBinding(node, binding.skill) !== null;
839
- if (applicabilityGated && isNewChange(state) && (await frontendCriterion(state.activeChange)).applicable) continue;
803
+ if (applicabilityGated && (await frontendCriterion(state.activeChange)).applicable) continue;
840
804
  if (!checks.includes(check)) checks.push(check);
841
805
  }
842
806
  evidence.completedChecks = checks;
@@ -856,6 +820,14 @@ export async function runEvidenceCompletionGate({ protocol, node, state, evidenc
856
820
  // (全 parallel 无 SUMMARY 属预期);含串行任务的 change 豁免不生效,照常校验,不得静默放行。生效
857
821
  // 时追加被跳过项清单(EMPTY-EXIT-SKIPPED)。
858
822
  export async function runArtifactGate({ protocol, node, state, emptyExitApproved, emptyExitExempt }) {
823
+ // 归档目录名不合规(AC-6):本 change 的归档目录在盘上但名字不是 <YYYY-MM-DD>-<change-id> —— 这条
824
+ // 规则先于在场判定失败,报文给期望格式 + 实际目录名 + 可照抄的改名命令。放在缺件之前:错名目录不是
825
+ // 「某件产物不在场」,报成缺件会让人去补一件其实存在的产物(同一事实两种说法)。
826
+ const archiveNameProblems = archiveDirNameNotice(state.activeChange, node.id);
827
+ if (archiveNameProblems.length > 0) {
828
+ for (const line of archiveNameProblems) console.error(line);
829
+ process.exit(1);
830
+ }
859
831
  const checkedArtifacts = await missingRequiredArtifacts(protocol, node, state.activeChange);
860
832
  let missingArtifacts = checkedArtifacts;
861
833
  if (emptyExitApproved && emptyExitExempt) {