flow-comet 1.6.4 → 1.7.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.
- package/.flow-comet/skills/flow-comet/INSTALLED_VERSION +1 -1
- package/.flow-comet/skills/flow-comet/SKILL.md +36 -6
- package/.flow-comet/skills/flow-comet/reference/artifact-template-overlay.md +154 -0
- package/.flow-comet/skills/flow-comet/reference/artifact-templates.json +387 -0
- package/.flow-comet/skills/flow-comet/reference/commit-discipline.md +1 -1
- package/.flow-comet/skills/flow-comet/reference/entry-detail.md +29 -4
- package/.flow-comet/skills/flow-comet/reference/workflow-protocol.json +22 -0
- package/.flow-comet/skills/flow-comet/scripts/context-init.mjs +26 -23
- package/.flow-comet/skills/flow-comet/scripts/evolve.mjs +174 -0
- package/.flow-comet/skills/flow-comet/scripts/guard-self-test.mjs +17 -95
- package/.flow-comet/skills/flow-comet/scripts/health.mjs +28 -4
- package/.flow-comet/skills/flow-comet/scripts/items/a.mjs +136 -19
- package/.flow-comet/skills/flow-comet/scripts/items/b.mjs +54 -18
- package/.flow-comet/skills/flow-comet/scripts/items/c.mjs +6 -6
- package/.flow-comet/skills/flow-comet/scripts/items/e.mjs +52 -10
- package/.flow-comet/skills/flow-comet/scripts/items/h.mjs +25 -10
- package/.flow-comet/skills/flow-comet/scripts/items/l.mjs +4 -2
- package/.flow-comet/skills/flow-comet/scripts/items/m.mjs +21 -13
- package/.flow-comet/skills/flow-comet/scripts/items/n.mjs +163 -0
- package/.flow-comet/skills/flow-comet/scripts/lib/ac-coverage.mjs +317 -0
- package/.flow-comet/skills/flow-comet/scripts/lib/guard-artifact-skeleton.mjs +448 -0
- package/.flow-comet/skills/flow-comet/scripts/lib/guard-evidence-gates.mjs +396 -27
- package/.flow-comet/skills/flow-comet/scripts/lib/guard-gates.mjs +1035 -172
- package/.flow-comet/skills/flow-comet/scripts/lib/guard-routing.mjs +129 -98
- package/.flow-comet/skills/flow-comet/scripts/lib/guard-state-io.mjs +8 -6
- package/.flow-comet/skills/flow-comet/scripts/lib/guard-template-fidelity.mjs +797 -232
- package/.flow-comet/skills/flow-comet/scripts/lib/guard-uidesign.mjs +91 -22
- package/.flow-comet/skills/flow-comet/scripts/lib/lessons-hits.mjs +160 -0
- package/.flow-comet/skills/flow-comet/scripts/lib/run-root.mjs +21 -0
- package/.flow-comet/skills/flow-comet/scripts/lib/section-body.mjs +92 -0
- package/.flow-comet/skills/flow-comet/scripts/lib/state-commands-admin.mjs +69 -13
- package/.flow-comet/skills/flow-comet/scripts/lib/state-commands-flow.mjs +454 -135
- package/.flow-comet/skills/flow-comet/scripts/lib/state-commands-recovery.mjs +66 -0
- package/.flow-comet/skills/flow-comet/scripts/lib/state-explain.mjs +109 -13
- package/.flow-comet/skills/flow-comet/scripts/lib/state-io.mjs +55 -2
- package/.flow-comet/skills/flow-comet/scripts/lib/state-skillmarkers.mjs +149 -34
- package/.flow-comet/skills/flow-comet/scripts/lib/system-fixtures.mjs +79 -9
- package/.flow-comet/skills/flow-comet/scripts/lib/task-graph.mjs +84 -31
- package/.flow-comet/skills/flow-comet/scripts/lib/test-fixtures.mjs +78 -8
- package/.flow-comet/skills/flow-comet/scripts/lib/test-helpers.mjs +60 -3
- package/.flow-comet/skills/flow-comet/scripts/lib/text-anchor-checks.mjs +167 -3
- package/.flow-comet/skills/flow-comet/scripts/lib/wave-projection.mjs +341 -0
- package/.flow-comet/skills/flow-comet/scripts/protocol-utils.mjs +287 -0
- package/.flow-comet/skills/flow-comet/scripts/scenarios/a.mjs +1454 -16
- package/.flow-comet/skills/flow-comet/scripts/scenarios/b.mjs +1202 -8
- package/.flow-comet/skills/flow-comet/scripts/scenarios/c.mjs +1205 -77
- package/.flow-comet/skills/flow-comet/scripts/scenarios/d.mjs +753 -5
- package/.flow-comet/skills/flow-comet/scripts/scenarios/e.mjs +52 -11
- package/.flow-comet/skills/flow-comet/scripts/scenarios/f.mjs +582 -3
- package/.flow-comet/skills/flow-comet/scripts/scenarios/g.mjs +9 -1
- package/.flow-comet/skills/flow-comet/scripts/scenarios/i.mjs +5 -0
- package/.flow-comet/skills/flow-comet/scripts/scenarios/j.mjs +22 -6
- package/.flow-comet/skills/flow-comet/scripts/scenarios/k.mjs +2 -0
- package/.flow-comet/skills/flow-comet/scripts/scenarios/l.mjs +18 -5
- package/.flow-comet/skills/flow-comet/scripts/scenarios/n.mjs +4100 -0
- package/.flow-comet/skills/flow-comet/scripts/state-schema.mjs +135 -0
- package/.flow-comet/skills/flow-comet/scripts/system-test.mjs +6 -5
- package/.flow-comet/skills/flow-comet/scripts/workflow-guard.mjs +203 -4
- package/.flow-comet/skills/flow-comet/scripts/workflow-handoff.mjs +312 -63
- package/.flow-comet/skills/flow-comet/scripts/workflow-state.mjs +5 -2
- package/.flow-comet/skills/flow-comet-archive/SKILL.md +6 -2
- package/.flow-comet/skills/flow-comet-change/SKILL.md +6 -2
- package/.flow-comet/skills/flow-comet-design/GUIDANCE.md +13 -3
- package/.flow-comet/skills/flow-comet-design/SKILL.md +15 -8
- package/.flow-comet/skills/flow-comet-dev/SKILL.md +1 -1
- package/.flow-comet/skills/flow-comet-evolve/SKILL.md +1 -0
- package/.flow-comet/skills/flow-comet-execute/SKILL.md +42 -15
- package/.flow-comet/skills/flow-comet-health/SKILL.md +1 -1
- package/.flow-comet/skills/flow-comet-integration/SKILL.md +1 -1
- package/.flow-comet/skills/flow-comet-open/GUIDANCE.md +14 -4
- package/.flow-comet/skills/flow-comet-open/SKILL.md +11 -9
- package/.flow-comet/skills/flow-comet-plan/GUIDANCE.md +13 -3
- package/.flow-comet/skills/flow-comet-plan/SKILL.md +21 -10
- package/.flow-comet/skills/flow-comet-requirement/SKILL.md +1 -1
- package/.flow-comet/skills/flow-comet-review/SKILL.md +33 -18
- package/.flow-comet/skills/flow-comet-subagent-execute/GUIDANCE.md +13 -3
- package/.flow-comet/skills/flow-comet-subagent-execute/SKILL.md +44 -16
- package/.flow-comet/skills/flow-comet-task/SKILL.md +3 -2
- package/.flow-comet/skills/flow-comet-test/SKILL.md +6 -2
- package/.flow-comet/skills/flow-comet-ui-design/SKILL.md +2 -2
- package/.flow-comet/skills/flow-comet-verify/SKILL.md +12 -8
- package/README.md +3 -3
- package/package.json +1 -1
- package/scripts/dsh-bridge.mjs +2 -2
- package/scripts/lib/installer-flowkit.mjs +43 -3
|
@@ -1,15 +1,30 @@
|
|
|
1
|
-
// 证据与产物门禁(守卫模块):直显授权约束、在飞委托、SUMMARY 必填段与自检方法、
|
|
2
|
-
//
|
|
1
|
+
// 证据与产物门禁(守卫模块):直显授权约束、在飞委托、SUMMARY 必填段与自检方法、LESSONS 扫描段
|
|
2
|
+
// 与命中核对、execute 出口、
|
|
3
|
+
// verify 出口(真实执行验证命令并记录失败计数)、AC 覆盖(verify 出口 BLOCK / review 出口汇总 WARN)、
|
|
4
|
+
// Return Contract、subagent-execute 摘要与多趟完成
|
|
3
5
|
// 判定、required-skill / schema / 产物 存在性门禁——即「完成声明必须有证据与产物」这一族判据。
|
|
4
6
|
//
|
|
5
7
|
// 分级沿用既有语义:新 change(init 标记)强制 BLOCKED + 恢复指引,旧 change 渐进 WARN 不阻断。
|
|
6
8
|
|
|
7
9
|
import { promises as fs } from 'fs';
|
|
8
10
|
import path from 'path';
|
|
9
|
-
import {
|
|
10
|
-
import {
|
|
11
|
+
import { fileURLToPath } from 'url';
|
|
12
|
+
import {
|
|
13
|
+
validateStateFields,
|
|
14
|
+
verifyFailuresFor,
|
|
15
|
+
setVerifyFailuresFor,
|
|
16
|
+
} from '../state-schema.mjs';
|
|
17
|
+
import { EXECUTE_FAMILY_NODE_IDS, analyzeDependencyGraph, normalizeHeading } from '../route-node.mjs';
|
|
11
18
|
import { taskOpeningAttrs, taskBlocks as extractTaskBlocks } from '../task-parsing.mjs';
|
|
12
|
-
|
|
19
|
+
// 声明面的事实与命令装配各归一处:协议面事实(该节点该声明哪些技能、没有必需技能时退到哪个名字)
|
|
20
|
+
// 取 protocol-utils;条件提示词(判前端时才是必读面)取 NODE_CONDITIONAL_PROMPTS;命令文本与
|
|
21
|
+
// 「全部 --prompt + 模板全清单」的拼装取 state-explain 的 declarationCommands——本模块不再各拼一半。
|
|
22
|
+
import {
|
|
23
|
+
NODE_CONDITIONAL_PROMPTS,
|
|
24
|
+
declarationSkillFallback,
|
|
25
|
+
guardedDeclarationSkills,
|
|
26
|
+
} from '../protocol-utils.mjs';
|
|
27
|
+
import { runRoot, packageRoot, fileExists, statePath, writeJson, protocolPath } from './guard-state-io.mjs';
|
|
13
28
|
import {
|
|
14
29
|
eligibleParallelBlocks,
|
|
15
30
|
inFlightHandoffRequests,
|
|
@@ -23,6 +38,31 @@ import {
|
|
|
23
38
|
verifySummaries,
|
|
24
39
|
} from './guard-routing.mjs';
|
|
25
40
|
import { applicabilityGatedBinding, frontendCriterion } from './guard-uidesign.mjs';
|
|
41
|
+
import { buildSkeleton, headingPattern, LESSONS_SCAN_SECTION } from './guard-artifact-skeleton.mjs';
|
|
42
|
+
// 段界(同级标题 / 围栏 / 分隔线 / 文末)取 lib/section-body.mjs 的唯一实现:LESSONS 扫描段此前自带一份
|
|
43
|
+
// 同名语义的按行扫描(只认反引号围栏),波浪号围栏里的 `## ` 会把它截断。
|
|
44
|
+
import { sectionBody } from './section-body.mjs';
|
|
45
|
+
// AC 覆盖判定(纯判定模块):verify 出口的 BLOCK / review 出口的汇总 WARN 共用同一份判定与报文,
|
|
46
|
+
// 分级只在下方门禁函数一处表达。
|
|
47
|
+
import {
|
|
48
|
+
acCoverageReportLines,
|
|
49
|
+
acCoverageReview,
|
|
50
|
+
acCoverageSummaryLine,
|
|
51
|
+
acCoverageUnjudgeableLines,
|
|
52
|
+
} from './ac-coverage.mjs';
|
|
53
|
+
// LESSONS 命中集(路径词元 × 条目关键词)的单一实现:与 handoff request 的开工前打印共用,执行者
|
|
54
|
+
// 看到的集合必须就是出口验收的集合。
|
|
55
|
+
import { lessonsEntries, lessonsHits, lessonsPathTokens, taskWriteFilesById } from './lessons-hits.mjs';
|
|
56
|
+
// 命令文本的唯一实现(平台化脚本根 + 整条路径加引号):运行期恢复指引与 explain 的 COMMAND 行
|
|
57
|
+
// 同源;本模块不再自拼路径(L-067:同一推导两处表达必然分叉)。
|
|
58
|
+
import { declarationCommand, declarationCommands, protocolContextArgs, scriptCommand } from './state-explain.mjs';
|
|
59
|
+
// 声明标记目录的路径规则(活动路径优先、归档兜底)归状态族的路径上下文模块:本模块只按守卫运行根
|
|
60
|
+
// 取用(guard → state-* 是允许的单向边),不在此另写一份扫描。
|
|
61
|
+
import { findSkillLoadsDir } from './state-io.mjs';
|
|
62
|
+
|
|
63
|
+
// 本模块位于 <技能包>/scripts/lib:脚本目录由自身位置推导一次——「自己在哪」与运行根是本模块提供
|
|
64
|
+
// 的两个事实,平台化与引号形态本身在 state-explain。
|
|
65
|
+
const scriptsDir = path.resolve(path.dirname(fileURLToPath(import.meta.url)), '..');
|
|
26
66
|
|
|
27
67
|
// directOverride 授权约束(direct 是用户决策点,不可自决——机制约束)——execute / subagent-execute
|
|
28
68
|
// 出口校验:executionMode=direct 且 directOverride=true(显式直显授权态)须存在授权审计记录
|
|
@@ -65,8 +105,112 @@ export function runInFlightHandoffGate({ node, state }) {
|
|
|
65
105
|
}
|
|
66
106
|
}
|
|
67
107
|
|
|
108
|
+
// ---------- LESSONS 扫描(R1.8 · AC-18:开工前扫描可核对)----------
|
|
109
|
+
//
|
|
110
|
+
// 两条判据:① 每份 *-SUMMARY.md 含 `## LESSONS 扫描` 增量段;② 按任务 write_files 的路径段与该
|
|
111
|
+
// 段内应回应的条目编号(关键词求交、取前 5)必须逐条出现在该段里。段名 / 必填 / 位置三件事都来自
|
|
112
|
+
// 登记表(reference/artifact-templates.json 的 SUMMARY.increments)——位置语义由模板保真门禁按同一
|
|
113
|
+
// 条目执行,本门禁只判「在场 + 命中回应」,不写第二份位置判据(L-067)。
|
|
114
|
+
//
|
|
115
|
+
// 命中集算法(路径词元 → 条目关键词求交、取前 5)与 handoff request 的开工前打印**共用同一实现**
|
|
116
|
+
// (lib/lessons-hits.mjs):执行者看到的集合必须就是出口验收的集合,两处各算一套必然分叉。
|
|
117
|
+
|
|
118
|
+
// 段名 / 必填来自登记表;登记表或模板缺席时退回段名常量并保持必填——扫描段由 AC-18 要求,不因模板
|
|
119
|
+
// 派生失败而免检(「模板缺失」只让模板派生判据跳过,不让扫描声明消失)。
|
|
120
|
+
async function lessonsScanRule() {
|
|
121
|
+
const skeleton = await buildSkeleton('summary');
|
|
122
|
+
const wanted = normalizeHeading(LESSONS_SCAN_SECTION);
|
|
123
|
+
const entry = (skeleton.increments ?? []).find((item) => item.norm === wanted);
|
|
124
|
+
if (entry && entry.kind === 'section') {
|
|
125
|
+
return {
|
|
126
|
+
name: entry.section,
|
|
127
|
+
required: entry.required,
|
|
128
|
+
pattern: entry.pattern ?? headingPattern(entry.section, 2),
|
|
129
|
+
registered: true,
|
|
130
|
+
};
|
|
131
|
+
}
|
|
132
|
+
return { name: LESSONS_SCAN_SECTION, required: true, pattern: headingPattern(LESSONS_SCAN_SECTION, 2), registered: false };
|
|
133
|
+
}
|
|
134
|
+
|
|
135
|
+
// write_files 原文(键 = 任务 id):块提取与开标签解析在 lib/lessons-hits.mjs 的同一实现里,本处
|
|
136
|
+
// 只负责读 TASK.md——出口与开工前打印共用同一个提取,两侧的写面输入不会分叉。
|
|
137
|
+
async function taskWriteFiles(changeDir) {
|
|
138
|
+
let text = '';
|
|
139
|
+
try {
|
|
140
|
+
text = await fs.readFile(path.join(changeDir, 'TASK.md'), 'utf8');
|
|
141
|
+
} catch {
|
|
142
|
+
return new Map();
|
|
143
|
+
}
|
|
144
|
+
return taskWriteFilesById(text);
|
|
145
|
+
}
|
|
146
|
+
|
|
147
|
+
// 编号在段内出现的判定:两侧非数字边界(L-501 不算命中 L-5012),大小写不敏感(执行者常写小写
|
|
148
|
+
// `l-501`)。转义集不含 `-`——字符类外的连字符本就是字面量,而在 `u` 标志下 `\-` 是非法转义
|
|
149
|
+
// (会抛 Invalid regular expression)。
|
|
150
|
+
function mentionsLessonsId(body, id) {
|
|
151
|
+
const escaped = id.replace(/[.*+?^${}()|[\]\\]/gu, '\\$&');
|
|
152
|
+
return new RegExp('(^|[^0-9])' + escaped + '(?![0-9])', 'iu').test(body);
|
|
153
|
+
}
|
|
154
|
+
|
|
155
|
+
// 每份 SUMMARY 的两条判据 → 问题描述数组(分级由调用方按 isNewChange 决定:新 change BLOCKED /
|
|
156
|
+
// 旧 change WARN——C10 无例外)。TASK.md 或 .specs/LESSONS.md 缺席时对应输入为空:段在场判据照常,
|
|
157
|
+
// 命中计算自然为空集(无条目可命中)。
|
|
158
|
+
async function lessonsScanProblems(changeDir, summaryFiles) {
|
|
159
|
+
if (summaryFiles.length === 0) return [];
|
|
160
|
+
const rule = await lessonsScanRule();
|
|
161
|
+
const lessonsText = await fs.readFile(path.join(runRoot, '.specs', 'LESSONS.md'), 'utf8').catch(() => '');
|
|
162
|
+
const entries = lessonsEntries(lessonsText);
|
|
163
|
+
const writeFilesById = await taskWriteFiles(changeDir);
|
|
164
|
+
const problems = [];
|
|
165
|
+
for (const file of summaryFiles) {
|
|
166
|
+
let content = '';
|
|
167
|
+
try {
|
|
168
|
+
content = await fs.readFile(path.join(changeDir, file), 'utf8');
|
|
169
|
+
} catch (error) {
|
|
170
|
+
// 读失败不得静默跳过(L-079:依赖解析失败必须可见)——判据无法求值本身就是问题,按同一分级上报。
|
|
171
|
+
problems.push(file + ' 无法读取(' + String(error?.message ?? error) + ')——LESSONS 扫描判据无法求值');
|
|
172
|
+
continue;
|
|
173
|
+
}
|
|
174
|
+
// 段界由 lib/section-body.mjs 单点决定(围栏内的 `## ` / `---` 是正文示例,不结束段体)。
|
|
175
|
+
// 段缺席 → null(缺声明),与「段在场但正文为空」区分(后者由正文判据另行处理)。
|
|
176
|
+
const body = sectionBody(content, rule.pattern, { level: 2, endOnSeparator: true });
|
|
177
|
+
if (body === null) {
|
|
178
|
+
if (rule.required) {
|
|
179
|
+
problems.push(file + ' 缺 ## ' + rule.name + ' 段(SUMMARY 增量段须声明扫描结果与命中回应'
|
|
180
|
+
+ (rule.registered ? ';位置按登记表登记:自检方法之后' : '') + ')');
|
|
181
|
+
}
|
|
182
|
+
continue;
|
|
183
|
+
}
|
|
184
|
+
const taskId = file.replace(/-SUMMARY\.md$/iu, '');
|
|
185
|
+
const hits = lessonsHits(lessonsPathTokens(writeFilesById.get(taskId) ?? ''), entries);
|
|
186
|
+
const unanswered = hits.filter((hit) => !mentionsLessonsId(body, hit.id));
|
|
187
|
+
if (unanswered.length > 0) {
|
|
188
|
+
problems.push(file + ' 的 ## ' + rule.name + ' 段未回应命中条目 '
|
|
189
|
+
+ unanswered.map((hit) => hit.id + '(关键词: ' + hit.shared.join('、') + ')').join('、')
|
|
190
|
+
+ '——R1.8 要求逐条声明「仍适用 / 差异是 X」');
|
|
191
|
+
}
|
|
192
|
+
}
|
|
193
|
+
return problems;
|
|
194
|
+
}
|
|
195
|
+
|
|
196
|
+
// SUMMARY 两段的**段头识别**(正则只表达「如何识别段」,段界交给 lib/section-body.mjs 单源):
|
|
197
|
+
// · 「6 维自查」允许模板标题的括注后缀(`## 6 维自查(生产代码改动必填 …)`);
|
|
198
|
+
// · 「自检方法」允许括号后缀——括号是说明不是段名,执行者常按模板标题原样书写。
|
|
199
|
+
// 行锚定(`^`)是必须的:段内正文里引用段名不是段头。
|
|
200
|
+
const SIX_DIM_HEADING_PATTERN = /^##\s*6\s*维自查/u;
|
|
201
|
+
const SELF_CHECK_METHOD_HEADING_PATTERN = /^##\s*自检方法(?:[((][^))\n]*[))])?\s*$/u;
|
|
202
|
+
|
|
203
|
+
// 段体:围栏代码块里的 `## ` / `---` 是正文示例,不结束段体;围栏外的同级标题与分隔线照常结束。
|
|
204
|
+
function summarySixDimBody(content) {
|
|
205
|
+
return sectionBody(content, SIX_DIM_HEADING_PATTERN, { level: 2, endOnSeparator: true });
|
|
206
|
+
}
|
|
207
|
+
|
|
208
|
+
function summarySelfCheckMethodBody(content) {
|
|
209
|
+
return sectionBody(content, SELF_CHECK_METHOD_HEADING_PATTERN, { level: 2, endOnSeparator: true });
|
|
210
|
+
}
|
|
211
|
+
|
|
68
212
|
// execute / subagent-execute 出口校验每份 SUMMARY 含三个必填段 + 6 维自查非空 + 自检方法声明
|
|
69
|
-
// (brooks-review / cache-brooks / builtin-quickcheck
|
|
213
|
+
// (brooks-review / cache-brooks / builtin-quickcheck 三级降级路径)+ LESSONS 扫描段与命中核对
|
|
70
214
|
export async function runSummarySectionsGate({ node, state }) {
|
|
71
215
|
if (!EXECUTE_FAMILY_NODE_IDS.has(node.id)) return;
|
|
72
216
|
const changeDir = path.join(runRoot, '.specs', state.activeChange ?? '');
|
|
@@ -76,14 +220,13 @@ export async function runSummarySectionsGate({ node, state }) {
|
|
|
76
220
|
for (const f of summaryFiles) {
|
|
77
221
|
try {
|
|
78
222
|
const content = await fs.readFile(path.join(changeDir, f), 'utf8');
|
|
79
|
-
//
|
|
80
|
-
//
|
|
81
|
-
|
|
82
|
-
const sixDim = content.match(/##\s*6\s*维自查[\s\S]*?(?=\n##\s|\n---|(?![\s\S]))/i);
|
|
223
|
+
// 段界由 lib/section-body.mjs 单点决定(围栏代码块里的 `## ` 是正文示例,不结束段体;围栏外的
|
|
224
|
+
// 同级标题与分隔线照常结束;`###` 级子标题如 "### 🟢 R1" 属段内内容——级别由 level 表达)。
|
|
225
|
+
const sixDimBody = summarySixDimBody(content);
|
|
83
226
|
// 6 维自查段非空——去掉所有标题行后剩余实质内容 ≥ 10 字符。按行过滤标题(/^\s*#/)比正则
|
|
84
227
|
// 替换稳健:任何标题格式(emoji 🟢/中英文/数字)都不计入内容
|
|
85
|
-
const dimBody =
|
|
86
|
-
if (
|
|
228
|
+
const dimBody = sixDimBody === null ? '' : sixDimBody.split('\n').filter(l => !/^\s*#/.test(l)).join('').trim();
|
|
229
|
+
if (sixDimBody !== null && dimBody.length < 10) {
|
|
87
230
|
violations.push(f + ' 的 6 维自查段无实质内容');
|
|
88
231
|
}
|
|
89
232
|
// 生产代码任务必填 ## 自检方法,声明 brooks-review 或 builtin-quickcheck。格式兼容:方法名行
|
|
@@ -92,11 +235,10 @@ export async function runSummarySectionsGate({ node, state }) {
|
|
|
92
235
|
// 段名部分,执行者常按模板标题原样书写导致旧正则不匹配落入"旧格式 WARN";括号后缀与段名等价)。
|
|
93
236
|
// 分隔符用 .?(任意字符)而非 \.?(字面点):canonical 名 "brooks-review"/"builtin-quickcheck"
|
|
94
237
|
// 是连字符,与既有 /brooks.?review/ 约定一致。真实项目端到端验证实证:方法名可能在段内后续行
|
|
95
|
-
//
|
|
96
|
-
|
|
97
|
-
const
|
|
98
|
-
|
|
99
|
-
const method = methodSection ? /brooks.?review|cache.?brooks|builtin.?quickcheck/i.exec(methodSection) : null;
|
|
238
|
+
// (子代理列表写法)——段内全文搜索而非仅第一行。段界同样由单源决定(围栏内的示例标题不截断)
|
|
239
|
+
const methodSection = summarySelfCheckMethodBody(content);
|
|
240
|
+
const method = methodSection === null ? null
|
|
241
|
+
: /brooks.?review|cache.?brooks|builtin.?quickcheck/i.exec(methodSection);
|
|
100
242
|
if (!method) {
|
|
101
243
|
// 过渡规则:旧格式 SUMMARY 无 ## 自检方法 段——若全文已声明 brooks-review/cache-brooks/
|
|
102
244
|
// builtin(旧模板行为),WARN 兼容不 BLOCKED;无任何自检声明才 BLOCKED
|
|
@@ -127,7 +269,7 @@ export async function runSummarySectionsGate({ node, state }) {
|
|
|
127
269
|
console.error('BROOKS-LINT WARN: ' + f + ' 使用 builtin-quickcheck 但未声明缓存尝试证据(应先 Read 插件缓存协议文件手动执行完整 brooks 流程)');
|
|
128
270
|
}
|
|
129
271
|
}
|
|
130
|
-
if (
|
|
272
|
+
if (sixDimBody !== null && !/brooks.?review|cache.?brooks/i.test(sixDimBody)) {
|
|
131
273
|
if (isNewChange(state)) {
|
|
132
274
|
console.error('BLOCKED: SUMMARY 的 6 维自查未声明使用 /brooks-review(新 change 强制声明自检方法);恢复: 在 6 维自查段声明 /brooks-review 或理由');
|
|
133
275
|
process.exit(1);
|
|
@@ -136,8 +278,23 @@ export async function runSummarySectionsGate({ node, state }) {
|
|
|
136
278
|
}
|
|
137
279
|
} catch {}
|
|
138
280
|
}
|
|
281
|
+
// LESSONS 扫描(AC-18):每份 SUMMARY 的扫描段在场 + 命中条目逐条回应。分级沿用既有语义——
|
|
282
|
+
// 新 change BLOCKED / 旧 change WARN(C10 无例外)。
|
|
283
|
+
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
|
+
}
|
|
139
293
|
if (violations.length > 0) {
|
|
140
294
|
console.error('BLOCKED: SUMMARY 关键段校验失败: ' + violations.join('; '));
|
|
295
|
+
if (lessonsProblems.length > 0 && isNewChange(state)) {
|
|
296
|
+
console.error('恢复: 按 flow-kit/templates/SUMMARY.md 在 ## 自检方法 之后补 ## LESSONS 扫描 段,并逐条写出命中条目编号与差异声明(无命中写「无 active 条目命中」);命中来源 = TASK.md 该任务 write_files 的路径段 × .specs/LESSONS.md 条目的关键词行');
|
|
297
|
+
}
|
|
141
298
|
process.exit(1);
|
|
142
299
|
}
|
|
143
300
|
}
|
|
@@ -257,6 +414,50 @@ export async function runExecuteExitGate({ protocol, node, state, emptyExitAppro
|
|
|
257
414
|
return { exempt };
|
|
258
415
|
}
|
|
259
416
|
|
|
417
|
+
// AC 覆盖出口校验(verify 出口 BLOCKED / review 出口只汇总 WARN)——判据(纯判定)在
|
|
418
|
+
// lib/ac-coverage.mjs,本处只负责分级与打印:同一份判定两处消费,分支纪律因此只有一处表达。
|
|
419
|
+
// · 判不了的两支按成因分开(与波次判据同口径,见 ac-coverage 文件头):
|
|
420
|
+
// ① **模板缺席**(段名无从派生)→ verify 出口打印「未校验(…)」且**不改变退出码**(判据没有
|
|
421
|
+
// 可判对象;未验证既不冒充通过也不冒充失败)。这是本出口唯一还会放行的「判不了」;
|
|
422
|
+
// ② **工件内容不可判**——**change 自己的载体文件被删**(REQUIREMENT.md / TEST.md 不在)与承载段 /
|
|
423
|
+
// 清单读不出(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 渐进。
|
|
428
|
+
// · review 出口:一条汇总 WARN(列缺失编号),不阻断、不影响退出码——review 出口今天不要求
|
|
429
|
+
// TEST.md,权威判定在 verify 出口;两支「判不了」都不打印(不制造噪音)。
|
|
430
|
+
// 归档 change 与 verify 出口的既有豁免同源(历史归档不重判)。
|
|
431
|
+
export async function runAcCoverageGate({ node, state }) {
|
|
432
|
+
if (node.id !== 'verify' && node.id !== 'review') return;
|
|
433
|
+
if (!state.activeChange) return;
|
|
434
|
+
if (await isArchivedChange(state.activeChange)) return;
|
|
435
|
+
const coverage = await acCoverageReview(path.join(runRoot, '.specs', state.activeChange));
|
|
436
|
+
if (coverage.unverified !== null) {
|
|
437
|
+
if (node.id === 'verify') console.error(coverage.unverified.notice);
|
|
438
|
+
return;
|
|
439
|
+
}
|
|
440
|
+
if (coverage.unjudgeable !== null) {
|
|
441
|
+
if (node.id === 'review') return;
|
|
442
|
+
const blocking = isNewChange(state);
|
|
443
|
+
for (const line of acCoverageUnjudgeableLines({ coverage, level: blocking ? 'BLOCKED' : 'WARN' })) {
|
|
444
|
+
console.error(line);
|
|
445
|
+
}
|
|
446
|
+
if (blocking) process.exit(1);
|
|
447
|
+
return;
|
|
448
|
+
}
|
|
449
|
+
if (coverage.missing.length === 0) return;
|
|
450
|
+
if (node.id === 'review') {
|
|
451
|
+
console.error(acCoverageSummaryLine({ coverage }));
|
|
452
|
+
return;
|
|
453
|
+
}
|
|
454
|
+
const blocking = isNewChange(state);
|
|
455
|
+
for (const line of acCoverageReportLines({ coverage, level: blocking ? 'BLOCKED' : 'WARN' })) {
|
|
456
|
+
console.error(line);
|
|
457
|
+
}
|
|
458
|
+
if (blocking) process.exit(1);
|
|
459
|
+
}
|
|
460
|
+
|
|
260
461
|
// verify 出口必须真实跑命令(严格版)——历史归档 change 豁免(过渡规则)。命令来源三级:TEST.md 的
|
|
261
462
|
// ## 验证命令 段 → state 的 verifyCommand → 项目探测回退。失败按 change 隔离计数(≥4 次要求用户
|
|
262
463
|
// 决策)。二段式执行(受限沙箱兼容):首选管道式捕获,仅当 spawn 层被拒(EPERM)时以继承 stdio
|
|
@@ -264,6 +465,10 @@ export async function runExecuteExitGate({ protocol, node, state, emptyExitAppro
|
|
|
264
465
|
export async function runVerifyExitGate({ protocol, node, state }) {
|
|
265
466
|
if (node.id !== 'verify') return;
|
|
266
467
|
if (await isArchivedChange(state.activeChange)) return;
|
|
468
|
+
// AC 覆盖:结构判据先于命令执行——缺覆盖时不白跑一遍验证命令;「载体缺席」(文件 / 模板根本不在)
|
|
469
|
+
// 只打印不判红(下面的「## 验证命令 / 产物」判据照常),「工件内容不可判」(含承载段被删掉)按
|
|
470
|
+
// change 新旧分级(见 runAcCoverageGate)。
|
|
471
|
+
await runAcCoverageGate({ node, state });
|
|
267
472
|
// 越权委托兜底检测(verify 出口)——同 execute 出口的判定(TASK parallel done + completedNodes
|
|
268
473
|
// 无 subagent-execute + 非 direct + 协议含 subagent-execute 节点),verify 时仍未 exit → WARN
|
|
269
474
|
// 兜底(execute 出口未拦截的提示)
|
|
@@ -490,6 +695,136 @@ export async function runMultiPassCompletionGate({ node, state }) {
|
|
|
490
695
|
} catch {}
|
|
491
696
|
}
|
|
492
697
|
|
|
698
|
+
// ---------- 缺证据恢复指引的前置条件(record 自己的技能加载声明门) ----------
|
|
699
|
+
//
|
|
700
|
+
// record 除了写证据,还有一道前置门:节点技能加载声明标记(.specs/<change>/.skill-loads/<node>-*.json)
|
|
701
|
+
// 不在场时 BLOCKED。于是「照抄 record」在缺声明时走不通,而那道门的报文又把执行者推回 exit——恢复
|
|
702
|
+
// 路径被拆成两条报文里的两步。故缺声明时把前置条件与它的命令写进**同一段「恢复:」**(编排在
|
|
703
|
+
// evidenceRecoveryBlock),执行者按一条报文即可走完;已有声明时不加步骤。
|
|
704
|
+
//
|
|
705
|
+
// 判据与 record 前置门同形(<node>-*.json 任一在场即算已声明),但落点不同:state 命令族按状态入口
|
|
706
|
+
// 初始化的运行上下文解析 .specs/,守卫进程没有该上下文,只能按 runRoot 解析——目录解析(活动路径优先、
|
|
707
|
+
// 归档路径兜底)取状态族路径上下文模块(state-io)的同一实现 findSkillLoadsDir,不在此另写一份:本函数
|
|
708
|
+
// 只提供「声明在不在场」这一个判据,路径规则归它。
|
|
709
|
+
async function nodeSkillDeclared(nodeId, changeName) {
|
|
710
|
+
if (!nodeId || !changeName) return false;
|
|
711
|
+
const loadsDir = await findSkillLoadsDir(runRoot, changeName);
|
|
712
|
+
if (loadsDir === null) return false;
|
|
713
|
+
const prefix = nodeId + '-';
|
|
714
|
+
return (await fs.readdir(loadsDir.dir).catch(() => []))
|
|
715
|
+
.some((name) => name.startsWith(prefix) && name.endsWith('.json'));
|
|
716
|
+
}
|
|
717
|
+
|
|
718
|
+
// 守卫族的命令运行上下文(形状与状态命令族的 commandContext 相同):脚本目录由本模块位置推导,
|
|
719
|
+
// 运行根 / 包根 / 协议路径取守卫运行上下文——协议路径是本次 guard 实际解析到的那一份(含 state 绑定),
|
|
720
|
+
// 命令自带的协议上下文因此与本次运行一致。
|
|
721
|
+
function declarationContext() {
|
|
722
|
+
return { scriptsDir, runRoot, packageRoot, protocolPath };
|
|
723
|
+
}
|
|
724
|
+
|
|
725
|
+
// 本节点该声明哪些技能(单一实现:出口声明覆盖门的「要求覆盖」与恢复段的「照抄哪几条命令」共用
|
|
726
|
+
// 同一份判据):协议 requiredSkillCalls 中 enforcement==='guarded' 且**非 handoff scope** 的条目
|
|
727
|
+
// ——handoff scope 的技能由子代理加载,协调者不加载也无法诚实声明(与 record 侧同一口径);
|
|
728
|
+
// 适用性门控的绑定(design 的 ui-design)在判据不成立时不要求声明(非前端本就不加载它,「没声明」
|
|
729
|
+
// 不是缺陷),判据成立时与其它 guarded 技能同权。两处若各判一套,恢复段给出的命令会在下一次 exit
|
|
730
|
+
// 上被另一套判据点名——那正是「照抄走不通」的成因。过滤条件本身取自 protocol-utils(协议面事实)。
|
|
731
|
+
export async function declarationSkillNames(node, state) {
|
|
732
|
+
const skills = guardedDeclarationSkills(node);
|
|
733
|
+
if (skills.length === 0) return [];
|
|
734
|
+
if (!skills.some((skill) => applicabilityGatedBinding(node, skill) !== null)) return skills;
|
|
735
|
+
const frontend = await frontendCriterion(state?.activeChange);
|
|
736
|
+
return skills
|
|
737
|
+
.filter((skill) => applicabilityGatedBinding(node, skill) === null || frontend.applicable === true);
|
|
738
|
+
}
|
|
739
|
+
|
|
740
|
+
// 「怎么重新声明技能加载」的完整形态(命令文本的单一来源:缺证据恢复段的第一步、出口声明覆盖门的补齐
|
|
741
|
+
// 命令、门控绑定缺证据的补证据步骤三处都从这里取,与状态命令族同一装配 state-explain 的
|
|
742
|
+
// declarationCommands)——三面同时给全,缺一照抄后必被另一道门拦一次:
|
|
743
|
+
// · 该节点**全部**协议文件 → 多个 --prompt(open / review 各两份:只给首份,覆盖门会点名另一份);
|
|
744
|
+
// 前端 change 上还要并上该节点的条件提示词(design 的 2a-ui-design.md——入口会打印那一行,声明
|
|
745
|
+
// 却漏掉它,ui-design 的命令就与它该读的协议对不上);
|
|
746
|
+
// · 该节点的模板全清单 → --templates(零模板节点省略,省略即空集;漏了会被模板门拦下);
|
|
747
|
+
// · 技能按 declarationSkillNames 逐个展开——一条命令只写一个技能标记,故每个必需技能各一条。
|
|
748
|
+
// 没有任何 guarded 必需技能(自定义协议节点 / 只有 handoff 绑定的 subagent-execute)时退回协议面
|
|
749
|
+
// 已有的技能名(protocol-utils 的 declarationSkillFallback:实现技能 → 非 handoff 既有条目 → 占位符)。
|
|
750
|
+
//
|
|
751
|
+
// 返回命令条目 { skill, command }(命令文本的构造在 state-explain,本函数只决定「哪些技能」)。
|
|
752
|
+
function skillLoadDeclarationCommands({ node, skills, frontend }) {
|
|
753
|
+
return declarationCommands({ node, skills, frontend, context: declarationContext() });
|
|
754
|
+
}
|
|
755
|
+
|
|
756
|
+
export async function nodeSkillLoadCommands({ node, state }) {
|
|
757
|
+
const required = await declarationSkillNames(node, state);
|
|
758
|
+
const targets = required.length > 0 ? required : [declarationSkillFallback(node)];
|
|
759
|
+
const frontend = (NODE_CONDITIONAL_PROMPTS[node.id] ?? []).length > 0
|
|
760
|
+
&& (await frontendCriterion(state?.activeChange)).applicable === true;
|
|
761
|
+
return skillLoadDeclarationCommands({ node, skills: targets, frontend });
|
|
762
|
+
}
|
|
763
|
+
|
|
764
|
+
// 单个技能的声明命令(入口 --prompt 冲突的兜底:标记声明的技能不在本节点目标集里时,仍要给一条
|
|
765
|
+
// 覆写该标记的命令)。与上面同一装配,不另拼一份文本。
|
|
766
|
+
export function guardDeclarationCommand({ node, skill, frontend = false }) {
|
|
767
|
+
return declarationCommand({ node, skill, frontend, context: declarationContext() });
|
|
768
|
+
}
|
|
769
|
+
|
|
770
|
+
// record 命令与「这条命令怎么执行」的说明分行给出(两处恢复段共用):命令单独成行才是可整行照抄的
|
|
771
|
+
// 片段——说明接在命令行尾时,整行丢给 shell 会把说明当成参数(载荷因此被拼成不合法 JSON:命令看起来
|
|
772
|
+
// 在场,照抄即失败)。说明行以「说明:」开头,与命令行的判别只靠行首(断言据此把两者分开)。
|
|
773
|
+
const RECORD_RETRY_NOTE = '说明: bash / PowerShell 可直接执行;cmd.exe 请把单引号换成双引号,'
|
|
774
|
+
+ '并转义载荷里原有的双引号';
|
|
775
|
+
|
|
776
|
+
function recordRecoveryCommand(node, completedChecks = []) {
|
|
777
|
+
const payload = { summary: '<本节点完成摘要>' };
|
|
778
|
+
if (completedChecks.length > 0) payload.completedChecks = completedChecks;
|
|
779
|
+
return scriptCommand({
|
|
780
|
+
scriptsDir,
|
|
781
|
+
runRoot,
|
|
782
|
+
script: 'workflow-state.mjs',
|
|
783
|
+
args: ['record', node.id, "'" + JSON.stringify(payload) + "'", ...protocolContextArgs(declarationContext())],
|
|
784
|
+
});
|
|
785
|
+
}
|
|
786
|
+
|
|
787
|
+
// 「补证据」恢复段(单一实现):两个门禁点打印同一段——缺 Output Schema 字段
|
|
788
|
+
// (runEvidenceCompletionGate)与完全没有证据对象(guard-gates 的 requireNodeEvidence)。两处说的
|
|
789
|
+
// 是同一件事(节点已完成、证据不在),各自拼一份必然分叉:一条带协议上下文与前置声明步骤、另一条
|
|
790
|
+
// 只剩 record,照抄的人在半路撞上 record 自己的声明门,还要回头去另一条报文里找第二步的命令。
|
|
791
|
+
//
|
|
792
|
+
// 形态只由「本节点技能声明在不在场」决定,与哪道门命中无关:
|
|
793
|
+
// · 声明已在场 → 一步:record 补证据;
|
|
794
|
+
// · 缺声明 → 两步,按**执行顺序**(第一步声明技能加载、第二步 record)——record 有自己的前置
|
|
795
|
+
// 门,照抄它之前必须先声明;步骤标注跟着各自的命令走(从上往下抄一遍就通)。
|
|
796
|
+
// lead 是**本门禁**对「它看到缺了什么」的点名(不同的门看到的缺项不同,恢复段的其余部分不随之分叉);
|
|
797
|
+
// 命令文本、参数段、尾部重试提示与步骤编排都只在这里产出(返回值 = 该段按序打印的各行)。
|
|
798
|
+
// 异步只为读声明标记:两个调用点都在可 await 的位置(缺证据门在出口链上,调用位随之声明 async)。
|
|
799
|
+
export async function evidenceRecoveryBlock({ node, state, lead = null }) {
|
|
800
|
+
const recordCommand = recordRecoveryCommand(node);
|
|
801
|
+
const leadPrefix = lead === null ? '' : lead + '——';
|
|
802
|
+
if (!state.activeChange || (await nodeSkillDeclared(node.id, state.activeChange))) {
|
|
803
|
+
return [
|
|
804
|
+
'恢复: ' + leadPrefix + '照抄下面的命令补齐它后重试 exit:',
|
|
805
|
+
' ' + recordCommand,
|
|
806
|
+
' ' + RECORD_RETRY_NOTE,
|
|
807
|
+
];
|
|
808
|
+
}
|
|
809
|
+
// 第一步的命令由协议派生(nodeSkillLoadCommands):该节点全部协议文件(多个 --prompt)、每个
|
|
810
|
+
// guarded 必需技能各一条(含该节点的模板全清单)。三面正是出口声明覆盖门与模板门核对的东西
|
|
811
|
+
// ——旧形态只声明实现技能 + 首份协议、且不带模板清单时,照抄完同一 exit 仍会被拦(恢复步骤自己
|
|
812
|
+
// 走不通)。单声明节点(只有一个必需技能)因此仍是一条命令,不因派生多出步骤。
|
|
813
|
+
const declarations = await nodeSkillLoadCommands({ node, state });
|
|
814
|
+
const placeholder = declarations.some((entry) => entry.skill === '<skill>');
|
|
815
|
+
return [
|
|
816
|
+
'恢复: ' + leadPrefix + '本节点还缺技能加载声明(.skill-loads/' + node.id + '-*.json,'
|
|
817
|
+
+ '新 change 下 record 会先被它拦下)'
|
|
818
|
+
+ (lead === null ? '——按下面的顺序走完两步后重试 exit:' : ';按下面的顺序走完两步后重试 exit:'),
|
|
819
|
+
' 第一步 声明本节点技能加载'
|
|
820
|
+
+ (placeholder ? '(技能名按 entry 的 LOAD SKILL 行填,下面用 <skill> 占位):' : ':'),
|
|
821
|
+
...declarations.map((entry) => ' ' + entry.command),
|
|
822
|
+
' 第二步 补证据并重试 exit:',
|
|
823
|
+
' ' + recordCommand,
|
|
824
|
+
' ' + RECORD_RETRY_NOTE,
|
|
825
|
+
];
|
|
826
|
+
}
|
|
827
|
+
|
|
493
828
|
// 自动补 required-skill completedChecks——节点被完成即视为其实现 skill 已加载。分派(ui-design 门):
|
|
494
829
|
// 仅「guarded 且适用性判据成立(判前端)」的登记绑定在**新 change** 上停止自动补——该绑定须真实
|
|
495
830
|
// skill-load 声明,由后续 missingRequiredSkillChecks 拦截;判据不成立(非前端)、旧 change(渐进
|
|
@@ -509,6 +844,10 @@ export async function runEvidenceCompletionGate({ protocol, node, state, evidenc
|
|
|
509
844
|
const missingSchemaEvidence = missingRequiredSchemaEvidence(protocol, node, evidence);
|
|
510
845
|
if (missingSchemaEvidence.length > 0) {
|
|
511
846
|
console.error('BLOCKED: missing Output Schema evidence: ' + missingSchemaEvidence.join(', '));
|
|
847
|
+
// 阻塞消息给可照抄的下一步:record 只写 summary 即视为产出证据(与判据同一口径),照抄执行后同一
|
|
848
|
+
// exit 即可通过——不再让执行者从字段清单反推该跑什么命令。恢复段取单一实现(guard-gates 的前置
|
|
849
|
+
// 门打印同一段):缺声明时两步、声明在场时一步,两处同形(顺序、命令、协议上下文都同源)。
|
|
850
|
+
console.error((await evidenceRecoveryBlock({ node, state })).join('\n'));
|
|
512
851
|
process.exit(1);
|
|
513
852
|
}
|
|
514
853
|
}
|
|
@@ -529,19 +868,49 @@ export async function runArtifactGate({ protocol, node, state, emptyExitApproved
|
|
|
529
868
|
}
|
|
530
869
|
}
|
|
531
870
|
|
|
532
|
-
//
|
|
533
|
-
//
|
|
871
|
+
// 受适用性门控的绑定缺证据时的「怎么补」——两件事必须同一段给全,缺一照抄完都还会撞同一道门:
|
|
872
|
+
// ① 真实 skill-load 声明:命令与缺证据恢复段同源(skillLoadDeclarationCommands——每个 guarded 必需
|
|
873
|
+
// 技能各一条,每条带该节点全部 --prompt(前端含条件提示词)与模板全清单);
|
|
874
|
+
// ② 带该 required-skill 的 record:出口只对**非**门控绑定自动补写,声明了却不把这条写进证据,同
|
|
875
|
+
// 一个 exit 仍会点名同一条(旧报文正是这个形态:占位提示词 + 不提 record = 死循环)。
|
|
876
|
+
// 前端判据在此不必再问一次:这条检查还能缺,前提就是本 change 为新 change 且判前端——判据不成立或
|
|
877
|
+
// 旧 change 时出口会把它自动补进证据(那里没有缺口),故条件提示词按适用计入。
|
|
878
|
+
function requiredSkillEvidenceRecovery({ node, evidence, missingChecks }) {
|
|
879
|
+
// 声明目标与覆盖门同一份判据(guarded ∧ 非 handoff):一次把该技能组全声明掉,下一步的覆盖门
|
|
880
|
+
// 因此不会再点名任何一条。
|
|
881
|
+
const gated = guardedDeclarationSkills(node);
|
|
882
|
+
const declarations = skillLoadDeclarationCommands({
|
|
883
|
+
node,
|
|
884
|
+
skills: gated.length > 0 ? gated : [declarationSkillFallback(node)],
|
|
885
|
+
frontend: true,
|
|
886
|
+
});
|
|
887
|
+
// 载荷写回**完整**清单(既有 ∪ 缺的):只写缺的那条,会把另一条已成立的 gated 声明抹掉——下一次
|
|
888
|
+
// exit 反过来点名它(同一个死循环的镜像形态)。
|
|
889
|
+
const checks = Array.isArray(evidence?.completedChecks) ? [...evidence.completedChecks] : [];
|
|
890
|
+
for (const check of missingChecks) if (!checks.includes(check)) checks.push(check);
|
|
891
|
+
return [
|
|
892
|
+
'恢复: ' + missingChecks.join('、') + ' 不再由出口自动补写(guarded + 适用性判据成立)'
|
|
893
|
+
+ '——按下面的顺序走完两步后重试 exit:',
|
|
894
|
+
' 第一步 声明本节点技能加载:',
|
|
895
|
+
...declarations.map((entry) => ' ' + entry.command),
|
|
896
|
+
' 第二步 补证据(record 载荷带上 ' + missingChecks.join('、') + '):',
|
|
897
|
+
' ' + recordRecoveryCommand(node, checks),
|
|
898
|
+
' ' + RECORD_RETRY_NOTE,
|
|
899
|
+
].join('\n');
|
|
900
|
+
}
|
|
901
|
+
|
|
902
|
+
// required-skill / augmentation 声明门禁:适用性门控绑定缺的是「真实 skill-load 声明 + 带上该条的
|
|
903
|
+
// 证据」(出口对该绑定不再自动补写)——恢复段两件事同一段给全(判据与该门同源:applicabilityGatedBinding
|
|
904
|
+
// 查询,不另写键表;命令装配与缺证据恢复段同源 skillLoadDeclarationCommands,不手拼半边命令)。
|
|
534
905
|
export function runRequiredEvidenceGate({ node, evidence }) {
|
|
535
906
|
const missingRequired = missingRequiredSkillChecks(node, evidence);
|
|
536
907
|
if (missingRequired.length > 0) {
|
|
537
908
|
console.error('BLOCKED: missing required Skill evidence: ' + missingRequired.join(', '));
|
|
538
|
-
|
|
539
|
-
|
|
540
|
-
|
|
541
|
-
|
|
542
|
-
|
|
543
|
-
+ ' --prompt <flow-kit/prompts/ 协议文件> 声明已加载后重试 exit');
|
|
544
|
-
}
|
|
909
|
+
const gatedMissing = missingRequired.filter((check) => (node.requiredSkillCalls ?? []).some((binding) => binding
|
|
910
|
+
&& 'required-skill:' + node.id + '.' + binding.skill === check
|
|
911
|
+
&& applicabilityGatedBinding(node, binding.skill) !== null));
|
|
912
|
+
if (gatedMissing.length > 0) {
|
|
913
|
+
console.error(requiredSkillEvidenceRecovery({ node, evidence, missingChecks: gatedMissing }));
|
|
545
914
|
}
|
|
546
915
|
process.exit(1);
|
|
547
916
|
}
|