flow-comet 1.6.5 → 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 (89) hide show
  1. package/.flow-comet/skills/flow-comet/INSTALLED_VERSION +1 -1
  2. package/.flow-comet/skills/flow-comet/SKILL.md +32 -18
  3. package/.flow-comet/skills/flow-comet/reference/commit-discipline.md +2 -2
  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 +30 -11
  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/context-init.mjs +26 -23
  16. package/.flow-comet/skills/flow-comet/scripts/guard-self-test.mjs +14 -94
  17. package/.flow-comet/skills/flow-comet/scripts/items/a.mjs +122 -11
  18. package/.flow-comet/skills/flow-comet/scripts/items/b.mjs +79 -40
  19. package/.flow-comet/skills/flow-comet/scripts/items/c.mjs +11 -9
  20. package/.flow-comet/skills/flow-comet/scripts/items/e.mjs +52 -10
  21. package/.flow-comet/skills/flow-comet/scripts/items/f.mjs +1 -1
  22. package/.flow-comet/skills/flow-comet/scripts/items/h.mjs +128 -56
  23. package/.flow-comet/skills/flow-comet/scripts/items/k.mjs +357 -3
  24. package/.flow-comet/skills/flow-comet/scripts/items/l.mjs +26 -1
  25. package/.flow-comet/skills/flow-comet/scripts/items/m.mjs +6 -2
  26. package/.flow-comet/skills/flow-comet/scripts/items/n.mjs +29 -21
  27. package/.flow-comet/skills/flow-comet/scripts/lib/ac-coverage.mjs +317 -0
  28. package/.flow-comet/skills/flow-comet/scripts/lib/fix-loop-node.mjs +4 -15
  29. package/.flow-comet/skills/flow-comet/scripts/lib/guard-artifact-skeleton.mjs +47 -5
  30. package/.flow-comet/skills/flow-comet/scripts/lib/guard-evidence-gates.mjs +357 -219
  31. package/.flow-comet/skills/flow-comet/scripts/lib/guard-gates.mjs +725 -309
  32. package/.flow-comet/skills/flow-comet/scripts/lib/guard-routing.mjs +182 -54
  33. package/.flow-comet/skills/flow-comet/scripts/lib/guard-state-io.mjs +8 -6
  34. package/.flow-comet/skills/flow-comet/scripts/lib/guard-template-fidelity.mjs +224 -83
  35. package/.flow-comet/skills/flow-comet/scripts/lib/guard-uidesign.mjs +17 -28
  36. package/.flow-comet/skills/flow-comet/scripts/lib/lessons-hits.mjs +160 -0
  37. package/.flow-comet/skills/flow-comet/scripts/lib/run-root.mjs +21 -0
  38. package/.flow-comet/skills/flow-comet/scripts/lib/section-body.mjs +92 -0
  39. package/.flow-comet/skills/flow-comet/scripts/lib/state-commands-admin.mjs +61 -33
  40. package/.flow-comet/skills/flow-comet/scripts/lib/state-commands-flow.mjs +663 -205
  41. package/.flow-comet/skills/flow-comet/scripts/lib/state-commands-recovery.mjs +68 -9
  42. package/.flow-comet/skills/flow-comet/scripts/lib/state-determine.mjs +11 -4
  43. package/.flow-comet/skills/flow-comet/scripts/lib/state-explain.mjs +92 -13
  44. package/.flow-comet/skills/flow-comet/scripts/lib/state-io.mjs +232 -11
  45. package/.flow-comet/skills/flow-comet/scripts/lib/state-skillmarkers.mjs +140 -74
  46. package/.flow-comet/skills/flow-comet/scripts/lib/system-fixtures.mjs +8 -4
  47. package/.flow-comet/skills/flow-comet/scripts/lib/task-graph.mjs +84 -31
  48. package/.flow-comet/skills/flow-comet/scripts/lib/test-assertions.mjs +0 -3
  49. package/.flow-comet/skills/flow-comet/scripts/lib/test-fixtures.mjs +248 -24
  50. package/.flow-comet/skills/flow-comet/scripts/lib/test-helpers.mjs +63 -3
  51. package/.flow-comet/skills/flow-comet/scripts/lib/text-anchor-checks.mjs +181 -8
  52. package/.flow-comet/skills/flow-comet/scripts/lib/wave-projection.mjs +340 -0
  53. package/.flow-comet/skills/flow-comet/scripts/protocol-utils.mjs +132 -20
  54. package/.flow-comet/skills/flow-comet/scripts/route-node.mjs +12 -5
  55. package/.flow-comet/skills/flow-comet/scripts/scenarios/a.mjs +1564 -54
  56. package/.flow-comet/skills/flow-comet/scripts/scenarios/b.mjs +1489 -38
  57. package/.flow-comet/skills/flow-comet/scripts/scenarios/c.mjs +1466 -243
  58. package/.flow-comet/skills/flow-comet/scripts/scenarios/d.mjs +743 -24
  59. package/.flow-comet/skills/flow-comet/scripts/scenarios/e.mjs +220 -92
  60. package/.flow-comet/skills/flow-comet/scripts/scenarios/f.mjs +657 -21
  61. package/.flow-comet/skills/flow-comet/scripts/scenarios/g.mjs +41 -27
  62. package/.flow-comet/skills/flow-comet/scripts/scenarios/h.mjs +285 -9
  63. package/.flow-comet/skills/flow-comet/scripts/scenarios/i.mjs +7 -6
  64. package/.flow-comet/skills/flow-comet/scripts/scenarios/j.mjs +21 -15
  65. package/.flow-comet/skills/flow-comet/scripts/scenarios/k.mjs +8 -5
  66. package/.flow-comet/skills/flow-comet/scripts/scenarios/l.mjs +45 -36
  67. package/.flow-comet/skills/flow-comet/scripts/scenarios/m.mjs +2 -2
  68. package/.flow-comet/skills/flow-comet/scripts/scenarios/n.mjs +2381 -85
  69. package/.flow-comet/skills/flow-comet/scripts/state-schema.mjs +135 -2
  70. package/.flow-comet/skills/flow-comet/scripts/workflow-guard.mjs +143 -16
  71. package/.flow-comet/skills/flow-comet/scripts/workflow-handoff.mjs +339 -103
  72. package/.flow-comet/skills/flow-comet/scripts/workflow-state.mjs +5 -2
  73. package/.flow-comet/skills/flow-comet-archive/SKILL.md +33 -11
  74. package/.flow-comet/skills/flow-comet-change/SKILL.md +1 -1
  75. package/.flow-comet/skills/flow-comet-design/SKILL.md +5 -3
  76. package/.flow-comet/skills/flow-comet-dev/SKILL.md +2 -2
  77. package/.flow-comet/skills/flow-comet-execute/SKILL.md +37 -13
  78. package/.flow-comet/skills/flow-comet-integration/SKILL.md +10 -4
  79. package/.flow-comet/skills/flow-comet-plan/GUIDANCE.md +1 -1
  80. package/.flow-comet/skills/flow-comet-plan/SKILL.md +13 -6
  81. package/.flow-comet/skills/flow-comet-review/SKILL.md +21 -12
  82. package/.flow-comet/skills/flow-comet-subagent-execute/GUIDANCE.md +1 -1
  83. package/.flow-comet/skills/flow-comet-subagent-execute/SKILL.md +43 -18
  84. package/.flow-comet/skills/flow-comet-task/SKILL.md +4 -2
  85. package/.flow-comet/skills/flow-comet-ui-design/SKILL.md +2 -2
  86. package/.flow-comet/skills/flow-comet-verify/SKILL.md +1 -1
  87. package/README.md +2 -2
  88. package/package.json +1 -1
  89. package/scripts/dsh-bridge.mjs +238 -21
