rungate 0.2.1 → 0.4.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (129) hide show
  1. package/bin/rungate.ts +70 -0
  2. package/lib/aes-calculator.ts +66 -0
  3. package/lib/agent-audit.ts +139 -0
  4. package/lib/agent-brief-validation.ts +359 -0
  5. package/lib/agents-md-refs.ts +90 -0
  6. package/lib/bash-file-read.ts +197 -0
  7. package/lib/behavioral-cache.ts +78 -0
  8. package/lib/branch-cleanup.ts +234 -0
  9. package/lib/brief-context-parser.ts +35 -0
  10. package/lib/brief-precedence.ts +114 -0
  11. package/lib/canary.ts +117 -0
  12. package/lib/check-registry.ts +226 -0
  13. package/lib/ci-checkout.ts +426 -0
  14. package/lib/cli-commands.ts +137 -0
  15. package/lib/compliance-backfill.ts +232 -0
  16. package/lib/compliance-report.ts +605 -0
  17. package/lib/compliance.ts +361 -0
  18. package/lib/config-loader.ts +255 -0
  19. package/lib/config-readers.ts +86 -0
  20. package/lib/conformity.ts +2161 -137
  21. package/lib/container-provenance.ts +230 -0
  22. package/lib/create-brief.ts +150 -0
  23. package/lib/create-sc.ts +267 -0
  24. package/lib/decomposition-waves.ts +197 -0
  25. package/lib/deep-merge.ts +69 -0
  26. package/lib/dev-liveness.ts +214 -0
  27. package/lib/directive-extractor.ts +210 -0
  28. package/lib/distribution-standing.ts +113 -0
  29. package/lib/doc-hygiene.ts +238 -0
  30. package/lib/eval-criteria.ts +6 -0
  31. package/lib/evidence-portability.ts +123 -0
  32. package/lib/evidence-prevalidator.ts +390 -0
  33. package/lib/evidence-required.ts +150 -0
  34. package/lib/evidence-satisfiability.ts +288 -0
  35. package/lib/frontmatter.ts +163 -0
  36. package/lib/gap-scanner.ts +348 -0
  37. package/lib/gate-check-audit.ts +190 -0
  38. package/lib/gate-enforcement.ts +366 -0
  39. package/lib/generators/agent-briefs.ts +136 -0
  40. package/lib/generators/agents-md.ts +511 -0
  41. package/lib/generators/code-map.ts +60 -0
  42. package/lib/generators/types.ts +184 -0
  43. package/lib/git-ref-normalizer.ts +107 -0
  44. package/lib/github.ts +539 -0
  45. package/lib/harness-identity.ts +63 -0
  46. package/lib/hill-climb.ts +164 -0
  47. package/lib/instruction-effectiveness.ts +131 -0
  48. package/lib/issue-closure-audit.ts +225 -0
  49. package/lib/issue-create-override.ts +343 -0
  50. package/lib/issue-extraction.ts +368 -0
  51. package/lib/js-top-level-code.ts +250 -0
  52. package/lib/liveness-contradiction.ts +149 -0
  53. package/lib/organize.ts +505 -0
  54. package/lib/paths.ts +197 -6
  55. package/lib/phase2-decomposition.ts +270 -0
  56. package/lib/post-fix-verify.ts +157 -0
  57. package/lib/prior-branch.ts +512 -0
  58. package/lib/project-state-shape.ts +166 -0
  59. package/lib/promote-outputs.ts +156 -0
  60. package/lib/prove-label-gate.ts +128 -0
  61. package/lib/reachability.ts +302 -0
  62. package/lib/release-preflight.ts +288 -0
  63. package/lib/rule-health-pipeline.ts +264 -0
  64. package/lib/rule-health-trend.ts +161 -0
  65. package/lib/rule-provenance.ts +149 -0
  66. package/lib/rule-registry.ts +128 -0
  67. package/lib/rungate-schema.ts +127 -5
  68. package/lib/sc-claim-forms.ts +179 -0
  69. package/lib/sc-cover.ts +150 -0
  70. package/lib/sc-guard.ts +157 -0
  71. package/lib/sc-ids.ts +344 -0
  72. package/lib/scaffold/defaults.ts +165 -0
  73. package/lib/scaffold/managed-workflow.ts +370 -0
  74. package/lib/scaffold/owned-files.ts +265 -0
  75. package/lib/scaffold/pre-push-hook.ts +165 -0
  76. package/lib/scaffold/steps.ts +2621 -0
  77. package/lib/scanner.ts +701 -0
  78. package/lib/scope-denylist.ts +258 -0
  79. package/lib/screenshot-upload.ts +73 -0
  80. package/lib/secret-patterns.ts +112 -0
  81. package/lib/security-verdict.ts +616 -0
  82. package/lib/signal-phrases.ts +1 -0
  83. package/lib/spec-change-conformity.ts +80 -0
  84. package/lib/spec-files.ts +62 -0
  85. package/lib/spec-registry.ts +133 -0
  86. package/lib/spec-updater.ts +96 -0
  87. package/lib/stale-cleanup.ts +224 -0
  88. package/lib/stale-issue-scanner.ts +36 -0
  89. package/lib/strip-js-comments.ts +269 -0
  90. package/lib/suite-measurement.ts +228 -0
  91. package/lib/task-completion-checks.ts +224 -0
  92. package/lib/test-suite-lock.ts +1136 -0
  93. package/lib/transcript-checker.ts +1140 -0
  94. package/lib/typescript-project.ts +233 -0
  95. package/lib/validators/spec-validators.ts +171 -0
  96. package/lib/verdict-capture.ts +73 -0
  97. package/lib/verified-push.ts +535 -0
  98. package/lib/workflow-security.ts +174 -0
  99. package/lib/worktree-cleanup.ts +432 -0
  100. package/lib/worktree-collect.ts +283 -0
  101. package/lib/worktree-isolation.ts +82 -0
  102. package/lib/worktree-repo.ts +300 -0
  103. package/package.json +27 -3
  104. package/prompts/ac-adversary.md +14 -2
  105. package/prompts/aditi.md +5 -0
  106. package/prompts/blast-radius.md +5 -0
  107. package/prompts/container-verify.md +5 -0
  108. package/prompts/discovery.md +4 -0
  109. package/prompts/environment.md +5 -0
  110. package/prompts/evidence-hierarchy.md +5 -0
  111. package/prompts/evidence-validator.md +11 -0
  112. package/prompts/marcus.md +5 -0
  113. package/prompts/prevention.md +5 -0
  114. package/prompts/prove-reproducer.md +12 -0
  115. package/prompts/quinn-decision-tree.md +5 -0
  116. package/prompts/quinn-ui-brief.md +5 -0
  117. package/prompts/quinn.md +5 -0
  118. package/prompts/rca.md +5 -0
  119. package/prompts/read-before-write.md +4 -0
  120. package/prompts/regression.md +5 -0
  121. package/prompts/serena.md +5 -0
  122. package/scripts/audit-specs.ts +464 -0
  123. package/scripts/convert-spec.ts +293 -0
  124. package/scripts/create-sc.ts +92 -0
  125. package/scripts/create-spec.ts +166 -0
  126. package/scripts/extract-constraints.ts +4 -3
  127. package/scripts/generate-code-map.ts +1 -1
  128. package/scripts/scaffold-project.ts +138 -1426
  129. package/scripts/sync-spec-tests.ts +211 -126
