flow-comet 1.7.0 → 1.8.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.flow-comet/skills/flow-comet/INSTALLED_VERSION +1 -1
- package/.flow-comet/skills/flow-comet/SKILL.md +16 -14
- package/.flow-comet/skills/flow-comet/reference/commit-discipline.md +1 -1
- package/.flow-comet/skills/flow-comet/reference/decision-points.md +5 -5
- package/.flow-comet/skills/flow-comet/reference/dirty-worktree.md +1 -1
- package/.flow-comet/skills/flow-comet/reference/entry-detail.md +9 -9
- package/.flow-comet/skills/flow-comet/reference/fix-loop.md +4 -4
- package/.flow-comet/skills/flow-comet/reference/init-detection.md +1 -1
- package/.flow-comet/skills/flow-comet/reference/platform-facts.md +2 -2
- package/.flow-comet/skills/flow-comet/reference/post-archive-handoff.md +264 -0
- package/.flow-comet/skills/flow-comet/reference/recovery.md +1 -1
- package/.flow-comet/skills/flow-comet/reference/replan.md +1 -1
- package/.flow-comet/skills/flow-comet/scripts/comet-check.mjs +1 -0
- package/.flow-comet/skills/flow-comet/scripts/comet-hook-guard.mjs +270 -30
- package/.flow-comet/skills/flow-comet/scripts/items/a.mjs +25 -8
- package/.flow-comet/skills/flow-comet/scripts/items/b.mjs +41 -38
- package/.flow-comet/skills/flow-comet/scripts/items/c.mjs +11 -9
- package/.flow-comet/skills/flow-comet/scripts/items/e.mjs +2 -2
- package/.flow-comet/skills/flow-comet/scripts/items/f.mjs +1 -1
- package/.flow-comet/skills/flow-comet/scripts/items/h.mjs +112 -53
- package/.flow-comet/skills/flow-comet/scripts/items/k.mjs +357 -3
- package/.flow-comet/skills/flow-comet/scripts/items/l.mjs +24 -1
- package/.flow-comet/skills/flow-comet/scripts/items/m.mjs +2 -2
- package/.flow-comet/skills/flow-comet/scripts/items/n.mjs +9 -10
- package/.flow-comet/skills/flow-comet/scripts/lib/ac-coverage.mjs +8 -8
- package/.flow-comet/skills/flow-comet/scripts/lib/fix-loop-node.mjs +4 -15
- package/.flow-comet/skills/flow-comet/scripts/lib/guard-evidence-gates.mjs +79 -107
- package/.flow-comet/skills/flow-comet/scripts/lib/guard-gates.mjs +183 -232
- package/.flow-comet/skills/flow-comet/scripts/lib/guard-routing.mjs +91 -14
- package/.flow-comet/skills/flow-comet/scripts/lib/guard-template-fidelity.mjs +20 -32
- package/.flow-comet/skills/flow-comet/scripts/lib/guard-uidesign.mjs +10 -19
- package/.flow-comet/skills/flow-comet/scripts/lib/state-commands-admin.mjs +27 -17
- package/.flow-comet/skills/flow-comet/scripts/lib/state-commands-flow.mjs +240 -87
- package/.flow-comet/skills/flow-comet/scripts/lib/state-commands-recovery.mjs +15 -22
- package/.flow-comet/skills/flow-comet/scripts/lib/state-determine.mjs +11 -4
- package/.flow-comet/skills/flow-comet/scripts/lib/state-io.mjs +192 -24
- package/.flow-comet/skills/flow-comet/scripts/lib/state-skillmarkers.mjs +55 -44
- package/.flow-comet/skills/flow-comet/scripts/lib/system-fixtures.mjs +2 -4
- package/.flow-comet/skills/flow-comet/scripts/lib/test-assertions.mjs +0 -3
- package/.flow-comet/skills/flow-comet/scripts/lib/test-fixtures.mjs +191 -17
- package/.flow-comet/skills/flow-comet/scripts/lib/test-helpers.mjs +3 -0
- package/.flow-comet/skills/flow-comet/scripts/lib/text-anchor-checks.mjs +23 -5
- package/.flow-comet/skills/flow-comet/scripts/lib/wave-projection.mjs +10 -11
- package/.flow-comet/skills/flow-comet/scripts/protocol-utils.mjs +40 -3
- package/.flow-comet/skills/flow-comet/scripts/route-node.mjs +12 -5
- package/.flow-comet/skills/flow-comet/scripts/scenarios/a.mjs +193 -111
- package/.flow-comet/skills/flow-comet/scripts/scenarios/b.mjs +314 -57
- package/.flow-comet/skills/flow-comet/scripts/scenarios/c.mjs +311 -216
- package/.flow-comet/skills/flow-comet/scripts/scenarios/d.mjs +33 -62
- package/.flow-comet/skills/flow-comet/scripts/scenarios/e.mjs +188 -91
- package/.flow-comet/skills/flow-comet/scripts/scenarios/f.mjs +94 -37
- package/.flow-comet/skills/flow-comet/scripts/scenarios/g.mjs +36 -27
- package/.flow-comet/skills/flow-comet/scripts/scenarios/h.mjs +285 -9
- package/.flow-comet/skills/flow-comet/scripts/scenarios/i.mjs +2 -6
- package/.flow-comet/skills/flow-comet/scripts/scenarios/j.mjs +5 -15
- package/.flow-comet/skills/flow-comet/scripts/scenarios/k.mjs +6 -5
- package/.flow-comet/skills/flow-comet/scripts/scenarios/l.mjs +40 -36
- package/.flow-comet/skills/flow-comet/scripts/scenarios/m.mjs +2 -2
- package/.flow-comet/skills/flow-comet/scripts/scenarios/n.mjs +346 -25
- package/.flow-comet/skills/flow-comet/scripts/state-schema.mjs +0 -2
- package/.flow-comet/skills/flow-comet/scripts/workflow-handoff.mjs +41 -54
- package/.flow-comet/skills/flow-comet-archive/SKILL.md +33 -11
- package/.flow-comet/skills/flow-comet-change/SKILL.md +1 -1
- package/.flow-comet/skills/flow-comet-design/SKILL.md +5 -3
- package/.flow-comet/skills/flow-comet-dev/SKILL.md +2 -2
- package/.flow-comet/skills/flow-comet-execute/SKILL.md +11 -11
- package/.flow-comet/skills/flow-comet-integration/SKILL.md +10 -4
- 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 +8 -8
- package/.flow-comet/skills/flow-comet-subagent-execute/GUIDANCE.md +1 -1
- package/.flow-comet/skills/flow-comet-subagent-execute/SKILL.md +14 -14
- package/.flow-comet/skills/flow-comet-task/SKILL.md +3 -2
- package/.flow-comet/skills/flow-comet-ui-design/SKILL.md +2 -2
- package/.flow-comet/skills/flow-comet-verify/SKILL.md +1 -1
- package/README.md +2 -2
- package/package.json +1 -1
- package/scripts/dsh-bridge.mjs +238 -21
|
@@ -11,6 +11,9 @@
|
|
|
11
11
|
//
|
|
12
12
|
// 待实现面:本组场景先于实现落盘(RED),由产出物门禁扩展 / 加载链 / 扫描与提名 / 侧命令 /
|
|
13
13
|
// 文本同步各任务转绿。
|
|
14
|
+
//
|
|
15
|
+
// 尾部 352 号场景不属模板权威族:它守的是**分发参考册**(`reference/post-archive-handoff.md`
|
|
16
|
+
// 的协议要素与段序)。共处一组只因场景按组文件顺序编号——新场景追加在本文件末尾,既有编号不动。
|
|
14
17
|
|
|
15
18
|
import fs from 'fs';
|
|
16
19
|
import path from 'path';
|
|
@@ -22,16 +25,15 @@ import {
|
|
|
22
25
|
assertOut,
|
|
23
26
|
assertTrue,
|
|
24
27
|
baseState,
|
|
28
|
+
installSkillTreeCopy,
|
|
25
29
|
runGuard,
|
|
30
|
+
runPrintedCommand,
|
|
26
31
|
runState,
|
|
27
32
|
writeFile,
|
|
28
33
|
writeState,
|
|
29
34
|
} from '../lib/test-helpers.mjs';
|
|
30
35
|
import {
|
|
31
36
|
CHANGE_ID,
|
|
32
|
-
REPO_ROOT,
|
|
33
|
-
SCRIPTS_DIR,
|
|
34
|
-
TASK_DONE,
|
|
35
37
|
customProtocol,
|
|
36
38
|
dropNamedImport,
|
|
37
39
|
engineCodeText,
|
|
@@ -40,9 +42,13 @@ import {
|
|
|
40
42
|
engineDefinitionPattern,
|
|
41
43
|
engineImportsSymbolFrom,
|
|
42
44
|
engineScriptTexts,
|
|
43
|
-
handoffFor,
|
|
44
45
|
HANDOFF,
|
|
46
|
+
handoffFor,
|
|
47
|
+
REPO_ROOT,
|
|
48
|
+
SCRIPTS_DIR,
|
|
45
49
|
STATE,
|
|
50
|
+
TASK_DONE,
|
|
51
|
+
writeAllNodeDeclarationMarkers,
|
|
46
52
|
writeNodeDeclarationMarkers,
|
|
47
53
|
} from '../lib/test-fixtures.mjs';
|
|
48
54
|
import { scenarioProtocolPath } from '../lib/test-assertions.mjs';
|
|
@@ -397,7 +403,6 @@ function renderDoc(key, opts = {}) {
|
|
|
397
403
|
|
|
398
404
|
function newChangeState(node) {
|
|
399
405
|
const st = baseState(node);
|
|
400
|
-
st.newChange = true;
|
|
401
406
|
st.enteredNodes = [node];
|
|
402
407
|
return st;
|
|
403
408
|
}
|
|
@@ -592,8 +597,8 @@ function repoFileText(rel) {
|
|
|
592
597
|
return fs.readFileSync(path.join(REPO_ROOT, ...rel.split('/')), 'utf8');
|
|
593
598
|
}
|
|
594
599
|
|
|
595
|
-
function repoFileExists(rel) {
|
|
596
|
-
return fs.existsSync(path.join(
|
|
600
|
+
function repoFileExists(rel, root = REPO_ROOT) {
|
|
601
|
+
return fs.existsSync(path.join(root, ...rel.split('/')));
|
|
597
602
|
}
|
|
598
603
|
|
|
599
604
|
// 公开面缺席判据(同一实现驱动真实断言与变异探针):形态判据认定本检出带公开面时(docs/、
|
|
@@ -644,6 +649,105 @@ function assertProbesDiscriminate(problems, docs, rules, probes) {
|
|
|
644
649
|
}
|
|
645
650
|
}
|
|
646
651
|
|
|
652
|
+
// 归档后交接协议页(`reference/post-archive-handoff.md`,分发参考册)的判据:场景 352 与它自己
|
|
653
|
+
// 的变异探针共用同一实现——文本进、问题清单出。只判协议要素(段序 / 选项 / 命令 / 降级 /
|
|
654
|
+
// 不写状态 / 草稿视角 / roadmap 结构);其中若干要素以固定措辞出现(如「内容 + 命令」「不声明已创建」),
|
|
655
|
+
// 那几句的措辞即判据:改措辞须同批改本文件的锚,否则场景会红。
|
|
656
|
+
const HANDOFF_PAGE_SECTIONS = [
|
|
657
|
+
['触发', '## 触发与顺序'],
|
|
658
|
+
['探测', '## 探测(只读)'],
|
|
659
|
+
['一次询问', '## 一次载体询问'],
|
|
660
|
+
['展示与确认', '## 展示、粒度与确认'],
|
|
661
|
+
['降级', '## 降级与失败'],
|
|
662
|
+
];
|
|
663
|
+
// 四选项按**整行**认:这四个词在推荐矩阵里各自也出现,只按词判会让「整张表被删」仍然全绿。
|
|
664
|
+
const HANDOFF_PAGE_OPTIONS = [
|
|
665
|
+
'| GitHub Issues | 用 `gh` 按目标项目现有 issue 模板创建 |',
|
|
666
|
+
'| GitLab Issues | 用 `glab` 创建 |',
|
|
667
|
+
'| 本地 roadmap | 写进项目自己的路线图文件(索引 + 每条一份文件) |',
|
|
668
|
+
'| 暂不处理 | 结束本步骤,不写盘;不记忆,下一次归档仍会问 |',
|
|
669
|
+
];
|
|
670
|
+
const HANDOFF_PAGE_PROBE_COMMANDS = [
|
|
671
|
+
'git rev-parse --is-inside-work-tree',
|
|
672
|
+
'git remote get-url origin',
|
|
673
|
+
'gh --version',
|
|
674
|
+
'glab --version',
|
|
675
|
+
'gh auth status --hostname',
|
|
676
|
+
'glab auth status --hostname',
|
|
677
|
+
];
|
|
678
|
+
// 降级 = 内容 + 可照抄的命令两件套,且不得把「没创建」写成「已创建」。
|
|
679
|
+
const HANDOFF_PAGE_DEGRADE = ['内容 + 命令', 'gh issue create', 'glab issue create', '不声明已创建'];
|
|
680
|
+
// 步骤权威:八步顺序有两处表达(归档册 / 本页),页内必须声明以归档册为准,否则下次改顺序只会改一处。
|
|
681
|
+
const HANDOFF_PAGE_AUTHORITY = ['步骤权威', 'flow-comet-archive'];
|
|
682
|
+
// 缺陷类草稿的七段按**编号**认(编号即骨架顺序):页内别处出现的同名单词不算骨架在场。
|
|
683
|
+
const HANDOFF_PAGE_DRAFT_PARTS = [
|
|
684
|
+
'1. 用户版本', '2. 终端', '3. 现象', '4. 复现', '5. 期望', '6. 代码位置', '7. 未验证',
|
|
685
|
+
];
|
|
686
|
+
const HANDOFF_PAGE_ROADMAP_COLUMNS = ['索引七列', 'ID', '标题', '状态', '优先级', '时间向', '负责人', '链接'];
|
|
687
|
+
const HANDOFF_PAGE_ROADMAP_SECTIONS = ['每条六段', 'What', 'Why', 'Context', 'Acceptance', 'Links', 'Notes'];
|
|
688
|
+
const HANDOFF_PAGE_STATE_FILE = '.flow-comet/flow-comet-state.json';
|
|
689
|
+
|
|
690
|
+
function handoffPageProblems(text) {
|
|
691
|
+
if (typeof text !== 'string') return ['归档后交接协议页不在检出面'];
|
|
692
|
+
const problems = [];
|
|
693
|
+
// ① 段序:五段俱全,且 触发 → 探测 → 一次询问 → 展示 → 降级 严格递增(缺段与乱序分开报)。
|
|
694
|
+
let previousIndex = -1;
|
|
695
|
+
let previousHeading = null;
|
|
696
|
+
for (const [label, heading] of HANDOFF_PAGE_SECTIONS) {
|
|
697
|
+
const index = text.indexOf(heading);
|
|
698
|
+
if (index < 0) { problems.push('缺段「' + heading + '」(' + label + ')'); continue; }
|
|
699
|
+
if (previousIndex >= 0 && index < previousIndex) {
|
|
700
|
+
problems.push('段序颠倒:「' + heading + '」排在「' + previousHeading + '」之前');
|
|
701
|
+
}
|
|
702
|
+
previousIndex = index;
|
|
703
|
+
previousHeading = heading;
|
|
704
|
+
}
|
|
705
|
+
// ② 四选项:少一个就是替用户排除了一条路。
|
|
706
|
+
for (const option of HANDOFF_PAGE_OPTIONS) {
|
|
707
|
+
if (!text.includes(option)) problems.push('缺载体选项行「' + option + '」');
|
|
708
|
+
}
|
|
709
|
+
// ③ 固定探测命令块:git 在树内 → remote 分类 → CLI 版本 → 认证状态。
|
|
710
|
+
for (const command of HANDOFF_PAGE_PROBE_COMMANDS) {
|
|
711
|
+
if (!text.includes(command)) problems.push('缺探测命令「' + command + '」');
|
|
712
|
+
}
|
|
713
|
+
// ④ 降级两件套与「不声明已创建」。
|
|
714
|
+
for (const needle of HANDOFF_PAGE_DEGRADE) {
|
|
715
|
+
if (!text.includes(needle)) problems.push('缺降级要素「' + needle + '」');
|
|
716
|
+
}
|
|
717
|
+
// ④b 步骤权威:顺序不能有两处权威——页内必须声明以归档册为准。
|
|
718
|
+
for (const needle of HANDOFF_PAGE_AUTHORITY) {
|
|
719
|
+
if (!text.includes(needle)) problems.push('缺步骤权威声明「' + needle + '」');
|
|
720
|
+
}
|
|
721
|
+
// ⑤ 不写状态:只拦「紧贴着把状态文件当写入目标」的句子(正向写入检测)——
|
|
722
|
+
// 否定在句首(`不写状态文件(<路径>):…`)或在路径之后的从句(`<路径> 只读,不写入`)都不误伤;
|
|
723
|
+
// 而 `写入 <路径>,不新增字段` / `不写报告,但写入 <路径>` 这类「否定在别处」的句子仍必须红。
|
|
724
|
+
const WRITE_VERB_TAIL_RE = /(写|写入|修改|覆盖|改动)\s*`?\s*$/;
|
|
725
|
+
const NEGATED_WRITE_TAIL_RE = /(不写|不写入|禁止写|不得写|不要写|勿写|绝不写|不直接写|不手动写)\s*`?\s*$/;
|
|
726
|
+
const stateLines = text.split(/\r?\n/).filter((line) => line.includes(HANDOFF_PAGE_STATE_FILE));
|
|
727
|
+
if (stateLines.length === 0) problems.push('缺「不写状态文件」边界(页内未点名状态文件)');
|
|
728
|
+
for (const line of stateLines) {
|
|
729
|
+
const before = line.slice(0, line.indexOf(HANDOFF_PAGE_STATE_FILE));
|
|
730
|
+
if (WRITE_VERB_TAIL_RE.test(before) && !NEGATED_WRITE_TAIL_RE.test(before)) {
|
|
731
|
+
problems.push('状态文件出现在肯定语境「' + line.trim().slice(0, 60) + '」');
|
|
732
|
+
}
|
|
733
|
+
}
|
|
734
|
+
// ⑥ 公开草稿视角:七段骨架 + 维护者第一遍读 + 0 命中不等于通过。
|
|
735
|
+
for (const part of HANDOFF_PAGE_DRAFT_PARTS) {
|
|
736
|
+
if (!text.includes(part)) problems.push('缺草稿骨架「' + part + '」');
|
|
737
|
+
}
|
|
738
|
+
for (const needle of ['第一遍读', '0 命中']) {
|
|
739
|
+
if (!text.includes(needle)) problems.push('缺草稿视角「' + needle + '」');
|
|
740
|
+
}
|
|
741
|
+
// ⑦ 本地 roadmap 的规定形式:索引七列 + 每条六段。
|
|
742
|
+
for (const needle of HANDOFF_PAGE_ROADMAP_COLUMNS) {
|
|
743
|
+
if (!text.includes(needle)) problems.push('缺 roadmap 索引结构「' + needle + '」');
|
|
744
|
+
}
|
|
745
|
+
for (const needle of HANDOFF_PAGE_ROADMAP_SECTIONS) {
|
|
746
|
+
if (!text.includes(needle)) problems.push('缺 roadmap 条目结构「' + needle + '」');
|
|
747
|
+
}
|
|
748
|
+
return problems;
|
|
749
|
+
}
|
|
750
|
+
|
|
647
751
|
// 公开面自检的**形态分派**(判定本体在 lib:publicFaceSelfCheck)——各载体形态各造一个临时根、驱动
|
|
648
752
|
// 同一判定,分派对错因此成为常驻断言,不必等到在包形态里整跑一次套件才知道:
|
|
649
753
|
// ① 包形态(技能树锚在场、docs/ + CONTRIBUTING.md + .github/ 三者俱缺)→ SKIP 通知 + 零问题:
|
|
@@ -666,6 +770,15 @@ function countFaceFiles() {
|
|
|
666
770
|
])];
|
|
667
771
|
}
|
|
668
772
|
|
|
773
|
+
// 夹具预检(只回答「照真迹复制的夹具能不能从本检出构造」,root 可覆盖以便在临时根上反向构造):
|
|
774
|
+
// 逐份判存在、返回缺席清单,不复制也不写盘。它与产品面的缺席判据(publicFaceAbsenceProblems)
|
|
775
|
+
// 分工不同——后者判「公开面文档在不在检出面」,本函数判「构造夹具所需的受检面文件在不在」。
|
|
776
|
+
// 少了这层,复制循环里的 copyfile 会以文件错误崩在半路,读者会把 ENOENT 读成产品缺陷,而真因是
|
|
777
|
+
// 「本检出被判为带公开面、却缺公开文档」——那个判红本身是对的,只是崩法不可读。
|
|
778
|
+
function missingShapeFixtureFiles(root = REPO_ROOT) {
|
|
779
|
+
return countFaceFiles().filter((rel) => !repoFileExists(rel, root));
|
|
780
|
+
}
|
|
781
|
+
|
|
669
782
|
function copyRepoFileInto(root, rel) {
|
|
670
783
|
const parts = rel.split('/');
|
|
671
784
|
const dest = path.join(root, ...parts);
|
|
@@ -673,7 +786,7 @@ function copyRepoFileInto(root, rel) {
|
|
|
673
786
|
fs.copyFileSync(path.join(REPO_ROOT, ...parts), dest);
|
|
674
787
|
}
|
|
675
788
|
|
|
676
|
-
async function assertPublicFaceSelfCheckShapes(dir) {
|
|
789
|
+
async function assertPublicFaceSelfCheckShapes(dir, { repoRoot = REPO_ROOT } = {}) {
|
|
677
790
|
const shapeRoot = (name, { authoritative = true } = {}) => {
|
|
678
791
|
const root = path.join(dir, 'shape-' + name);
|
|
679
792
|
fs.mkdirSync(root, { recursive: true });
|
|
@@ -698,6 +811,16 @@ async function assertPublicFaceSelfCheckShapes(dir) {
|
|
|
698
811
|
throw new Error('包形态的跳过提示必须写明「未校验」(跳过 ≠ 通过): ' + packaged.skip.notice);
|
|
699
812
|
}
|
|
700
813
|
// ② 权威源形态完整:受检面文件照真迹复制,计数自然同步(不硬编码数字)
|
|
814
|
+
// 复制之前先预检:受检面清单里缺任何一份,copyfile 都会以文件错误崩在循环半路,而真因是
|
|
815
|
+
// 「本检出被判为带公开面、却缺公开文档」。预检把缺席逐份点名后再抛,读者不会把文件错误
|
|
816
|
+
// 读成产品缺陷;清单为空才进入复制与 shape 自检。
|
|
817
|
+
const missingFixture = missingShapeFixtureFiles(repoRoot);
|
|
818
|
+
if (missingFixture.length > 0) {
|
|
819
|
+
throw new Error('形态自检夹具无法构造:本检出被判为带公开面(docs/、CONTRIBUTING.md 或 .github/'
|
|
820
|
+
+ ' 任一在场),但照真迹复制的受检面文件缺 ' + missingFixture.length + ' 份——'
|
|
821
|
+
+ missingFixture.join('、') + '。这是「本检出被判为带公开面」的判红形态,不是复制文件失败;'
|
|
822
|
+
+ '补齐上述文件后重跑本套件(相对根 ' + repoRoot + ')');
|
|
823
|
+
}
|
|
701
824
|
const full = shapeRoot('authoritative');
|
|
702
825
|
for (const rel of countFaceFiles()) copyRepoFileInto(full, rel);
|
|
703
826
|
const complete = await publicFaceSelfCheck({ root: full });
|
|
@@ -1744,42 +1867,43 @@ export const ENTRIES = [
|
|
|
1744
1867
|
},
|
|
1745
1868
|
},
|
|
1746
1869
|
|
|
1747
|
-
// TA-11 ·
|
|
1748
|
-
//
|
|
1870
|
+
// TA-11 · 单轨缺段判级(AC-11)——同一份缺损工件在**无任何新旧标记字段**的状态下同样 BLOCKED
|
|
1871
|
+
// (不再有「旧 change 只 WARN」这一侧);design 侧「视觉调性」段缺席同判。
|
|
1749
1872
|
// ⑤ 追加「视觉调性」段体的围栏语义:段里贴了含 `## ` 的围栏示例时,示例之后的「不适用」声明
|
|
1750
1873
|
// 仍要被读到(段界只由围栏外的标题决定)。
|
|
1751
1874
|
{
|
|
1752
|
-
name: 'TA-11
|
|
1875
|
+
name: 'TA-11 缺段一律 BLOCKED(无字段状态同判);视觉调性段内的围栏示例不截断',
|
|
1753
1876
|
run: async (dir) => {
|
|
1754
1877
|
const missing = { omit: ['影响面'] };
|
|
1755
|
-
// ①
|
|
1878
|
+
// ① 缺段:拦(对照基准——同一份缺损工件)
|
|
1756
1879
|
setupOpen(dir, missing);
|
|
1757
1880
|
const newRes = exitNode(dir, 'open');
|
|
1758
1881
|
assertExit(newRes, 1);
|
|
1759
|
-
|
|
1882
|
+
assertOut(newRes, 'BLOCKED');
|
|
1883
|
+
// ② 同构缺段(无任何新旧标记字段):同判 BLOCKED(单一等级)
|
|
1760
1884
|
setupOpen(dir, missing);
|
|
1761
1885
|
const legacy = baseState('open');
|
|
1762
1886
|
legacy.evidence.open = { summary: 'intake complete' };
|
|
1763
1887
|
writeState(dir, legacy);
|
|
1764
1888
|
const legacyRes = exitNode(dir, 'open');
|
|
1765
|
-
assertExit(legacyRes,
|
|
1766
|
-
assertOut(legacyRes, '
|
|
1767
|
-
assertNotOut(legacyRes, 'BLOCKED');
|
|
1889
|
+
assertExit(legacyRes, 1);
|
|
1890
|
+
assertOut(legacyRes, 'BLOCKED');
|
|
1768
1891
|
// ③ design 侧段缺席:同一判据——CHANGE.md「视觉调性」段缺席,新 change 由 uidesign 门兜底拦,
|
|
1769
1892
|
// 不再默认判非前端(段缺席与段内声明「不适用」是两件事,只有后者是决策)。
|
|
1770
1893
|
setupDesign(dir, { changeOpts: { omit: ['视觉调性'] } });
|
|
1771
1894
|
const designNew = exitNode(dir, 'design');
|
|
1772
1895
|
assertExit(designNew, 1);
|
|
1773
1896
|
assertOut(designNew, '「视觉调性」段缺席');
|
|
1774
|
-
assertOut(designNew, '
|
|
1775
|
-
// ④
|
|
1897
|
+
assertOut(designNew, '须显式标注「不适用」');
|
|
1898
|
+
// ④ 同构缺段(无任何新旧标记字段):同判 BLOCKED(单一等级,不再有兼容跳过)
|
|
1776
1899
|
setupDesign(dir, { changeOpts: { omit: ['视觉调性'] } });
|
|
1777
1900
|
const designLegacy = baseState('design');
|
|
1778
1901
|
designLegacy.evidence.design = { summary: 'design done' };
|
|
1779
1902
|
writeState(dir, designLegacy);
|
|
1780
1903
|
const designLegacyRes = exitNode(dir, 'design');
|
|
1781
|
-
assertExit(designLegacyRes,
|
|
1782
|
-
assertOut(designLegacyRes, '
|
|
1904
|
+
assertExit(designLegacyRes, 1);
|
|
1905
|
+
assertOut(designLegacyRes, '「视觉调性」段缺席');
|
|
1906
|
+
assertNotOut(designLegacyRes, '旧 change 兼容');
|
|
1783
1907
|
// ⑤ 段体围栏语义:「视觉调性」段里贴一段含 `## ` 的围栏示例,「不适用」声明写在围栏**之后**
|
|
1784
1908
|
// ⇒ 段体不被示例里的标题截断,判据仍读到声明(围栏是正文示例,不是段界)。旧的按行扫描
|
|
1785
1909
|
// 在这里截断段体 → 标记消失 → 判成前端 → 要求一份本不该存在的 UI-DESIGN.md(BLOCKED)。
|
|
@@ -2057,7 +2181,6 @@ export const ENTRIES = [
|
|
|
2057
2181
|
writeFile(dir, changeDirOf(), renderDoc('CHANGE', { omit: ['影响面'] }));
|
|
2058
2182
|
const st = baseState('brainstorm');
|
|
2059
2183
|
st.activeChange = CHANGE_ID;
|
|
2060
|
-
st.newChange = true;
|
|
2061
2184
|
st.enteredNodes = ['brainstorm'];
|
|
2062
2185
|
st.evidence.brainstorm = { summary: 'notes done' };
|
|
2063
2186
|
writeState(dir, st);
|
|
@@ -2637,6 +2760,7 @@ export const ENTRIES = [
|
|
|
2637
2760
|
{
|
|
2638
2761
|
name: 'TA-19 归档提名:缺字段/编号不存在/份数不符三负例拦,补齐后通过',
|
|
2639
2762
|
run: async (dir) => {
|
|
2763
|
+
writeNodeDeclarationMarkers(dir, 'archive');
|
|
2640
2764
|
// ① 缺 lessonsNomination 字段
|
|
2641
2765
|
setupArchive(dir);
|
|
2642
2766
|
const missingField = exitNode(dir, 'archive');
|
|
@@ -2699,6 +2823,48 @@ export const ENTRIES = [
|
|
|
2699
2823
|
assertExit(decoyOnly, 1);
|
|
2700
2824
|
assertOut(decoyOnly, '工件目录缺失');
|
|
2701
2825
|
assertNotOut(decoyOnly, 'ALL CHECKS PASSED');
|
|
2826
|
+
// ④c 多候选按日期(in-place 扩展):同名 change 有多份**合规**归档目录时,取日期最新的一份。
|
|
2827
|
+
// 夹具用「结论可判别」的份数(最新 = 2、更早 = 5):退回「取第一个命中」或「取更早的一份」都会
|
|
2828
|
+
// 让下面的份数对账判红——这是日期判定真正在起作用的证据。
|
|
2829
|
+
setupArchive(dir, {
|
|
2830
|
+
evidence: { lessonsNomination: { scanned: 2, nominated: ['L-501'], reasonIfNone: '' } },
|
|
2831
|
+
});
|
|
2832
|
+
fs.renameSync(path.join(dir, CHANGE_DIR), path.join(archiveRoot, '2026-11-10-' + CHANGE_ID));
|
|
2833
|
+
fs.renameSync(path.join(archiveRoot, '2026-10-20-' + CHANGE_ID, 'KNOWN-ISSUES.md'),
|
|
2834
|
+
path.join(archiveRoot, '2026-11-10-' + CHANGE_ID, 'KNOWN-ISSUES.md'));
|
|
2835
|
+
fs.rmSync(path.join(archiveRoot, '2026-10-20-' + CHANGE_ID), { recursive: true, force: true });
|
|
2836
|
+
writeFile(dir, '.specs/archive/2026-11-01-' + CHANGE_ID + '/KNOWN-ISSUES.md', '# KNOWN-ISSUES\n\n无遗留。\n');
|
|
2837
|
+
for (let i = 3; i <= 7; i += 1) {
|
|
2838
|
+
writeFile(dir, '.specs/archive/2026-11-01-' + CHANGE_ID + '/T0' + i + '-SUMMARY.md',
|
|
2839
|
+
'# SUMMARY\n\n## 做了什么\n\n更早候选的份数(被选中即判红)。\n');
|
|
2840
|
+
}
|
|
2841
|
+
const newestCandidate = runGuard(['exit', 'archive'], dir);
|
|
2842
|
+
assertExit(newestCandidate, 0);
|
|
2843
|
+
assertOut(newestCandidate, 'ALL CHECKS PASSED');
|
|
2844
|
+
// 反向构造(单变量 = 只把声明份数改成更早候选的 5):取最新 ⇒ 声明与最新一份的 2 份不符 → BLOCK
|
|
2845
|
+
const olderDeclared = newChangeState('archive');
|
|
2846
|
+
olderDeclared.evidence.archive = {
|
|
2847
|
+
summary: 'archived',
|
|
2848
|
+
lessonsNomination: { scanned: 5, nominated: [], reasonIfNone: '无新增条目' },
|
|
2849
|
+
};
|
|
2850
|
+
writeState(dir, olderDeclared);
|
|
2851
|
+
const olderCount = runGuard(['exit', 'archive'], dir);
|
|
2852
|
+
assertExit(olderCount, 1);
|
|
2853
|
+
assertOut(olderCount, '≠ 该 change 内 *-SUMMARY.md 份数 2');
|
|
2854
|
+
// ④d 排除早于 createdAt 的候选(AC-7 的另一半):两份候选都早于本 change 的创建日期 ⇒ 无合格
|
|
2855
|
+
// 候选,份数无从核对(fail-closed「工件目录缺失」),不得拿更早的归档目录凑数——不设下界时
|
|
2856
|
+
// 这里会选中 2026-11-10 的 2 份而与声明一致,判据随之变绿(假放行)。
|
|
2857
|
+
const allTooEarly = newChangeState('archive');
|
|
2858
|
+
allTooEarly.createdAt = '2026-12-01T00:00:00.000Z';
|
|
2859
|
+
allTooEarly.evidence.archive = {
|
|
2860
|
+
summary: 'archived',
|
|
2861
|
+
lessonsNomination: { scanned: 2, nominated: [], reasonIfNone: '无新增条目' },
|
|
2862
|
+
};
|
|
2863
|
+
writeState(dir, allTooEarly);
|
|
2864
|
+
const allEarly = runGuard(['exit', 'archive'], dir);
|
|
2865
|
+
assertExit(allEarly, 1);
|
|
2866
|
+
assertOut(allEarly, '工件目录缺失');
|
|
2867
|
+
assertNotOut(allEarly, 'ALL CHECKS PASSED');
|
|
2702
2868
|
// ⑤ 扫描份数的**类型**在写入前就拦(in-place 扩展):scanned 是出口按**数值**比对的字段
|
|
2703
2869
|
// (份数相等才算留痕成立),故字符串 "2" 必须被 record 拒。修复前它能落库成功、要等到 archive
|
|
2704
2870
|
// 出口才因 "2" !== 2 炸——正是 record 形状校验要消灭的「错误延后暴露」(出错的是 record,
|
|
@@ -2717,12 +2883,45 @@ export const ENTRIES = [
|
|
|
2717
2883
|
'类型非法的载荷不得落库: ' + JSON.stringify(afterReject.evidence.archive));
|
|
2718
2884
|
// 反向构造(单变量:只把 "2" 改成 2):同一载荷 record 通过并原样写入——判据只判类型,
|
|
2719
2885
|
// 不新增业务规则,合法载荷不因这条形状校验变得不可写。
|
|
2886
|
+
writeNodeDeclarationMarkers(dir, 'archive');
|
|
2720
2887
|
const numericScanned = runState(['record', 'archive',
|
|
2721
2888
|
'{"summary":"archived","lessonsNomination":{"scanned":2,"nominated":[],"reasonIfNone":"无新增条目"}}'], dir);
|
|
2722
2889
|
assertExit(numericScanned, 0);
|
|
2723
2890
|
const afterAccept = JSON.parse(fs.readFileSync(path.join(dir, '.flow-comet', 'flow-comet-state.json'), 'utf8'));
|
|
2724
2891
|
assertTrue(afterAccept.evidence.archive.lessonsNomination?.scanned === 2,
|
|
2725
2892
|
'类型合法的载荷应原样写入 scanned: ' + JSON.stringify(afterAccept.evidence.archive));
|
|
2893
|
+
// ⑥ 提名恢复命令可照抄(in-place 扩展):拒绝面必须给**可执行**的命令——脚本路径由唯一装配
|
|
2894
|
+
// (state-explain 的 scriptCommand)平台化拼出、并带本次运行的协议上下文。断言不看「像不像
|
|
2895
|
+
// 命令」,而是把它从报文里解析出来**真执行**:裸脚本名(workflow-state.mjs …)在这一步是
|
|
2896
|
+
// command not found,照抄即失败。
|
|
2897
|
+
setupArchive(dir, { evidence: {} }); // 只有 summary,缺 lessonsNomination
|
|
2898
|
+
const missingNomination = runGuard(['exit', 'archive'], dir);
|
|
2899
|
+
assertExit(missingNomination, 1);
|
|
2900
|
+
assertOut(missingNomination, 'lessonsNomination');
|
|
2901
|
+
const nominationRecoveryStart = missingNomination.output.lastIndexOf('恢复:');
|
|
2902
|
+
const nominationRecovery = nominationRecoveryStart < 0
|
|
2903
|
+
? ''
|
|
2904
|
+
: missingNomination.output.slice(nominationRecoveryStart);
|
|
2905
|
+
const nominationRecordCommand =
|
|
2906
|
+
(nominationRecovery.match(/^\s*(node "[^"]+" record archive [^\n]*)$/m) || [])[1];
|
|
2907
|
+
assertTrue(typeof nominationRecordCommand === 'string',
|
|
2908
|
+
'提名门的恢复段缺可解析的 record 命令(裸脚本名不可照抄):\n' + missingNomination.output);
|
|
2909
|
+
installSkillTreeCopy(dir, path.join('.claude', 'skills'));
|
|
2910
|
+
const nominationRecorded = runPrintedCommand(nominationRecordCommand, dir, {
|
|
2911
|
+
FLOW_COMET_RUN_ROOT: dir,
|
|
2912
|
+
FLOW_COMET_PROTOCOL: '',
|
|
2913
|
+
});
|
|
2914
|
+
assertTrue(nominationRecorded.status === 0,
|
|
2915
|
+
'照抄的提名恢复命令跑不通\n 命令: ' + nominationRecordCommand
|
|
2916
|
+
+ '\n exit ' + nominationRecorded.status + '\n' + nominationRecorded.output);
|
|
2917
|
+
const nominationState = JSON.parse(
|
|
2918
|
+
fs.readFileSync(path.join(dir, '.flow-comet', 'flow-comet-state.json'), 'utf8'));
|
|
2919
|
+
assertTrue(nominationState.evidence.archive.lessonsNomination?.scanned === 2,
|
|
2920
|
+
'照抄恢复命令后应按该 change 的 SUMMARY 份数落盘 scanned: '
|
|
2921
|
+
+ JSON.stringify(nominationState.evidence.archive));
|
|
2922
|
+
const nominationExit = runGuard(['exit', 'archive'], dir);
|
|
2923
|
+
assertExit(nominationExit, 0);
|
|
2924
|
+
assertOut(nominationExit, 'ALL CHECKS PASSED');
|
|
2726
2925
|
},
|
|
2727
2926
|
},
|
|
2728
2927
|
|
|
@@ -2811,7 +3010,7 @@ export const ENTRIES = [
|
|
|
2811
3010
|
assertOut(ctxFenced, 'INIT-DONE');
|
|
2812
3011
|
assertNotOut(ctxFenced, 'INIT-VALIDATE-FAILED');
|
|
2813
3012
|
writeFile(ctxRoot, '.specs/CONTEXT.md', contextDoc(true));
|
|
2814
|
-
const ctxFencedOnly = runState(['init', CHANGE_ID + '-ctx2', '--init-context'], ctxRoot);
|
|
3013
|
+
const ctxFencedOnly = runState(['init', CHANGE_ID + '-ctx2', '--init-context', '--replace', CHANGE_ID + '-ctx', '--reason', '验证段内围栏示例判定'], ctxRoot);
|
|
2815
3014
|
assertExit(ctxFencedOnly, 0);
|
|
2816
3015
|
assertOut(ctxFencedOnly, 'INIT-VALIDATE-FAILED');
|
|
2817
3016
|
assertOut(ctxFencedOnly, 'evolve 元数据');
|
|
@@ -3577,7 +3776,6 @@ export const ENTRIES = [
|
|
|
3577
3776
|
writeState(cwdRepo, {
|
|
3578
3777
|
...baseState('open'),
|
|
3579
3778
|
activeChange: 'live-change',
|
|
3580
|
-
newChange: true,
|
|
3581
3779
|
status: 'running',
|
|
3582
3780
|
enteredNodes: ['open'],
|
|
3583
3781
|
evidence: {
|
|
@@ -3652,7 +3850,10 @@ export const ENTRIES = [
|
|
|
3652
3850
|
// ⑤ 反向构造(同一夹具、去掉变量):解析退回进程 cwd —— 上面「cwd 零改动」三条断言正是会红的
|
|
3653
3851
|
// 那三条;这里直接证明夹具确实能把 cwd 侧改写照出来(不是恒绿)。
|
|
3654
3852
|
const envRootStateBefore = stateBytesAt(envRoot);
|
|
3655
|
-
|
|
3853
|
+
// 反向构造同样要过覆盖闸门:cwd 侧本就有在途 change(live-change),显式 --replace 让它放行并
|
|
3854
|
+
// 留档——本格要证的是「state 落在了哪个根」,不是「闸门要不要拦」(那是另一格的面)。
|
|
3855
|
+
const noRootInit = asRes(spawnSync(process.execPath,
|
|
3856
|
+
[STATE, 'init', 'cwd-change', '--replace', 'live-change', '--reason', '反向构造:证明无变量时写回进程 cwd'], {
|
|
3656
3857
|
cwd: cwdRepo,
|
|
3657
3858
|
env: {
|
|
3658
3859
|
...process.env,
|
|
@@ -3939,6 +4140,27 @@ export const ENTRIES = [
|
|
|
3939
4140
|
// 形态分派自身的常驻判别力锚:临时根上驱动同一判定,分派对错不再只能靠「在包形态里整跑一次
|
|
3940
4141
|
// 套件」才知道。夹具的「完整形态」从本检出的公开面真迹复制,故只在声明了公开面的检出上跑。
|
|
3941
4142
|
await assertPublicFaceSelfCheckShapes(dir);
|
|
4143
|
+
// 夹具预检的 in-place 判别力锚:给 shape 自检一个缺全部受检面文件的源根,真实预检必须逐份
|
|
4144
|
+
// 点名并抛「形态自检夹具无法构造」。把预检从 shape 自检里拿掉,这里就会看到「没有抛错」而红——
|
|
4145
|
+
// 这是本探针唯一要证明的行为(只测 helper 的清单会把实现删掉仍留绿)。
|
|
4146
|
+
const truncatedFixtureRoot = path.join(dir, 'face-truncated');
|
|
4147
|
+
fs.mkdirSync(truncatedFixtureRoot, { recursive: true });
|
|
4148
|
+
let fixturePreflightError = null;
|
|
4149
|
+
try {
|
|
4150
|
+
await assertPublicFaceSelfCheckShapes(path.join(dir, 'face-preflight'), { repoRoot: truncatedFixtureRoot });
|
|
4151
|
+
} catch (error) {
|
|
4152
|
+
fixturePreflightError = error;
|
|
4153
|
+
}
|
|
4154
|
+
const fixturePreflightMessage = fixturePreflightError ? String(fixturePreflightError.message) : '';
|
|
4155
|
+
if (!fixturePreflightMessage.includes('形态自检夹具无法构造')) {
|
|
4156
|
+
throw new Error('形态预检在缺文件的源根上没有抛「形态自检夹具无法构造」(拿掉预检的回归): '
|
|
4157
|
+
+ (fixturePreflightMessage || '没有抛错'));
|
|
4158
|
+
}
|
|
4159
|
+
for (const rel of ['README-zh.md', 'CONTRIBUTING-zh.md']) {
|
|
4160
|
+
if (!fixturePreflightMessage.includes(rel)) {
|
|
4161
|
+
throw new Error('形态预检没有逐份点名缺席文件 ' + rel + ':' + fixturePreflightMessage);
|
|
4162
|
+
}
|
|
4163
|
+
}
|
|
3942
4164
|
// 判据面完整在册(缺席用 null 占位而不是从集合里删掉):缺席由下面的缺席判据逐份点名,
|
|
3943
4165
|
// 「少了哪份文件」因此是**判据事实**,不是可以静默缩小的受检面。
|
|
3944
4166
|
const docs = new Map();
|
|
@@ -4049,7 +4271,9 @@ export const ENTRIES = [
|
|
|
4049
4271
|
'docs/internal/DOC-CHECKLIST.md',
|
|
4050
4272
|
'docs/internal/ROADMAP.md',
|
|
4051
4273
|
];
|
|
4052
|
-
|
|
4274
|
+
// 以箭头函数传参:本函数带可选的根参数,直接把函数名交给 filter 会把下标当成 root,
|
|
4275
|
+
// 在 path.join 处以「Received type number」崩掉(同形调用点一律显式包一层)。
|
|
4276
|
+
const present = maintainerDocs.filter((rel) => repoFileExists(rel));
|
|
4053
4277
|
if (present.length !== maintainerDocs.length) {
|
|
4054
4278
|
console.log('SKIP: 治理落盘判据——docs/internal/ 维护者面缺席(' + maintainerDocs.filter((rel) => !repoFileExists(rel)).join('、')
|
|
4055
4279
|
+ ');本次检出未校验该面,请回维护者主树重跑');
|
|
@@ -4097,4 +4321,101 @@ export const ENTRIES = [
|
|
|
4097
4321
|
if (problems.length > 0) throw new Error('治理落盘不符: ' + problems.join('; '));
|
|
4098
4322
|
},
|
|
4099
4323
|
},
|
|
4324
|
+
// 352 号场景:归档后交接协议页(分发参考册)的文本锚。这一步没有脚本可跑,协议页就是行为唯一
|
|
4325
|
+
// 的可判载体——要素在场且成序,才谈得上「每批都按同一套流程交接」。
|
|
4326
|
+
// ① 段序(触发 → 探测 → 一次询问 → 展示 → 降级)② 四选项 ③ 固定探测命令块
|
|
4327
|
+
// ④ 降级两件套且不声明已创建 ⑤ 不写状态 ⑥ 公开草稿视角(七段 + 第一遍读 + 0 命中)
|
|
4328
|
+
// ⑦ 本地 roadmap 结构(索引七列 + 每条六段)⑧ 步骤权威声明在场(页内以归档册为准)。
|
|
4329
|
+
// 判据与探针**共用同一函数**(handoffPageProblems):原页零问题(判据不恒真);抽掉任一条锚点
|
|
4330
|
+
// ⇒ 必报它自己那句;把降级段提到最前 ⇒ 必报段序颠倒;状态文件写成肯定句 ⇒ 必报、写成否定句 ⇒ 不报。
|
|
4331
|
+
{
|
|
4332
|
+
name: '352 归档后交接协议页:段序/四选项/探测命令/降级/不写状态/草稿视角/roadmap 结构(含反向构造)',
|
|
4333
|
+
run: () => {
|
|
4334
|
+
const page = fs.readFileSync(
|
|
4335
|
+
path.join(SCRIPTS_DIR, '..', 'reference', 'post-archive-handoff.md'), 'utf8');
|
|
4336
|
+
const problems = handoffPageProblems(page);
|
|
4337
|
+
// 正向探针:每条锚点抽掉后必须报出**它自己那句**(完整期望片段比对——「报了别的问题」
|
|
4338
|
+
// 不算判别力)。抽掉的落点用同一个标记串,便于一眼看出探针动过哪里。
|
|
4339
|
+
const probes = [
|
|
4340
|
+
['段序(触发段)', '## 触发与顺序', '缺段「## 触发与顺序」(触发)'],
|
|
4341
|
+
['段序(降级段)', '## 降级与失败', '缺段「## 降级与失败」(降级)'],
|
|
4342
|
+
['四选项(本地 roadmap 行)', '| 本地 roadmap | 写进项目自己的路线图文件(索引 + 每条一份文件) |',
|
|
4343
|
+
'缺载体选项行「| 本地 roadmap | 写进项目自己的路线图文件(索引 + 每条一份文件) |」'],
|
|
4344
|
+
['探测(工作树判定)', 'git rev-parse --is-inside-work-tree',
|
|
4345
|
+
'缺探测命令「git rev-parse --is-inside-work-tree」'],
|
|
4346
|
+
['探测(remote 分类)', 'git remote get-url origin', '缺探测命令「git remote get-url origin」'],
|
|
4347
|
+
['探测(认证状态)', 'glab auth status --hostname', '缺探测命令「glab auth status --hostname」'],
|
|
4348
|
+
['降级两件套', '内容 + 命令', '缺降级要素「内容 + 命令」'],
|
|
4349
|
+
['降级不声明已创建', '不声明已创建', '缺降级要素「不声明已创建」'],
|
|
4350
|
+
['草稿七段(第 7 段)', '7. 未验证', '缺草稿骨架「7. 未验证」'],
|
|
4351
|
+
['草稿视角(第一遍读)', '第一遍读', '缺草稿视角「第一遍读」'],
|
|
4352
|
+
['草稿视角(0 命中)', '0 命中', '缺草稿视角「0 命中」'],
|
|
4353
|
+
['roadmap 索引七列', '索引七列', '缺 roadmap 索引结构「索引七列」'],
|
|
4354
|
+
['roadmap 每条六段', '每条六段', '缺 roadmap 条目结构「每条六段」'],
|
|
4355
|
+
['步骤权威(归档册)', '步骤权威', '缺步骤权威声明「步骤权威」'],
|
|
4356
|
+
];
|
|
4357
|
+
for (const [label, needle, expected] of probes) {
|
|
4358
|
+
if (!page.includes(needle)) {
|
|
4359
|
+
problems.push('反向构造前提失效(' + label + '):协议页本就不含「' + needle + '」');
|
|
4360
|
+
continue;
|
|
4361
|
+
}
|
|
4362
|
+
const stripped = page.split(needle).join('(反向构造:抽掉)');
|
|
4363
|
+
if (!handoffPageProblems(stripped).includes(expected)) {
|
|
4364
|
+
problems.push('反向构造判别力缺失(' + label + ':抽掉「' + needle + '」未被判「' + expected + '」)');
|
|
4365
|
+
}
|
|
4366
|
+
}
|
|
4367
|
+
// 段序的判别力不能只靠「段没了」证:把降级段提到最前,判据必须报乱序而不是当缺段。
|
|
4368
|
+
const reordered = '## 降级与失败\n' + page;
|
|
4369
|
+
if (!handoffPageProblems(reordered).some((problem) => problem.startsWith('段序颠倒'))) {
|
|
4370
|
+
problems.push('反向构造判别力缺失(降级段提到最前未被判段序颠倒)');
|
|
4371
|
+
}
|
|
4372
|
+
// 状态边界的方向性:判据读语义、不认固定串——肯定句必报,否定句不报(两向都构造)。
|
|
4373
|
+
const stateClaim = '- 写入 `' + HANDOFF_PAGE_STATE_FILE + '` 记住本批选择。';
|
|
4374
|
+
const stateDenial = '- 不写 `' + HANDOFF_PAGE_STATE_FILE + '`,也不新增字段。';
|
|
4375
|
+
const claimed = handoffPageProblems(page + '\n' + stateClaim);
|
|
4376
|
+
if (!claimed.some((problem) => problem.startsWith('状态文件出现在肯定语境'))) {
|
|
4377
|
+
problems.push('反向构造判别力缺失(状态文件出现在肯定语境未被判违规)');
|
|
4378
|
+
}
|
|
4379
|
+
const denied = handoffPageProblems(page + '\n' + stateDenial);
|
|
4380
|
+
if (denied.length > 0) {
|
|
4381
|
+
problems.push('反向构造误报(否定句「不写 <状态文件>」被判成状态写入): ' + denied.join('; '));
|
|
4382
|
+
}
|
|
4383
|
+
// 混合句:句子里有「写 state」也有别处的否定——否定必须就近落在这次写入上。
|
|
4384
|
+
const stateMixed = '- 写入 `' + HANDOFF_PAGE_STATE_FILE + '`,不新增字段。';
|
|
4385
|
+
const mixed = handoffPageProblems(page + '\n' + stateMixed);
|
|
4386
|
+
if (!mixed.some((problem) => problem.startsWith('状态文件出现在肯定语境'))) {
|
|
4387
|
+
problems.push('反向构造判别力缺失(混合句「写入 state,不新增字段」未被判违规)');
|
|
4388
|
+
}
|
|
4389
|
+
// 前置子句的否定同样不能替状态写入开脱。
|
|
4390
|
+
const stateMasked = '- 不写报告,但写入 `' + HANDOFF_PAGE_STATE_FILE + '`。';
|
|
4391
|
+
const masked = handoffPageProblems(page + '\n' + stateMasked);
|
|
4392
|
+
if (!masked.some((problem) => problem.startsWith('状态文件出现在肯定语境'))) {
|
|
4393
|
+
problems.push('反向构造判别力缺失(前置子句的否定掩盖了状态写入)');
|
|
4394
|
+
}
|
|
4395
|
+
// 四选项的判别力不能靠「词还在别处」:整张选项表删掉也必须红(推荐矩阵里同样有这四个词)。
|
|
4396
|
+
{
|
|
4397
|
+
const tableStart = page.indexOf('| 选项 | 说明 |');
|
|
4398
|
+
const tableEndIndex = page.indexOf('| 暂不处理 |');
|
|
4399
|
+
if (tableStart < 0 || tableEndIndex < tableStart) {
|
|
4400
|
+
problems.push('反向构造前提失效(找不到载体选项表)');
|
|
4401
|
+
} else {
|
|
4402
|
+
const endOfRow = page.indexOf('\n', tableEndIndex);
|
|
4403
|
+
const withoutTable = page.slice(0, tableStart) + page.slice(endOfRow + 1);
|
|
4404
|
+
if (!handoffPageProblems(withoutTable).some((problem) => problem.startsWith('缺载体选项行'))) {
|
|
4405
|
+
problems.push('反向构造判别力缺失(整张载体选项表被删未被判缺选项)');
|
|
4406
|
+
}
|
|
4407
|
+
}
|
|
4408
|
+
}
|
|
4409
|
+
// 误伤侧:句首否定与「路径之后」的否定都是自然写法,不得判违规(两个方向都要锁)。
|
|
4410
|
+
const leadingNegation = '- **不写状态文件**(`' + HANDOFF_PAGE_STATE_FILE + '`):不写入、不改写。';
|
|
4411
|
+
const trailingNegation = '- `' + HANDOFF_PAGE_STATE_FILE + '` 只读,不写入。';
|
|
4412
|
+
for (const [label, line] of [['句首否定', leadingNegation], ['路径后否定', trailingNegation]]) {
|
|
4413
|
+
const found = handoffPageProblems(page + '\n' + line);
|
|
4414
|
+
if (found.some((problem) => problem.startsWith('状态文件出现在肯定语境'))) {
|
|
4415
|
+
problems.push('反向构造误报(' + label + '形态被判成状态写入): ' + line);
|
|
4416
|
+
}
|
|
4417
|
+
}
|
|
4418
|
+
if (problems.length > 0) throw new Error('归档后交接协议页不符: ' + problems.join('; '));
|
|
4419
|
+
},
|
|
4420
|
+
},
|
|
4100
4421
|
];
|
|
@@ -123,8 +123,6 @@ export const STATE_FIELD_VALIDATORS = [
|
|
|
123
123
|
{ field: 'taskHash', check: (v) => typeof v === 'string' || v === undefined },
|
|
124
124
|
// M1: 节点进入标记(entry 写入,exit 检测未 entry;旧 state 缺失放行)
|
|
125
125
|
{ field: 'enteredNodes', check: (v) => (Array.isArray(v) && v.every((x) => typeof x === 'string')) || v === undefined || v === null },
|
|
126
|
-
// R6: 新 change 标记(init 写入 true——新旧判定的确定性依据,不依赖 entry;旧 state 缺失 = 旧 change 渐进兼容)
|
|
127
|
-
{ field: 'newChange', check: (v) => v === true || v === undefined || v === null },
|
|
128
126
|
// 分支模式与 PR 审查开关字段(readState 默认补后类型校验;旧 state 缺失字段放行)
|
|
129
127
|
{ field: 'branchMode', check: (v) => typeof v === 'boolean' },
|
|
130
128
|
{ field: 'enablePrReview', check: (v) => typeof v === 'boolean' },
|