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.
Files changed (107) hide show
  1. package/.flow-comet/skills/flow-comet/INSTALLED_VERSION +1 -1
  2. package/.flow-comet/skills/flow-comet/SKILL.md +64 -46
  3. package/.flow-comet/skills/flow-comet/reference/KNOWN-ISSUES-template.md +1 -1
  4. package/.flow-comet/skills/flow-comet/reference/commit-discipline.md +32 -0
  5. package/.flow-comet/skills/flow-comet/reference/dirty-worktree.md +1 -1
  6. package/.flow-comet/skills/flow-comet/{GUIDANCE.md → reference/entry-detail.md} +18 -28
  7. package/.flow-comet/skills/flow-comet/reference/fix-loop.md +57 -0
  8. package/.flow-comet/skills/flow-comet/reference/platform-facts.md +58 -0
  9. package/.flow-comet/skills/flow-comet/reference/replan.md +23 -0
  10. package/.flow-comet/skills/flow-comet/scripts/comet-check.mjs +5 -4
  11. package/.flow-comet/skills/flow-comet/scripts/comet-hook-guard.mjs +266 -25
  12. package/.flow-comet/skills/flow-comet/scripts/context-init.mjs +2 -2
  13. package/.flow-comet/skills/flow-comet/scripts/evolve.mjs +6 -6
  14. package/.flow-comet/skills/flow-comet/scripts/guard-self-test.mjs +67 -16325
  15. package/.flow-comet/skills/flow-comet/scripts/health.mjs +1 -1
  16. package/.flow-comet/skills/flow-comet/scripts/items/a.mjs +1030 -0
  17. package/.flow-comet/skills/flow-comet/scripts/items/b.mjs +830 -0
  18. package/.flow-comet/skills/flow-comet/scripts/items/c.mjs +781 -0
  19. package/.flow-comet/skills/flow-comet/scripts/items/d.mjs +99 -0
  20. package/.flow-comet/skills/flow-comet/scripts/items/e.mjs +185 -0
  21. package/.flow-comet/skills/flow-comet/scripts/items/f.mjs +90 -0
  22. package/.flow-comet/skills/flow-comet/scripts/items/g.mjs +59 -0
  23. package/.flow-comet/skills/flow-comet/scripts/items/h.mjs +815 -0
  24. package/.flow-comet/skills/flow-comet/scripts/items/i.mjs +77 -0
  25. package/.flow-comet/skills/flow-comet/scripts/items/j.mjs +75 -0
  26. package/.flow-comet/skills/flow-comet/scripts/items/k.mjs +1427 -0
  27. package/.flow-comet/skills/flow-comet/scripts/items/l.mjs +275 -0
  28. package/.flow-comet/skills/flow-comet/scripts/items/m.mjs +614 -0
  29. package/.flow-comet/skills/flow-comet/scripts/lib/count-derivation.mjs +97 -0
  30. package/.flow-comet/skills/flow-comet/scripts/lib/fix-loop-node.mjs +196 -0
  31. package/.flow-comet/skills/flow-comet/scripts/lib/guard-evidence-gates.mjs +553 -0
  32. package/.flow-comet/skills/flow-comet/scripts/lib/guard-gates.mjs +837 -0
  33. package/.flow-comet/skills/flow-comet/scripts/lib/guard-routing.mjs +404 -0
  34. package/.flow-comet/skills/flow-comet/scripts/lib/guard-state-io.mjs +404 -0
  35. package/.flow-comet/skills/flow-comet/scripts/lib/guard-template-fidelity.mjs +302 -0
  36. package/.flow-comet/skills/flow-comet/scripts/lib/guard-uidesign.mjs +133 -0
  37. package/.flow-comet/skills/flow-comet/scripts/lib/reentry-node.mjs +237 -0
  38. package/.flow-comet/skills/flow-comet/scripts/lib/replan-node.mjs +209 -0
  39. package/.flow-comet/skills/flow-comet/scripts/lib/state-branch.mjs +49 -0
  40. package/.flow-comet/skills/flow-comet/scripts/lib/state-bridgecheck.mjs +201 -0
  41. package/.flow-comet/skills/flow-comet/scripts/lib/state-commands-admin.mjs +141 -0
  42. package/.flow-comet/skills/flow-comet/scripts/lib/state-commands-flow.mjs +700 -0
  43. package/.flow-comet/skills/flow-comet/scripts/lib/state-commands-recovery.mjs +578 -0
  44. package/.flow-comet/skills/flow-comet/scripts/lib/state-determine.mjs +52 -0
  45. package/.flow-comet/skills/flow-comet/scripts/lib/state-evolve-hint.mjs +55 -0
  46. package/.flow-comet/skills/flow-comet/scripts/lib/state-explain.mjs +106 -0
  47. package/.flow-comet/skills/flow-comet/scripts/lib/state-intelscan.mjs +58 -0
  48. package/.flow-comet/skills/flow-comet/scripts/lib/state-io.mjs +147 -0
  49. package/.flow-comet/skills/flow-comet/scripts/lib/state-skillmarkers.mjs +189 -0
  50. package/.flow-comet/skills/flow-comet/scripts/lib/system-fixtures.mjs +1441 -0
  51. package/.flow-comet/skills/flow-comet/scripts/lib/task-graph.mjs +471 -0
  52. package/.flow-comet/skills/flow-comet/scripts/lib/test-assertions.mjs +509 -0
  53. package/.flow-comet/skills/flow-comet/scripts/lib/test-fixtures.mjs +1228 -0
  54. package/.flow-comet/skills/flow-comet/scripts/lib/test-helpers.mjs +237 -0
  55. package/.flow-comet/skills/flow-comet/scripts/lib/text-anchor-checks.mjs +2484 -0
  56. package/.flow-comet/skills/flow-comet/scripts/protocol-utils.mjs +2 -2
  57. package/.flow-comet/skills/flow-comet/scripts/route-node.mjs +73 -1077
  58. package/.flow-comet/skills/flow-comet/scripts/scenarios/a.mjs +966 -0
  59. package/.flow-comet/skills/flow-comet/scripts/scenarios/b.mjs +1233 -0
  60. package/.flow-comet/skills/flow-comet/scripts/scenarios/c.mjs +1382 -0
  61. package/.flow-comet/skills/flow-comet/scripts/scenarios/d.mjs +483 -0
  62. package/.flow-comet/skills/flow-comet/scripts/scenarios/e.mjs +1388 -0
  63. package/.flow-comet/skills/flow-comet/scripts/scenarios/f.mjs +1466 -0
  64. package/.flow-comet/skills/flow-comet/scripts/scenarios/g.mjs +1364 -0
  65. package/.flow-comet/skills/flow-comet/scripts/scenarios/h.mjs +1287 -0
  66. package/.flow-comet/skills/flow-comet/scripts/scenarios/i.mjs +1436 -0
  67. package/.flow-comet/skills/flow-comet/scripts/scenarios/j.mjs +1384 -0
  68. package/.flow-comet/skills/flow-comet/scripts/scenarios/k.mjs +1338 -0
  69. package/.flow-comet/skills/flow-comet/scripts/scenarios/l.mjs +1484 -0
  70. package/.flow-comet/skills/flow-comet/scripts/scenarios/m.mjs +971 -0
  71. package/.flow-comet/skills/flow-comet/scripts/state-schema.mjs +14 -1
  72. package/.flow-comet/skills/flow-comet/scripts/system-test.mjs +58 -6692
  73. package/.flow-comet/skills/flow-comet/scripts/time-utils.mjs +4 -4
  74. package/.flow-comet/skills/flow-comet/scripts/workflow-guard.mjs +151 -2428
  75. package/.flow-comet/skills/flow-comet/scripts/workflow-handoff.mjs +116 -9
  76. package/.flow-comet/skills/flow-comet/scripts/workflow-state.mjs +29 -2086
  77. package/.flow-comet/skills/flow-comet-archive/SKILL.md +10 -19
  78. package/.flow-comet/skills/flow-comet-change/SKILL.md +2 -3
  79. package/.flow-comet/skills/flow-comet-compose/SKILL.md +1 -1
  80. package/.flow-comet/skills/flow-comet-design/SKILL.md +6 -6
  81. package/.flow-comet/skills/flow-comet-execute/SKILL.md +58 -16
  82. package/.flow-comet/skills/flow-comet-integration/SKILL.md +8 -5
  83. package/.flow-comet/skills/flow-comet-open/SKILL.md +5 -1
  84. package/.flow-comet/skills/flow-comet-plan/GUIDANCE.md +1 -1
  85. package/.flow-comet/skills/flow-comet-plan/SKILL.md +8 -8
  86. package/.flow-comet/skills/flow-comet-review/SKILL.md +9 -12
  87. package/.flow-comet/skills/flow-comet-subagent-execute/SKILL.md +59 -16
  88. package/.flow-comet/skills/flow-comet-task/SKILL.md +3 -2
  89. package/.flow-comet/skills/flow-comet-ui-design/SKILL.md +3 -3
  90. package/.flow-comet/skills/flow-comet-verify/SKILL.md +8 -17
  91. package/README.md +53 -70
  92. package/package.json +3 -2
  93. package/scripts/dsh-bridge.mjs +59 -26
  94. package/scripts/lib/installer-cleanup.mjs +152 -0
  95. package/scripts/lib/installer-flowkit.mjs +119 -0
  96. package/scripts/lib/installer-hooks.mjs +363 -0
  97. package/scripts/lib/installer-loader.mjs +220 -0
  98. package/scripts/lib/installer-migrate.mjs +236 -0
  99. package/scripts/lib/installer-platforms.mjs +314 -0
  100. package/scripts/prepare-env.mjs +36 -1164
  101. package/.flow-comet/skills/flow-comet/reference/TEST-MATRIX.md +0 -116
  102. package/.flow-comet/skills/flow-comet/reference/composition-report.md +0 -65
  103. package/.flow-comet/skills/flow-comet/reference/dsh-platform.md +0 -184
  104. package/.flow-comet/skills/flow-comet/reference/resolved-skills.json +0 -661
  105. package/.flow-comet/skills/flow-comet/reference/skill-review.md +0 -13
  106. package/.flow-comet/skills/flow-comet/reference/subagents/script-author.md +0 -7
  107. package/.flow-comet/skills/flow-comet/reference/worktree-notes.md +0 -70