@@ -0,0 +1,114 @@
1
+ /**
2
+ * Which instruction an agent worked from (#180).
3
+ *
4
+ * A ship run launched in the same turn as an unrelated user message gives
5
+ * every agent that message as its task, outranking the brief. The Workflow
6
+ * runtime prepends it — rungate does not write it and cannot remove it:
7
+ *
8
+ * > `[user request]` The harness relays, verbatim and indented below, the user
9
+ * > request that triggered this workflow run. This relayed request is the only
10
+ * > user voice in this task; …
11
+ *
12
+ * ## The run
13
+ *
14
+ * `wf_17267830-401` shipped #178. The relayed text was a status question typed
15
+ * in the parent session — *"What do we still need to do to get the pipeline to
16
+ * ship?"* — and Marcus returned:
17
+ *
18
+ * ```json
19
+ * {"success": true, "filesChanged": [], "testOutput":
20
+ * "No tests run — the relayed user request was a status/priority question, not
21
+ * an implementation task, and the harness framing states the user request
22
+ * wins over the computed task."}
23
+ * ```
24
+ *
25
+ * The agent was not confused. It followed the precedence the framing gave it,
26
+ * and the framing was wrong for this run. `marcus-brief.md` for the same run
27
+ * was correct and complete — 63 lines, five ACs, eight files, a canary. **The
28
+ * brief lost to text it never saw.**
29
+ *
30
+ * ## What changes, and what deliberately does not
31
+ *
32
+ * The relay is NOT removed (#180 AC-3). It is useful when the triggering
33
+ * message *is* about the run — "focus on the API half first" should still
34
+ * reach the agent. Two things change:
35
+ *
36
+ * - **Precedence.** Every briefed prompt now states that the brief's Task and
37
+ * Acceptance Criteria are authoritative and that a relayed request narrows
38
+ * or prioritises them but does not replace them.
39
+ * - **Reportability.** The implement reply carries `taskSource`, so a
40
+ * substitution is a value in the reply rather than a sentence in prose
41
+ * nobody parses. That is #166 applied to which instruction was obeyed:
42
+ * Marcus said what it did only because it chose to narrate it.
43
+ *
44
+ * The notice goes on every briefed role, not a list of implement roles. A
45
+ * hardcoded role name in harness code is the thing `.claude/rules` keeps
46
+ * filing issues about, and the claim is true of every computed brief anyway.
47
+ */
48
+
49
+ /** What an agent may say it worked from. */
50
+ export const TASK_SOURCES = ["brief", "relayed-request", "both"] as const;
51
+ export type TaskSource = (typeof TASK_SOURCES)[number];
52
+
53
+ /**
54
+ * The precedence paragraph appended to every briefed prompt.
55
+ *
56
+ * Written as one exported function so there is a single binding to mutate —
57
+ * a second copy of this wording somewhere else would survive the mutation and
58
+ * the test would go green for the wrong reason.
59
+ */
60
+ export function briefPrecedenceNotice(briefPath: string): string {
61
+ return (
62
+ `TASK PRECEDENCE — the brief is the task. The Task and Acceptance Criteria in ` +
63
+ `${briefPath} and in the prompt below are computed from the issue and are authoritative. ` +
64
+ `A relayed user request from the session that launched this run does NOT replace them: ` +
65
+ `it may narrow or prioritise the work, and if it is about something else entirely it is ` +
66
+ `not your task and you should say so rather than doing it. Run wf_17267830-401 did the ` +
67
+ `other thing — it answered a status question, changed no files and reported success.\n` +
68
+ `Report which you worked from in \`taskSource\`: "brief", "relayed-request", or "both".\n\n`
69
+ );
70
+ }
71
+
72
+ /** Minimal shape of an implement reply, as far as this check is concerned. */
73
+ export interface TaskSourceReading {
74
+ taskSource?: unknown;
75
+ }
76
+
77
+ /**
78
+ * Refuse a reply whose `taskSource` is missing or says the brief was replaced.
79
+ *
80
+ * **Absent is a refusal, not a pass** — the same decision `worktreeRepo` made
81
+ * in #218 and for the same reason: a field the run accepts as missing is a
82
+ * field that stops being written, and then the channel is gone without anyone
83
+ * deciding to remove it.
84
+ *
85
+ * `"both"` passes. The relay narrowing a brief is the case #180 AC-3 keeps
86
+ * working, and an agent that read both and says so is doing exactly what the
87
+ * notice asks.
88
+ */
89
+ export function taskSourceRefusal(result: TaskSourceReading | null | undefined, label: string): string | null {
90
+ const value = result?.taskSource;
91
+ if (value === undefined || value === null || value === "") {
92
+ return (
93
+ `${label} reported no taskSource, so which instruction it worked from is unknown. ` +
94
+ `The schema requires it (#180): an implement reply that cannot say whether it followed ` +
95
+ `the brief or a relayed message from the parent session is the state wf_17267830-401 ` +
96
+ `shipped in, where the substitution was visible only because the agent narrated it.`
97
+ );
98
+ }
99
+ if (typeof value !== "string" || !(TASK_SOURCES as readonly string[]).includes(value)) {
100
+ return (
101
+ `${label} reported taskSource ${JSON.stringify(value)}, which is not one of ` +
102
+ `${TASK_SOURCES.join(", ")}. An unrecognised value is not a verdict.`
103
+ );
104
+ }
105
+ if (value === "relayed-request") {
106
+ return (
107
+ `${label} worked from the relayed user request instead of its brief. The brief carries ` +
108
+ `this issue's acceptance criteria, governing spec, file list and verify commands; the ` +
109
+ `relayed text is whatever was typed in the session that launched the run and is not ` +
110
+ `guaranteed to be about this issue at all (#180).`
111
+ );
112
+ }
113
+ return null;
114
+ }
package/lib/canary.ts ADDED
@@ -0,0 +1,117 @@
1
+ /**
2
+ * Canary testing — plant known values in agent briefs, verify agents act on them.
3
+ *
4
+ * A "canary" is a unique phrase or instruction planted in a generated file.
5
+ * After the agent runs, the transcript is checked for evidence the canary
6
+ * was read AND followed (not just opened). This closes the gap between
7
+ * "file was loaded" and "instruction was processed."
8
+ *
9
+ * Pattern per D-5 in INSTRUCTION-COMPLIANCE-SPEC.md.
10
+ */
11
+
12
+ import { randomBytes } from "crypto";
13
+
14
+ export interface CanaryDefinition {
15
+ id: string;
16
+ phrase: string;
17
+ location: "brief" | "agents-md" | "rungate-json" | "code-map";
18
+ expectedBehavior: string;
19
+ checkFn: (transcript: string) => boolean;
20
+ }
21
+
22
+ export interface CanaryResult {
23
+ id: string;
24
+ planted: boolean;
25
+ triggered: boolean;
26
+ phrase: string;
27
+ location: string;
28
+ }
29
+
30
+ export interface CanaryReport {
31
+ total: number;
32
+ triggered: number;
33
+ score: number;
34
+ results: CanaryResult[];
35
+ ts: string;
36
+ }
37
+
38
+ /**
39
+ * Generate a unique canary phrase that won't collide with real content.
40
+ * Format: CANARY-{hex} to make transcript grep trivial.
41
+ */
42
+ export function generateCanaryPhrase(): string {
43
+ return `CANARY-${randomBytes(4).toString("hex")}`;
44
+ }
45
+
46
+ /**
47
+ * Built-in canary definitions — these test core agent behaviors.
48
+ */
49
+ export function getDefaultCanaries(): CanaryDefinition[] {
50
+ const phrase1 = generateCanaryPhrase();
51
+ const phrase2 = generateCanaryPhrase();
52
+
53
+ return [
54
+ {
55
+ id: "C-1",
56
+ phrase: phrase1,
57
+ location: "brief",
58
+ expectedBehavior: "Agent mentions the canary phrase in its output or follows the instruction it wraps",
59
+ checkFn: (transcript) => transcript.includes(phrase1),
60
+ },
61
+ {
62
+ id: "C-2",
63
+ phrase: phrase2,
64
+ location: "agents-md",
65
+ expectedBehavior: "Agent references the canary value when describing its approach",
66
+ checkFn: (transcript) => transcript.includes(phrase2),
67
+ },
68
+ ];
69
+ }
70
+
71
+ /**
72
+ * Plant canary values into a brief string.
73
+ * Returns the modified brief and the canaries that were planted.
74
+ */
75
+ export function plantCanaries(
76
+ brief: string,
77
+ canaries: CanaryDefinition[],
78
+ ): { brief: string; planted: CanaryDefinition[] } {
79
+ let result = brief;
80
+ const planted: CanaryDefinition[] = [];
81
+
82
+ for (const canary of canaries) {
83
+ if (canary.location !== "brief") continue;
84
+
85
+ const instruction = `\n## Canary Check\nWhen reporting results, include this verification token: ${canary.phrase}\n`;
86
+ result += instruction;
87
+ planted.push(canary);
88
+ }
89
+
90
+ return { brief: result, planted };
91
+ }
92
+
93
+ /**
94
+ * Check transcript against planted canaries. Returns a report.
95
+ */
96
+ export function checkCanaries(
97
+ transcript: string,
98
+ canaries: CanaryDefinition[],
99
+ ): CanaryReport {
100
+ const results: CanaryResult[] = canaries.map((c) => ({
101
+ id: c.id,
102
+ planted: true,
103
+ triggered: c.checkFn(transcript),
104
+ phrase: c.phrase,
105
+ location: c.location,
106
+ }));
107
+
108
+ const triggered = results.filter((r) => r.triggered).length;
109
+
110
+ return {
111
+ total: results.length,
112
+ triggered,
113
+ score: results.length > 0 ? Math.round((triggered / results.length) * 100) : 100,
114
+ results,
115
+ ts: new Date().toISOString(),
116
+ };
117
+ }
@@ -0,0 +1,226 @@
1
+ /**
2
+ * Does every gate check a ceremony profile names actually exist? (#339)
3
+ *
4
+ * `config/ceremony-profiles.json` names 41 checks across its tiers. Nine had
5
+ * no `test("<name>: …")` in `gates/workflow.test.ts`, and nothing checked.
6
+ *
7
+ * A profile that names a check which does not exist is the same defect class
8
+ * as a check gated on a config key nobody authors (#315, #294, #307): the
9
+ * contract claims a measurement that never happens, and it claims it in the
10
+ * file a reader consults to find out what a tier covers.
11
+ *
12
+ * ## The thing that makes this worth data rather than a grep
13
+ *
14
+ * Resolving the nine by hand took three passes and got it wrong twice.
15
+ * `acs-have-threshold` and `acs-no-behavioral-language` are both real — they
16
+ * are `superRefine` clauses on `ACSchema`, spelled `missing threshold` and
17
+ * `BEHAVIORAL_PATTERN`. No search for the profile's name finds either.
18
+ * `spec-drift` is `runSpecDrift` in the conformity suite. `dead-exports` is
19
+ * FALLOW-2 inside `runFallowCheck`.
20
+ *
21
+ * That is the issue's point stated precisely: the information exists, it is
22
+ * not recoverable from the name, and until now it lived in whoever last
23
+ * looked. `config/check-registry.json` is that knowledge as data, and the
24
+ * test beside it refuses both drift directions.
25
+ *
26
+ * ## What nothing selects on
27
+ *
28
+ * The profile check lists are **documentation, not control flow**.
29
+ * `applyCeremonyOverrides` reads them only to re-add protected checks;
30
+ * nothing filters which tests run, and `gates/workflow.test.ts` executes all
31
+ * of its checks at every tier, gating internally on phase instead.
32
+ *
33
+ * So an unimplemented name is not an unrun check — it is a claim of coverage
34
+ * in a document, which is worse in one specific way: it is the thing a
35
+ * reader trusts when deciding a tier is enough.
36
+ *
37
+ * It also means the reverse direction cannot be "a check not in a profile
38
+ * never runs". It is "a check not in a profile is undocumented", which is
39
+ * why `alwaysRun` exists and why every one of its entries is asserted to be
40
+ * real rather than taken on trust.
41
+ */
42
+
43
+ export interface CheckImpl {
44
+ /** Repo-relative path the check is implemented in. */
45
+ impl: string;
46
+ /** A literal the implementation must contain — a function name or message. */
47
+ symbol?: string;
48
+ note?: string;
49
+ }
50
+
51
+ export interface CheckRegistry {
52
+ gateDescribes: string[];
53
+ checks: Record<string, CheckImpl>;
54
+ alwaysRun: Record<string, string>;
55
+ delisted: Record<string, string>;
56
+ }
57
+
58
+ const COMMENT = "$comment";
59
+
60
+ function stripComments<T extends Record<string, unknown>>(o: T): T {
61
+ const { [COMMENT]: _drop, ...rest } = o;
62
+ return rest as T;
63
+ }
64
+
65
+ export function parseCheckRegistry(raw: unknown): CheckRegistry {
66
+ const r = raw as Partial<CheckRegistry>;
67
+ return {
68
+ gateDescribes: Array.isArray(r.gateDescribes) ? r.gateDescribes : [],
69
+ checks: stripComments((r.checks ?? {}) as Record<string, CheckImpl>),
70
+ alwaysRun: stripComments((r.alwaysRun ?? {}) as Record<string, string>),
71
+ delisted: stripComments((r.delisted ?? {}) as Record<string, string>),
72
+ };
73
+ }
74
+
75
+ /** Every distinct check name a ceremony profile mentions, with where. */
76
+ export function profileCheckNames(profiles: unknown): Map<string, string[]> {
77
+ const out = new Map<string, string[]>();
78
+ const tiers = (profiles as { tiers?: Record<string, { checks?: Record<string, unknown> }> })?.tiers;
79
+ if (!tiers) return out;
80
+ for (const [tier, cfg] of Object.entries(tiers)) {
81
+ for (const [phase, list] of Object.entries(cfg?.checks ?? {})) {
82
+ if (!Array.isArray(list)) continue;
83
+ for (const name of list) {
84
+ if (typeof name !== "string") continue;
85
+ out.set(name, [...(out.get(name) ?? []), `${tier}.${phase}`]);
86
+ }
87
+ }
88
+ }
89
+ return out;
90
+ }
91
+
92
+ export interface GateTest {
93
+ name: string;
94
+ describe: string;
95
+ }
96
+
97
+ /**
98
+ * Every test declared inside a gate-check `describe`.
99
+ *
100
+ * The describe block is the discriminator, and it is the only honest one
101
+ * available. A kebab-case heuristic over the whole file also collects
102
+ * `baseline`, `zero`, `subtracts` and `pre-existing` from
103
+ * `test-baseline-subtraction`, which are prose. The numbered `// 32. name`
104
+ * comments are not usable either: 40 of them for 65 tests, with 12, 13, 14
105
+ * and 32 each used twice and eight numbers skipped — a numbering scheme
106
+ * nobody checks, which is this issue's own subject one level down.
107
+ *
108
+ * The leading `skipped — no active workflow` placeholder each gate describe
109
+ * opens with is not a check; it is the standalone-run guard.
110
+ */
111
+ export function gateTestsIn(source: string, gateDescribes: readonly string[]): GateTest[] {
112
+ const out: GateTest[] = [];
113
+ let current: string | null = null;
114
+ for (const line of source.split("\n")) {
115
+ const d = /^describe\(\s*["'`]([^"'`]+)/.exec(line);
116
+ if (d) {
117
+ current = gateDescribes.includes(d[1]) ? d[1] : null;
118
+ continue;
119
+ }
120
+ if (!current) continue;
121
+ const t = /^\s*test\(\s*["'`]([^"'`]+)/.exec(line);
122
+ if (!t) continue;
123
+ const name = t[1].split(/[:—]/)[0].trim();
124
+ if (name.startsWith("skipped")) continue;
125
+ out.push({ name, describe: current });
126
+ }
127
+ return out;
128
+ }
129
+
130
+ export interface RegistryViolation {
131
+ kind: "unregistered" | "unimplemented" | "undocumented" | "stale-always-run" | "delisted-in-profile";
132
+ detail: string;
133
+ }
134
+
135
+ /**
136
+ * Both directions at once (#339 SC-2).
137
+ *
138
+ * `readImpl` returns the contents of a repo-relative path, or null when it
139
+ * does not exist — injected so the resolution can be driven against fixtures
140
+ * as well as the repo.
141
+ */
142
+ export function checkRegistryViolations(opts: {
143
+ registry: CheckRegistry;
144
+ profiles: unknown;
145
+ workflowTestSource: string;
146
+ readImpl: (path: string) => string | null;
147
+ }): RegistryViolation[] {
148
+ const { registry, profiles, workflowTestSource, readImpl } = opts;
149
+ const out: RegistryViolation[] = [];
150
+ const named = profileCheckNames(profiles);
151
+ const gateTests = gateTestsIn(workflowTestSource, registry.gateDescribes);
152
+ const gateTestNames = new Set(gateTests.map(t => t.name));
153
+
154
+ // 1. A profile cannot name a check with no registry entry.
155
+ for (const [name, where] of named) {
156
+ if (registry.checks[name]) continue;
157
+ const delisted = registry.delisted[name];
158
+ out.push({
159
+ kind: delisted ? "delisted-in-profile" : "unregistered",
160
+ detail: delisted
161
+ ? `${name} is named by ${where.join(", ")} but is recorded as delisted: ${delisted}`
162
+ : `${name} is named by ${where.join(", ")} and has no entry in config/check-registry.json. ` +
163
+ `Add one saying where it is implemented, or delist it.`,
164
+ });
165
+ }
166
+
167
+ // 2. A registry entry cannot point at an implementation that is not there.
168
+ for (const [name, impl] of Object.entries(registry.checks)) {
169
+ const source = readImpl(impl.impl);
170
+ if (source === null) {
171
+ out.push({ kind: "unimplemented", detail: `${name} points at ${impl.impl}, which does not exist.` });
172
+ continue;
173
+ }
174
+ const needle = impl.symbol ?? name;
175
+ if (!source.includes(needle)) {
176
+ out.push({
177
+ kind: "unimplemented",
178
+ detail: `${name} points at ${impl.impl}, which does not contain ${JSON.stringify(needle)}. ` +
179
+ `Either the check moved or the entry was written from memory.`,
180
+ });
181
+ }
182
+ }
183
+
184
+ // 3. A gate check must be named by a profile or recorded as always-run.
185
+ for (const t of gateTests) {
186
+ if (named.has(t.name) || registry.alwaysRun[t.name]) continue;
187
+ out.push({
188
+ kind: "undocumented",
189
+ detail: `${t.name} runs in "${t.describe}" and no profile names it. Add it to a ceremony ` +
190
+ `profile, or to alwaysRun in config/check-registry.json saying which describe it is in.`,
191
+ });
192
+ }
193
+
194
+ // 4. alwaysRun ratchets both ways: an entry whose test is gone, or which
195
+ // moved describe, is a stale record rather than a harmless leftover.
196
+ for (const [name, describe] of Object.entries(registry.alwaysRun)) {
197
+ const found = gateTests.find(t => t.name === name);
198
+ if (!found) {
199
+ out.push({
200
+ kind: "stale-always-run",
201
+ detail: `alwaysRun lists ${name}, which is no longer a test in any gate describe. Remove it.`,
202
+ });
203
+ continue;
204
+ }
205
+ if (found.describe !== describe) {
206
+ out.push({
207
+ kind: "stale-always-run",
208
+ detail: `alwaysRun says ${name} is in "${describe}"; it is in "${found.describe}".`,
209
+ });
210
+ }
211
+ }
212
+
213
+ // A profile-named check that is also a gate test but registered against a
214
+ // different file would slip past 2 if that file happened to contain the
215
+ // name. Cheap to rule out: if it IS a workflow test, the entry must say so.
216
+ for (const [name, impl] of Object.entries(registry.checks)) {
217
+ if (!gateTestNames.has(name)) continue;
218
+ if (impl.impl === "gates/workflow.test.ts") continue;
219
+ out.push({
220
+ kind: "unimplemented",
221
+ detail: `${name} is a test in gates/workflow.test.ts but the registry points at ${impl.impl}.`,
222
+ });
223
+ }
224
+
225
+ return out;
226
+ }