@@ -45,7 +45,10 @@ export async function inspectWorkflowPathSegments(
45
45
  target,
46
46
  label,
47
47
  expected = 'any',
48
+ options = {},
48
49
  ) {
50
+ const followLinks = options.followLinks === true;
51
+ const wantPhysical = options.physicalRel === true;
49
52
  const lexicalRoot = path.resolve(projectRoot);
50
53
  const lexicalTarget = path.resolve(target);
51
54
  if (!workflowPathInside(lexicalRoot, lexicalTarget)) {
@@ -56,9 +59,14 @@ export async function inspectWorkflowPathSegments(
56
59
  throw new Error(label + ' project root must be a real directory');
57
60
  }
58
61
  const realRoot = await fs.realpath(lexicalRoot);
62
+ const toRel = (absolute) => {
63
+ const relativeToRoot = path.relative(realRoot, absolute);
64
+ return relativeToRoot === '' ? '.' : relativeToRoot.replaceAll('\\', '/');
65
+ };
59
66
  const relative = path.relative(lexicalRoot, lexicalTarget);
60
67
  const segments = relative === '' ? [] : relative.split(path.sep);
61
68
  let cursor = lexicalRoot;
69
+ let physicalCursor = realRoot;
62
70
  for (let index = 0; index < segments.length; index++) {
63
71
  cursor = path.join(cursor, segments[index]);
64
72
  let stat;
@@ -70,13 +78,37 @@ export async function inspectWorkflowPathSegments(
70
78
  typeof error === 'object' &&
71
79
  (error.code === 'ENOENT' || error.code === 'ENOTDIR')
72
80
  ) {
73
- return { target: lexicalTarget, exists: false };
81
+ const remainder = segments.slice(index).join(path.sep);
82
+ return {
83
+ target: lexicalTarget,
84
+ exists: false,
85
+ physicalRel: wantPhysical
86
+ ? toRel(remainder ? path.join(physicalCursor, remainder) : physicalCursor)
87
+ : null,
88
+ };
74
89
  }
75
90
  throw error;
76
91
  }
77
92
  const display = path.relative(lexicalRoot, cursor).replaceAll('\\', '/');
78
93
  if (stat.isSymbolicLink()) {
79
- throw new Error(label + ' crosses a symbolic link or junction at ' + display);
94
+ if (!followLinks) {
95
+ throw new Error(label + ' crosses a symbolic link or junction at ' + display);
96
+ }
97
+ const physical = await fs.realpath(cursor);
98
+ if (!workflowPathInside(realRoot, physical)) {
99
+ throw new Error(label + ' resolves outside the project root at ' + display);
100
+ }
101
+ physicalCursor = physical;
102
+ if (index === segments.length - 1 && expected !== 'any') {
103
+ const resolved = await fs.stat(physical);
104
+ if (
105
+ (expected === 'file' && !resolved.isFile()) ||
106
+ (expected === 'directory' && !resolved.isDirectory())
107
+ ) {
108
+ throw new Error(label + ' must be a real ' + expected);
109
+ }
110
+ }
111
+ continue;
80
112
  }
81
113
  const final = index === segments.length - 1;
82
114
  if (!final && !stat.isDirectory()) {
@@ -94,8 +126,13 @@ export async function inspectWorkflowPathSegments(
94
126
  if (!workflowPathInside(realRoot, physical)) {
95
127
  throw new Error(label + ' resolves outside the project root');
96
128
  }
129
+ physicalCursor = physical;
97
130
  }
98
- return { target: lexicalTarget, exists: true };
131
+ return {
132
+ target: lexicalTarget,
133
+ exists: true,
134
+ physicalRel: wantPhysical ? toRel(physicalCursor) : null,
135
+ };
99
136
  }
100
137
 
101
138
  // 兼容既有消费方(readWorkflowProtectedFile / comet-hook-guard):受保护读取使用同一段
@@ -437,6 +474,24 @@ export function templateKeyOf(value) {
437
474
  return normalizeTemplateName(value).toLowerCase();
438
475
  }
439
476
 
477
+ // 声明工件名 → 模板键(单一实现):「节点声明的哪份工件对应哪份模板」只在此派生,两个消费面共用——
478
+ // 结构预检(缺件报文里的模板指针)与模板保真门禁(该工件用哪份骨架校验)。两处曾各持一份等价实现,
479
+ // 副本一旦漂移,预检与收尾就会对同一份工件给出两套口径——这正是本函数存在的理由。
480
+ // 口径(以模板保真门禁的既有实现为基准,它更新):
481
+ // ① 路径归一:`\` 与 `/` 同权(与 workflowRelativeSegments 对声明路径的口径一致),只取末段——
482
+ // 调用方传整条声明路径(`<change-id>/*-SUMMARY.md`)或裸文件名都可以;
483
+ // ② 通配:取末个 `*` 之后(通配只出现在文件名前缀:`*-SUMMARY.md` → `-SUMMARY.md`);
484
+ // ③ 去首部非字母数字(`-SUMMARY` → `SUMMARY`):通配残渣不是名字的一部分;
485
+ // ④ 空基名 → null(没有可派生的名字)——调用方据此「不给模板指针 / 不校验」,不臆造键;
486
+ // ⑤ 键归一(去尾 `.md` + 小写)由 templateKeyOf 承担,不在此另写一份。
487
+ // 只回答「键」,不回答「该节点是否允许这份模板」:声明集合比对(C11)与指针格式化留在调用方——
488
+ // 两侧对未知键的处置本就不同(预检不编造指针、模板保真门禁跳过未登记工件)。
489
+ export function templateKeyFromArtifactName(value) {
490
+ const base = String(value ?? '').replaceAll('\\', '/').split('/').pop();
491
+ const tail = base.split('*').pop().replace(/^[^A-Za-z0-9]+/u, '');
492
+ return tail === '' ? null : templateKeyOf(tail);
493
+ }
494
+
440
495
  // 逗号分隔的模板清单(`--templates CHANGE.md,REQUIREMENT.md`;单模板可省略逗号)→ 去重保序数组。
441
496
  export function parseTemplateList(value) {
442
497
  const names = [];
@@ -520,23 +575,6 @@ export function templatePointerPath(name) {
520
575
  return TEMPLATE_ROOT + '/' + normalizeTemplateName(name) + '.md';
521
576
  }
522
577
 
523
- // 重新声明的命令指引(skill-load 校验失败与 record 声明核对两处共用):两处本说的是同一件事
524
- // 「怎么重新声明」——各拼一份必然分叉(命令形态改一次要改两地方)。零模板节点不拼 --templates
525
- // (省略即空集,与 C11 的「可省略」一致);无 skill 名的场景用 <skill> 占位。
526
- // --prompt 一并拼上:模板与提示词是同一次声明的两面,而 skill-load 重跑会**覆写**同一标记——
527
- // 只补 --templates 的指引会把 protocol 写成 null,下一次 exit 反被判「缺协议声明标记」(恢复步骤
528
- // 自己弄坏协议声明)。路径取该节点的首个内置协议文件,与入口的 READ PROMPT 同源;自定义节点没有
529
- // 内置映射(协议自己也声明提示词路径)→ 不拼,不编造路径也不打占位符。
530
- export function templateDeclareCommand(declaration, { nodeId, skillName } = {}) {
531
- const skill = typeof skillName === 'string' && skillName !== '' ? skillName : '<skill>';
532
- const flag = declaration.required.length > 0
533
- ? ' --templates ' + declaration.required.map((name) => name + '.md').join(',')
534
- : '';
535
- const promptFile = (NODE_PROTOCOL_FILES[nodeId] ?? [])[0];
536
- const promptFlag = typeof promptFile === 'string' ? ' --prompt ' + promptPointerPath(promptFile) : '';
537
- return 'workflow-state.mjs skill-load ' + nodeId + ' ' + skill + flag + promptFlag;
538
- }
539
-
540
578
  // 指针行(入口与 explain 共用:同一判据一份实现,两处输出措辞一致)。
541
579
  // label:内置入口用 `READ TEMPLATE`,现问通道用 `TEMPLATE`;conditional=true 时追出条件模板行。
542
580
  export function templatePointerLines(declaration, options = {}) {
@@ -609,3 +647,77 @@ export function promptDeclarationConflict({ node, declaredProtocol } = {}) {
609
647
  const expected = [...nodeFiles, ...(NODE_CONDITIONAL_PROMPTS[node?.id] ?? [])];
610
648
  return expected.includes(declared) ? null : { declared, expected };
611
649
  }
650
+
651
+ // ---------- 声明命令:参数面的一处装配 ----------
652
+ //
653
+ // 一次 skill-load 声明要携带的东西只有三样:哪个节点的哪个技能、该节点该读的**每一份**协议文件
654
+ // (条件提示词在适用时并入)、以及该节点的模板全清单。这条装配此前散在几处各拼一份——重跑声明的
655
+ // 指引只带首份 --prompt、公开册把占位符写进 --prompt 的值位置(bash 下 `<` 是重定向)、门禁报文
656
+ // 干脆不带 --templates(照抄即撞模板门)。故参数面只在这里拼,调用方只提供事实(节点、技能)。
657
+ //
658
+ // 命令**文本**(脚本路径 / 引号 / 协议上下文)不在这里:那是运行面的事实(平台布局、本次解析到的
659
+ // 协议),由 lib/state-explain.mjs 的 declarationCommand 一处补齐——状态命令族与守卫族取同一份。
660
+ //
661
+ // 同步面与异步面的差别只有一处输入:条件提示词(design 的 2a-ui-design.md)是否适用。守卫的
662
+ // nodeSkillLoadCommands 判得了前端,按结论并入;状态命令族与册子拿不到该结论,改为「本次声明的
663
+ // 技能自己承载哪份条件提示词就并入哪份」(ui-design → 2a)——同步面不替一个异步判据下结论。
664
+ // 零模板节点不拼 --templates(省略即空集,与 C11 的「可省略」一致)。
665
+ function declarationPromptFiles({ nodeId, skill, frontend }) {
666
+ const files = [...(NODE_PROTOCOL_FILES[nodeId] ?? [])];
667
+ const own = SKILL_PROTOCOL_FILES[skill] ?? [];
668
+ for (const file of NODE_CONDITIONAL_PROMPTS[nodeId] ?? []) {
669
+ if (frontend || own.includes(file)) files.push(file);
670
+ }
671
+ return files.filter((file, index) => files.indexOf(file) === index);
672
+ }
673
+
674
+ // 一次声明的参数面(argv 形态,`skill-load` 起头):脚本路径与协议上下文由调用方追加——它们是
675
+ // 运行面的事实(平台路径 / 本次解析到的协议),不是声明内容。
676
+ export function skillLoadDeclarationArgs({ node, skill, frontend = false } = {}) {
677
+ const args = ['skill-load', node?.id, skill];
678
+ for (const file of declarationPromptFiles({ nodeId: node?.id, skill, frontend })) {
679
+ args.push('--prompt', promptPointerPath(file));
680
+ }
681
+ const declaration = nodeTemplateDeclaration(node);
682
+ if (declaration.required.length > 0) {
683
+ args.push('--templates', declaration.required.map((name) => name + '.md').join(','));
684
+ }
685
+ return args;
686
+ }
687
+
688
+ // 该节点要求声明的技能(guarded ∧ 非 handoff)——协议面的事实,唯一实现:守卫的异步适用性判据、
689
+ // 同步出口的覆盖门与回退取值全从这里取(第二个过滤条件在各处各写一遍,就是「两份判据各自演进」
690
+ // 的起点)。
691
+ export function guardedDeclarationSkills(node) {
692
+ return (node?.requiredSkillCalls ?? [])
693
+ .filter((binding) => binding
694
+ && binding.enforcement === 'guarded'
695
+ && binding.scope !== 'handoff'
696
+ && typeof binding.skill === 'string'
697
+ && binding.skill !== '')
698
+ .map((binding) => binding.skill);
699
+ }
700
+
701
+ // 没有可展开的必需技能时,声明该写哪个技能名(**不臆造**):优先节点实现技能(它是这个节点的实现
702
+ // 者),其次该节点 requiredSkillCalls 里非 handoff 的既有条目,两者皆无才留占位符。
703
+ // 占位符是最后的诚实选择——它落在位置实参位,在 bash 下 `<skill>` 是输入重定向、照抄即失败,
704
+ // 故只有当协议面确实没有可用的技能名时才出现,且报文会说明要按 entry 的 LOAD SKILL 行填。
705
+ export function declarationSkillFallback(node) {
706
+ const implementation = node?.implementation;
707
+ const implementationSkill = implementation && typeof implementation === 'object' ? implementation.skill : null;
708
+ if (typeof implementationSkill === 'string' && implementationSkill.trim() !== '') return implementationSkill.trim();
709
+ const mainScoped = (node?.requiredSkillCalls ?? [])
710
+ .find((binding) => binding && binding.scope !== 'handoff'
711
+ && typeof binding.skill === 'string' && binding.skill !== '');
712
+ return mainScoped ? mainScoped.skill : '<skill>';
713
+ }
714
+
715
+ // 该节点本次该声明哪些技能(**同步面**的目标集):guarded 必需技能,但条件绑定(design 的 ui-design:
716
+ // 技能自身承载的协议文件就是该节点的条件提示词)不在此展开——它是否适用要读 CHANGE.md 判前端,
717
+ // 同步面不替它下结论,缺那一项时由判得了前端的出口指引补。一个都不剩时按 declarationSkillFallback 退。
718
+ export function declarationSkillTargets(node) {
719
+ const skills = guardedDeclarationSkills(node)
720
+ .filter((skill) => !(SKILL_PROTOCOL_FILES[skill] ?? [])
721
+ .some((file) => (NODE_CONDITIONAL_PROMPTS[node?.id] ?? []).includes(file)));
722
+ return skills.length > 0 ? skills : [declarationSkillFallback(node)];
723
+ }
@@ -150,11 +150,13 @@ export function resolveDelegationTarget({
150
150
  }
151
151
 
152
152
  // 判定核心(行为逐字等价——重构保持锚):
153
- // 输入 { runRoot, changeName, protocol, completedNodes = [] } → 输出节点 id 或 null(完成态)。
153
+ // 输入 { runRoot, changeName, protocol, completedNodes = [], changeDir = null } → 输出节点 id 或
154
+ // null(完成态)。changeDir 是**可选**的产物根替换值:该 change 目录相对 .specs/ 的 POSIX 路径
155
+ // ('<id>' / 'archive/<日期>-<id>',由 state-io.resolveChangeDir 的 relative 给出)。
154
156
  // 判定顺序:① completedNodes 全齐 → null;② execute 家族之前的节点产物门控;③ 无 execute 家族 →
155
157
  // 最后节点;④ 任务状态特判(pending 且依赖满足的 parallel → subagent-execute / 串行 pending →
156
158
  // execute / 全 done 但缺 SUMMARY → execute / 后置节点产物门控 / 全部通过 → 最后节点);⑤ 解析失败兜底 execute。
157
- export async function resolveNextNode({ runRoot, changeName, protocol, completedNodes = [] }) {
159
+ export async function resolveNextNode({ runRoot, changeName, protocol, completedNodes = [], changeDir = null }) {
158
160
  const specsRoot = path.join(runRoot, '.specs');
159
161
  // 全部节点已完成 → 完成态,不产出最后节点。自定义协议无 archive 节点时,completedNodes 全齐后
160
162
  // next 仍会输出 NODE: <最后节点>(产物推导只返回最后节点 id)——此处(产物推导之前)判定:
@@ -166,12 +168,17 @@ export async function resolveNextNode({ runRoot, changeName, protocol, completed
166
168
  if (protocolNodeIds.length > 0 && protocolNodeIds.every((id) => completedNodes.includes(id))) {
167
169
  return null;
168
170
  }
169
- const changeDir = path.join(specsRoot, changeName);
171
+ // 产物根替换值:目录已搬进归档时用归档目录(移动后产物仍在归档目录里,file-as-truth 认产物不认
172
+ // 位置)。只换 `<change-id>` 的替换值——nodeFlagsComplete 的根推导(specs-root / project)不动,
173
+ // 那条判据与守卫侧同源,改根会让两侧对「产物在哪」有两种说法。取值形态由生产侧唯一决定
174
+ // (state-io.resolveChangeDir 的 relative:POSIX,'<id>' / 'archive/<日期>-<id>'),本模块不做
175
+ // 二次归一——多一处形态转换就多一处「与解析结果不一致」的机会。
176
+ const changeRef = typeof changeDir === 'string' && changeDir !== '' ? changeDir : changeName;
170
177
  // 节点完成判定: 节点完成标志从协议 outputSchemas 推导(内置协议缺省行为与现硬编码逐字节一致)
171
- const nodeFlags = buildNodeCompletionFlags(protocol, changeName);
178
+ const nodeFlags = buildNodeCompletionFlags(protocol, changeRef);
172
179
  // 任务文件路径:协议可选 taskFile 字段(相对 changeDir),无声明时缺省 TASK.md。
173
180
  // 自定义协议无 taskFile 时 parallel 检测自然降级为串行(任务文件缺失 → 不路由 subagent-execute)。
174
- const taskPath = protocolTaskFilePath(protocol, changeName, specsRoot);
181
+ const taskPath = protocolTaskFilePath(protocol, changeRef, specsRoot);
175
182
 
176
183
  // 节点顺序 = 协议 nodes 顺序(disabled 过滤,见 task-graph 的 route);execute/subagent-execute 由
177
184
  // 任务状态特判。按协议顺序拆分:execute/subagent-execute 之前的节点走产物门控(内置 = open →