@@ -0,0 +1,971 @@
1
+ // 场景组 m — 侧命令边界与单一来源锚 · 文本锚与漂移判据
2
+ // 元素形态:`{ name, run }`;计数由 `lib/count-derivation.mjs` 从本目录聚合,不手抄数字。
3
+ // 组界按场景名前缀与文件内既有分段划,与入口 `SCENARIOS` 的拼接顺序一致。
4
+
5
+ import fs from 'fs';
6
+ import path from 'path';
7
+ import { execFileSync } from 'child_process';
8
+ import {
9
+ assertEqual,
10
+ assertExit,
11
+ assertNotOut,
12
+ assertOut,
13
+ assertTrue,
14
+ baseState,
15
+ cleanupTmpDir,
16
+ writeFile,
17
+ writeState,
18
+ } from '../lib/test-helpers.mjs';
19
+ import {
20
+ CHANGE_ID,
21
+ REPO_ROOT,
22
+ SCRIPTS_DIR,
23
+ SIDE_CONTEXT_SCAN,
24
+ SIDE_EVOLVE,
25
+ SIDE_HEALTH,
26
+ contextInitModule,
27
+ copyEngineTree,
28
+ engineDefinitionHits,
29
+ engineReachableFrom,
30
+ engineScriptFiles,
31
+ hasNamedImport,
32
+ makeTmp,
33
+ requireModuleExport,
34
+ runSideScript,
35
+ skillsRootForScriptsDir,
36
+ sleepSync,
37
+ stateSchemaModule,
38
+ timeUtilsModule,
39
+ } from '../lib/test-fixtures.mjs';
40
+ import {
41
+ assertStateBytesUnchanged,
42
+ readStateBytes,
43
+ runStateWithProtocol,
44
+ } from '../lib/test-assertions.mjs';
45
+ import {
46
+ BACKUP_IMPL_FACE,
47
+ BARE_ISO_ENGINE_WHITELIST,
48
+ BARE_ISO_SIDE_COMMANDS,
49
+ INTEL_FIELD_SUFFIX,
50
+ INTEL_FIELD_VALUE,
51
+ OVERRIDE_FALLBACK_RE,
52
+ TIME_DISCIPLINE_RULES,
53
+ bareIsoTimestampHits,
54
+ bareIsoWhitelistProblems,
55
+ contextFixtureText,
56
+ crlfLineViolations,
57
+ dateContentMatchHits,
58
+ datePrefixRegexpHits,
59
+ deterministicReproProblems,
60
+ evolveReportBulletProblems,
61
+ healthReportFixture,
62
+ healthReportWithSnapshot,
63
+ inlineBackupHits,
64
+ intelFieldToken,
65
+ intelMetadataNameDeclarations,
66
+ intelMetadataNameProblems,
67
+ maintainerFacePresent,
68
+ overrideDeclarationBlock,
69
+ overrideDeclarationProblems,
70
+ snapshotEntryCount,
71
+ snapshotSectionOf,
72
+ timeDisciplineTextProblems,
73
+ upstreamArtifactPaths,
74
+ } from '../lib/text-anchor-checks.mjs';
75
+
76
+ export const ENTRIES = [
77
+
78
+ // 295: health 基线日期判据单源——报告名的「日期前缀 + 日历自洽」判定收敛到 time-utils
79
+ //(真实消费 `archiveDateFromName`),本模块不再自写前缀正则:日历不自洽的
80
+ // `2026-02-30-HEALTH.md` 不再被采作基线(旧实现单独在场时直接采作基线、并输出看似有据的
81
+ // ↑/↓ 趋势;与合法旧报告并存时又因「取排序最后一份」必然取到它)。判据面配**合成目录
82
+ // 反向构造**:第二份前缀正则丢进合成引擎目录必须被检出(证明形态判据不恒真空过)。
83
+ {
84
+ name: '295 health 基线日期判据单源:日历不自洽前缀不入选·合法旧报告入选 + 零自写前缀正则',
85
+ run: (dir) => {
86
+ writeFile(dir, '.specs/CONTEXT.md', contextFixtureText());
87
+ writeState(dir, baseState('open'));
88
+
89
+ // ① 负例:前缀形态合法、日历不自洽(2026-02-30 不存在)——不得被采作基线。快照哨兵
90
+ // `lessons.entries=123456` 一旦出现在输出里,即证明这份报告被当成了基线。
91
+ writeFile(dir, '.specs/health/2026-02-30-HEALTH.md', healthReportFixture('2026-02-30', 123456));
92
+ const invalidOnly = runSideScript(SIDE_HEALTH, ['--root', dir, '--stdout'], dir);
93
+ assertExit(invalidOnly, 0);
94
+ assertOut(invalidOnly, '基线:无(`.specs/health` 下无日期不同的历史报告)');
95
+ assertNotOut(invalidOnly, '2026-02-30-HEALTH.md');
96
+ assertNotOut(invalidOnly, '123456');
97
+
98
+ // ② 正例 + 越界:合法旧报告与日历不自洽者并存 → 取合法那份(日历不自洽的名字排序在后,
99
+ // 旧实现「取最后一份」必然取到它 → 哨兵串成 123456 而非 999999)
100
+ writeFile(dir, '.specs/health/2026-01-05-HEALTH.md', healthReportFixture('2026-01-05', 999999));
101
+ const picked = runSideScript(SIDE_HEALTH, ['--root', dir, '--stdout'], dir);
102
+ assertExit(picked, 0);
103
+ assertOut(picked, '基线:`.specs/health/2026-01-05-HEALTH.md`');
104
+ assertOut(picked, '`lessons.entries`:999999 → ');
105
+ assertNotOut(picked, '2026-02-30-HEALTH.md');
106
+ assertNotOut(picked, '123456');
107
+
108
+ // ③ 结构锚:health 真实消费 time-utils 的日期判定;收敛面内只许 time-utils 表达该形态
109
+ const healthText = fs.readFileSync(SIDE_HEALTH, 'utf8');
110
+ assertTrue(hasNamedImport(healthText, './time-utils.mjs', 'archiveDateFromName'),
111
+ 'health.mjs 未从 time-utils.mjs 具名 import archiveDateFromName(日期判据第二份表达)');
112
+ assertTrue(healthText.includes('archiveDateFromName('),
113
+ 'health.mjs 未真实消费 archiveDateFromName(单一权威应被调用)');
114
+ const faceHits = datePrefixRegexpHits(SCRIPTS_DIR);
115
+ const contentMatchHits = dateContentMatchHits(SCRIPTS_DIR);
116
+ assertEqual(contentMatchHits.length, 1,
117
+ '归档日志日期条目匹配(文档内容面)应恰一处,实际 ' + JSON.stringify(contentMatchHits));
118
+ assertEqual(contentMatchHits[0].count, 2, '归档日志日期条目匹配处数(行锚 + 内容条目两处形态)');
119
+ const allowedDateSites = new Set(['time-utils.mjs', contentMatchHits[0].file]);
120
+ const unexpected = faceHits.filter((hit) => !allowedDateSites.has(hit.file));
121
+ assertEqual(unexpected.length, 0,
122
+ '日期前缀形态只许由 time-utils.mjs 表达(内容条目匹配通道除外),出现第二份实现: ' + JSON.stringify(unexpected));
123
+ assertEqual(faceHits.find((hit) => hit.file === 'time-utils.mjs')?.count, 1,
124
+ 'time-utils.mjs 内日期前缀形态处数(应恰 1 处单源表达)实际 ' + JSON.stringify(faceHits));
125
+
126
+ // ③b 边界锚(可见,不静默排除):归档日志的两处日期匹配是文档**内容**里的日期条目匹配
127
+ //(行锚 + `matchAll(.../gm)`),不是文件名前缀判定——上一步的允许集正是由**形态锚**认出的
128
+ // 这一处通道(不写文件名);它还必须在 **guard 的判定链**内(例外不许漂到无关模块),
129
+ // 形态一旦改变即变红(检出 0 处),强制重评日期前缀判据的收敛面。
130
+ const guardClosure = engineReachableFrom(['workflow-guard.mjs']);
131
+ assertTrue(guardClosure.has(contentMatchHits[0].file),
132
+ '归档日志日期条目匹配通道必须落在 guard 的判定链内(例外不许漂到无关模块): ' + contentMatchHits[0].file);
133
+
134
+ // ④ 反向构造:合成引擎目录(单份前缀正则 → 检出 1;再放第二份 → 检出 2)
135
+ const synthetic = makeTmp();
136
+ try {
137
+ writeFile(synthetic, 'single.mjs', "const REPORT_DATE_PREFIX = /^(\\d{4}-\\d{2}-\\d{2})/;\n");
138
+ assertEqual(datePrefixRegexpHits(synthetic).length, 1, '合成目录单实现检出数');
139
+ writeFile(synthetic, 'second.mjs',
140
+ "function reportDateOf(name) {\n return /^(\\d{4}-\\d{2}-\\d{2})/.exec(name);\n}\n");
141
+ assertEqual(datePrefixRegexpHits(synthetic).length, 2, '合成目录第二份实现检出数(判据须变红)');
142
+ } finally {
143
+ cleanupTmpDir(synthetic);
144
+ }
145
+ },
146
+ },
147
+
148
+ // 296: context-scan 改写 CONTEXT.md 前落备份——命名族(目标文档同目录 + `.bak-<本地日期>`)与
149
+ // 失败处置由 state-schema.mjs 的共享助手单源提供(消费关系与零内联见场景 301):备份内容 =
150
+ // 改写前版本;同日重复改写只保留一份当日备份(同名覆盖,不堆积);复制不成功时目标与 state
151
+ // 逐字节不变(备份**先于**写入,不是事后补)。
152
+ {
153
+ name: '296 context-scan 改写前落备份:同形命名·内容为改写前版本·复制失败 fail-closed 零写入',
154
+ run: (dir) => {
155
+ const contextFile = path.join(dir, '.specs', 'CONTEXT.md');
156
+ const original = contextFixtureText();
157
+ const today = requireModuleExport(timeUtilsModule, 'formatLocalDate', 'time-utils.mjs')(new Date());
158
+ writeFile(dir, '.specs/CONTEXT.md', original);
159
+ writeState(dir, baseState('open'));
160
+
161
+ // ① 改写落备份:同目录、命名族 `.bak-<日期>`、内容 = 改写前版本;双落点写入照常
162
+ const first = runSideScript(SIDE_CONTEXT_SCAN, ['--root', dir], dir);
163
+ assertExit(first, 0);
164
+ const backups = fs.readdirSync(path.join(dir, '.specs'))
165
+ .filter((name) => /^CONTEXT\.md\.bak-\d{4}-\d{2}-\d{2}$/.test(name));
166
+ assertEqual(backups.length, 1, '改写前的备份份数(应恰 1 份同目录 `.bak-<日期>`)实际 ' + JSON.stringify(backups));
167
+ assertEqual(backups[0], 'CONTEXT.md.bak-' + today, '备份命名(应为改写当日的本地日期)');
168
+ assertEqual(fs.readFileSync(path.join(dir, '.specs', backups[0]), 'utf8'), original, '备份内容应为改写前版本');
169
+ assertTrue(fs.readFileSync(contextFile, 'utf8') !== original, 'CONTEXT.md 未被改写(夹具前提不成立)');
170
+
171
+ // ② 同日再改写:同名覆盖——只保留一份当日备份,内容为该轮改写前版本(不堆积、链路不丢)
172
+ const intermediate = contextFixtureText().replace('2026-09-01T10:00:00+08:00', '2026-09-02T10:00:00+08:00');
173
+ writeFile(dir, '.specs/CONTEXT.md', intermediate);
174
+ const second = runSideScript(SIDE_CONTEXT_SCAN, ['--root', dir], dir);
175
+ assertExit(second, 0);
176
+ assertEqual(fs.readdirSync(path.join(dir, '.specs'))
177
+ .filter((name) => name.startsWith('CONTEXT.md.bak-')).length, 1, '同日重复改写的当日备份份数');
178
+ assertEqual(fs.readFileSync(path.join(dir, '.specs', backups[0]), 'utf8'), intermediate,
179
+ '第二轮的备份内容应为该轮改写前版本');
180
+
181
+ // ③ 复制不成功 → fail-closed:目标文档与 state 逐字节不变(备份先于写入,写入面不留半态)
182
+ writeFile(dir, '.specs/CONTEXT.md', original);
183
+ const stateBytes = readStateBytes(dir);
184
+ fs.rmSync(path.join(dir, '.specs', backups[0]), { force: true });
185
+ fs.mkdirSync(path.join(dir, '.specs', backups[0]));
186
+ const blocked = runSideScript(SIDE_CONTEXT_SCAN, ['--root', dir], dir);
187
+ assertExit(blocked, 1);
188
+ assertOut(blocked, 'BLOCKED');
189
+ assertEqual(fs.readFileSync(contextFile, 'utf8'), original, '备份失败的一轮改写了 CONTEXT.md');
190
+ assertStateBytesUnchanged(dir, stateBytes, '备份失败的一轮');
191
+
192
+ // ④ 命名族与失败处置的**同源**判据已随备份助手抽取移到场景 301(唯一定义 + 两消费方零内联
193
+ // + 合成反向构造):此处不重复表达同一判据,只保留上面的真实行为锚。
194
+ },
195
+ },
196
+
197
+ // 297: health 的审计行与报告落盘路径**恒输出**——报告是唯一写入面,调用方至少要能从标准输出
198
+ // 确认「跑没跑、落在哪、基线是谁」:不带 `--stdout` 时此前 stdout 为空(审计行 0 命中),
199
+ // 报告路径无处可见;`--stdout` 时报告正文在前、审计行追加在后(正文仍是落盘字节,审计行不进
200
+ // 报告)。审计行内容当日确定(日期 / 在场判定 / 基线),不引入新的易变行。另锚:审计行用的
201
+ // CLI 路径标签是三条侧命令的**共享助手**(evolve.mjs 唯一定义),不给同一显示决定留下第二份。
202
+ {
203
+ name: '297 health 审计行恒输出:HEALTH: 行与报告落盘路径(不带 --stdout 亦然)+ 正文不回流 + --help 不产报告',
204
+ run: (dir) => {
205
+ writeFile(dir, '.specs/CONTEXT.md', contextFixtureText());
206
+ writeState(dir, baseState('open'));
207
+ const today = requireModuleExport(timeUtilsModule, 'formatLocalDate', 'time-utils.mjs')(new Date());
208
+ const reportFile = path.join(dir, '.specs', 'health', today + '-HEALTH.md');
209
+ const reportLine = 'HEALTH: 报告 `.specs/health/' + today + '-HEALTH.md`';
210
+
211
+ // ① 不带 `--stdout`:审计行与报告路径仍必须输出,且**不**把报告正文回流
212
+ const quiet = runSideScript(SIDE_HEALTH, ['--root', dir], dir);
213
+ assertExit(quiet, 0);
214
+ assertOut(quiet, reportLine);
215
+ assertOut(quiet, 'HEALTH-DONE');
216
+ assertNotOut(quiet, '## 确定性层(机器可判)');
217
+ // 审计行点名的路径必须是真实落盘的工件(文案与产物同源)
218
+ assertTrue(fs.existsSync(reportFile), '审计行点名的报告未落盘: ' + reportFile);
219
+
220
+ // ② 带 `--stdout`:报告正文在前(与落盘逐字节一致)、审计行在后
221
+ const loud = runSideScript(SIDE_HEALTH, ['--root', dir, '--stdout'], dir);
222
+ assertExit(loud, 0);
223
+ assertOut(loud, reportLine);
224
+ assertOut(loud, 'HEALTH-DONE');
225
+ const reportText = fs.readFileSync(reportFile, 'utf8');
226
+ assertTrue(loud.output.startsWith(reportText), '--stdout 的报告正文应与落盘逐字节一致(审计行追加在后)');
227
+ assertTrue(loud.output.indexOf('HEALTH-DONE') > loud.output.indexOf(reportText),
228
+ '审计行应在报告正文之后(顺序反了会让消费方把摘要当正文)');
229
+
230
+ // ③ 审计行回显本次采用的基线:合法旧报告在场时点名它(同日重跑不与自己对比)
231
+ writeFile(dir, '.specs/health/2026-01-05-HEALTH.md', healthReportFixture('2026-01-05', 999999));
232
+ const withBaseline = runSideScript(SIDE_HEALTH, ['--root', dir], dir);
233
+ assertExit(withBaseline, 0);
234
+ assertOut(withBaseline, 'HEALTH: 日期 ' + today);
235
+ assertOut(withBaseline, '基线 `.specs/health/2026-01-05-HEALTH.md`');
236
+
237
+ // ④ `--help` 短路:打用法、不产报告、不输出审计行(用法面语义不变)
238
+ const help = runSideScript(SIDE_HEALTH, ['--help'], dir);
239
+ assertExit(help, 0);
240
+ assertOut(help, 'health.mjs');
241
+ assertNotOut(help, 'HEALTH: 报告');
242
+
243
+ // ⑤ 结构锚:CLI 路径标签**单一来源**(三条命令的摘要行同形)——定义只在共享助手模块
244
+ // evolve.mjs(侧命令共享助手的既有落点),另两条具名 import 后真实调用;第二份同名
245
+ // 助手(或改回各处内联)即红。
246
+ const labelDefinition = engineDefinitionHits('relativeLabel');
247
+ assertEqual(labelDefinition.length, 1, 'relativeLabel 定义面(全引擎应恰 1 处)实际 ' + JSON.stringify(labelDefinition));
248
+ assertEqual(labelDefinition[0].file, 'evolve.mjs', 'relativeLabel 定义文件');
249
+ for (const file of ['health.mjs', 'context-scan.mjs']) {
250
+ const text = fs.readFileSync(path.join(SCRIPTS_DIR, file), 'utf8');
251
+ assertTrue(hasNamedImport(text, './evolve.mjs', 'relativeLabel'),
252
+ file + ' 未从共享助手模块 import 路径标签(第二份同名助手或未接线)');
253
+ assertTrue(text.includes('relativeLabel('), file + ' 未真实调用共享路径标签');
254
+ }
255
+ },
256
+ },
257
+
258
+ // 298: 禁裸拼接静态锚(DESIGN R4 的落地)——时间形态 / 格式化的唯一权威是 time-utils.mjs:
259
+ // 三条侧命令零容忍(人可见报告 / CLI 摘要行 / 备份名);其余**引擎面**(入口 ∪ `lib/**`,递归)
260
+ // 走**显式白名单 + 逐条理由**(既有落点都是已持久化的机器字段,迁移留专门窗口;新增写入路径
261
+ // 一律走 time-utils,不得把白名单当增量口——撤回留痕 withdrawnAt 即按此落 nowTimestamp)。
262
+ // 判别力两条:① 白名单判定是纯函数,合成输入可驱动「条数漂移(增 / 减)」与「未登记文件」三态
263
+ // 必报;② 反向构造:第二处裸拼接注入 `lib/` ⇒ 真实面检出必增(证明递归面不恒真空过)。
264
+ // 注:白名单条目逐文件**精确对账**(增 / 减各自独立方向),不另设全局总数地板——总量型判据会让
265
+ //「合法新增一处」与「丢失一处」对冲,并把报错方向指向探针(本仓既有教训)。
266
+ {
267
+ name: '298 禁裸拼接静态锚:三侧命令零容忍 + 引擎面显式白名单(逐条理由)+ 反向构造',
268
+ run: () => {
269
+ // ① 三条侧命令零容忍(人可见面的时间形态只许走 time-utils)
270
+ const sideHits = bareIsoTimestampHits(SCRIPTS_DIR, BARE_ISO_SIDE_COMMANDS);
271
+ assertEqual(sideHits.length, 0,
272
+ '侧命令出现裸时间拼接(人可见面须走 time-utils 的 nowTimestamp / formatLocalTimestamp): ' + JSON.stringify(sideHits));
273
+
274
+ // ② 其余引擎面 = 精确白名单:条数逐文件相等 + 每条例外带非空理由
275
+ const engineHits = bareIsoTimestampHits(SCRIPTS_DIR).filter((hit) => !BARE_ISO_SIDE_COMMANDS.includes(hit.file));
276
+ const problems = bareIsoWhitelistProblems(engineHits, BARE_ISO_ENGINE_WHITELIST);
277
+ assertEqual(problems.length, 0, '白名单漂移: ' + problems.join(' | '));
278
+ for (const entry of BARE_ISO_ENGINE_WHITELIST) {
279
+ assertTrue(typeof entry.reason === 'string' && entry.reason.length >= 20,
280
+ entry.file + ' 的白名单条目缺理由(豁免必须是显式且有据的,不是静默名单)');
281
+ }
282
+
283
+ // ③ 白名单判定的判别力(纯函数 · 合成输入):等价集合不报;三类漂移各自必报
284
+ // (合成等价集合由**白名单自身**的条数派生——不手抄数字,也不会随条目增删失配)
285
+ const equivalent = BARE_ISO_ENGINE_WHITELIST.map((entry, index) => ({ file: 'probe-' + index + '.mjs', count: entry.count }));
286
+ const whitelist = BARE_ISO_ENGINE_WHITELIST.map((entry, index) => ({ ...entry, file: equivalent[index].file }));
287
+ const firstCount = equivalent[0].count;
288
+ assertEqual(bareIsoWhitelistProblems(equivalent, whitelist).length, 0, '等价集合不应报白名单漂移');
289
+ const newcomer = bareIsoWhitelistProblems([...equivalent, { file: 'newcomer.mjs', count: 1 }], whitelist);
290
+ assertTrue(newcomer.some((problem) => problem.includes('newcomer.mjs') && problem.includes('未登记白名单')),
291
+ '未登记文件的裸拼接未被判定: ' + JSON.stringify(newcomer));
292
+ const grown = bareIsoWhitelistProblems(
293
+ equivalent.map((hit, index) => (index === 0 ? { ...hit, count: hit.count + 1 } : hit)), whitelist);
294
+ assertTrue(grown.some((problem) => problem.includes('白名单 ' + firstCount + ' 处 / 实际 ' + (firstCount + 1) + ' 处')),
295
+ '白名单条数增长未被判定: ' + JSON.stringify(grown));
296
+ const shrunk = bareIsoWhitelistProblems(equivalent.slice(1), whitelist);
297
+ assertTrue(shrunk.some((problem) => problem.includes('白名单 ' + firstCount + ' 处 / 实际 0 处')),
298
+ '已迁移落点未同步收窄白名单未被判定: ' + JSON.stringify(shrunk));
299
+
300
+ // ④ 合成引擎目录反向构造:单处 → 检出 1;再注入一处 → 检出 2(判据不恒真空过)。
301
+ // 样例经拼接构造,避免套件自身源码携带该字面量而污染真实面计数(本套件同样在扫描面内)。
302
+ const bareIsoSample = 'new Date().' + 'toISOString()';
303
+ const synthetic = makeTmp();
304
+ try {
305
+ writeFile(synthetic, 'one.mjs', 'export const a = () => ' + bareIsoSample + ';\n');
306
+ assertEqual(bareIsoTimestampHits(synthetic).length, 1, '合成目录单处检出数');
307
+ writeFile(synthetic, 'two.mjs', 'export const b = () => ' + bareIsoSample + ';\n');
308
+ assertEqual(bareIsoTimestampHits(synthetic).length, 2, '合成目录第二处检出数(判据须变红)');
309
+ // 注释里的引用不算实现(判据只看代码)
310
+ writeFile(synthetic, 'three.mjs', '// 反例引用: ' + bareIsoSample + '\nexport const c = 1;\n');
311
+ assertEqual(bareIsoTimestampHits(synthetic).length, 2, '行注释中的引用不应计入实现面');
312
+ } finally {
313
+ cleanupTmpDir(synthetic);
314
+ }
315
+
316
+ // ⑤ 递归面探针(真实形态 shadow 树):引擎脚本树整棵复制后,在 `lib/` 下注入一处裸拼接 ⇒
317
+ // 检出必增(平铺扫描的旧形态只看顶层、对 `lib/` 内新增静默失明——正是本锚修复的缺陷形态)。
318
+ const shadow = makeTmp();
319
+ try {
320
+ const shadowScripts = copyEngineTree(shadow);
321
+ const baseHits = bareIsoTimestampHits(shadowScripts);
322
+ writeFile(shadowScripts, path.join('lib', 'probe.mjs'),
323
+ 'export const probe = () => ' + bareIsoSample + ';\n');
324
+ const grownHits = bareIsoTimestampHits(shadowScripts);
325
+ assertEqual(grownHits.length, baseHits.length + 1,
326
+ 'lib/ 下的第二处裸拼接必须被递归面检出(平铺面会静默失明): '
327
+ + JSON.stringify({ base: baseHits.length, grown: grownHits.length }));
328
+ } finally {
329
+ cleanupTmpDir(shadow);
330
+ }
331
+ },
332
+ },
333
+
334
+ // 299: 可选工具超时预算(60s 内)+ 超时不静默——常量与调用点同源,且「工具在场但运行未完成」
335
+ // 必须把降级原因(含本次超时预算)写进报告、快照读数按 `present` 而非 `ok` 落盘,退出码仍 0
336
+ // (可选工具不可用不是失败)。判别力:常量越预算即红;夹具工具(在场但跑不起来)触发同一
337
+ // 失败分支,报告里必须看到降级原因——不静默、不冒充成功读数。
338
+ {
339
+ name: '299 工具超时收口:常量 ≤ 60s 且与调用点同源 + 在场但运行失败必记降级原因(含预算)',
340
+ run: (dir) => {
341
+ const healthText = fs.readFileSync(SIDE_HEALTH, 'utf8');
342
+ const match = /const TOOL_TIMEOUT_MS = (\d+);/.exec(healthText);
343
+ assertTrue(match !== null, 'health.mjs 缺工具超时常量 TOOL_TIMEOUT_MS');
344
+ const budget = Number(match[1]);
345
+ assertTrue(budget > 0 && budget <= 60000, '工具超时常量超出 60s 预算: ' + budget + ' ms');
346
+ assertTrue(/timeout: TOOL_TIMEOUT_MS/.test(healthText), '工具调用未消费超时常量(常量会变成装饰)');
347
+ assertTrue(healthText.includes('超时预算'), '降级原因未回显本次超时预算(超时须可自证,不静默)');
348
+
349
+ // 真实链路:夹具工具「在场」(探面命中 <根>/node_modules/.bin/)但跑不起来 → 同一失败分支
350
+ writeFile(dir, '.specs/CONTEXT.md', contextFixtureText());
351
+ writeFile(dir, '.specs/LESSONS.md', '# LESSONS\n\n### L-001 首条\n\n### L-002 次条\n');
352
+ fs.mkdirSync(path.join(dir, 'src'), { recursive: true });
353
+ fs.mkdirSync(path.join(dir, 'node_modules', '.bin'), { recursive: true });
354
+ const toolPath = path.join(dir, 'node_modules', '.bin', 'jscpd');
355
+ fs.writeFileSync(toolPath, '#!/usr/bin/env node\nprocess.exit(3);\n', 'utf8');
356
+ fs.chmodSync(toolPath, 0o755);
357
+ const res = runSideScript(SIDE_HEALTH, ['--root', dir, '--stdout'], dir);
358
+ assertExit(res, 0);
359
+ assertOut(res, '未采集——工具在场但运行未完成(超时预算 ' + budget + ' ms;');
360
+ assertOut(res, 'redundancy.jscpd=present');
361
+ assertNotOut(res, 'redundancy.jscpd=ok');
362
+ assertOut(res, '- **jscpd**:在场——字面重复块读数见「冗余扫描」段');
363
+ },
364
+ },
365
+
366
+ // 300: 读数快照的键形态**单一来源**——往返判据:把生产者自己产出的快照段整段当作历史基线
367
+ // 喂回去,每个产出的键都必须被读回(零「基线无此读数」、条数与产出条数相等);反例:给写方
368
+ // 真实产出的键写异常值 → 必出趋势行;近形状键(大小写不符)不得被读走。此前写方发 6 个含
369
+ // 大写字母的键、读方的键形态正则只认全小写:6/18 个键恒判「(基线无此读数)」,逐键趋势
370
+ // 静默失效且不报错(假绿形态)。
371
+ {
372
+ name: '300 快照键形态单一来源:产出快照往返零「基线无此读数」+ 真实键异常值必出趋势行 + 近形状键不误读',
373
+ run: (dir) => {
374
+ writeFile(dir, '.specs/CONTEXT.md', contextFixtureText());
375
+ writeFile(dir, '.specs/LESSONS.md', '# LESSONS\n\n### L-001 首条\n\n### L-002 次条\n');
376
+ writeState(dir, baseState('open'));
377
+
378
+ // ① 生产面自证:先跑一次拿到真实报告,取其快照段原文(不解析、不重排)
379
+ const firstRun = runSideScript(SIDE_HEALTH, ['--root', dir, '--stdout'], dir);
380
+ assertExit(firstRun, 0);
381
+ const firstReport = fs.readFileSync(path.join(dir, '.specs', 'health',
382
+ requireModuleExport(timeUtilsModule, 'formatLocalDate', 'time-utils.mjs')(new Date()) + '-HEALTH.md'), 'utf8');
383
+ const section = snapshotSectionOf(firstReport);
384
+ assertTrue(section !== null, '报告缺「## 读数快照」段(往返夹具前提不成立)');
385
+ const producedEntries = snapshotEntryCount(section);
386
+ assertTrue(producedEntries >= 10, '快照条数异常(往返判据的样本太小): ' + producedEntries);
387
+
388
+ // ② 往返:产出快照整段当作 2026-01-05 的历史基线 → 每个键都必须被读回
389
+ writeFile(dir, '.specs/health/2026-01-05-HEALTH.md', healthReportWithSnapshot('2026-01-05', section));
390
+ const roundTrip = runSideScript(SIDE_HEALTH, ['--root', dir, '--stdout'], dir);
391
+ assertExit(roundTrip, 0);
392
+ assertOut(roundTrip, '基线:`.specs/health/2026-01-05-HEALTH.md`');
393
+ assertNotOut(roundTrip, '(基线无此读数)');
394
+ const unchanged = (roundTrip.output.match(/(无变化)/g) ?? []).length;
395
+ assertEqual(unchanged, producedEntries, '往返后逐键「无变化」条数应等于产出条数(有键没被读回)');
396
+
397
+ // ③ 真实产出的键(含此前恒被判「基线无此读数」的驼峰键)写异常值 → 必出趋势行
398
+ const anomalous = section
399
+ .replace(/(^|\n)context\.lineCount=[^\n]*/, '$1context.lineCount=999999')
400
+ .replace(/(^|\n)git\.head=[^\n]*/, '$1git.head=ffffffff');
401
+ writeFile(dir, '.specs/health/2026-01-06-HEALTH.md', healthReportWithSnapshot('2026-01-06', anomalous));
402
+ const trend = runSideScript(SIDE_HEALTH, ['--root', dir, '--stdout'], dir);
403
+ assertExit(trend, 0);
404
+ assertOut(trend, '基线:`.specs/health/2026-01-06-HEALTH.md`');
405
+ assertOut(trend, '`context.lineCount`:999999 → ');
406
+ assertOut(trend, '`git.head`:ffffffff → ');
407
+ assertNotOut(trend, '999999(基线无此读数)');
408
+ assertNotOut(trend, 'ffffffff(基线无此读数)');
409
+
410
+ // ④ 近形状键(大小写不符)不是本版本的读数面:不得被读走(报「基线无此读数」而非伪造趋势)
411
+ const nearMiss = section.replace(/(^|\n)context\.lineCount=[^\n]*/, '$1context.linecount=888888');
412
+ writeFile(dir, '.specs/health/2026-01-07-HEALTH.md', healthReportWithSnapshot('2026-01-07', nearMiss));
413
+ const miss = runSideScript(SIDE_HEALTH, ['--root', dir, '--stdout'], dir);
414
+ assertExit(miss, 0);
415
+ assertOut(miss, '基线:`.specs/health/2026-01-07-HEALTH.md`');
416
+ assertNotOut(miss, '888888');
417
+ assertOut(miss, '`context.lineCount`:');
418
+ assertOut(miss, '(基线无此读数)');
419
+ },
420
+ },
421
+
422
+ // 301: 备份改写前版本**单一来源**——命名族(目标文档同目录 + `.bak-<本地日期>`)与失败处置
423
+ // 收敛为 state-schema.mjs 的单一导出(与原子写同址),evolve 与 context-scan 只消费导出:
424
+ // 命名族或失败处置再演进时不会只改到一侧。判别力:① 定义面唯一 + 两消费方零内联(第二份
425
+ // 实现 → 收敛面内检出 2 处);② evolve 真实链路(备份 = 改写前版本、命名族命中当日日期、
426
+ // 复制失败整轮 fail-closed:目标文档 / state / 报告三处零改动,与 context-scan 同处置);
427
+ // ③ 合成目录反向构造证明①的判据不恒真空过。
428
+ {
429
+ name: '301 备份助手单一来源:state-schema 唯一导出·两消费方零内联 + evolve 真实链路 fail-closed',
430
+ run: async (dir) => {
431
+ // ① 收敛面内恰一处实现(命名族字面量 + 复制调用同现者)——修复前 evolve 与 context-scan
432
+ // 各一份(同形但两份),此断言即「第二份实现必红」的落点
433
+ const impl = inlineBackupHits(SCRIPTS_DIR, BACKUP_IMPL_FACE);
434
+ assertEqual(impl.length, 1, '备份实现面(收敛面内应恰 1 处)实际 ' + JSON.stringify(impl));
435
+ assertEqual(impl[0].file, 'state-schema.mjs', '备份实现落点文件');
436
+
437
+ // ② 定义面唯一 + 两消费方具名 import 与真实调用
438
+ const definition = engineDefinitionHits('backupBeforeWrite');
439
+ assertEqual(definition.length, 1, 'backupBeforeWrite 定义面(全引擎应恰 1 处)实际 ' + JSON.stringify(definition));
440
+ assertEqual(definition[0].file, 'state-schema.mjs', 'backupBeforeWrite 定义文件');
441
+ const backupHelper = requireModuleExport(stateSchemaModule, 'backupBeforeWrite', 'state-schema.mjs');
442
+ for (const file of ['evolve.mjs', 'context-scan.mjs']) {
443
+ const text = fs.readFileSync(path.join(SCRIPTS_DIR, file), 'utf8');
444
+ assertTrue(hasNamedImport(text, './state-schema.mjs', 'backupBeforeWrite'),
445
+ file + ' 未从 state-schema.mjs 具名 import 备份助手(第二份实现或未接线)');
446
+ assertTrue(text.includes('backupBeforeWrite('), file + ' 未真实调用共享备份助手');
447
+ }
448
+
449
+ // ③ 单一导出的行为(命名族由共享实现派生:`.bak-<本地日期>`,内容 = 改写前版本)
450
+ const today = requireModuleExport(timeUtilsModule, 'formatLocalDate', 'time-utils.mjs')(new Date());
451
+ const stamp = requireModuleExport(timeUtilsModule, 'nowTimestamp', 'time-utils.mjs')();
452
+ const probe = makeTmp();
453
+ try {
454
+ const target = path.join(probe, 'doc.md');
455
+ writeFile(probe, 'doc.md', '改写前内容\n');
456
+ await backupHelper(target, stamp);
457
+ const produced = target + '.bak-' + today;
458
+ assertTrue(fs.existsSync(produced), '备份未按「同目录 + 当日本地日期」落点: ' + produced);
459
+ assertEqual(fs.readFileSync(produced, 'utf8'), '改写前内容\n', '备份内容应为改写前版本');
460
+ } finally {
461
+ cleanupTmpDir(probe);
462
+ }
463
+
464
+ // ④ evolve 真实链路:apply 落备份(内容 = 改写前版本)
465
+ writeFile(dir, '.specs/archive/2026-10-02-backup/DESIGN.md',
466
+ '# DESIGN\n\n## 9. 架构沉淀\n\n### 可复用抽象\n\n- 备份单一来源夹具条目\n');
467
+ const original = contextFixtureText();
468
+ const contextFile = path.join(dir, '.specs', 'CONTEXT.md');
469
+ const backupFile = contextFile + '.bak-' + today;
470
+ writeFile(dir, '.specs/CONTEXT.md', original);
471
+ writeState(dir, baseState('open'));
472
+ const apply = runSideScript(SIDE_EVOLVE, ['apply', '2026-10-02-backup#1', '--root', dir], dir);
473
+ assertExit(apply, 0);
474
+ assertTrue(fs.existsSync(backupFile), 'evolve apply 未落改写前备份: ' + backupFile);
475
+ assertEqual(fs.readFileSync(backupFile, 'utf8'), original, '备份内容应为改写前版本');
476
+ assertTrue(fs.readFileSync(contextFile, 'utf8') !== original, 'CONTEXT.md 未被改写(夹具前提不成立)');
477
+
478
+ // ⑤ 复制不成功 → fail-closed:目标文档 / state / 报告三处零改动(与 context-scan 同处置)
479
+ writeFile(dir, '.specs/CONTEXT.md', original);
480
+ const stateBytes = readStateBytes(dir);
481
+ const reportFile = path.join(dir, '.specs', 'evolve', today + '-EVOLVE.md');
482
+ const reportBefore = fs.readFileSync(reportFile);
483
+ fs.rmSync(backupFile, { force: true });
484
+ fs.mkdirSync(backupFile);
485
+ const blocked = runSideScript(SIDE_EVOLVE, ['apply', '2026-10-02-backup#1', '--root', dir], dir);
486
+ assertExit(blocked, 1);
487
+ assertOut(blocked, 'BLOCKED');
488
+ assertEqual(fs.readFileSync(contextFile, 'utf8'), original, '备份失败的 apply 轮改写了 CONTEXT.md');
489
+ assertStateBytesUnchanged(dir, stateBytes, '备份失败的 apply 轮');
490
+ assertTrue(fs.readFileSync(reportFile).equals(reportBefore), '备份失败的 apply 轮改写了报告');
491
+
492
+ // ⑥ 合成目录反向构造:单实现 → 1;再放第二份 → 2
493
+ const synthetic = makeTmp();
494
+ try {
495
+ writeFile(synthetic, 'single.mjs',
496
+ "export async function duplicateBackup(file, ts) {\n"
497
+ + " const backup = file + '.bak-' + ts;\n"
498
+ + ' await fs.copyFile(file, backup);\n'
499
+ + '}\n');
500
+ assertEqual(inlineBackupHits(synthetic).length, 1, '合成目录单实现检出数');
501
+ writeFile(synthetic, 'second.mjs',
502
+ "async function anotherBackup(file, ts) {\n"
503
+ + " const backup = file + '.bak-' + ts;\n"
504
+ + ' await fs.copyFile(file, backup);\n'
505
+ + '}\n');
506
+ assertEqual(inlineBackupHits(synthetic).length, 2, '合成目录第二份实现检出数(判据须变红)');
507
+ } finally {
508
+ cleanupTmpDir(synthetic);
509
+ }
510
+ },
511
+ },
512
+
513
+ // 302: AC-11 的四条时间硬规则文本锚(存在级,但**指真实实体**):① 分发面技能文本(入口 SKILL
514
+ // 的侧命令「共同边界」)陈述规则 ①②③;② 验证阶梯(docs/internal/WORKING-METHOD.md 一·五 的
515
+ // 「环境 / 过程纪律·时间」条)承载规则 ①~③ 并落实 ④(纪律已写入阶梯本身);③ 文本点名的实体
516
+ // 在树内真实存在——`time-utils.mjs` 在场且真实定义被点名的判据符号(防锚指向幽灵:散文提到的
517
+ // 东西必须在树里找得到)。维护者面结构性缺席(CI 全新检出 / worktree)时验证阶梯半边输出可见
518
+ // SKIP 行(未验证 ≠ 通过),分发面半边恒检。
519
+ {
520
+ name: '302 时间纪律四条硬规则文本锚:入口技能陈述 ①②③ + 验证阶梯承载四条 + 点名实体真实在场',
521
+ run: () => {
522
+ const skillsRoot = skillsRootForScriptsDir(SCRIPTS_DIR);
523
+ const entrySkill = path.join(skillsRoot, 'flow-comet', 'SKILL.md');
524
+ const skillText = fs.readFileSync(entrySkill, 'utf8');
525
+ const skillProblems = timeDisciplineTextProblems('入口 SKILL', skillText);
526
+ assertEqual(skillProblems.length, 0, '时间纪律文本锚: ' + skillProblems.join(' | '));
527
+
528
+ // 反向构造(真实文本逐条移除 · 合成输入驱动同一判据):任一条规则的关键词被移走 → 该条必报。
529
+ for (const [rule, tokens] of TIME_DISCIPLINE_RULES) {
530
+ const stripped = tokens.reduce((text, token) => text.replace(token, '(反向构造:移除)'), skillText);
531
+ assertTrue(stripped !== skillText, '反向构造前提不成立(入口 SKILL 缺该条关键词): ' + rule);
532
+ assertTrue(timeDisciplineTextProblems('入口 SKILL', stripped).some((problem) => problem.includes(rule)),
533
+ '逐条移除未被判违规(判别力缺失): ' + rule);
534
+ }
535
+
536
+ if (maintainerFacePresent()) {
537
+ const ladder = fs.readFileSync(path.join(REPO_ROOT, 'docs/internal/WORKING-METHOD.md'), 'utf8');
538
+ const ladderProblems = timeDisciplineTextProblems('验证阶梯', ladder);
539
+ assertEqual(ladderProblems.length, 0, '验证阶梯文本锚: ' + ladderProblems.join(' | '));
540
+ assertTrue(ladder.includes('环境 / 过程纪律'), '验证阶梯缺「环境 / 过程纪律」条(规则④的落点)');
541
+ assertTrue(ladder.includes('L-096'), '验证阶梯的时间纪律条未点名 L-096 实证(规则③的依据)');
542
+ } else {
543
+ console.log('SKIP: 302 的验证阶梯面(docs/internal/WORKING-METHOD.md 一·五「环境 / 过程纪律」条)'
544
+ + '——维护者面结构性缺席;本次检出未校验规则 ①~④ 已写入验证阶梯,请在维护者主树重跑本套件');
545
+ }
546
+
547
+ // 点名实体真实在场:time-utils.mjs(规则①②的单一权威)在场,且真实定义被点名的判据符号。
548
+ const timeUtilsFile = path.join(SCRIPTS_DIR, 'time-utils.mjs');
549
+ assertTrue(fs.existsSync(timeUtilsFile), '入口 SKILL 的时间纪律点名 time-utils.mjs,但树内无此文件(锚指向幽灵实体)');
550
+ for (const symbol of ['formatLocalTimestamp', 'parseTimestamp']) {
551
+ assertTrue(engineDefinitionHits(symbol).some((hit) => hit.file === 'time-utils.mjs'),
552
+ 'time-utils.mjs 未定义被点名的判据符号 ' + symbol + '(散文与实现脱节)');
553
+ }
554
+ },
555
+ },
556
+
557
+ // 303: 收尾打磨之首——`evolve` 在 **CRLF 文档**上追加「## evolve 元数据」段前不得留裸 LF 行。
558
+ // 复现形态(`-->\r\n\n\r\n---`):`split('\n')` 对「以换行收尾的文档」留有一个零长度
559
+ // 哨兵元素,旧实现直接在哨兵之后 push,于是拼出一条**无 `\r` 的空行**(同一文件两种行尾)。
560
+ // 断言面:整篇每条行都以 CRLF 终结(逐行行号可读)+ 追加块前后形态逐字 + LF 文档对照
561
+ // (证明修复不是「CRLF 专属补丁」——两种行尾约定下追加块都退化为**单空行**)。
562
+ {
563
+ name: '303 侧命令 CRLF 追加块:evolve 追加元数据段零裸 LF 行 · 两种行尾约定形态一致',
564
+ run: (dir) => {
565
+ writeFile(dir, '.specs/archive/2026-10-02-crlf/DESIGN.md',
566
+ '# DESIGN\n\n## 9. 架构沉淀\n\n### 可复用抽象\n\n- CRLF 夹具条目\n');
567
+ writeFile(dir, '.specs/CONTEXT.md', contextFixtureText());
568
+ writeState(dir, baseState('open'));
569
+
570
+ // ① CRLF 文档:夹具本身必须整篇 CRLF(否则「裸 LF」判据的前提不成立)
571
+ const crlfFixture = contextFixtureText({ tail: '<!-- crlf-tail -->' }).replace(/\n/g, '\r\n');
572
+ assertEqual(crlfLineViolations(crlfFixture).length, 0, '夹具前提不成立:CRLF 夹具本身含非 CRLF 行');
573
+ writeFile(dir, '.specs/CONTEXT.md', crlfFixture);
574
+
575
+ const applied = runSideScript(SIDE_EVOLVE, ['apply', '2026-10-02-crlf#1', '--root', dir], dir);
576
+ assertExit(applied, 0);
577
+ assertOut(applied, 'EVOLVE-OK');
578
+ const crlfText = fs.readFileSync(path.join(dir, '.specs', 'CONTEXT.md'), 'utf8');
579
+ const violations = crlfLineViolations(crlfText);
580
+ assertEqual(violations.join(','), '',
581
+ 'CRLF 文档追加后出现非 CRLF 行(行号): ' + violations.join(','));
582
+ assertTrue(crlfText.includes('<!-- crlf-tail -->\r\n\r\n---\r\n\r\n## evolve 元数据\r\n\r\n'),
583
+ '追加块前后形态不符(期望单空行 + 全 CRLF): '
584
+ + JSON.stringify(crlfText.slice(crlfText.indexOf('<!-- crlf-tail -->'))));
585
+ // 判别力(合成变异驱动同一判据):把修复前形态灌回真实文本 → 必报
586
+ const regressed = crlfText.replace('\r\n\r\n---\r\n', '\r\n\n\r\n---\r\n');
587
+ assertTrue(regressed !== crlfText, '反向构造前提不成立(追加块形态已变)');
588
+ assertTrue(crlfLineViolations(regressed).length > 0, '裸 LF 行未被判违规(判别力缺失)');
589
+
590
+ // ② LF 文档对照:行尾约定不变(单空行 + 全 LF),且不得被写入 CR
591
+ writeFile(dir, '.specs/CONTEXT.md', contextFixtureText({ tail: '<!-- lf-tail -->' }));
592
+ writeState(dir, baseState('open'));
593
+ const appliedLf = runSideScript(SIDE_EVOLVE, ['apply', '2026-10-02-crlf#1', '--root', dir], dir);
594
+ assertExit(appliedLf, 0);
595
+ const lfText = fs.readFileSync(path.join(dir, '.specs', 'CONTEXT.md'), 'utf8');
596
+ assertTrue(lfText.includes('<!-- lf-tail -->\n\n---\n\n## evolve 元数据\n\n'),
597
+ 'LF 文档追加块形态回归: ' + JSON.stringify(lfText.slice(lfText.indexOf('<!-- lf-tail -->'))));
598
+ assertTrue(!lfText.includes('\r'), 'LF 文档被写入 CR(行尾约定不得被改写)');
599
+ },
600
+ },
601
+
602
+ // 304: 收尾打磨之二——EVOLVE 报告的「## 应用 patch」条目此前是 ` - ` 前缀与条目自带的 `- `
603
+ // 叠加(` - - <条目>`):Markdown 渲染成「空壳父项 + 子项」两条,报告读者数不清应用了几条。
604
+ // 断言面:报告零 `- -` 双符号行 + 条目行逐字(单符号)+ 父项在场(子项挂在正确的父项下)。
605
+ {
606
+ name: '304 EVOLVE 报告条目单一列表符号:零 `- -` 双符号行 · 条目行逐字',
607
+ run: (dir) => {
608
+ writeFile(dir, '.specs/archive/2026-10-02-report/DESIGN.md',
609
+ '# DESIGN\n\n## 9. 架构沉淀\n\n### 可复用抽象\n\n- 报告条目夹具\n');
610
+ writeFile(dir, '.specs/CONTEXT.md', contextFixtureText());
611
+ writeState(dir, baseState('open'));
612
+ const applied = runSideScript(SIDE_EVOLVE, ['apply', '2026-10-02-report#1', '--root', dir], dir);
613
+ assertExit(applied, 0);
614
+ assertOut(applied, 'EVOLVE-OK');
615
+
616
+ const date = requireModuleExport(timeUtilsModule, 'formatLocalDate', 'time-utils.mjs')(new Date());
617
+ const reportFile = path.join(dir, '.specs', 'evolve', date + '-EVOLVE.md');
618
+ assertTrue(fs.existsSync(reportFile), 'EVOLVE 报告未落盘: ' + reportFile);
619
+ const reportText = fs.readFileSync(reportFile, 'utf8');
620
+ const bulletProblems = evolveReportBulletProblems(reportText);
621
+ assertEqual(bulletProblems.length, 0, 'EVOLVE 报告列表符号: ' + bulletProblems.join(' | '));
622
+ assertTrue(reportText.includes('- [2026-10-02-report#1] → `.specs/CONTEXT.md`「既有抽象索引」'),
623
+ '报告缺应用项的父条目行: ' + JSON.stringify(reportText.slice(reportText.indexOf('## 应用 patch'))));
624
+ assertTrue(reportText.includes(' - 报告条目夹具 · 来源 @.specs/archive/2026-10-02-report/DESIGN.md'),
625
+ '报告条目行不是单一列表符号: ' + JSON.stringify(reportText.slice(reportText.indexOf('## 应用 patch'))));
626
+ // 判别力(合成变异驱动同一判据):把双符号灌回真实报告 → 必报
627
+ const regressed = reportText.replace(' - 报告条目夹具', ' - - 报告条目夹具');
628
+ assertTrue(regressed !== reportText, '反向构造前提不成立(报告缺条目行)');
629
+ assertTrue(evolveReportBulletProblems(regressed).length > 0, '双列表符号未被判违规(判别力缺失)');
630
+ },
631
+ },
632
+
633
+ // 305: 收尾打磨之三——`health` 的「技术债表项数」复现命令此前硬编码 H3(`/^### 技术债/`),
634
+ // 而同一项的判据把段标题层级放宽到二~四级:`## 技术债` 的项目照抄命令复现不出报告读数
635
+ // (读数说 0,其实段在场有表项)——命令与判据各说一套。
636
+ // 同一条判据的残留边界(同批收口):段边界此前按「任意 H1~H4 标题」截断,段内**子标题**之后的
637
+ // 表格整段丢失(`## 技术债` + `### 明细` 与 `### 技术债` + `#### 明细` 都读成 0 表项)——层级
638
+ // 必须与段标题自身比较。断言面 = 标题层级 × 有无子标题的**六格矩阵**(H4 + 更深子标题是控制格:
639
+ // 更深子标题本就不该截断),复现命令的段终点同步改为「同级或更高级标题,或分隔线」而与判据同源。
640
+ {
641
+ name: '305 health 技术债段级与段边界按判据动态取:H2/H3/H4 × 子标题六格矩阵 · 段缺席退回区间',
642
+ run: (dir) => {
643
+ const withDebt = (heading, sub) => contextFixtureText()
644
+ + '\n' + heading + '(夹具技术债)\n\n' + (sub === '' ? '' : sub + '\n\n')
645
+ + '| 项 | 说明 |\n|---|---|\n| 债 A | 说明 A |\n| 债 B | 说明 B |\n';
646
+ // 复现命令的段级与段终点都取自判据本身(段级 = 文档里真实命中的标题层级;终点 = 同级或更
647
+ // 高级标题,或分隔线)——命令与读数才是同一件事的两种说法。
648
+ const reproLine = (bound) => "- 复现命令:`awk 'f&&(/^#{1," + bound
649
+ + "}[[:space:]]/||/^-{3,}[[:space:]]*$/){exit} /^#{2,4}[[:space:]]*技术债/{f=1} f' .specs/CONTEXT.md"
650
+ + " | grep -c '^|'`(含表头与分隔行,减去 2 即表项数)";
651
+
652
+ for (const [label, heading, sub, bound] of [
653
+ ['H2', '## 技术债', '', '2'],
654
+ ['H2-sub', '## 技术债', '### 明细', '2'],
655
+ ['H3', '### 技术债', '', '3'],
656
+ ['H3-sub', '### 技术债', '#### 明细', '3'],
657
+ ['H4', '#### 技术债', '', '4'],
658
+ ['H4-sub', '#### 技术债', '##### 明细', '4'],
659
+ ]) {
660
+ const root = path.join(dir, label.toLowerCase());
661
+ writeFile(root, '.specs/CONTEXT.md', withDebt(heading, sub));
662
+ writeFile(root, '.specs/LESSONS.md', '# LESSONS\n\n### L-001 首条\n');
663
+ const res = runSideScript(SIDE_HEALTH, ['--root', root, '--stdout'], dir);
664
+ assertExit(res, 0);
665
+ assertOut(res, '- 表项数:2');
666
+ assertOut(res, reproLine(bound));
667
+ if (bound !== '3') assertNotOut(res, reproLine('3'));
668
+ }
669
+ // 命令形态已换(段终点须能表达「同级或更高级」)——旧的 `/^---/` 单终点形态不得再出现
670
+ const h2 = runSideScript(SIDE_HEALTH, ['--root', path.join(dir, 'h2'), '--stdout'], dir);
671
+ assertNotOut(h2, "- 复现命令:`sed -n ");
672
+
673
+ // 段缺席:没有可取的层级 → 退回判据的层级区间(二~四级)形态;读数仍为 0(复现命令成立)
674
+ const absentRoot = path.join(dir, 'absent');
675
+ writeFile(absentRoot, '.specs/CONTEXT.md', contextFixtureText());
676
+ writeFile(absentRoot, '.specs/LESSONS.md', '# LESSONS\n\n### L-001 首条\n');
677
+ const absent = runSideScript(SIDE_HEALTH, ['--root', absentRoot, '--stdout'], dir);
678
+ assertExit(absent, 0);
679
+ assertOut(absent, '- 表项数:0');
680
+ assertOut(absent, reproLine('4'));
681
+ },
682
+ },
683
+
684
+ // 306: 验收条款子句的机检锚——「确定性层**每项**都带可复现命令」。此前该子句只由「state 字节
685
+ // 零改写」间接代表(锚偏弱):报告里说「逐项带计数与判据」,但「每项都有复现命令」
686
+ // 无人核。断言面:确定性层逐项都有 `- 复现命令:` 行(非仓库态与真实 git 仓库态两态)+ 逐项
687
+ // 抽掉该项的复现命令 → 每抽一次必报(判据不是只看第一项)。
688
+ {
689
+ name: '306 health 确定性层每项带复现命令:逐项机检 + 逐项抽掉必报 + git 两态覆盖',
690
+ run: (dir) => {
691
+ writeFile(dir, '.specs/CONTEXT.md', contextFixtureText());
692
+ writeFile(dir, '.specs/LESSONS.md', '# LESSONS\n\n### L-001 首条\n');
693
+ const plain = runSideScript(SIDE_HEALTH, ['--root', dir, '--stdout'], dir);
694
+ assertExit(plain, 0);
695
+ assertOut(plain, '### 5 · 版本历史统计(git)');
696
+ const plainProblems = deterministicReproProblems(plain.output);
697
+ assertEqual(plainProblems.length, 0, '确定性层缺复现命令: ' + plainProblems.join(' | '));
698
+
699
+ // 逐项判别力(合成变异驱动同一判据):确定性子集逐项各抽掉一次复现命令 → 每次都必报
700
+ const rows = plain.output.split('\n');
701
+ const starts = rows.map((line, i) => (line.startsWith('### ') ? i : -1)).filter((i) => i >= 0);
702
+ assertTrue(starts.length >= 5, '确定性层分项数不足(判据无从覆盖): ' + starts.length);
703
+ for (const start of starts) {
704
+ const nextStart = rows.findIndex((line, i) => i > start && line.startsWith('### '));
705
+ const stop = nextStart < 0 ? rows.length : nextStart;
706
+ const at = rows.findIndex((line, i) => i > start && i < stop && line.startsWith('- 复现命令:'));
707
+ assertTrue(at >= 0, '确定性项缺复现命令: ' + rows[start]);
708
+ const mutated = [...rows.slice(0, at), ...rows.slice(at + 1)].join('\n');
709
+ assertTrue(deterministicReproProblems(mutated).length > 0,
710
+ '抽掉该项复现命令未被判违规(判别力缺失): ' + rows[start]);
711
+ }
712
+
713
+ // git 在场态:另起一个真实仓库根(`git init`)→ 第 5 项走「是」分支,同样带复现命令
714
+ const repoRoot = path.join(dir, 'repo-root');
715
+ writeFile(repoRoot, '.specs/CONTEXT.md', contextFixtureText());
716
+ writeFile(repoRoot, '.specs/LESSONS.md', '# LESSONS\n\n### L-001 首条\n');
717
+ execFileSync('git', ['init', '-q'], { cwd: repoRoot, stdio: 'ignore' });
718
+ const inRepo = runSideScript(SIDE_HEALTH, ['--root', repoRoot, '--stdout'], dir);
719
+ assertExit(inRepo, 0);
720
+ assertOut(inRepo, '- git 仓库:是');
721
+ const repoProblems = deterministicReproProblems(inRepo.output);
722
+ assertEqual(repoProblems.length, 0, 'git 在场态确定性层缺复现命令: ' + repoProblems.join(' | '));
723
+ },
724
+ },
725
+
726
+ // 307: 覆盖声明四要素机检锚——三处「上游 vendored 只读」覆盖声明此前是
727
+ // **纯文本、无机检**。四要素:① 上游文件标记为只读基准(且点名的上游文件真实在场);
728
+ // ② 「不采用」栏 ≥1 条;③ 「沿用上游」栏 ≥1 条(入口为**指针式** → 该栏豁免,细则在各自技能册);
729
+ // ④ 「以…为准」兜底语。负向控制:把任一要素从**真实文本**里抽掉 → 必红。
730
+ {
731
+ name: '307 上游覆盖声明四要素:三处声明齐备 + 点名上游实体在场 + 逐要素抽掉必红',
732
+ run: () => {
733
+ const skillsRoot = skillsRootForScriptsDir(SCRIPTS_DIR);
734
+ const declarations = [
735
+ { label: 'flow-comet-health/SKILL.md', file: path.join(skillsRoot, 'flow-comet-health', 'SKILL.md'), pointer: false },
736
+ { label: 'flow-comet-evolve/SKILL.md', file: path.join(skillsRoot, 'flow-comet-evolve', 'SKILL.md'), pointer: false },
737
+ { label: 'flow-comet/SKILL.md', file: path.join(skillsRoot, 'flow-comet', 'SKILL.md'), pointer: true },
738
+ ];
739
+ for (const declaration of declarations) {
740
+ const text = fs.readFileSync(declaration.file, 'utf8');
741
+ const problems = overrideDeclarationProblems(declaration.label, text, { pointer: declaration.pointer });
742
+ assertEqual(problems.length, 0, '覆盖声明四要素: ' + problems.join(' | '));
743
+
744
+ // 逐要素抽掉(真实文本驱动同一判据):该要素必报——判据不恒真空过。
745
+ // 兜底语取**声明块内**的匹配(文件里别处的 `冲突…以文件为准` 一类行文不是该要素,
746
+ // 抽错目标会让判别力断言变成假绿)。
747
+ const probes = [
748
+ { element: '只读基准', strip: (value) => value.replaceAll('只读基准', '(反向构造:抽掉)') },
749
+ { element: '不采用栏', strip: (value) => value.replaceAll('不采用', '(反向构造:抽掉)') },
750
+ {
751
+ element: '兜底语',
752
+ strip: (value) => {
753
+ const blockFallback = OVERRIDE_FALLBACK_RE.exec(overrideDeclarationBlock(value));
754
+ return value.replace(blockFallback[0], '(反向构造:抽掉)');
755
+ },
756
+ },
757
+ ];
758
+ if (!declaration.pointer) {
759
+ probes.push({ element: '沿用上游栏', strip: (value) => value.replaceAll('沿用上游', '(反向构造:抽掉)') });
760
+ }
761
+ for (const probe of probes) {
762
+ const stripped = probe.strip(text);
763
+ assertTrue(stripped !== text, '反向构造前提不成立(文本缺该要素): ' + declaration.label + ' / ' + probe.element);
764
+ assertTrue(overrideDeclarationProblems(declaration.label, stripped, { pointer: declaration.pointer })
765
+ .some((problem) => problem.includes(probe.element.replace(/栏$/, '')) || problem.includes('兜底语')),
766
+ '抽掉要素未被判违规(判别力缺失): ' + declaration.label + ' / ' + probe.element);
767
+ }
768
+ }
769
+
770
+ // 点名的上游实体真实在场:vendored 上游面结构性缺席时输出可见 SKIP(未验证 ≠ 通过)。
771
+ // 取「声明块内」点名的路径——文件别处的说明性写法(`flow-kit/prompts/<阶段>.md` 占位)
772
+ // 不是本声明的落点。
773
+ const promptsRoot = path.join(REPO_ROOT, 'flow-kit', 'prompts');
774
+ if (fs.existsSync(promptsRoot)) {
775
+ for (const declaration of declarations) {
776
+ const block = overrideDeclarationBlock(fs.readFileSync(declaration.file, 'utf8'));
777
+ const paths = upstreamArtifactPaths(block);
778
+ assertTrue(paths.length > 0, declaration.label + ' 未点名任何上游工件(声明的锚缺落点)');
779
+ for (const rel of paths) {
780
+ assertTrue(fs.existsSync(path.join(REPO_ROOT, rel)),
781
+ declaration.label + ' 点名的上游文件不存在(锚指向幽灵实体): ' + rel);
782
+ }
783
+ }
784
+ } else {
785
+ console.log('SKIP: 307 的上游实体面(flow-kit/prompts 为 vendored 上游面,可能结构性缺席)'
786
+ + '——本次检出未校验「覆盖声明点名的上游文件真实在场」,请在 vendored 上游在场处重跑本套件');
787
+ }
788
+ },
789
+ },
790
+
791
+ // 308: `last_intel_scan` 双落点一致(原症状顺序 · 真实链路)——先 `context-scan` 建双落点,真实时间
792
+ // 流逝后再跑 `init --init-context`:state 侧取值必须以**统一形态**(本地时间 + 显式偏移,经
793
+ // time-utils)写入;段侧不由 init 改写(段行的唯一写通道是 context-scan,其改写与备份实现只有
794
+ // 一份);两者取值不一致时**必须有可见提示**并点名收敛命令——修复前是「写 `Z` 形态 + 段未更新 +
795
+ // 零提示」的静默漂移。反向控制:两处取值一致时零提示(不误报),且未刷新路径不改写既有取值。
796
+ // 段行夹具 = **真实生成件形态**(取值词元 + 行尾说明,见 INTEL_FIELD_SUFFIX):读侧若按整行剩余
797
+ // 文本比对,则同刻同形态(②)与收敛后(⑥)都会恒亮、漂移类别退化成「段内取值不是合法时间戳」
798
+ // (④)——三条都是本场景的判据;⑦ 单变量对照(只剥掉说明)证明判别条件是词元口径而非说明本身。
799
+ {
800
+ name: '308 双落点一致:带行尾说明的段行同刻静默 + 漂移类别正确 + 重扫收敛后零提示 + 单变量对照',
801
+ run: (dir) => {
802
+ const parse = requireModuleExport(timeUtilsModule, 'parseTimestamp', 'time-utils.mjs');
803
+ const extract = requireModuleExport(contextInitModule, 'extractContextStructure', 'context-init.mjs');
804
+ const readContext = () => fs.readFileSync(path.join(dir, '.specs', 'CONTEXT.md'), 'utf8');
805
+ const readLandedState = () => JSON.parse(
806
+ fs.readFileSync(path.join(dir, '.flow-comet', 'flow-comet-state.json'), 'utf8')).last_intel_scan;
807
+ // 段侧取值的读取口径与生产侧同源:结构提取定位字段 → 取**取值词元**(写侧只换词元,说明原样保留)
808
+ const readLandedSection = () => {
809
+ const field = extract(readContext()).metadata['intel-scan 元数据'];
810
+ return field === undefined ? undefined : intelFieldToken(field.last_intel_scan.value);
811
+ };
812
+
813
+ writeFile(dir, '.specs/CONTEXT.md', contextFixtureText());
814
+ writeState(dir, baseState('open'));
815
+
816
+ // ① 首扫:双落点建立且同刻同形态;段行的行尾说明原样保留(写侧只替换取值词元)
817
+ const scan = runSideScript(SIDE_CONTEXT_SCAN, ['--root', dir], dir);
818
+ assertExit(scan, 0);
819
+ assertOut(scan, 'CONTEXT-SCAN-DONE');
820
+ const scanned = readLandedState();
821
+ assertEqual(readLandedSection(), scanned, '首扫后双落点应同刻同形态');
822
+ assertTrue(readContext().includes(INTEL_FIELD_SUFFIX), '重扫改写了段行的行尾说明(写侧只应替换取值词元)');
823
+
824
+ // ② 带行尾说明的同刻同形态 ⇒ **静默**(未刷新路径的 init 不改写既有取值)——整行口径的读侧在此恒亮
825
+ const quietLanded = runStateWithProtocol(dir, ['init', CHANGE_ID]);
826
+ assertExit(quietLanded, 0);
827
+ assertEqual(readLandedState(), scanned, '未刷新路径应原样保留既有扫描时刻');
828
+ assertNotOut(quietLanded, 'INIT-NOTICE');
829
+
830
+ // ③ 真实时间流逝——时间戳是秒级精度,同一秒内的两次写入取值可能相同(漂移不可判)
831
+ sleepSync(1100);
832
+
833
+ // ④ 原症状顺序:`init --init-context`(CONTEXT 校验通过路径 → 记录扫描时刻)
834
+ const reinit = runStateWithProtocol(dir, ['init', CHANGE_ID, '--init-context']);
835
+ assertExit(reinit, 0);
836
+ assertOut(reinit, 'INIT-DONE');
837
+ const stateAfter = readLandedState();
838
+ assertTrue(/^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}[+-]\d{2}:\d{2}$/.test(stateAfter),
839
+ 'init 写入的扫描时刻形态非「本地时间 + 显式偏移」: ' + stateAfter);
840
+ assertTrue(parse(stateAfter) > parse(scanned),
841
+ 'init 写入的扫描时刻应晚于首扫(不得回退): ' + stateAfter + ' vs ' + scanned);
842
+ assertEqual(readLandedSection(), scanned, 'init 不应改写 CONTEXT 段(该段行的写通道是 context-scan)');
843
+ // 漂移不得静默:提示在场 + 两侧取值回显 + 点名收敛命令 + **类别正确**(两侧同为「本地时间 +
844
+ // 显式偏移」形态、仅时刻不同 ⇒ 「刻与形态均不一致」;行尾说明不得把类别打成取值非法)
845
+ assertOut(reinit, 'INIT-NOTICE');
846
+ assertOut(reinit, stateAfter);
847
+ assertOut(reinit, scanned);
848
+ assertOut(reinit, '刻与形态均不一致');
849
+ assertNotOut(reinit, '段内取值不是合法时间戳');
850
+ assertOut(reinit, 'context-scan');
851
+
852
+ // ⑤ 收敛:重扫一次 → 双落点同刻同形态(行尾说明原样保留)
853
+ const converge = runSideScript(SIDE_CONTEXT_SCAN, ['--root', dir], dir);
854
+ assertExit(converge, 0);
855
+ assertOut(converge, 'CONTEXT-SCAN-DONE');
856
+ const converged = readLandedState();
857
+ assertEqual(readLandedSection(), converged, '重扫后双落点应收敛为同刻同形态');
858
+ assertTrue(readContext().includes(INTEL_FIELD_SUFFIX), '收敛轮改写了段行的行尾说明');
859
+
860
+ // ⑥ 收敛后:取值一致时的 init(未授权刷新 → 原样保留既有扫描时刻)零提示——提示承诺的收敛可达
861
+ const quiet = runStateWithProtocol(dir, ['init', CHANGE_ID]);
862
+ assertExit(quiet, 0);
863
+ assertEqual(readLandedState(), converged, '未刷新路径应原样保留既有扫描时刻');
864
+ assertNotOut(quiet, 'INIT-NOTICE');
865
+
866
+ // ⑦ 单变量对照:**只**剥掉段行的行尾说明(取值词元不变、state 不变)→ 仍然静默——判别条件是
867
+ // 「取值词元」口径而非「有没有说明」;裸取值行(无说明)是写侧支持的既有形态,须继续正确
868
+ const bareLine = readContext().replace(INTEL_FIELD_SUFFIX, '');
869
+ assertTrue(bareLine !== readContext(), '单变量对照前提不成立:段行不含夹具行尾说明');
870
+ writeFile(dir, '.specs/CONTEXT.md', bareLine);
871
+ const quietBare = runStateWithProtocol(dir, ['init', CHANGE_ID]);
872
+ assertExit(quietBare, 0);
873
+ assertNotOut(quietBare, 'INIT-NOTICE');
874
+
875
+ // ⑧ 向后兼容:取值词元带 markdown 引号(`` `…` ``;模板/旧夹具形态)时按词元归一后比对 → 静默
876
+ writeFile(dir, '.specs/CONTEXT.md',
877
+ contextFixtureText().replace(INTEL_FIELD_VALUE + INTEL_FIELD_SUFFIX,
878
+ '`' + converged + '`' + INTEL_FIELD_SUFFIX));
879
+ const quietQuoted = runStateWithProtocol(dir, ['init', CHANGE_ID]);
880
+ assertExit(quietQuoted, 0);
881
+ assertNotOut(quietQuoted, 'INIT-NOTICE');
882
+ },
883
+ },
884
+
885
+ // 309: 漂移判据的形态边界与反向控制(判别力 + 零误报)——① **同一时刻的两种形态**(state 为历史
886
+ // `Z` 值、段侧为本地偏移)也判漂移:提示在场且点名形态差异(修复前该形态零提示、state 被原样保留);
887
+ // ② 段缺席 = 无可比对面 → 零提示(不无中生有);③ 段内取值不可解析(占位)→ 仍判漂移(不静默);
888
+ // 提示一律不阻断 init(exit 0);④ 判据输入端的两条命名声明(段名 / 字段名)跨文件逐字一致——
889
+ // 段行夹具一律**带行尾说明**(真实生成件形态):整行口径的读侧会让 ① 退化成「取值非法」、③ 的
890
+ // 类别也由说明决定——故 ① 显式断言「同刻不同形态」且不得落到取值非法类别。
891
+ // 两处各写一份字面量是本机制的既有形态(单一来源收口须改到写边界外的脚本,见 SUMMARY 的已知接受),
892
+ // 故此处把「不得静默漂移」机检化:任一侧改名即红,而漂移的后果正是 ② 的静默路径。
893
+ {
894
+ name: '309 漂移判据边界:同刻不同形态必报 + 段缺席零误报 + 段内占位取值不静默 + 命名声明跨文件一致',
895
+ run: (dir) => {
896
+ const readContext = () => fs.readFileSync(path.join(dir, '.specs', 'CONTEXT.md'), 'utf8');
897
+ const readLandedState = () => JSON.parse(
898
+ fs.readFileSync(path.join(dir, '.flow-comet', 'flow-comet-state.json'), 'utf8')).last_intel_scan;
899
+
900
+ // ① state = `Z` 形态(历史写入的真实形态);段 = 同一时刻的「本地时间 + 显式偏移」,**带行尾说明**
901
+ // (真实生成件形态)——两侧同刻 ⇒ 类别必须是「同刻不同形态」,不得退化成取值非法
902
+ const zForm = '2026-09-24T18:14:23Z';
903
+ const localForm = '2026-09-25T02:14:23+08:00';
904
+ writeState(dir, { ...baseState('open'), last_intel_scan: zForm });
905
+ writeFile(dir, '.specs/CONTEXT.md',
906
+ contextFixtureText().replace(INTEL_FIELD_VALUE, localForm));
907
+ const sameMoment = runStateWithProtocol(dir, ['init', CHANGE_ID]);
908
+ assertExit(sameMoment, 0);
909
+ assertOut(sameMoment, 'INIT-NOTICE');
910
+ assertOut(sameMoment, '同刻不同形态');
911
+ assertNotOut(sameMoment, '段内取值不是合法时间戳');
912
+ assertOut(sameMoment, zForm);
913
+ assertOut(sameMoment, localForm);
914
+ assertEqual(readLandedState(), zForm, '未刷新路径不得改写既有扫描时刻');
915
+
916
+ // ② 段缺席(CONTEXT 不含 intel-scan 段)→ 无可比对面 → 零提示
917
+ writeFile(dir, '.specs/CONTEXT.md', contextFixtureText({ intelSection: false }));
918
+ const noSection = runStateWithProtocol(dir, ['init', CHANGE_ID + '-no-section']);
919
+ assertExit(noSection, 0);
920
+ assertNotOut(noSection, 'INIT-NOTICE');
921
+
922
+ // ③ 段内取值词元不可解析(占位形态)→ 仍判漂移且点明该类别(静默放过会让「段侧从未被正确
923
+ // 写入」长期不可见);占位词元之后的说明不参与判定(类别由词元决定)
924
+ writeFile(dir, '.specs/CONTEXT.md',
925
+ contextFixtureText().replace(INTEL_FIELD_VALUE, '(待扫描)'));
926
+ const placeholder = runStateWithProtocol(dir, ['init', CHANGE_ID + '-placeholder']);
927
+ assertExit(placeholder, 0);
928
+ assertOut(placeholder, 'INIT-NOTICE');
929
+ assertOut(placeholder, '段内取值不是合法时间戳');
930
+ assertOut(placeholder, '(待扫描)');
931
+
932
+ // ④ 取值词元口径的夹具前提(合成输入 · 纯函数口径):段行带行尾说明时,结构提取返回的是
933
+ // 「词元 + 说明」整串——按整行比对会落「取值非法」(缺陷形态),按词元比对才落正确类别
934
+ // (类别本身已在 ① 的真实命令面断言)。此处把夹具形态与词元提取钉住:夹具若退回裸词元,
935
+ // 本锚立即红(防「缺陷形态重新变得不可见」的假绿)。
936
+ const fieldsWithSuffix = requireModuleExport(contextInitModule, 'extractContextStructure', 'context-init.mjs')(
937
+ contextFixtureText()).metadata['intel-scan 元数据'].last_intel_scan.value;
938
+ assertTrue(fieldsWithSuffix.includes(INTEL_FIELD_SUFFIX),
939
+ '夹具段行未带行尾说明(真实生成件形态前提不成立): ' + JSON.stringify(fieldsWithSuffix));
940
+ assertTrue(intelFieldToken(fieldsWithSuffix) === INTEL_FIELD_VALUE,
941
+ '取值词元口径提取错误: ' + JSON.stringify(intelFieldToken(fieldsWithSuffix)));
942
+
943
+ // ⑤ 命名声明跨文件一致(结构锚 + 反向构造):init 侧按段名 / 字段名定位段内取值,两处声明
944
+ // 漂移会让判据静默退化成 ② 的「无可比对面」——故两处字面量必须逐字相等,合成改写即红。
945
+ // 落点**按形态反查**(不写文件名):声明 intel-scan 段名 / 字段名字面量的引擎模块,写侧 =
946
+ // 重扫命令本身,读侧 = 其余的那个声明方(迁移后的落点是 `lib/state-intelscan.mjs`)。
947
+ const consumerDeclarers = engineScriptFiles().filter((rel) =>
948
+ Object.keys(intelMetadataNameDeclarations(fs.readFileSync(path.join(SCRIPTS_DIR, rel), 'utf8'))).length > 0);
949
+ assertEqual(consumerDeclarers.length, 2,
950
+ 'intel-scan 命名声明应恰两处(写侧 + 读侧),实际: ' + JSON.stringify(consumerDeclarers));
951
+ const producerRel = path.relative(SCRIPTS_DIR, SIDE_CONTEXT_SCAN).split(path.sep).join('/');
952
+ const consumerRel = consumerDeclarers.find((rel) => rel !== producerRel);
953
+ assertTrue(consumerRel !== undefined,
954
+ 'intel-scan 命名声明的写侧(重扫命令)不在声明方内: ' + JSON.stringify(consumerDeclarers));
955
+ const consumerText = fs.readFileSync(path.join(SCRIPTS_DIR, consumerRel), 'utf8');
956
+ const producerText = fs.readFileSync(SIDE_CONTEXT_SCAN, 'utf8');
957
+ const namingProblems = intelMetadataNameProblems(consumerText, producerText);
958
+ assertEqual(namingProblems.length, 0, 'intel-scan 命名声明漂移: ' + namingProblems.join(' | '));
959
+ const tamperedSection = producerText.replace("'intel-scan 元数据'", "'intel-scan 元数据(漂移)'");
960
+ assertTrue(tamperedSection !== producerText, '反向构造前提不成立:重扫命令侧缺段名字面量声明');
961
+ assertTrue(intelMetadataNameProblems(consumerText, tamperedSection)
962
+ .some((problem) => problem.includes('段名字面量两处声明不一致')),
963
+ '段名漂移未被判定(判别力缺失)');
964
+ const tamperedField = producerText.replace("'last_intel_scan'", "'last_intel_scan_v2'");
965
+ assertTrue(tamperedField !== producerText, '反向构造前提不成立:重扫命令侧缺字段名字面量声明');
966
+ assertTrue(intelMetadataNameProblems(consumerText, tamperedField)
967
+ .some((problem) => problem.includes('字段名字面量两处声明不一致')),
968
+ '字段名漂移未被判定(判别力缺失)');
969
+ },
970
+ },
971
+ ];