flow-comet 1.6.2 → 1.6.4
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.
- package/.flow-comet/skills/flow-comet/INSTALLED_VERSION +1 -1
- package/.flow-comet/skills/flow-comet/SKILL.md +64 -46
- package/.flow-comet/skills/flow-comet/reference/KNOWN-ISSUES-template.md +1 -1
- package/.flow-comet/skills/flow-comet/reference/commit-discipline.md +32 -0
- package/.flow-comet/skills/flow-comet/reference/dirty-worktree.md +1 -1
- package/.flow-comet/skills/flow-comet/{GUIDANCE.md → reference/entry-detail.md} +18 -28
- package/.flow-comet/skills/flow-comet/reference/fix-loop.md +57 -0
- package/.flow-comet/skills/flow-comet/reference/platform-facts.md +58 -0
- package/.flow-comet/skills/flow-comet/reference/replan.md +23 -0
- package/.flow-comet/skills/flow-comet/scripts/comet-check.mjs +5 -4
- package/.flow-comet/skills/flow-comet/scripts/comet-hook-guard.mjs +266 -25
- package/.flow-comet/skills/flow-comet/scripts/context-init.mjs +2 -2
- package/.flow-comet/skills/flow-comet/scripts/evolve.mjs +6 -6
- package/.flow-comet/skills/flow-comet/scripts/guard-self-test.mjs +67 -16325
- package/.flow-comet/skills/flow-comet/scripts/health.mjs +1 -1
- package/.flow-comet/skills/flow-comet/scripts/items/a.mjs +1030 -0
- package/.flow-comet/skills/flow-comet/scripts/items/b.mjs +830 -0
- package/.flow-comet/skills/flow-comet/scripts/items/c.mjs +781 -0
- package/.flow-comet/skills/flow-comet/scripts/items/d.mjs +99 -0
- package/.flow-comet/skills/flow-comet/scripts/items/e.mjs +185 -0
- package/.flow-comet/skills/flow-comet/scripts/items/f.mjs +90 -0
- package/.flow-comet/skills/flow-comet/scripts/items/g.mjs +59 -0
- package/.flow-comet/skills/flow-comet/scripts/items/h.mjs +815 -0
- package/.flow-comet/skills/flow-comet/scripts/items/i.mjs +77 -0
- package/.flow-comet/skills/flow-comet/scripts/items/j.mjs +75 -0
- package/.flow-comet/skills/flow-comet/scripts/items/k.mjs +1427 -0
- package/.flow-comet/skills/flow-comet/scripts/items/l.mjs +275 -0
- package/.flow-comet/skills/flow-comet/scripts/items/m.mjs +614 -0
- package/.flow-comet/skills/flow-comet/scripts/lib/count-derivation.mjs +97 -0
- package/.flow-comet/skills/flow-comet/scripts/lib/fix-loop-node.mjs +196 -0
- package/.flow-comet/skills/flow-comet/scripts/lib/guard-evidence-gates.mjs +553 -0
- package/.flow-comet/skills/flow-comet/scripts/lib/guard-gates.mjs +837 -0
- package/.flow-comet/skills/flow-comet/scripts/lib/guard-routing.mjs +404 -0
- package/.flow-comet/skills/flow-comet/scripts/lib/guard-state-io.mjs +404 -0
- package/.flow-comet/skills/flow-comet/scripts/lib/guard-template-fidelity.mjs +302 -0
- package/.flow-comet/skills/flow-comet/scripts/lib/guard-uidesign.mjs +133 -0
- package/.flow-comet/skills/flow-comet/scripts/lib/reentry-node.mjs +237 -0
- package/.flow-comet/skills/flow-comet/scripts/lib/replan-node.mjs +209 -0
- package/.flow-comet/skills/flow-comet/scripts/lib/state-branch.mjs +49 -0
- package/.flow-comet/skills/flow-comet/scripts/lib/state-bridgecheck.mjs +201 -0
- package/.flow-comet/skills/flow-comet/scripts/lib/state-commands-admin.mjs +141 -0
- package/.flow-comet/skills/flow-comet/scripts/lib/state-commands-flow.mjs +700 -0
- package/.flow-comet/skills/flow-comet/scripts/lib/state-commands-recovery.mjs +578 -0
- package/.flow-comet/skills/flow-comet/scripts/lib/state-determine.mjs +52 -0
- package/.flow-comet/skills/flow-comet/scripts/lib/state-evolve-hint.mjs +55 -0
- package/.flow-comet/skills/flow-comet/scripts/lib/state-explain.mjs +106 -0
- package/.flow-comet/skills/flow-comet/scripts/lib/state-intelscan.mjs +58 -0
- package/.flow-comet/skills/flow-comet/scripts/lib/state-io.mjs +147 -0
- package/.flow-comet/skills/flow-comet/scripts/lib/state-skillmarkers.mjs +189 -0
- package/.flow-comet/skills/flow-comet/scripts/lib/system-fixtures.mjs +1441 -0
- package/.flow-comet/skills/flow-comet/scripts/lib/task-graph.mjs +471 -0
- package/.flow-comet/skills/flow-comet/scripts/lib/test-assertions.mjs +509 -0
- package/.flow-comet/skills/flow-comet/scripts/lib/test-fixtures.mjs +1228 -0
- package/.flow-comet/skills/flow-comet/scripts/lib/test-helpers.mjs +237 -0
- package/.flow-comet/skills/flow-comet/scripts/lib/text-anchor-checks.mjs +2484 -0
- package/.flow-comet/skills/flow-comet/scripts/protocol-utils.mjs +2 -2
- package/.flow-comet/skills/flow-comet/scripts/route-node.mjs +73 -1077
- package/.flow-comet/skills/flow-comet/scripts/scenarios/a.mjs +966 -0
- package/.flow-comet/skills/flow-comet/scripts/scenarios/b.mjs +1233 -0
- package/.flow-comet/skills/flow-comet/scripts/scenarios/c.mjs +1382 -0
- package/.flow-comet/skills/flow-comet/scripts/scenarios/d.mjs +483 -0
- package/.flow-comet/skills/flow-comet/scripts/scenarios/e.mjs +1388 -0
- package/.flow-comet/skills/flow-comet/scripts/scenarios/f.mjs +1466 -0
- package/.flow-comet/skills/flow-comet/scripts/scenarios/g.mjs +1364 -0
- package/.flow-comet/skills/flow-comet/scripts/scenarios/h.mjs +1287 -0
- package/.flow-comet/skills/flow-comet/scripts/scenarios/i.mjs +1436 -0
- package/.flow-comet/skills/flow-comet/scripts/scenarios/j.mjs +1384 -0
- package/.flow-comet/skills/flow-comet/scripts/scenarios/k.mjs +1338 -0
- package/.flow-comet/skills/flow-comet/scripts/scenarios/l.mjs +1484 -0
- package/.flow-comet/skills/flow-comet/scripts/scenarios/m.mjs +971 -0
- package/.flow-comet/skills/flow-comet/scripts/state-schema.mjs +14 -1
- package/.flow-comet/skills/flow-comet/scripts/system-test.mjs +58 -6692
- package/.flow-comet/skills/flow-comet/scripts/time-utils.mjs +4 -4
- package/.flow-comet/skills/flow-comet/scripts/workflow-guard.mjs +151 -2428
- package/.flow-comet/skills/flow-comet/scripts/workflow-handoff.mjs +116 -9
- package/.flow-comet/skills/flow-comet/scripts/workflow-state.mjs +29 -2086
- package/.flow-comet/skills/flow-comet-archive/SKILL.md +10 -19
- package/.flow-comet/skills/flow-comet-change/SKILL.md +2 -3
- package/.flow-comet/skills/flow-comet-compose/SKILL.md +1 -1
- package/.flow-comet/skills/flow-comet-design/SKILL.md +6 -6
- package/.flow-comet/skills/flow-comet-execute/SKILL.md +58 -16
- package/.flow-comet/skills/flow-comet-integration/SKILL.md +8 -5
- package/.flow-comet/skills/flow-comet-open/SKILL.md +5 -1
- package/.flow-comet/skills/flow-comet-plan/GUIDANCE.md +1 -1
- package/.flow-comet/skills/flow-comet-plan/SKILL.md +8 -8
- package/.flow-comet/skills/flow-comet-review/SKILL.md +9 -12
- package/.flow-comet/skills/flow-comet-subagent-execute/SKILL.md +59 -16
- package/.flow-comet/skills/flow-comet-task/SKILL.md +3 -2
- package/.flow-comet/skills/flow-comet-ui-design/SKILL.md +3 -3
- package/.flow-comet/skills/flow-comet-verify/SKILL.md +8 -17
- package/README.md +53 -70
- package/package.json +3 -2
- package/scripts/dsh-bridge.mjs +59 -26
- package/scripts/lib/installer-cleanup.mjs +152 -0
- package/scripts/lib/installer-flowkit.mjs +119 -0
- package/scripts/lib/installer-hooks.mjs +363 -0
- package/scripts/lib/installer-loader.mjs +220 -0
- package/scripts/lib/installer-migrate.mjs +236 -0
- package/scripts/lib/installer-platforms.mjs +314 -0
- package/scripts/prepare-env.mjs +36 -1164
- package/.flow-comet/skills/flow-comet/reference/TEST-MATRIX.md +0 -116
- package/.flow-comet/skills/flow-comet/reference/composition-report.md +0 -65
- package/.flow-comet/skills/flow-comet/reference/dsh-platform.md +0 -184
- package/.flow-comet/skills/flow-comet/reference/resolved-skills.json +0 -661
- package/.flow-comet/skills/flow-comet/reference/skill-review.md +0 -13
- package/.flow-comet/skills/flow-comet/reference/subagents/script-author.md +0 -7
- package/.flow-comet/skills/flow-comet/reference/worktree-notes.md +0 -70
|
@@ -28,22 +28,17 @@ This node finalizes a completed change by extracting reusable lessons from the d
|
|
|
28
28
|
|
|
29
29
|
1. **Scan SUMMARY.md files for lessons**: Read all `<task-id>-SUMMARY.md` files in `.specs/<change-id>/`. Focus on "decisions and deviations" sections. Also check any remaining `<task-id>-PROGRESS.md` "excluded solutions" sections.
|
|
30
30
|
|
|
31
|
-
2. **Apply nomination criteria**:
|
|
32
|
-
- Debugging/trial-and-error took > 30 minutes -> nominate.
|
|
33
|
-
- Error is not task-specific, other tasks would hit it too -> nominate.
|
|
34
|
-
- Reasonable probability of retry within 6 months -> nominate.
|
|
35
|
-
- Otherwise do not nominate (avoid pollution of LESSONS.md).
|
|
31
|
+
2. **Apply nomination criteria**: 三条判据(含「其余一律不提名」兜底)见 `flow-comet-integration` 册的「LESSONS 提名」段——该段是判据的**单一权威**,本册不复述、以该册为准。
|
|
36
32
|
|
|
37
33
|
3. **Add qualifying lessons to LESSONS.md**: For each nominated lesson:
|
|
38
|
-
- Assign next `L-NNN` number (continuing from existing).
|
|
39
34
|
- Fill required fields: label, keywords, applicable tech stack, status (active).
|
|
40
|
-
-
|
|
41
|
-
- **Do NOT archive LESSONS.md** — it is a project-level permanent file that accumulates across changes.
|
|
35
|
+
- 写回 `.specs/LESSONS.md`;编号、插入位置与「不随 change 归档」的判定**以 `flow-comet-integration` 册「LESSONS 提名」段为准**(本册不复述)。
|
|
42
36
|
|
|
43
|
-
4. **Check existing lessons for superseded/deprecated**:
|
|
37
|
+
4. **Check existing lessons for superseded/deprecated**: 扫描 `.specs/LESSONS.md` 的 active 条目,被本次结论取代 / 废弃的更新其状态——判定口径以 `flow-comet-integration` 册「LESSONS 提名」段为准(本册不复述)。
|
|
44
38
|
|
|
45
39
|
5. **Compile the leftover issues list (problem-handling principle)**: Before the move, collect everything that remains open or known-limited in this change:
|
|
46
40
|
- REVIEW.md findings marked `[转待办]` (deferred — recorded but not fixed) plus any known limitations captured during the change.
|
|
41
|
+
- **需要模板时**读 `../flow-comet/reference/KNOWN-ISSUES-template.md`(当你归档时要编遗留清单、需要模板时读它)——含「遗留清单」段骨架与「使用说明」(模板本身是分发产物:零过程代号;归档实例不受此限)。
|
|
47
42
|
- Write `.specs/<change-id>/KNOWN-ISSUES.md` — each entry: issue description, why it was deferred, and where it may surface again.
|
|
48
43
|
- The file moves with the change into `.specs/archive/<YYYY-MM-DD>-<change-id>/` (archived alongside the other artifacts), so the leftover issues never silently vanish after archive.
|
|
49
44
|
- If there are no leftovers, still state that explicitly in the file (e.g. "无遗留问题" / "No known leftover issues").
|
|
@@ -64,7 +59,7 @@ This node finalizes a completed change by extracting reusable lessons from the d
|
|
|
64
59
|
Archived to .specs/archive/<YYYY-MM-DD>-<change-id>/
|
|
65
60
|
遗留问题清单(KNOWN-ISSUES.md,随工件归档): <each leftover issue, or 无>
|
|
66
61
|
This change's DESIGN section 9 has N architecture sedimentation candidates, deferred for batch sync.
|
|
67
|
-
Recommended: run A-evolve workflow after >= 5
|
|
62
|
+
Recommended: run A-evolve workflow after >= 5 个带 `§9` 的归档 change,或距上次沉淀 > 60 天(阈值与入口册 `EVOLVE-DUE` 提示同口径)——批量 review 后 patch CONTEXT.md。
|
|
68
63
|
```
|
|
69
64
|
|
|
70
65
|
10. **Record evidence**: Run `node .claude/skills/flow-comet/scripts/workflow-state.mjs record archive '<evidence JSON>'` to record archive completion.
|
|
@@ -73,18 +68,14 @@ This node finalizes a completed change by extracting reusable lessons from the d
|
|
|
73
68
|
|
|
74
69
|
### 归档后发现缺陷(受控重入)
|
|
75
70
|
|
|
76
|
-
归档已 entry 但归档移动尚未发生(`.specs/<change-id>/` 仍在原位、`status !== 'completed'`)时,review / verify /
|
|
71
|
+
归档已 entry 但归档移动尚未发生(`.specs/<change-id>/` 仍在原位、`status !== 'completed'`)时,review / verify / 执行阶段发现的新缺陷**不得**在归档阶段就地修完——工作归属须先受控归位回既有生命周期,再按修复回路收口。要点:
|
|
77
72
|
|
|
78
|
-
- **未移动** → 受控重入:由用户显式授权后运行
|
|
79
|
-
|
|
80
|
-
```bash
|
|
81
|
-
node .claude/skills/flow-comet/scripts/workflow-state.mjs reenter <target> --authorized-by <source> --reason <text> [--continue-round <n>]
|
|
82
|
-
```
|
|
83
|
-
|
|
84
|
-
目标限 `execute` / `subagent-execute` / `review` / `verify` 之一;每次调用都需要用户显式授权,每 change 上限 3 轮(达上限后凭显式续轮授权 `--continue-round <n>`(n ≥ 已用轮次 + 1)可继续并计入下一轮);命令先自动落 state 备份快照(`.specs/<change-id>/.reentry-backups/`),再转移工作归属,并打印 `REENTRY: archive → <target>(授权源 <source>;第 n/3 轮;备份 <file>)` 与 `REASON: <text>` 行(续轮审计行为 `第 n 轮(显式授权续轮,上限 3)`)。缺授权、目标越界、超上限或归档移动已发生一律 BLOCKED(state 字节零改写),不会静默跳过。
|
|
73
|
+
- **未移动** → 受控重入:由用户显式授权后运行 `node .claude/skills/flow-comet/scripts/workflow-state.mjs reenter <target> --authorized-by <source> --reason <text>`——目标限 `execute` / `subagent-execute` / `review` / `verify` 之一;每次调用都需要用户显式授权,每 change 上限 3 轮(达上限后凭显式续轮授权 `--continue-round <n>`,n ≥ 已用轮次 + 1);命令先自动落 state 备份快照(`.specs/<change-id>/.reentry-backups/`),再转移工作归属;缺授权、目标越界、超上限或归档移动已发生一律 BLOCKED(state 字节零改写),不会静默跳过。
|
|
85
74
|
- **已移动 / 已合并** → 人工处置或新 change:归档移动已发生(`.specs/archive/<日期>-<change-id>/`)或 change 已 `completed` / 已合并时,受控重入不适用(不承诺把文件搬回原位);走人工处置,或把修复放进新 change / hotfix,并在遗留清单里登记指针。
|
|
75
|
+
- **写权限顺序(先转移后写 TASK)**:先跑 `reenter` 完成转移(写入权限随即跟随目标节点),再在目标节点权限内追加 Fix 任务 / 修改工件;archive 阶段 hook 对 change 目录只放行 `KNOWN-ISSUES.md` 这一个精确文件(另有 `.specs/archive/`、`.specs/CHANGELOG.md`、`.specs/LESSONS.md`、`STATE.md`),**不要试图在归档阶段先写 TASK.md**。
|
|
76
|
+
- **回源路径不因归档而放宽**:修复回路本身不变——回到 `execute` 生命周期时照样跑完四类出口,随后**回源节点跑出口**(`entry <源节点>` → `exit <源节点> --apply`);受控重入只改工作归属,不写任何闭合标记,也**禁止绕过**目标节点入口 / 出口与源节点出口门禁。
|
|
86
77
|
|
|
87
|
-
|
|
78
|
+
**何时读完整规格**:要核对完整边界——命令全形与三态审计行(`REENTRY:` / `FIX-BATCH: 归位` / `RETURN:`)的区分、备份快照与 sha256 指纹、续轮授权形态与轮次记账、重复调用同一目标的空操作语义、「已移动 / 已合并」的处置面——读 `../flow-comet/reference/fix-loop.md`(**当你归档后发现缺陷、要把工作归属受控归位回既有生命周期时读它**)。
|
|
88
79
|
|
|
89
80
|
### 归档提交(R4.1 交付闭环)
|
|
90
81
|
|
|
@@ -28,12 +28,11 @@ description: "flow-kit CHANGE 阶段协议:反问澄清、change-id 自动生
|
|
|
28
28
|
|
|
29
29
|
## 视觉调性段的标记约定(前端 / 非前端)
|
|
30
30
|
|
|
31
|
-
`CHANGE.md` 的 `## 视觉调性` 段(段名取自 `flow-kit/templates/CHANGE.md`)不只承载调性选择,还是下游 design
|
|
31
|
+
`CHANGE.md` 的 `## 视觉调性` 段(段名取自 `flow-kit/templates/CHANGE.md`)不只承载调性选择,还是下游 design 出口判定「是否前端」的**结构级判据**的输入面——它的在场状态必须与项目实情一致:
|
|
32
32
|
|
|
33
|
-
-
|
|
33
|
+
- **判据与强制等级(唯一权威)**:判据全文与 `guarded` 绑定、`required-skill:design.flow-comet-ui-design` 声明要求、非前端 `UI-DESIGN: skipped(非前端)` 的出口口径都在 `flow-comet-ui-design` 册的「触发与跳过」段——本节不复述,只描述怎么填段。
|
|
34
34
|
- **前端项目**:按步骤 0.6 的预选结果填段(选定 / 理由 / 参考产品 / 明确排除),不要以结构形态标注「不适用」。
|
|
35
35
|
- **非前端项目**:保留该段并以**结构形态**标注「不适用」(可附一句理由,例如「CLI 工具,无用户可见界面」)。段缺席同样按非前端处理,但缺席不留可读证据,故约定**显式标注**。
|
|
36
|
-
- **判据与强制等级**(下游据此分派):`flow-comet-ui-design` 在 design 节点的绑定等级为 `guarded`——段在场且无结构形态标记 ⇒ 判前端 ⇒ design 出口要求 `.specs/<change-id>/UI-DESIGN.md` 在场,并要求 `required-skill:design.flow-comet-ui-design` 真实声明(先加载、再声明);段缺席或有结构形态标记 ⇒ 判非前端 ⇒ 出口打印 `UI-DESIGN: skipped(非前端)` 与命中片段后放行,不要求 UI-DESIGN.md。
|
|
37
36
|
- **改判走本阶段**:change 进行中要改前端 / 非前端判定,回到这里改这一个段,不在 design / execute / verify 里就地绕开判据——改段即改变了 design 出口的判据输入。
|
|
38
37
|
|
|
39
38
|
## 状态推进
|
|
@@ -15,7 +15,7 @@ description: "Use only when explicitly invoked as /flow-comet-compose. Not part
|
|
|
15
15
|
- **guard 校验**:`workflow-guard.mjs` 按节点 guardrail(artifact-exists / evidence-only / state-transition)做阶段门禁
|
|
16
16
|
- **hook 拦截**:`comet-hook-guard.mjs` 按 writeWhitelist 做写入边界守卫
|
|
17
17
|
|
|
18
|
-
**内置 8
|
|
18
|
+
**内置 8 节点协议不可被取代**:`../flow-comet/reference/workflow-protocol.json`(open→design→plan→execute→subagent-execute→review→verify→archive)永远是默认工作流;自定义协议只在用户显式指定时加载(见「与内置协议的关系」)。
|
|
19
19
|
|
|
20
20
|
## 交互流程(逐步)
|
|
21
21
|
|
|
@@ -58,11 +58,11 @@ This node transforms requirements into an actionable technical design. It produc
|
|
|
58
58
|
|
|
59
59
|
5. **Data flow / architecture diagram (section 2)**: ASCII or Mermaid diagram showing data/event flow, key state machines, boundaries.
|
|
60
60
|
|
|
61
|
-
6. **ADR (section
|
|
61
|
+
6. **ADR (section 4)**: For any decision that could be reversed later, write ADR to `.specs/adr/<NNN>-<title>.md` with Context / Decision / Consequences structure.
|
|
62
62
|
|
|
63
|
-
7. **Risk assessment (section
|
|
63
|
+
7. **Risk assessment (section 5)**: At least 3 risks (implementation / launch / long-term debt), each with mitigation.
|
|
64
64
|
|
|
65
|
-
8. **Out of scope (section
|
|
65
|
+
8. **Out of scope (section 6)**: Explicitly list what this design does NOT solve but will need future attention.
|
|
66
66
|
|
|
67
67
|
9. **Architecture sedimentation suggestions (section 9)**: If this change introduces project-level reusable value (new abstractions, tech decisions, cross-module contracts, dependency changes, forbidden-list updates), fill section 9. Otherwise write "No architecture sedimentation suggestions for this change."
|
|
68
68
|
|
|
@@ -111,9 +111,9 @@ The design node reads CHANGE.md and REQUIREMENT.md, then produces DESIGN.md thro
|
|
|
111
111
|
|
|
112
112
|
**加载声明(阶段层 · 双步硬规则)**:本节点技能已由入口路由经 Skill 工具加载(你正在阅读的就是它);本节点 Required Skill Calls 的加载与声明同样不可跳过:
|
|
113
113
|
|
|
114
|
-
1. 本节点的同名条目已随路由加载——同名 required 条目(`flow-comet-design`)无需重复加载,仅需运行下方声明命令(只读取 SKILL.md 文件不叫加载,**不得跳过**真正的 Skill 工具注入步骤)。`flow-comet-ui-design` 为 **guarded 但仅前端适用**的条目——前端项目用 Skill 工具加载其已装副本后**必须**运行对应 `skill-load` 声明建标记,并在 record 载荷带 `required-skill:design.flow-comet-ui-design
|
|
114
|
+
1. 本节点的同名条目已随路由加载——同名 required 条目(`flow-comet-design`)无需重复加载,仅需运行下方声明命令(只读取 SKILL.md 文件不叫加载,**不得跳过**真正的 Skill 工具注入步骤)。`flow-comet-ui-design` 为 **guarded 但仅前端适用**的条目——前端项目用 Skill 工具加载其已装副本后**必须**运行对应 `skill-load` 声明建标记,并在 record 载荷带 `required-skill:design.flow-comet-ui-design`;非前端项目不加载不声明(出口打印可见的 `UI-DESIGN: skipped(非前端)` 后放行);旧 change 保持渐进,缺件仅 WARN。
|
|
115
115
|
|
|
116
|
-
> **前端判据(结构级 ·
|
|
116
|
+
> **前端判据(结构级 · 唯一权威 → `flow-comet-ui-design` 册的「触发与跳过」段)**:判据全文与 `guarded` 绑定的判级口径都在该册——本节不复述,判定与出口行为一律以该册为准。
|
|
117
117
|
2. 加载完成后**立即**运行声明命令(节点退出与证据记录会核对声明标记;声明如实记录加载动作,不等于产出证明):
|
|
118
118
|
|
|
119
119
|
```bash
|
|
@@ -160,6 +160,6 @@ If the script prints `SKILL: flow-comet-plan`, load that Skill next.
|
|
|
160
160
|
|
|
161
161
|
1. Re-run entry check to confirm workflow state.
|
|
162
162
|
2. Read `.specs/<change-id>/DESIGN.md` — 轻量流程允许 `.specs/<change-id>/DESIGN-lite.md`(guard 同口径:DESIGN.md 优先、DESIGN-lite 兜底)——if exists with section 0 populated and user confirmed, design phase is done.
|
|
163
|
-
3. If the design doc exists but incomplete, resume from the first missing section (check 0, 0.5, 1-
|
|
163
|
+
3. If the design doc exists but incomplete, resume from the first missing section (check 0, 0.5, 1-6, 9).
|
|
164
164
|
4. If frontend project: check `.specs/<change-id>/UI-DESIGN.md` existence.
|
|
165
165
|
5. Do not repeat confirmed decisions. Resume from the first incomplete artifact.
|
|
@@ -11,7 +11,7 @@ Complete the `execute` Node for `flow-comet`.
|
|
|
11
11
|
|
|
12
12
|
Responsibility: 按 TASK.md 逐任务执行(**执行模式按 executionMode**:subagent 默认统一委托子代理、direct 逃生口主代理直写)。串行任务的 TDD + 6 维自查 + LESSONS 扫描 + diff 边界 verify 由执行者承担,无论哪种模式都必须加载 flow-comet-dev 协议。
|
|
13
13
|
|
|
14
|
-
In subagent mode (default) this node is a coordinator: it does not write implementation code directly — it delegates the pending serial tasks to fresh-context subagents
|
|
14
|
+
In subagent mode (default) this node is a coordinator: it does not write implementation code directly — it delegates the pending serial tasks to fresh-context subagents (all three platforms delegate under one identity-based criterion; worktree isolation is one optional implementation of attribute ①, not a requirement — see the four-attribute contract below), each subagent applies the full dev protocol (TDD RED/GREEN/REFACTOR, LESSONS scan, existing abstraction grep, self-review, diff boundary verification, atomic commits) and returns a Return Contract. 趟次协作:并行委托节点(subagent-execute)可多次往返——每趟委托全部依赖已满足的并行任务,本节点在趟间消化串行任务,直至两者清空。The coordinator records handoff evidence, verifies each SUMMARY, and marks tasks done in TASK.md. In direct mode (escape hatch, user-confirmed) the main agent implements serial tasks directly — see 执行模型 below.
|
|
15
15
|
|
|
16
16
|
## Guidance
|
|
17
17
|
|
|
@@ -29,7 +29,7 @@ guard 校验见 workflow-guard.mjs NODE_TRANSITION_GATES / W1-B;「填得好
|
|
|
29
29
|
|
|
30
30
|
### 执行模型(按 executionMode,用户显式选择)
|
|
31
31
|
|
|
32
|
-
- **subagent(默认)**: 统一委托子代理——协调者流程(构造 handoff →
|
|
32
|
+
- **subagent(默认)**: 统一委托子代理——协调者流程(构造 handoff → 按平台通道委托(三平台同一身份判据;worktree 为属性①的可选实现)→ 收集 Return Contract → 验收标 done)
|
|
33
33
|
- **direct(逃生口,需用户显式切换)**: 主代理直接执行串行任务——但必须加载 flow-comet-dev 完整协议
|
|
34
34
|
(TDD/6 维自查/越界检查/原子 commit),SUMMARY 必填段 + `## 自检方法` 强制(guard 校验兜底)
|
|
35
35
|
- 无论哪种模式:`parallel="true"` 任务始终由 subagent-execute 并行委托,不在此节点执行。
|
|
@@ -44,7 +44,9 @@ execute 节点**只处理 `parallel="false"`(或未标注 parallel)的 pendi
|
|
|
44
44
|
|
|
45
45
|
**TASK 签名校验(C3,execute 期间)**:entry execute 时记录任务集签名(行尾规范化 + 标记属性剥离);exit 时比对——execute 期间 TASK.md **只允许改开标签的标记属性**(`status` done/pending;时间戳如需记录写在开标签属性如 `completed_at`——签名剥离白名单允许;**禁止写入 action/其他 task 内容**),增删任务/改 action/改边界/改其他内容会在 exit 被 BLOCKED(签名不匹配)。回退修复任务(review/verify 发现缺陷追加)须先经 review 流程追加到 `## Fix 任务` 段,再按下方「修复回路状态机路径」受控归位 execute,并由 entry execute 刷新签名(端到端验证实证:直接注入任务会被签名拦截)。
|
|
46
46
|
|
|
47
|
-
|
|
47
|
+
**任务集已修订 ⇒ 出口报「签名不匹配」时的合法出口**:**不要手改状态**——跑 `workflow-state.mjs replan "<原因>" --authorized-by <来源>` 重校重签(需用户显式授权;**要判定该不该重校、或签名不匹配要处置时读 `../flow-comet/reference/replan.md`**)。
|
|
48
|
+
|
|
49
|
+
本节点**不直接写实现代码**。所有 pending 任务统一委托 fresh-context 子代理执行(加载 flow-comet-dev + 回传 Return Contract);委托通道按平台(差异只在谁建树),见下方「并行安全四属性契约」与 `../flow-comet/reference/platform-facts.md`(三平台通道对照表)。
|
|
48
50
|
|
|
49
51
|
- `parallel="true"` 的 pending 任务由 subagent-execute 节点负责并行委托
|
|
50
52
|
- execute 遍历 TASK.md 时,遇到 `parallel="true" status="pending"` 的任务块应**跳过**
|
|
@@ -52,7 +54,48 @@ execute 节点**只处理 `parallel="false"`(或未标注 parallel)的 pendi
|
|
|
52
54
|
1. 正常流程下 determineNode 的 路由逻辑会**直接路由到 subagent-execute**(无需经过 execute 空退出)——协调者确认 路由逻辑生效(`NODE: subagent-execute`)后直接进入该节点
|
|
53
55
|
2. 若已进入 execute 且确认无串行任务可做:按正常 exit 流程处理(record execute evidence + 满足产物校验),需要豁免越俎代庖检测时用 `record execute '{"parallelTakeoverApproved":true}'` 显式声明;[P] 任务由 execute 完成属越权委托——新 change BLOCKED(旧 change WARN 渐进)
|
|
54
56
|
3. **显式空退出豁免(新 change 可用)**:确认全 parallel 无串行可做且无法路由时,用 `record execute '{"emptyExitApproved":true}'` 显式声明后 exit 通过(跳过串行 pending 与产物校验;防规划错误仍默认 BLOCKED——豁免须显式声明;exit 输出 EMPTY-EXIT 审计提示)
|
|
55
|
-
- determineNode 路由逻辑会优先检测依赖已满足的 parallel 任务并路由到 subagent-execute;若 determineNode 路由到了 execute,说明当前趟存在需要 execute
|
|
57
|
+
- determineNode 路由逻辑会优先检测依赖已满足的 parallel 任务并路由到 subagent-execute;若 determineNode 路由到了 execute,说明当前趟存在需要 execute 处理的串行任务(此时应执行而非空退出——**除非已显式声明空退出豁免** `emptyExitApproved`,见上条第 3 项)——串行消化完成后再次路由,剩余并行任务回到 subagent-execute 的下一趟(多趟循环直至无可并行 pending 且无串行残留)
|
|
58
|
+
|
|
59
|
+
### 并行安全四属性契约
|
|
60
|
+
|
|
61
|
+
> **并行安全四属性契约**:契约对象是**四属性**,不是 worktree——`worktree` 只是属性①「写权限」的**实现之一**,不是契约本身;「一律 worktree」的口号已作废(本仓决策:契约对象 = 四属性,worktree 降为实现之一)。三平台在同一判据下平行对等,**唯一差异是「谁建树」**。
|
|
62
|
+
>
|
|
63
|
+
> | # | 属性 | 含义 | 满足形态 |
|
|
64
|
+
> |---|------|------|----------|
|
|
65
|
+
> | ① | **写权限** | 每个写者必须有一条被守卫认可的写入通道 | **身份分派**(CC / Codex 载荷含 `agent_id` ⇒ 子代理语义;dsh 桥接以环境变量 `FLOW_COMET_AGENT_DEPTH` 透传正整数身份深度,**并同时注入桥接通道标记 `FLOW_COMET_AGENT_DEPTH_SOURCE`——守卫要求标记与深度同时在场才接受该通道**)——**worktree 只是本属性的实现之一**,不是必须;**最小保护集除外**:身份在场时 `.flow-comet/flow-comet-state.json` 与 `../flow-comet/reference/workflow-protocol.json` 仍受拦(三平台一致 BLOCKED) |
|
|
66
|
+
> | ② | **提交隔离** | 提交只含自己 `write_files` 的字面路径 | 提交面 pathspec 纪律五要素(见 Guidance 同名小节) |
|
|
67
|
+
> | ③ | **验证隔离** | 同一时刻只有一个写者:全量判据不得与在飞写者并行 | 出口校验锚 = `handoffRequests` 有 request 无对应 `handoffResult` ⇒ 新 change BLOCKED / 旧 change WARN;全部有 result ⇒ 放行;无证据 ⇒ 零输出(**已撤回的 request 不构成在飞委托**:`workflow-handoff.mjs withdraw <task-id> --by <来源>` 在原记录上留痕 `withdrawnAt` + `withdrawnBy`,已撤回 = 终态、历史不删) |
|
|
68
|
+
> | ④ | **集成纪律** | 机制选择 / 顺序 / 审计 / 冲突处置四项均有明文规则 | 集成纪律四要素(见 Guidance 同名小节) |
|
|
69
|
+
>
|
|
70
|
+
> **写面含 gitignored 面的任务(四属性映射 · 与其他任务同一判据)**:任务 `write_files` 全为 gitignored 字面路径时,四属性的满足方式不变——① **写权限**仍走**身份通道**(载荷 `agent_id` / 环境变量身份深度 ⇒ 子代理语义放行,项目内任意路径可写(含 gitignored);gitignored 只是路径属性,不是通道差异);② **提交隔离**走既有 **`noCommit` 资格**(request 按 `.gitignore` 命中记 `noCommit:true` ⇒ 任务零提交,「提交只含自己 `write_files` 的字面路径」由**无提交**满足,不是放宽校验;资格 fail-closed:glob / `..` 越界 / 非 git 仓 / tracked 文件 / 链接逃逸一律不授予,result 时刻按同一判据重验,失败即撤销资格);③④ 与其他任务同形(同一时刻单写者 + 集成四要素)。**并行 × 零提交**因此合法:任务可标 `parallel="true"` 并被并行委派,出口校验按 request 的 `noCommit` 资格豁免缺 `commitHash`。
|
|
71
|
+
> **留痕的边界(诚实声明 · 与 `directOverride` / `completedChecks` / `reentryAuthorization` 同族)**:留痕记录的是「**发生过委派**」,**不是**对执行者身份的物理证明——`handoffRequests` / `handoffResult` 只证明协调者写下过 request 与 result 两条记录,不证明写入确实由子代理完成;与 `completedChecks` 只能记录声明、`directOverride` 只能记录授权、`reentryAuthorization` 只能记录授权源同理。声明与事实不符属流程违规,验收以 transcript 可见的委派触发为准。
|
|
72
|
+
>
|
|
73
|
+
> **平台事实(三平台通道 · 判级三态 · 实测与边界)**:要判定平台能力(能否并行委派 / 谁建树 / 写通道是什么)或引用判级口径时读 `../flow-comet/reference/platform-facts.md`——三平台通道对照表、判级三态(证实 / 推翻 / 未覆盖)与该次实测的限定边界原文在该文件,本册不复述。
|
|
74
|
+
|
|
75
|
+
### 提交面 pathspec 纪律(要点 · 带适用条件)
|
|
76
|
+
|
|
77
|
+
**适用条件(先读)**:本条纪律适用于「**多个写者共享同一工作区**」形态——并发写者同处一个工作树(CC 非 worktree 委托 / Codex 共享工作区 / dsh 进程内子代理)。**各自独立工作区(worktree 等)内的局部 `reset` / `clean` 不在禁令内**;但只要本趟存在**任一**共享工作区的写者,本条即对整个并行趟生效。
|
|
78
|
+
|
|
79
|
+
要点(五要素 + 并行波次附加两条):
|
|
80
|
+
|
|
81
|
+
1. **`git add -- <自己字面路径>`** + **`git commit -- <同一路径>`**:逐条字面路径(取自本任务 `write_files`),两步路径集逐字一致——提交只含自己的文件;禁用 `.` / `-A` / `-u` 等宽泛形态。
|
|
82
|
+
2. **锁失败重试**:并发提交撞 `index.lock` / `cannot lock ref` ⇒ **失败即重试**,不得因锁失败改用宽泛命令。
|
|
83
|
+
3. **禁裸 `add` / `commit -a` / `stash` / `clean` / `reset`**:并发写者共享**同一个索引与工作树**——宽泛命令有**并发索引竞态**(把同伴半成品纳入自己的提交),`stash` / `clean` / `reset` 更会破坏同伴的未提交工作。
|
|
84
|
+
4. **并行波次禁用 `git commit --amend`**:共享工作区下 HEAD 会被并行写者推进;确需修正必须**先断言 `git rev-parse HEAD` 等于自己刚提交的哈希**,否则一律改用**新提交追加**。
|
|
85
|
+
5. **误改后的自救通道**(第 3 条「禁 `reset`」的定向例外):断言 HEAD 后 `git reset --soft <自己的父提交>`(**只用 `--soft`**),再以 **pathspec** 重建自己的提交。
|
|
86
|
+
|
|
87
|
+
> **要判定提交边界、或撞上锁 / 误改要收拾时读 `../flow-comet/reference/commit-discipline.md`**——五要素与并行波次附加两条的完整判据(含实测依据)在该文件。
|
|
88
|
+
|
|
89
|
+
### 集成纪律(要点)
|
|
90
|
+
|
|
91
|
+
要点(四要素):
|
|
92
|
+
|
|
93
|
+
1. **机制选择**:优先 **`git merge --no-ff`**(保留父子关系、可审计;comet 先例:集成用 `--no-ff`、交付用 `--ff-only`);冲突难解时**降级 `git cherry-pick` 并强制记因**(审计行写明降级原因)。
|
|
94
|
+
2. **顺序(确定性规则)**:先按 `depends_on` 的**拓扑序**(被依赖者先入),同一拓扑层内按 **task id 升序**——**不得依赖书写顺序** / 提交到达顺序 / 完成先后等运行期不确定量。
|
|
95
|
+
3. **审计留痕**:每次集成输出一行 `INTEGRATE: <task-id> <commitHash> → <集成提交>`(降级路径记降级原因),映射(task-id → commitHash → 集成提交)记入该趟流程记录(`<task-id>-SUMMARY.md` / handoff evidence 文本字段);**判级**:审计行是**执行纪律**(review 把关),本节点不声称存在机械门禁校验它。
|
|
96
|
+
4. **冲突处置(两类分别动作)**:**机械冲突**(不改用户可见行为)执行者**可自行解决** + 必须跑**合并后验证**并在审计行记因;**语义冲突**(两侧对同一行为 / 契约 / 接口给出不同语义)**必须中止集成并上抛**(记 BLOCKED + 恢复指引,由协调者 / 用户裁决)——不得由执行者自行拍板。
|
|
97
|
+
|
|
98
|
+
> **要在集成前定规则、或遇冲突 / 降级要判定时读 `../flow-comet/reference/commit-discipline.md`**——四要素的完整判据与 comet 先例在该文件。
|
|
56
99
|
|
|
57
100
|
### Prerequisites
|
|
58
101
|
|
|
@@ -61,15 +104,16 @@ execute 节点**只处理 `parallel="false"`(或未标注 parallel)的 pendi
|
|
|
61
104
|
- `.specs/LESSONS.md` must exist (or be created from template if missing).
|
|
62
105
|
- For frontend/UI tasks: `.specs/<change-id>/UI-DESIGN.md` must exist.
|
|
63
106
|
- 若当前任务的 `<task-id>-PROGRESS.md`(位于 `.specs/<change>/`;与 Recovery 段及归档期 `*-PROGRESS.md` 扫描同口径)存在,必须先读取"已排除方案"段(R1.6 反重复),确认当前计划不在排除列表中。完成后删除该文件,有用信息迁移至 SUMMARY。
|
|
64
|
-
- 委托前按
|
|
107
|
+
- 委托前按 `../flow-comet/reference/dirty-worktree.md` 检查脏工作树(`.specs/<change-id>/` 未提交工件会触发 entry execute 的 WORKTREE WARN;verify 前为自查建议,无 guard 检查)。
|
|
65
108
|
|
|
66
109
|
### Steps(subagent 模式 · 协调者流程,统一委托子代理)
|
|
67
110
|
|
|
68
111
|
对 TASK.md 每个 pending 串行任务,协调者执行:
|
|
69
112
|
|
|
70
113
|
1. **读 task 块,构造 handoff request**:读 `<task>` XML 块(`action` / `read_files` / `write_files` / `verify` / `done`)。若内容有歧义,停下询问——不要猜。构造 handoff request 内容:task 全文 + DESIGN §0/§0.5 + AC + read/write_files 边界。运行 `node .claude/skills/flow-comet/scripts/workflow-handoff.mjs request <task-id>` 记录。**委托即记 request**——直接记录 result 而无对应 request 时,write_files 允许列表为空会被 BLOCKED(新 change 强制委托边界),补 request 后再重录 result 即可(执行者实证)。
|
|
71
|
-
2.
|
|
114
|
+
2. **委托子代理**:按平台通道委托 fresh-context 子代理(三平台同一身份判据,差异只在谁建树;`isolation: "worktree"` 是属性①的可选实现,非强制——见「并行安全四属性契约」)。handoff prompt 强制协议:子代理用 **Skill 工具**加载 flow-comet-dev 并按 `flow-kit/prompts/4-dev.md` 协议执行(TDD RED/GREEN/REFACTOR、LESSONS 扫描、既有抽象 grep、verify、6 维自查、越界检查、原子 commit `<type>(<scope>): <subject>`(scope 推荐可选:子系统短词;禁 change-id/日期作 scope;任务号放提交正文尾注 Task: <task-id>,change-id 不入标题)),按 `flow-kit/templates/SUMMARY.md` 模板写 `.specs/<change-id>/<task-id>-SUMMARY.md`(标题/首部/段序保真,另补 flow-comet 增量 `## 自检方法` 段),回传 Return Contract(含 commitHash + greenEvidence + completedChecks + selfReview)。**SUMMARY 自引用 hash 注**:提交内容无法包含自身 hash——若子代理 amend 提交,SUMMARY 内记录的 commitHash 为 amend 前值属预期(文件集一致即可,以实际提交对象为准)。
|
|
72
115
|
**提交从属规则**:任务专属的 `<task-id>-SUMMARY.md`(位于 `.specs/<change-id>/`,是 flow-comet 强制产物)允许随任务提交属流程默认豁免——目标仓库的既有规定优先,若目标仓库忽略清单等既有规定拒绝其入库,被拒即为正确行为,严禁 force-add 强加越库提交;委托校验对任务摘要的豁免属于校验宽容度,不是入库指令。
|
|
116
|
+
**提交面 pathspec 纪律(五要素,见 Guidance 同名小节)**:handoff prompt 必须要求子代理用 `git add -- <自己字面路径>` + `git commit -- <同一路径>` 提交、锁失败重试、禁裸 `add` / `commit -a` / `stash` / `clean` / `reset`(适用条件:**多个写者共享同一工作区**;各自独立工作区内的局部 `reset` / `clean` 不在禁令内)。**集成纪律(四要素,见 Guidance 同名小节)**:协调者集成时优先 `git merge --no-ff`、降级 `cherry-pick` 记因、顺序按 `depends_on` 拓扑序 + 同层 task id 升序、冲突按机械 / 语义两类分别处置。
|
|
73
117
|
3. **记录 handoff result**:子代理回传后,运行 `node .claude/skills/flow-comet/scripts/workflow-handoff.mjs result <task-id> '<JSON>'` 记录(Return Contract 含 commitHash + greenEvidence + completedChecks + selfReview)。
|
|
74
118
|
4. **验收 SUMMARY,TASK.md 标 done**:确认 SUMMARY 按 `flow-kit/templates/SUMMARY.md` 填写且**模板保真**(标题 `# SUMMARY:` / 首部 4 字段 / 段序一致)、含 `## 自检方法` 段(声明 brooks-review / cache-brooks / builtin-quickcheck 三值之一)、verify 输出真实、6 维自查与越界检查有实质内容;通过后在 TASK.md 将任务标 `status="done"` 并加时间戳。
|
|
75
119
|
5. **下一个 pending 任务**:重复步骤 1-4。
|
|
@@ -107,18 +151,16 @@ This node is truly done when:
|
|
|
107
151
|
|
|
108
152
|
## 修复回路状态机路径
|
|
109
153
|
|
|
110
|
-
review / verify
|
|
154
|
+
review / verify 发现缺陷后的修复**必须回到 `execute` 节点生命周期内完成**,禁止驻留源节点「顺手修完」;路径要点(`<源节点>` = review 或 verify):
|
|
111
155
|
|
|
112
|
-
1. **追加 Fix
|
|
113
|
-
2. **受控归位 execute
|
|
114
|
-
3.
|
|
115
|
-
4.
|
|
116
|
-
|
|
117
|
-
|
|
118
|
-
- **`next` 回程审计行语义**:回程豁免行始终输出中性 `RETURN: 回程源节点 <源节点>`(源节点产物在场且未出口;保留源节点跑出口),不再输出 FIX-BATCH;受控归位行的 `FIX-BATCH: 归位 <execute 家族>` 保留(真实 Fix 回退行),两者不得混同。
|
|
119
|
-
6. **禁止绕过**:驻留源节点不归位、顺手改完后直接跑源节点 exit 收场会被 BLOCKED(存在未归位/未跑出口的修复回路),必须按上述路径恢复;不得用跳过归位或出口门禁的手段(含手动改写 `.flow-comet/flow-comet-state.json`)替代本路径。
|
|
156
|
+
1. **追加 Fix 任务**:写进 `.specs/<change-id>/TASK.md` 的 `## Fix 任务` 段(完整任务字段),**禁止文件尾追加**;任务集修订必须在 `entry` 之前完成。
|
|
157
|
+
2. **受控归位 execute**:`workflow-state next`(或 `workflow-guard entry execute`)⇒ 引擎把当前节点受控归位为 `execute`(`currentNode=execute`)并输出 `FIX-BATCH` 审计行(`next` 同时输出 `NODE: execute`);用 `status` 确认 `stateCurrentNode` 已是 `execute` 再开工,未归位不得硬开工。
|
|
158
|
+
3. **执行修复 + 跑 execute 四类出口**:按节点生命周期完成全部 Fix 任务(委托 / 直写规则不变)→ `record execute` → `exit execute --apply`——**全任务 done / 逐任务 SUMMARY 完备 / 6 维自查 + 自检方法声明 / 任务集签名一致**,任一缺失即 BLOCKED 并给恢复指引;`entry execute` 刷新并锁定追加后的任务集(**归位后不得再增删任务或改任务内容**);通过后引擎在二次完成时把当前节点推回源节点。
|
|
159
|
+
4. **审计行三态**:真实 Fix 回炉保留 `FIX-BATCH: 回源节点 <源节点>`;正常多趟收尾(签名全等且无 Fix 标记)输出中性 `RETURN: 回源节点 <源节点>`;旧 state 缺闭合 / 修复证据输出 `RETURN: …(旧 state 缺闭合/修复证据,未分类)`——分类只改审计行文本,路由与 state 写入零变化(`RETURN:` 是审计行前缀,与子代理的 Return Contract 无关)。
|
|
160
|
+
5. **回源节点跑出口**:回到源节点后 `next` 应输出 `NODE: review` / `NODE: verify`(不因产物已存在而跳过),随后 `entry <源节点>` → `exit <源节点> --apply`;通过后继续正常路由(必要时进入下一轮 Fix 闭环)。
|
|
161
|
+
6. **禁止绕过**:不归位、顺手改完直接跑源节点 exit 收场、或手改 `.flow-comet/flow-comet-state.json` 一律 BLOCKED——不得用跳过归位 / 出口门禁的手段替代本路径。
|
|
120
162
|
|
|
121
|
-
|
|
163
|
+
> **要判定该不该开修复回路、要受控归位或受控重入、核对归档侧重入边界时读 `../flow-comet/reference/fix-loop.md`**——上述 6 步的完整判据 + 受控重入完整规格(archive 源:`workflow-state.mjs reenter <target> --authorized-by <source> --reason <text>`,每次需用户显式授权、每 change 上限 3 轮、自动落 state 备份、打印 `REENTRY` 审计行)+ 归档侧边界原文在该文件。
|
|
122
164
|
|
|
123
165
|
## Entry Check
|
|
124
166
|
|
|
@@ -20,19 +20,22 @@ description: "flow-kit INTEGRATION 阶段协议:集成验证 + UAT + 失败诊
|
|
|
20
20
|
3. **失败诊断**:root cause → fix-plan → 回到 execute 修复 → 重跑
|
|
21
21
|
- **自动重试 ≤ 3 轮**(R2.6),超限暂停等人工决策
|
|
22
22
|
|
|
23
|
-
### LESSONS 提名(archive
|
|
23
|
+
### LESSONS 提名(archive 前必跑 · 判据单一权威在本册)
|
|
24
24
|
|
|
25
|
-
扫描本次 change 的所有 `*-SUMMARY.md
|
|
25
|
+
扫描本次 change 的所有 `*-SUMMARY.md`(重点「决策与偏差」段)与遗留 `*-PROGRESS.md`(「已排除方案」段),按提名条件逐条筛选:
|
|
26
26
|
- 调试/试错耗时 > 30 分钟 → 提名
|
|
27
|
-
-
|
|
27
|
+
- 错因不限于本任务(其他任务也会撞上)→ 提名
|
|
28
28
|
- 6 个月内有合理概率被再次尝试 → 提名
|
|
29
|
+
- 其余一律不提名(避免污染 `.specs/LESSONS.md`)
|
|
29
30
|
|
|
30
|
-
|
|
31
|
+
提名动作:新条目编号 = 当前最大编号 + 1(续 `L-NNN`),插入 `## 条目区` 末尾(文件内升序,继续现有编号)——**禁止文件尾追加与乱序插入**;同时扫既有 active 条目,被本次结论取代 / 废弃的更新其状态。**不归档** `.specs/LESSONS.md`(项目级常驻,跨 change 累积)。
|
|
32
|
+
|
|
33
|
+
> 本段是提名判据的**单一权威**(本册同时是 verify 与 archive 两节点的 Required Skill,判据必然在上下文里);各节点册的同口径表述一律**以本册为准**——同一口径多处表达必分叉。
|
|
31
34
|
|
|
32
35
|
### 归档(archive 阶段)
|
|
33
36
|
|
|
34
37
|
1. `.specs/<change-id>/` → `.specs/archive/<YYYY-MM-DD>-<change-id>/`
|
|
35
|
-
2. `.specs/CHANGELOG.md`
|
|
38
|
+
2. `.specs/CHANGELOG.md` 顶部按日期倒序插入一行——**跟随项目既有格式**(非表格格式同样在顶部插入,不强制转表格;guard 的倒序检测只针对表格格式行)——完整协议见 `flow-comet-archive` 册
|
|
36
39
|
3. **不归档** `.specs/LESSONS.md`(项目级常驻)
|
|
37
40
|
4. DESIGN.md § 9 架构沉淀建议留待 A-evolve 批量同步
|
|
38
41
|
|
|
@@ -134,10 +134,14 @@ Evidence: `intake-summary` (required)
|
|
|
134
134
|
|
|
135
135
|
## Evidence Record
|
|
136
136
|
|
|
137
|
+
Record the node after the artifacts exist and before running the exit (the exit validates the evidence is present). Ask the engine for this node's commands — the printed `record` command carries the platform-correct script path, so there is no copy here to drift:
|
|
138
|
+
|
|
137
139
|
```bash
|
|
138
|
-
node .claude/skills/flow-comet/scripts/workflow-state.mjs
|
|
140
|
+
node .claude/skills/flow-comet/scripts/workflow-state.mjs explain open
|
|
139
141
|
```
|
|
140
142
|
|
|
143
|
+
A good `summary` names what was produced, for example `CHANGE.md + REQUIREMENT.md generated, user confirmed`.
|
|
144
|
+
|
|
141
145
|
## Guardrails
|
|
142
146
|
|
|
143
147
|
| Guardrail ID | Label | Validation Type |
|
|
@@ -17,7 +17,7 @@ Responsibility: 拆原子任务(XML 格式)+ 波次划分。生成 TASK.md
|
|
|
17
17
|
|
|
18
18
|
| 文件 | guard 强制段(缺失 = BLOCKED) | 其余模板段(模板要求,guard 不拦) |
|
|
19
19
|
|------|-------------------------------|-----------------------------------|
|
|
20
|
-
| TASK.md | 至少一个 `<task>` 块 + 每个任务含 `<verify>` 字段
|
|
20
|
+
| TASK.md | 至少一个 `<task>` 块 + 每个任务含 `<verify>` 字段 + 新格式任务的 7 字段在场(集合见本册 `SKILL.md`「必填段清单」表行;单一权威 = 技能脚本的 `lib/task-graph.mjs` 导出的 `TASK7_REQUIRED` 常量,本文不复述集合) | 任务规模 / 粒度 / 字段内容质量(模板要求,guard 不拦)——**填得好不好**由 review 把关;`id` 是 `<task>` 元素的属性(不是字段:`<task id="T01" parallel="true" status="pending">`) |
|
|
21
21
|
|
|
22
22
|
guard 校验见 workflow-guard.mjs NODE_TRANSITION_GATES / W1-B;「填得好不好」由 review 把关。
|
|
23
23
|
|
|
@@ -19,9 +19,9 @@ Responsibility: 拆原子任务(XML 格式)+ 波次划分。生成 TASK.md
|
|
|
19
19
|
|
|
20
20
|
| 文件 | guard 强制段(缺失 = BLOCKED) | 其余模板段(模板要求,guard 不拦) |
|
|
21
21
|
|------|-------------------------------|-----------------------------------|
|
|
22
|
-
| TASK.md | 至少一个 `<task>` 块 + 每个任务含 `<verify>` 字段
|
|
22
|
+
| TASK.md | 至少一个 `<task>` 块 + 每个任务含 `<verify>` 字段 + 新格式任务的 7 字段在场(`name` / `read_files` / `write_files` / `action` / `verify` / `done` / `depends_on`) | 任务规模 / 粒度 / 字段内容质量(模板要求,guard 不拦)——**填得好不好**由 review 把关 |
|
|
23
23
|
|
|
24
|
-
guard 校验见 workflow-guard.mjs NODE_TRANSITION_GATES / W1-B
|
|
24
|
+
guard 校验见 workflow-guard.mjs NODE_TRANSITION_GATES / W1-B:任务块结构、每任务 `<verify>`、**新格式任务的 7 字段在场**都由 guard 拦(新 change 缺任一 = 出口 BLOCKED;旧格式模板 / 旧 change 渐进 WARN);「填得好不好」——字段内容质量与任务粒度——由 review 把关。
|
|
25
25
|
|
|
26
26
|
> **模板权威**:本节点产出工件的段形唯一权威 = `flow-kit/templates/**`;`.specs/archive/**` 是历史证据、**不是模板来源**——不得以「上一轮就是这么写的」对齐段形。
|
|
27
27
|
|
|
@@ -31,7 +31,7 @@ guard 校验见 workflow-guard.mjs NODE_TRANSITION_GATES / W1-B;「填得好
|
|
|
31
31
|
|
|
32
32
|
**约束本体**:并行任务按依赖关系组织——每个并行任务显式声明 `depends_on`,合法性只取决于依赖图本身:`depends_on` 无环且引用的任务都存在,规划即合法。全并行、全串行、串→并、并→串四种基本形态与任意混排序列(如 `S→P→S`、`P→S→P`)一律放行——引擎按依赖拓扑自动分趟(每趟委托全部依赖已满足的并行任务,趟间回串行消化),混排序列由多趟路由按依赖拓扑自动分趟消化,并行任务的先后位置不受任何限制。
|
|
33
33
|
|
|
34
|
-
|
|
34
|
+
**硬性拦截(规划出口 BLOCKED,附恢复指引)**:任务块结构(至少一个 `<task>` 块)/ 每任务 `<verify>` 字段 / 新格式任务的 7 字段在场(集合见上表;新 change 缺任一即 BLOCKED,旧格式模板 / 旧 change 渐进 WARN)/ 任务图依赖环 / 缺失依赖(`depends_on` 引用不存在的任务 id)/ 并行写写冲突(并行任务 `write_files` 重叠)——任一项不成立即在规划出口被 BLOCKED(读写重叠仅 WARN),按提示修正后重新 exit 即可通过。任务间依赖不得成环(如 A→B→A),也不得构成不可满足的依赖链。
|
|
35
35
|
|
|
36
36
|
**警示**:落笔时先画依赖方向再标 [P],避免出口返工。
|
|
37
37
|
|
|
@@ -42,6 +42,7 @@ guard 校验见 workflow-guard.mjs NODE_TRANSITION_GATES / W1-B;「填得好
|
|
|
42
42
|
- **① 同一文件 ⇒ 同一任务**:一个文件只能有一个任务 owner;必须拆分时,在波次划分中显式排序并写明拆分理由与依赖方向,不得把同一文件的两处改动拆成无依赖的两个任务。
|
|
43
43
|
- **② [P] 只给本波确有并发同伴的任务**:`parallel="true"` 仅适用于同波确有其他可并行同伴、且 write_files 互不重叠的任务;孤立任务一律串行——「互不冲突」只是必要条件,不等于应标 `[P]`。
|
|
44
44
|
- **③ [P] × direct 模式**:`[P]` 任务只在 `subagent-execute` 节点委托消化;direct 模式只放行**串行任务**的主代理直写,`parallel="true"` 任务在 direct 下仍必须委托——direct 不是并行任务的逃生口。共享工作区下以 `write_files` 互斥 + 提交时点(提交前 diff 边界)作为并行子代理的相互隔离纪律。
|
|
45
|
+
- **④ 四属性可满足(并行安全的契约对象)**:标 `[P]` 前确认**并行安全四属性**(① 写权限 · ② 提交隔离 · ③ 验证隔离 · ④ 集成纪律)都能满足——worktree 只是「① 写权限」的实现之一,**不是** `[P]` 的前提。四属性的**含义与三平台通道**以入口册「并行委派契约(四属性)· 三平台通道」为单一来源,本节只点名不复述(同一口径两处表达必分叉)。
|
|
45
46
|
|
|
46
47
|
**上游语义显式覆盖**:flow-kit 上游(`flow-kit/prompts/3-task.md` 等 vendored 只读文件)的宽松语义——「无冲突即可标 [P]」「同层即同波并行」——以本节为准(显式覆盖;上游只读,不做修改)。
|
|
47
48
|
|
|
@@ -69,12 +70,11 @@ This node decomposes the technical design into atomic, executable tasks with cle
|
|
|
69
70
|
|
|
70
71
|
3. **Decompose by file conflict (vertical slices)**: Split tasks by file conflict, NOT by horizontal layers. Each task should be a vertical slice (one feature through model/API/UI) not a horizontal layer (all models first, then all APIs). Target: 2-10 minutes per task in fresh context. Do not split one file across tasks; if unavoidable, declare explicit order and reason.
|
|
71
72
|
|
|
72
|
-
4. **Mark parallel tasks with [P]**: only tasks with a genuine concurrent companion in the same wave and non-overlapping write_files get `parallel="true"`; isolated tasks are serial; under direct mode `[P]` tasks are still delegated at subagent-execute.
|
|
73
|
+
4. **Mark parallel tasks with [P]**: only tasks with a genuine concurrent companion in the same wave and non-overlapping write_files get `parallel="true"`; isolated tasks are serial; under direct mode `[P]` tasks are still delegated at subagent-execute. Each `[P]` task must also satisfy the four parallel-safety properties (write permission / commit isolation / verification isolation / integration discipline) — the contract object, with worktree as but one implementation of write permission and never a precondition; the entry SKILL's contract section is the single source for the per-platform channel facts.
|
|
73
74
|
|
|
74
75
|
5. **Declare depends_on**: Each task explicitly declares which tasks it depends on.
|
|
75
76
|
|
|
76
|
-
6. **Populate 7 required fields per task
|
|
77
|
-
- `id`: Format T01, T02, T02-1 etc. Continuous numbering.
|
|
77
|
+
6. **Populate 7 required fields per task** — `name` / `read_files` / `write_files` / `action` / `verify` / `done` / `depends_on` (the exact set the plan exit gate enforces). `id` is **not** one of the seven fields: it is an attribute of the `<task>` element (`<task id="T01" parallel="true" status="pending">`) — format T01, T02, T02-1 etc., continuous numbering. `depends_on` is a field, and its element must be present (write an empty element when the task has no dependency):
|
|
78
78
|
- `name`: One sentence.
|
|
79
79
|
- `read_files`: Files the task is allowed to read. Must include reuse targets from DESIGN 0.5. Supports glob patterns.
|
|
80
80
|
- `write_files`: Files the task is allowed to create/modify/delete. Must NOT include forbidden modules from DESIGN 0.5. Strictly controlled.
|
|
@@ -97,7 +97,7 @@ The full task decomposition protocol, XML template, and constraints are in:
|
|
|
97
97
|
|
|
98
98
|
This node is truly done when:
|
|
99
99
|
- `.specs/<change-id>/TASK.md` exists in XML format.
|
|
100
|
-
- At least one `<task>` block exists; every task carries a `<verify>` field
|
|
100
|
+
- At least one `<task>` block exists; every task carries a `<verify>` field, and the 7-field set `name` / `read_files` / `write_files` / `action` / `verify` / `done` / `depends_on` is present (`id` is an **attribute** of the `<task>` element, not a field) — field **presence** is enforced by the guard (missing any field on a new-format task in a new change = exit BLOCKED; old-format templates / old changes degrade to WARN), while **field content quality** is judged by review.
|
|
101
101
|
- Every `verify` field is an executable command (not a description).
|
|
102
102
|
- Every `write_files` is strictly within DESIGN.md touched + new modules range (not in forbidden list).
|
|
103
103
|
- Every `[P]` mark has a genuine concurrent companion in its wave with non-overlapping `write_files`; isolated tasks are serial (a fully serial plan is valid when no genuine companion exists).
|
|
@@ -160,7 +160,7 @@ node .claude/skills/flow-comet/scripts/workflow-state.mjs record plan '{"summary
|
|
|
160
160
|
| Guardrail ID | Label | Validation Type |
|
|
161
161
|
|--------------|-------|-----------------|
|
|
162
162
|
| `plan-artifacts` | TASK.md exists with XML tasks | artifact-exists |
|
|
163
|
-
| `task-fields-complete` | All tasks have 7 required fields |
|
|
163
|
+
| `task-fields-complete` | All tasks have 7 required fields | 结构在场(新格式任务缺任一字段 = 出口 BLOCKED;旧格式模板 / 旧 change 渐进 WARN)——**字段内容质量**由 review 把关 |
|
|
164
164
|
| `write-files-safe` | No write_files in DESIGN forbidden list | 执行纪律(review 把关),guard 不校验 |
|
|
165
165
|
| `has-parallel` | At least 1 [P] task (if applicable) | 执行纪律(review 把关),guard 不校验 |
|
|
166
166
|
|
|
@@ -128,18 +128,15 @@ This node is truly done when:
|
|
|
128
128
|
|
|
129
129
|
## 修复回路状态机路径
|
|
130
130
|
|
|
131
|
-
review /
|
|
132
|
-
|
|
133
|
-
1. **追加 Fix
|
|
134
|
-
2. **受控归位 execute
|
|
135
|
-
3.
|
|
136
|
-
4.
|
|
137
|
-
|
|
138
|
-
|
|
139
|
-
|
|
140
|
-
6. **禁止绕过**:驻留源节点不归位、顺手改完后直接跑源节点 exit 收场会被 BLOCKED(存在未归位/未跑出口的修复回路),必须按上述路径恢复;不得用跳过归位或出口门禁的手段(含手动改写 `.flow-comet/flow-comet-state.json`)替代本路径。
|
|
141
|
-
|
|
142
|
-
**由受控重入打开的场景(archive 源)**:缺陷在归档后才暴露、且归档移动尚未发生时,可先由用户显式授权把工作归属退回 `execute` / `subagent-execute` / `review` / `verify` 之一,再按本节路径回到 execute 生命周期完成修复。重入命令:`node .claude/skills/flow-comet/scripts/workflow-state.mjs reenter <target> --authorized-by <source> --reason <text> [--continue-round <n>]`——每次调用都需要用户显式授权,每 change 上限 3 轮(达上限后凭显式续轮授权 `--continue-round <n>`(n ≥ 已用轮次 + 1)可继续并计入下一轮);重入前自动落 state 备份快照(`.specs/<change-id>/.reentry-backups/`);成功打印 `REENTRY: archive → <target>(授权源 <source>;第 n/3 轮;备份 <file>)` 与 `REASON: <text>` 行(续轮审计行为 `第 n 轮(显式授权续轮,上限 3)`),与 Fix 回炉的 `FIX-BATCH` 行、正常多趟收尾的 `RETURN` 行三态可区分。归档移动已发生或 change 已 `completed` 时重入 BLOCKED,须走人工处置或新 change,不得静默跳过。重入只改工作归属,不写任何闭合标记,也不跳过目标节点入口 / 出口与源节点出口门禁;重复调用同一目标为空操作(输出 `REENTRY: 空操作——…`,不备份、不计数、不改写 state)。
|
|
131
|
+
review 发现 Critical / Major 后的修复必须回到 `execute` 节点生命周期内完成——**禁止驻留源节点「顺手修完」**(会被 BLOCKED)。要点:
|
|
132
|
+
|
|
133
|
+
1. **追加 Fix 任务**:把修复任务(完整任务字段)追加到 `.specs/<change-id>/TASK.md` 的 `## Fix 任务` 段内,**禁止文件尾追加**;任务集修订须在 `entry` 之前完成。
|
|
134
|
+
2. **受控归位 execute**:跑 `workflow-state next` 或 `workflow-guard entry execute` 触发受控归位(审计行 `FIX-BATCH: 归位`;`next` 同时输出 `NODE: execute`);用 `status` 确认 `stateCurrentNode` 已是 `execute` 再开工,未归位不得硬开工。
|
|
135
|
+
3. **跑完 execute 四类出口**:`record execute` → `exit execute --apply`——全任务 done / 逐任务 SUMMARY 完备 / 6 维自查 + 自检方法声明 / 任务集签名一致,任一缺失即 BLOCKED;通过后引擎把当前节点推回 review。
|
|
136
|
+
4. **回源节点跑出口**:回到源节点后跑该节点出口门禁(`entry <源节点>` → `exit <源节点> --apply`),通过后继续 review → verify 的正常路由,必要时进入下一轮 Fix 闭环。
|
|
137
|
+
5. **禁止绕过**:驻留源节点不归位、顺手改完后直接跑源节点 exit 收场会被 BLOCKED;不得用跳过归位或出口门禁的手段(含手动改写 `.flow-comet/flow-comet-state.json`)替代本路径。
|
|
138
|
+
|
|
139
|
+
**何时读完整规格**:要核对完整判据——Fix 任务与任务集签名的时序、受控归位的完整判定条件、`FIX-BATCH` / `RETURN` 审计行三态语义与回源节点的回程豁免、绕过的失败面与恢复指引——读 `../flow-comet/reference/fix-loop.md`(**当你 review 发现缺陷、要开修复回路把工作退回 execute 生命周期时读它**)。
|
|
143
140
|
|
|
144
141
|
## Entry Check
|
|
145
142
|
|