@3f-consulting/spec-controller-core 0.1.0-alpha.5 → 0.1.0-alpha.50

package/dist/parse/cucumber.js

@@ -1,61 +1,7 @@
-/**
- * The `ingest/cucumber` reader — the second named observed-evidence reader.
- * Reads Cucumber-JS's JSON formatter output and normalises each scenario that
- * carries an @SCN tag into an EvidenceObservation, LEVELLED by the scenario's own
- * tier tag (@integration / @e2e / @performance).
- *
- * The level is DERIVED from the cited scenario's own tier tag, NOT from the input
- * source (Cucumber-as-orchestrator-across-levels: the scenario NAMES its tier by tag, cucumber
- * runs whichever). An @e2e scenario proven via cucumber yields an e2e observation. The
- * caller-supplied level (the JS-ecosystem default, integration, set at the CLI edge)
- * survives only as the fallback for an UNTAGGED scenario. The reader classifies FOUR-WAY
- * (@SCN-PND-013, extended by @SCN-LDG-019): any AMBIGUOUS step → a `broken` observation (a broken
- * harness — two step definitions match, so the step cannot run); any failed step → a `failed`
- * observation; all passed → a `passed` observation; otherwise INCONCLUSIVE (undefined/pending/
- * skipped) → the scenario is DROPPED (no observation), so its obligation reconciles missing by
- * absence — pending is never inferred from status.
- *
- * Parent: @SCN-LDG-011 (the tag-derivation headline) over @SCN-LDG-001 (the foundation seam).
- */
 import { relativizeToRoot } from "../lib/portablePath.js";
-/**
- * Which tag on a REPORTED scenario is its `@SCN`.
- *
- * IT USED TO BE EXPORTED FOR A SECOND READER OF THIS SAME DOCUMENT — the fitness pass's own
- * cucumber report, read by `convertedFitnessCredits` (@SCN-LNT-021). That pass and that reader went
- * at 3F-3272: the converted checks' credits come off the CI run's own step record now, whose key IS
- * the code, so nothing there has a tag line to read. The export stands because the corpus reader
- * beside it takes the same pattern.
- */
-export const SCN_TAG = /^@?(SCN-[A-Z0-9]+-\d+)$/;
-/**
- * The non-unit runtime tiers a scenario can NAME by tag. A cucumber observation's
- * level is DERIVED from the cited scenario's own tier tag — the product thesis
- * of Cucumber-as-orchestrator-ACROSS-levels: the scenario names its tier (@integration /
- * @e2e / @performance) and cucumber runs whichever, so an @e2e scenario proven via cucumber
- * yields an e2e observation. `@unit` is deliberately NOT here: unit is the vitest substrate,
- * and a cucumber run genuinely exercises the integrated tiers, not isolation. The caller-supplied
- * `fallbackQualityCheck` survives only for a scenario carrying NO tier tag (the JS-ecosystem
- * default, set at the CLI edge).
- */
+import { SCN_ID_SOURCE } from "../domain/featureCode.js";
+export const SCN_TAG = new RegExp(`^@?(${SCN_ID_SOURCE})$`);
 const TIER_TAG = /^@?(integration|e2e|performance)$/;
-/**
- * Derive the SET of levels a cucumber observation discharges from the cited scenario's own
- * tier tag(s), falling back to a single caller-supplied level when the scenario carries none.
- *
- * The MULTI-TAG RULE (@SCN-LDG-014, generalising @SCN-LDG-011): a cucumber observation discharges
- * EVERY non-unit runtime obligation its cited scenario raises. So a scenario naming
- * `@integration @e2e` yields TWO levels from a SINGLE cucumber pass (integration + e2e); the caller
- * emits one observation per level. A single-tier scenario yields exactly ONE level (LDG-011/012/013
- * — the single-tier instances of this rule); an untagged scenario yields the single fallback tier.
- * Duplicates are collapsed so a repeated tag never fans out an extra observation.
- *
- * Why discharging both is honest, not double-crediting (Evidence Manifesto §11): §11 complementarity
- * is scoped to `@unit`-vs-the-run (isolation vs the integrated system, DIFFERENT runners) — so `@unit`
- * still needs its own vitest observation. §11 does NOT bite WITHIN the cucumber tiers: one cucumber
- * execution genuinely exercises the integrated components AND the end-to-end journey (the journey
- * CONTAINS the integration), so covering both from the one run is truthful.
- */
 function deriveLevels(tags, fallbackQualityCheck) {
     const levels = [];
     for (const t of tags) {
@@ -63,109 +9,57 @@ function deriveLevels(tags, fallbackQualityCheck) {
         if (m) {
             const level = m[1];
             if (!levels.includes(level))
-                levels.push(level); // dedup — one observation per distinct tier.
+                levels.push(level);
         }
     }
     return levels.length > 0 ? levels : [fallbackQualityCheck];
 }
-/**
- * SYNTHESISE the what-broke message of an ambiguous step's `broken` observation (@SCN-LDG-019).
- *
- * Cucumber emits NO `error_message` for an ambiguous step — its result object is exactly
- * `{ "status": "ambiguous", "duration": 0 }` (the "Multiple step definitions match: …" detail is
- * PRETTY-FORMATTER-ONLY, never in the JSON). So the reader cannot quote the runner as the vitest
- * reader does (which passes the collection error through VERBATIM); it must STATE THE DIAGNOSIS
- * itself, from the one thing the report does give: the step's keyword and text.
- *
- * It names WHAT BROKE — this step, matched by two or more step definitions, so it never ran. It
- * prescribes NO CURE: which of the colliding definitions is the wrong one is not the ledger's to
- * say.
- */
 function ambiguousMessage(step) {
     const text = `${(step.keyword ?? "").trim()} ${step.name ?? ""}`.trim();
     const named = text.length > 0 ? `The step "${text}"` : "A step";
     return `${named} is ambiguous — two or more step definitions match it, so the step never ran.`;
 }
-/**
- * Parse a Cucumber JSON report into observed results, each levelled by DERIVING it from the
- * cited scenario's own tier tag (falling back to `fallbackQualityCheck` for an untagged
- * scenario). One result per scenario: those carrying an @SCN tag cite that scenario; those with
- * NO @SCN tag emit a null-scnId credit (@SCN-LDG-007 — previously DROPPED). A null-scnId credit
- * cites no scenario, so the reconciler folds it into the SUSPENSE row. A scenario is classified
- * THREE-WAY (@SCN-PND-013): passed (all steps passed) / failed (any step failed) / INCONCLUSIVE
- * (otherwise) — an inconclusive scenario emits NOTHING, dropped so it reconciles missing by absence.
- */
 export function parseCucumberEvidenceObservations(report, fallbackQualityCheck, root) {
     const results = [];
     for (const feature of report) {
-        // The feature-file locator (the where-to-fix) — carried on every credit (ruling
-        // Q5), made portable relative to the run root (verbatim without root).
         const locator = relativizeToRoot(feature.uri ?? feature.name ?? "(unknown feature)", root);
         for (const scenario of feature.elements ?? []) {
-            const tags = scenario.tags ?? [];
-            const scnTag = tags
-                .map((t) => SCN_TAG.exec(t.name ?? ""))
-                .find((m) => m !== null);
-            const steps = scenario.steps ?? [];
-            // FOUR-WAY classification (@SCN-PND-013, extended by @SCN-LDG-019) — pending is NEVER
-            // inferred from status. The DROP is what realises inconclusive→missing and the `broken`
-            // FLAG is what realises ambiguous→suspense, so `EvidenceStatus` stays binary: no new
-            // status, no reconciler change. The drop is WHOLE-SCENARIO — an inconclusive scenario emits
-            // no observation at ANY named tier (the `continue` below). The statuses that stay dropped
-            // stay honest: `undefined` (no step definition is written — the test genuinely IS absent),
-            // `pending` (explicitly deferred), `skipped` (never ran).
-            //
-            // THE AMBIGUOUS ARM IS ORDERED FIRST (@SCN-LDG-019) because cucumber halts the scenario at
-            // the ambiguous step — every step after it reads `skipped`, so the inconclusive drop would
-            // otherwise swallow the ambiguity along with them. An ambiguous step is not a stub that
-            // proved nothing but a BROKEN HARNESS: two step definitions match one step, so the proof
-            // exists and cannot execute. Dropping it as inconclusive sent the reader the WRONG remedy —
-            // write a test that already exists, rather than fix the colliding step definitions. It is
-            // cucumber's instance of the `broken` outcome vitest's collection failure established
-            // (@SCN-LDG-017): evidence that NEVER MATERIALISED.
-            //
-            // ONE observation for the whole scenario (never one per named tier): the harness broke ONCE,
-            // so a multi-tier scenario posts ONE broken item, levelled at its first named tier. Unlike
-            // vitest's collection failure (citation-less by construction — a file that fails to collect
-            // names no test), this observation CARRIES the scnId: the cucumber scenario DID cite its
-            // @SCN; only its step could not run. The reconciler's fail-safe checks `broken` BEFORE
-            // `status`, so it can never discharge (or fail) the obligation it cites; it posts to the
-            // SUSPENSE row and the obligation reconciles `missing` BY ABSENCE (pinned in
-            // reconcile.test.ts [SCN-LDG-019], under BOTH status values).
-            const ambiguous = steps.find((s) => s.result?.status === "ambiguous");
-            if (ambiguous) {
-                results.push({
-                    qualityCheck: deriveLevels(tags, fallbackQualityCheck)[0],
-                    scnId: scnTag ? scnTag[1] : null,
-                    // Structurally required, and the step certainly did not pass; the reconciler's fail-safe
-                    // checks `broken` BEFORE `status`, so this never reconciles as `failing`.
-                    status: "failed",
-                    locator,
-                    broken: true,
-                    message: ambiguousMessage(ambiguous),
-                });
-                continue;
-            }
-            const anyFailed = steps.some((s) => s.result?.status === "failed");
-            const allPassed = steps.length > 0 && steps.every((s) => s.result?.status === "passed");
-            if (!anyFailed && !allPassed)
-                continue; // inconclusive → drop the whole scenario.
-            const status = anyFailed ? "failed" : "passed";
-            // One observation PER named non-unit tier: a cucumber run of an @integration @e2e
-            // scenario discharges BOTH obligations, so it emits an integration AND an e2e observation
-            // (the multi-tag ruling's teeth, @SCN-LDG-014). A single-tier or untagged scenario emits
-            // exactly one. The levels are DERIVED from the scenario's own tier tags, not the input
-            // source; the caller-supplied level is the fallback for an untagged scenario.
-            for (const level of deriveLevels(tags, fallbackQualityCheck)) {
-                results.push({
-                    qualityCheck: level,
-                    scnId: scnTag ? scnTag[1] : null, // no @SCN tag → an uncited credit (SUSPENSE).
-                    status,
-                    locator,
-                });
-            }
+            results.push(...scenarioObservations(scenario, locator, fallbackQualityCheck));
         }
     }
     return results;
 }
+function citedScnIdOf(tags) {
+    const scnTag = tags
+        .map((t) => SCN_TAG.exec(t.name ?? ""))
+        .find((m) => m !== null);
+    return scnTag ? scnTag[1] : null;
+}
+function scenarioObservations(scenario, locator, fallbackQualityCheck) {
+    const tags = scenario.tags ?? [];
+    const scnId = citedScnIdOf(tags);
+    const steps = scenario.steps ?? [];
+    const ambiguous = steps.find((s) => s.result?.status === "ambiguous");
+    if (ambiguous) {
+        return [{
+                qualityCheck: deriveLevels(tags, fallbackQualityCheck)[0],
+                scnId,
+                status: "failed",
+                locator,
+                broken: true,
+                message: ambiguousMessage(ambiguous),
+            }];
+    }
+    const anyFailed = steps.some((s) => s.result?.status === "failed");
+    const allPassed = steps.length > 0 && steps.every((s) => s.result?.status === "passed");
+    if (!anyFailed && !allPassed)
+        return [];
+    const status = anyFailed ? "failed" : "passed";
+    return deriveLevels(tags, fallbackQualityCheck).map((level) => ({
+        qualityCheck: level,
+        scnId,
+        status,
+        locator,
+    }));
+}
 //# sourceMappingURL=cucumber.js.map

package/dist/parse/cucumber.js.map

@@ -1 +1 @@
-{"version":3,"file":"cucumber.js","sourceRoot":"","sources":["../../src/parse/cucumber.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;GAkBG;AAGH,OAAO,EAAE,gBAAgB,EAAE,MAAM,wBAAwB,CAAC;AA+B1D;;;;;;;;GAQG;AACH,MAAM,CAAC,MAAM,OAAO,GAAG,yBAAyB,CAAC;AAEjD;;;;;;;;;GASG;AACH,MAAM,QAAQ,GAAG,mCAAmC,CAAC;AAErD;;;;;;;;;;;;;;;;GAgBG;AACH,SAAS,YAAY,CACnB,IAA8B,EAC9B,oBAAyC;IAEzC,MAAM,MAAM,GAA0B,EAAE,CAAC;IACzC,KAAK,MAAM,CAAC,IAAI,IAAI,EAAE,CAAC;QACrB,MAAM,CAAC,GAAG,QAAQ,CAAC,IAAI,CAAC,CAAC,CAAC,IAAI,IAAI,EAAE,CAAC,CAAC;QACtC,IAAI,CAAC,EAAE,CAAC;YACN,MAAM,KAAK,GAAG,CAAC,CAAC,CAAC,CAAwB,CAAC;YAC1C,IAAI,CAAC,MAAM,CAAC,QAAQ,CAAC,KAAK,CAAC;gBAAE,MAAM,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC,CAAC,6CAA6C;QAChG,CAAC;IACH,CAAC;IACD,OAAO,MAAM,CAAC,MAAM,GAAG,CAAC,CAAC,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC,oBAAoB,CAAC,CAAC;AAC7D,CAAC;AAED;;;;;;;;;;;;GAYG;AACH,SAAS,gBAAgB,CAAC,IAAyC;IACjE,MAAM,IAAI,GAAG,GAAG,CAAC,IAAI,CAAC,OAAO,IAAI,EAAE,CAAC,CAAC,IAAI,EAAE,IAAI,IAAI,CAAC,IAAI,IAAI,EAAE,EAAE,CAAC,IAAI,EAAE,CAAC;IACxE,MAAM,KAAK,GAAG,IAAI,CAAC,MAAM,GAAG,CAAC,CAAC,CAAC,CAAC,aAAa,IAAI,GAAG,CAAC,CAAC,CAAC,QAAQ,CAAC;IAChE,OAAO,GAAG,KAAK,+EAA+E,CAAC;AACjG,CAAC;AAED;;;;;;;;GAQG;AACH,MAAM,UAAU,iCAAiC,CAC/C,MAA0B,EAC1B,oBAAyC,EACzC,IAAa;IAEb,MAAM,OAAO,GAA0B,EAAE,CAAC;IAC1C,KAAK,MAAM,OAAO,IAAI,MAAM,EAAE,CAAC;QAC7B,gFAAgF;QAChF,uEAAuE;QACvE,MAAM,OAAO,GAAG,gBAAgB,CAAC,OAAO,CAAC,GAAG,IAAI,OAAO,CAAC,IAAI,IAAI,mBAAmB,EAAE,IAAI,CAAC,CAAC;QAC3F,KAAK,MAAM,QAAQ,IAAI,OAAO,CAAC,QAAQ,IAAI,EAAE,EAAE,CAAC;YAC9C,MAAM,IAAI,GAAG,QAAQ,CAAC,IAAI,IAAI,EAAE,CAAC;YACjC,MAAM,MAAM,GAAG,IAAI;iBAChB,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,IAAI,IAAI,EAAE,CAAC,CAAC;iBACtC,IAAI,CAAC,CAAC,CAAC,EAAwB,EAAE,CAAC,CAAC,KAAK,IAAI,CAAC,CAAC;YAEjD,MAAM,KAAK,GAAG,QAAQ,CAAC,KAAK,IAAI,EAAE,CAAC;YACnC,sFAAsF;YACtF,wFAAwF;YACxF,qFAAqF;YACrF,4FAA4F;YAC5F,0FAA0F;YAC1F,2FAA2F;YAC3F,0DAA0D;YAC1D,EAAE;YACF,2FAA2F;YAC3F,2FAA2F;YAC3F,wFAAwF;YACxF,yFAAyF;YACzF,4FAA4F;YAC5F,0FAA0F;YAC1F,sFAAsF;YACtF,oDAAoD;YACpD,EAAE;YACF,6FAA6F;YAC7F,2FAA2F;YAC3F,4FAA4F;YAC5F,yFAAyF;YACzF,uFAAuF;YACvF,yFAAyF;YACzF,6EAA6E;YAC7E,8DAA8D;YAC9D,MAAM,SAAS,GAAG,KAAK,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,MAAM,EAAE,MAAM,KAAK,WAAW,CAAC,CAAC;YACtE,IAAI,SAAS,EAAE,CAAC;gBACd,OAAO,CAAC,IAAI,CAAC;oBACX,YAAY,EAAE,YAAY,CAAC,IAAI,EAAE,oBAAoB,CAAC,CAAC,CAAC,CAAE;oBAC1D,KAAK,EAAE,MAAM,CAAC,CAAC,CAAC,MAAM,CAAC,CAAC,CAAE,CAAC,CAAC,CAAC,IAAI;oBACjC,yFAAyF;oBACzF,0EAA0E;oBAC1E,MAAM,EAAE,QAAQ;oBAChB,OAAO;oBACP,MAAM,EAAE,IAAI;oBACZ,OAAO,EAAE,gBAAgB,CAAC,SAAS,CAAC;iBACrC,CAAC,CAAC;gBACH,SAAS;YACX,CAAC;YACD,MAAM,SAAS,GAAG,KAAK,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,MAAM,EAAE,MAAM,KAAK,QAAQ,CAAC,CAAC;YACnE,MAAM,SAAS,GAAG,KAAK,CAAC,MAAM,GAAG,CAAC,IAAI,KAAK,CAAC,KAAK,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,MAAM,EAAE,MAAM,KAAK,QAAQ,CAAC,CAAC;YACxF,IAAI,CAAC,SAAS,IAAI,CAAC,SAAS;gBAAE,SAAS,CAAC,0CAA0C;YAClF,MAAM,MAAM,GAAmB,SAAS,CAAC,CAAC,CAAC,QAAQ,CAAC,CAAC,CAAC,QAAQ,CAAC;YAC/D,kFAAkF;YAClF,0FAA0F;YAC1F,yFAAyF;YACzF,uFAAuF;YACvF,8EAA8E;YAC9E,KAAK,MAAM,KAAK,IAAI,YAAY,CAAC,IAAI,EAAE,oBAAoB,CAAC,EAAE,CAAC;gBAC7D,OAAO,CAAC,IAAI,CAAC;oBACX,YAAY,EAAE,KAAK;oBACnB,KAAK,EAAE,MAAM,CAAC,CAAC,CAAC,MAAM,CAAC,CAAC,CAAE,CAAC,CAAC,CAAC,IAAI,EAAE,8CAA8C;oBACjF,MAAM;oBACN,OAAO;iBACR,CAAC,CAAC;YACL,CAAC;QACH,CAAC;IACH,CAAC;IACD,OAAO,OAAO,CAAC;AACjB,CAAC"}
+{"version":3,"file":"cucumber.js","sourceRoot":"","sources":["../../src/parse/cucumber.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,gBAAgB,EAAE,MAAM,wBAAwB,CAAC;AAC1D,OAAO,EAAE,aAAa,EAAE,MAAM,0BAA0B,CAAC;AAgBzD,MAAM,CAAC,MAAM,OAAO,GAAG,IAAI,MAAM,CAAC,OAAO,aAAa,IAAI,CAAC,CAAC;AAE5D,MAAM,QAAQ,GAAG,mCAAmC,CAAC;AAErD,SAAS,YAAY,CACnB,IAA8B,EAC9B,oBAAyC;IAEzC,MAAM,MAAM,GAA0B,EAAE,CAAC;IACzC,KAAK,MAAM,CAAC,IAAI,IAAI,EAAE,CAAC;QACrB,MAAM,CAAC,GAAG,QAAQ,CAAC,IAAI,CAAC,CAAC,CAAC,IAAI,IAAI,EAAE,CAAC,CAAC;QACtC,IAAI,CAAC,EAAE,CAAC;YACN,MAAM,KAAK,GAAG,CAAC,CAAC,CAAC,CAAwB,CAAC;YAC1C,IAAI,CAAC,MAAM,CAAC,QAAQ,CAAC,KAAK,CAAC;gBAAE,MAAM,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC;QAClD,CAAC;IACH,CAAC;IACD,OAAO,MAAM,CAAC,MAAM,GAAG,CAAC,CAAC,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC,oBAAoB,CAAC,CAAC;AAC7D,CAAC;AAED,SAAS,gBAAgB,CAAC,IAAyC;IACjE,MAAM,IAAI,GAAG,GAAG,CAAC,IAAI,CAAC,OAAO,IAAI,EAAE,CAAC,CAAC,IAAI,EAAE,IAAI,IAAI,CAAC,IAAI,IAAI,EAAE,EAAE,CAAC,IAAI,EAAE,CAAC;IACxE,MAAM,KAAK,GAAG,IAAI,CAAC,MAAM,GAAG,CAAC,CAAC,CAAC,CAAC,aAAa,IAAI,GAAG,CAAC,CAAC,CAAC,QAAQ,CAAC;IAChE,OAAO,GAAG,KAAK,+EAA+E,CAAC;AACjG,CAAC;AAED,MAAM,UAAU,iCAAiC,CAC/C,MAA0B,EAC1B,oBAAyC,EACzC,IAAa;IAEb,MAAM,OAAO,GAA0B,EAAE,CAAC;IAC1C,KAAK,MAAM,OAAO,IAAI,MAAM,EAAE,CAAC;QAC7B,MAAM,OAAO,GAAG,gBAAgB,CAAC,OAAO,CAAC,GAAG,IAAI,OAAO,CAAC,IAAI,IAAI,mBAAmB,EAAE,IAAI,CAAC,CAAC;QAC3F,KAAK,MAAM,QAAQ,IAAI,OAAO,CAAC,QAAQ,IAAI,EAAE,EAAE,CAAC;YAC9C,OAAO,CAAC,IAAI,CAAC,GAAG,oBAAoB,CAAC,QAAQ,EAAE,OAAO,EAAE,oBAAoB,CAAC,CAAC,CAAC;QACjF,CAAC;IACH,CAAC;IACD,OAAO,OAAO,CAAC;AACjB,CAAC;AAID,SAAS,YAAY,CAAC,IAA8B;IAClD,MAAM,MAAM,GAAG,IAAI;SAChB,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,IAAI,IAAI,EAAE,CAAC,CAAC;SACtC,IAAI,CAAC,CAAC,CAAC,EAAwB,EAAE,CAAC,CAAC,KAAK,IAAI,CAAC,CAAC;IACjD,OAAO,MAAM,CAAC,CAAC,CAAC,MAAM,CAAC,CAAC,CAAE,CAAC,CAAC,CAAC,IAAI,CAAC;AACpC,CAAC;AAED,SAAS,oBAAoB,CAC3B,QAA0B,EAC1B,OAAe,EACf,oBAAyC;IAEzC,MAAM,IAAI,GAAG,QAAQ,CAAC,IAAI,IAAI,EAAE,CAAC;IACjC,MAAM,KAAK,GAAG,YAAY,CAAC,IAAI,CAAC,CAAC;IACjC,MAAM,KAAK,GAAG,QAAQ,CAAC,KAAK,IAAI,EAAE,CAAC;IACnC,MAAM,SAAS,GAAG,KAAK,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,MAAM,EAAE,MAAM,KAAK,WAAW,CAAC,CAAC;IACtE,IAAI,SAAS,EAAE,CAAC;QACd,OAAO,CAAC;gBACN,YAAY,EAAE,YAAY,CAAC,IAAI,EAAE,oBAAoB,CAAC,CAAC,CAAC,CAAE;gBAC1D,KAAK;gBACL,MAAM,EAAE,QAAQ;gBAChB,OAAO;gBACP,MAAM,EAAE,IAAI;gBACZ,OAAO,EAAE,gBAAgB,CAAC,SAAS,CAAC;aACrC,CAAC,CAAC;IACL,CAAC;IACD,MAAM,SAAS,GAAG,KAAK,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,MAAM,EAAE,MAAM,KAAK,QAAQ,CAAC,CAAC;IACnE,MAAM,SAAS,GAAG,KAAK,CAAC,MAAM,GAAG,CAAC,IAAI,KAAK,CAAC,KAAK,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,MAAM,EAAE,MAAM,KAAK,QAAQ,CAAC,CAAC;IACxF,IAAI,CAAC,SAAS,IAAI,CAAC,SAAS;QAAE,OAAO,EAAE,CAAC;IACxC,MAAM,MAAM,GAAmB,SAAS,CAAC,CAAC,CAAC,QAAQ,CAAC,CAAC,CAAC,QAAQ,CAAC;IAC/D,OAAO,YAAY,CAAC,IAAI,EAAE,oBAAoB,CAAC,CAAC,GAAG,CAAC,CAAC,KAAK,EAAE,EAAE,CAAC,CAAC;QAC9D,YAAY,EAAE,KAAK;QACnB,KAAK;QACL,MAAM;QACN,OAAO;KACR,CAAC,CAAC,CAAC;AACN,CAAC"}

package/dist/parse/discoveryScope.d.ts

@@ -1,48 +1,3 @@
-/**
- * THE SCOPE DISCOVERY RANGED OVER (@SCN-USG-020, 3F-3343) — one entry per job of every workflow
- * `--ci` resolved: the file, the job, how many steps this run read from it, and how many of those
- * steps are candidate fitness checks.
- *
- * WHY THE REPORT SAYS IT AT ALL, AND WHY IT IS THE ANSWER RATHER THAN A CONSOLATION FOR NOT HAVING
- * ONE. This axis's analysis asked what the tool says when it is pointed somewhere that yields an
- * implausible answer — at a release workflow, or at one job of several. The answer is that it
- * makes NO judgement about plausibility and states its scope instead: a trigger-based or name-based
- * rule for "this looks like a release workflow" is exactly the judgement the ticket puts out of
- * scope, and it is a list of ours, which is the drift the whole inversion exists to remove. A
- * consumer reading the file, the job and the counts knows on sight, and corrects it by narrowing
- * `--ci` (@SCN-USG-008) or by naming the steps that are not checks (@SCN-USG-015).
- *
- * AND IT IS THE ANSWER TO THE QUIETER HALF — THE JOB THE TOOL NEVER LOOKED AT. The census reports
- * how many checks ran and nothing said how many jobs, in how many files, that number came from. A
- * consumer whose second job holds three checks reads exactly what a consumer with three checks in
- * one job reads, and neither figure can be got from the other.
- *
- * BOTH FIGURES PER JOB, because either alone is satisfiable by a reader wrong about the other, and
- * a job that reads its whole pipeline and contributes nothing is precisely the case a reader most
- * needs to see. A job every step of which something took out is reported with none, never dropped.
- *
- * THE CANDIDATE FIGURE IS THE OBSERVER'S OWN RULE, asked through `isCandidateStep`
- * (`parse/runningStaticChecks`) rather than restated here. A census re-deriving membership would
- * be measuring its own arithmetic — it would go on agreeing with the scope section while the books
- * beneath it said something else, which is the one disagreement a reader of this section cannot
- * see. Same walk, too (`ciWorkflowSteps`), so the two readers cannot come to disagree about which
- * steps a workflow even runs.
- *
- * NOT THE ACCOUNTING IDENTITY (@SCN-USG-018). That one asserts the dispositions sum to the steps
- * read, so nothing the reader saw was dropped; this one asserts the provenance — which files and
- * which jobs those steps came from. A reader satisfies either alone: a correct sum over a scope it
- * never names, or a named scope whose numbers do not add up.
- *
- * SORTED, so two runs over one tree cannot differ and a diff of two reports never turns on the
- * order a directory happened to be handed back in — the same reason `ciSourcePathsOf` sorts. The
- * sort is stable, so two jobs no name separates stay in the order their sources were read.
- *
- * NO FILESYSTEM, AND THE NAMES ARE INJECTED, for the reason `stepExclusions` states next door:
- * `ciSources` is an array of anonymous source strings and `ciSourcePaths.ts` is explicit that
- * keeping the core that way is the point. A source this run was given no name for is still a
- * source it READ, so its jobs keep their entries and lose only the half of their name nobody
- * supplied — the direction `reconcilerSteps` takes, and never a dropped row.
- */
 import { type CiWorkflowStep, type PackageJsonScripts } from "./checkScriptsRunInCI.js";
 import type { JobDiscoveryScope } from "../domain/evidenceReconciliation.js";
 export declare function discoveryScope(ciSources: readonly string[], ciSourceNames: readonly string[], packageJson: PackageJsonScripts, runners: Readonly<Record<string, string | null>>, isExcludedFromDiscovery?: (step: CiWorkflowStep) => boolean): readonly JobDiscoveryScope[];

package/dist/parse/discoveryScope.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"discoveryScope.d.ts","sourceRoot":"","sources":["../../src/parse/discoveryScope.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA4CG;AAEH,OAAO,EAAmB,KAAK,cAAc,EAAE,KAAK,kBAAkB,EAAE,MAAM,0BAA0B,CAAC;AAEzG,OAAO,KAAK,EAAE,iBAAiB,EAAE,MAAM,qCAAqC,CAAC;AAY7E,wBAAgB,cAAc,CAC5B,SAAS,EAAE,SAAS,MAAM,EAAE,EAC5B,aAAa,EAAE,SAAS,MAAM,EAAE,EAChC,WAAW,EAAE,kBAAkB,EAC/B,OAAO,EAAE,QAAQ,CAAC,MAAM,CAAC,MAAM,EAAE,MAAM,GAAG,IAAI,CAAC,CAAC,EAChD,uBAAuB,GAAE,CAAC,IAAI,EAAE,cAAc,KAAK,OAAqB,GACvE,SAAS,iBAAiB,EAAE,CAsB9B"}
+{"version":3,"file":"discoveryScope.d.ts","sourceRoot":"","sources":["../../src/parse/discoveryScope.ts"],"names":[],"mappings":"AAAA,OAAO,EAAmB,KAAK,cAAc,EAAE,KAAK,kBAAkB,EAAE,MAAM,0BAA0B,CAAC;AAEzG,OAAO,KAAK,EAAE,iBAAiB,EAAE,MAAM,qCAAqC,CAAC;AAM7E,wBAAgB,cAAc,CAC5B,SAAS,EAAE,SAAS,MAAM,EAAE,EAC5B,aAAa,EAAE,SAAS,MAAM,EAAE,EAChC,WAAW,EAAE,kBAAkB,EAC/B,OAAO,EAAE,QAAQ,CAAC,MAAM,CAAC,MAAM,EAAE,MAAM,GAAG,IAAI,CAAC,CAAC,EAChD,uBAAuB,GAAE,CAAC,IAAI,EAAE,cAAc,KAAK,OAAqB,GACvE,SAAS,iBAAiB,EAAE,CAiB9B"}

package/dist/parse/discoveryScope.js

@@ -1,63 +1,11 @@
-/**
- * THE SCOPE DISCOVERY RANGED OVER (@SCN-USG-020, 3F-3343) — one entry per job of every workflow
- * `--ci` resolved: the file, the job, how many steps this run read from it, and how many of those
- * steps are candidate fitness checks.
- *
- * WHY THE REPORT SAYS IT AT ALL, AND WHY IT IS THE ANSWER RATHER THAN A CONSOLATION FOR NOT HAVING
- * ONE. This axis's analysis asked what the tool says when it is pointed somewhere that yields an
- * implausible answer — at a release workflow, or at one job of several. The answer is that it
- * makes NO judgement about plausibility and states its scope instead: a trigger-based or name-based
- * rule for "this looks like a release workflow" is exactly the judgement the ticket puts out of
- * scope, and it is a list of ours, which is the drift the whole inversion exists to remove. A
- * consumer reading the file, the job and the counts knows on sight, and corrects it by narrowing
- * `--ci` (@SCN-USG-008) or by naming the steps that are not checks (@SCN-USG-015).
- *
- * AND IT IS THE ANSWER TO THE QUIETER HALF — THE JOB THE TOOL NEVER LOOKED AT. The census reports
- * how many checks ran and nothing said how many jobs, in how many files, that number came from. A
- * consumer whose second job holds three checks reads exactly what a consumer with three checks in
- * one job reads, and neither figure can be got from the other.
- *
- * BOTH FIGURES PER JOB, because either alone is satisfiable by a reader wrong about the other, and
- * a job that reads its whole pipeline and contributes nothing is precisely the case a reader most
- * needs to see. A job every step of which something took out is reported with none, never dropped.
- *
- * THE CANDIDATE FIGURE IS THE OBSERVER'S OWN RULE, asked through `isCandidateStep`
- * (`parse/runningStaticChecks`) rather than restated here. A census re-deriving membership would
- * be measuring its own arithmetic — it would go on agreeing with the scope section while the books
- * beneath it said something else, which is the one disagreement a reader of this section cannot
- * see. Same walk, too (`ciWorkflowSteps`), so the two readers cannot come to disagree about which
- * steps a workflow even runs.
- *
- * NOT THE ACCOUNTING IDENTITY (@SCN-USG-018). That one asserts the dispositions sum to the steps
- * read, so nothing the reader saw was dropped; this one asserts the provenance — which files and
- * which jobs those steps came from. A reader satisfies either alone: a correct sum over a scope it
- * never names, or a named scope whose numbers do not add up.
- *
- * SORTED, so two runs over one tree cannot differ and a diff of two reports never turns on the
- * order a directory happened to be handed back in — the same reason `ciSourcePathsOf` sorts. The
- * sort is stable, so two jobs no name separates stay in the order their sources were read.
- *
- * NO FILESYSTEM, AND THE NAMES ARE INJECTED, for the reason `stepExclusions` states next door:
- * `ciSources` is an array of anonymous source strings and `ciSourcePaths.ts` is explicit that
- * keeping the core that way is the point. A source this run was given no name for is still a
- * source it READ, so its jobs keep their entries and lose only the half of their name nobody
- * supplied — the direction `reconcilerSteps` takes, and never a dropped row.
- */
 import { ciWorkflowSteps } from "./checkScriptsRunInCI.js";
 import { isCandidateStep } from "./runningStaticChecks.js";
-/**
- * BY SOURCE INDEX AND JOB, never by the source's NAME. Two sources this run was given no name for
- * are two files it read, and keying on the name would fold their same-named jobs into one entry —
- * a job the reader ranged over, gone from the account of what it ranged over.
- */
 const keyOf = (step) => `${step.sourceIndex}:${step.jobId}`;
 export function discoveryScope(ciSources, ciSourceNames, packageJson, runners, isExcludedFromDiscovery = () => false) {
     const tallies = new Map();
     for (const step of ciWorkflowSteps(ciSources)) {
         const source = ciSourceNames[step.sourceIndex];
         const tally = tallies.get(keyOf(step)) ?? {
-            // Spread rather than a `source: undefined` assignment, so an entry for a source nobody named
-            // carries no key at all — the shape an absent citation has everywhere else in this engine.
             ...(source !== undefined ? { source } : {}),
             job: step.jobId,
             steps: 0,
@@ -68,9 +16,6 @@ export function discoveryScope(ciSources, ciSourceNames, packageJson, runners, i
             tally.candidates += 1;
         tallies.set(keyOf(step), tally);
     }
-    // BY FILE AND THEN BY JOB. A source with no name sorts ahead of every named one, which is a
-    // settled place rather than a chosen one: it is what an absent name compares as, and the point
-    // of the sort is that two runs over one tree agree.
     return [...tallies.values()].sort((a, b) => (a.source ?? "").localeCompare(b.source ?? "") || a.job.localeCompare(b.job));
 }
 //# sourceMappingURL=discoveryScope.js.map

package/dist/parse/discoveryScope.js.map

@@ -1 +1 @@
-{"version":3,"file":"discoveryScope.js","sourceRoot":"","sources":["../../src/parse/discoveryScope.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA4CG;AAEH,OAAO,EAAE,eAAe,EAAgD,MAAM,0BAA0B,CAAC;AACzG,OAAO,EAAE,eAAe,EAAE,MAAM,0BAA0B,CAAC;AAM3D;;;;GAIG;AACH,MAAM,KAAK,GAAG,CAAC,IAAoB,EAAU,EAAE,CAAC,GAAG,IAAI,CAAC,WAAW,IAAI,IAAI,CAAC,KAAK,EAAE,CAAC;AAEpF,MAAM,UAAU,cAAc,CAC5B,SAA4B,EAC5B,aAAgC,EAChC,WAA+B,EAC/B,OAAgD,EAChD,0BAA6D,GAAG,EAAE,CAAC,KAAK;IAExE,MAAM,OAAO,GAAG,IAAI,GAAG,EAAiB,CAAC;IACzC,KAAK,MAAM,IAAI,IAAI,eAAe,CAAC,SAAS,CAAC,EAAE,CAAC;QAC9C,MAAM,MAAM,GAAG,aAAa,CAAC,IAAI,CAAC,WAAW,CAAC,CAAC;QAC/C,MAAM,KAAK,GAAG,OAAO,CAAC,GAAG,CAAC,KAAK,CAAC,IAAI,CAAC,CAAC,IAAI;YACxC,6FAA6F;YAC7F,2FAA2F;YAC3F,GAAG,CAAC,MAAM,KAAK,SAAS,CAAC,CAAC,CAAC,EAAE,MAAM,EAAE,CAAC,CAAC,CAAC,EAAE,CAAC;YAC3C,GAAG,EAAE,IAAI,CAAC,KAAK;YACf,KAAK,EAAE,CAAC;YACR,UAAU,EAAE,CAAC;SACd,CAAC;QACF,KAAK,CAAC,KAAK,IAAI,CAAC,CAAC;QACjB,IAAI,eAAe,CAAC,IAAI,EAAE,WAAW,EAAE,OAAO,EAAE,uBAAuB,CAAC;YAAE,KAAK,CAAC,UAAU,IAAI,CAAC,CAAC;QAChG,OAAO,CAAC,GAAG,CAAC,KAAK,CAAC,IAAI,CAAC,EAAE,KAAK,CAAC,CAAC;IAClC,CAAC;IACD,4FAA4F;IAC5F,+FAA+F;IAC/F,oDAAoD;IACpD,OAAO,CAAC,GAAG,OAAO,CAAC,MAAM,EAAE,CAAC,CAAC,IAAI,CAC/B,CAAC,CAAC,EAAE,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,CAAC,MAAM,IAAI,EAAE,CAAC,CAAC,aAAa,CAAC,CAAC,CAAC,MAAM,IAAI,EAAE,CAAC,IAAI,CAAC,CAAC,GAAG,CAAC,aAAa,CAAC,CAAC,CAAC,GAAG,CAAC,CACvF,CAAC;AACJ,CAAC"}
+{"version":3,"file":"discoveryScope.js","sourceRoot":"","sources":["../../src/parse/discoveryScope.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,eAAe,EAAgD,MAAM,0BAA0B,CAAC;AACzG,OAAO,EAAE,eAAe,EAAE,MAAM,0BAA0B,CAAC;AAK3D,MAAM,KAAK,GAAG,CAAC,IAAoB,EAAU,EAAE,CAAC,GAAG,IAAI,CAAC,WAAW,IAAI,IAAI,CAAC,KAAK,EAAE,CAAC;AAEpF,MAAM,UAAU,cAAc,CAC5B,SAA4B,EAC5B,aAAgC,EAChC,WAA+B,EAC/B,OAAgD,EAChD,0BAA6D,GAAG,EAAE,CAAC,KAAK;IAExE,MAAM,OAAO,GAAG,IAAI,GAAG,EAAiB,CAAC;IACzC,KAAK,MAAM,IAAI,IAAI,eAAe,CAAC,SAAS,CAAC,EAAE,CAAC;QAC9C,MAAM,MAAM,GAAG,aAAa,CAAC,IAAI,CAAC,WAAW,CAAC,CAAC;QAC/C,MAAM,KAAK,GAAG,OAAO,CAAC,GAAG,CAAC,KAAK,CAAC,IAAI,CAAC,CAAC,IAAI;YACxC,GAAG,CAAC,MAAM,KAAK,SAAS,CAAC,CAAC,CAAC,EAAE,MAAM,EAAE,CAAC,CAAC,CAAC,EAAE,CAAC;YAC3C,GAAG,EAAE,IAAI,CAAC,KAAK;YACf,KAAK,EAAE,CAAC;YACR,UAAU,EAAE,CAAC;SACd,CAAC;QACF,KAAK,CAAC,KAAK,IAAI,CAAC,CAAC;QACjB,IAAI,eAAe,CAAC,IAAI,EAAE,WAAW,EAAE,OAAO,EAAE,uBAAuB,CAAC;YAAE,KAAK,CAAC,UAAU,IAAI,CAAC,CAAC;QAChG,OAAO,CAAC,GAAG,CAAC,KAAK,CAAC,IAAI,CAAC,EAAE,KAAK,CAAC,CAAC;IAClC,CAAC;IACD,OAAO,CAAC,GAAG,OAAO,CAAC,MAAM,EAAE,CAAC,CAAC,IAAI,CAC/B,CAAC,CAAC,EAAE,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,CAAC,MAAM,IAAI,EAAE,CAAC,CAAC,aAAa,CAAC,CAAC,CAAC,MAAM,IAAI,EAAE,CAAC,IAAI,CAAC,CAAC,GAAG,CAAC,aAAa,CAAC,CAAC,CAAC,GAAG,CAAC,CACvF,CAAC;AACJ,CAAC"}

package/dist/parse/fitnessCitations.d.ts

@@ -1,76 +1,5 @@
-/**
- * THE CITATION SEAM'S SURVIVING ROUTE — a consumer's own CI step states the code of the configured
- * row it answers, and this reads that row back as what the run cites.
- *
- * THE TWO-HOP REGISTRY ROUTE THIS FILE ONCE ALSO HELD IS RETIRED (3F-3161, @SCN-LNT-017 — the last
- * registry-`scn` scenario: a registry entry naming a scenario that carries a different
- * characteristic cited nothing, and no scenario is left needing that resolution at all).
- * The retired registry module (hop 1, script handle → bare check tag) and this module's own
- * `fitnessCitations` / `citationOfScript` (hop 2, bare check tag → the corpus's `@SCN`) went with
- * it. Every check now either states its own row's code on its CI step, or is a converted
- * `@fitness` row read through `domain/fitnessChecks` directly. `citationOfCitedRow` — the `id:`
- * route (@SCN-LNT-031) — is the whole of what is left.
- *
- * NOT A HOP, AND THE DIFFERENCE IS WHERE IT STARTS. The retired hops resolved a runnable script
- * HANDLE into a scenario, because a handle does not know what it is for. An `id:` is not a handle:
- * it is the consumer SAYING which row this check answers — a citation, never a declaration — so
- * there is nothing to resolve. The row keyed by that code carries the characteristic, and both
- * terms come off one configured row rather than one being recovered from the other.
- *
- * IT REFINES, IT DOES NOT MANUFACTURE (@SCN-LNT-031, and 3F-3261's rule kept whole). A code no
- * configured row answers returns `null` rather than a citation half-assembled from the handle that
- * ran: an `id:` names a ROW and never a characteristic, and reaching for the script's name for the
- * missing half is the name-match this axis retired, in a new spelling. A step carrying no code at
- * all is the same answer for the same reason — the target has said nothing about that check, so its
- * run cites nothing and posts to suspense, which is the state a consumer starts in.
- *
- * BARED ON THE WAY IN, because a manifest's `scn` is stored bare and a workflow is hand-authored:
- * the one spelling rule this repository has (`lib/bareTerm`) is what keeps a code written with a
- * sigil or a stray space from being looked up under a key no row is filed at.
- */
-import type { FitnessCheckIndex } from "../domain/fitnessChecks.js";
-/**
- * WHAT A RUN CITES — both terms the seam resolved, not just the far one.
- *
- * The `@SCN` says WHICH ROW the credit posts to; the bare check tag says WHICH OBLIGATION on that
- * row it answers. Both are needed, because neither is unique on its own: a row may carry more than
- * one bare check tag, so two runs can honestly cite the same `@SCN` (@SCN-LNT-012), and answering
- * by `@SCN` alone hands the first credit found to every fitness obligation the row raises.
- *
- * THE TAG IS THE OBSERVATION'S OWN CHARACTERISTIC, which is why it is carried rather than looked up
- * again downstream. The obligation names the BARE tag its stepless scenario carries (`typecheck`);
- * the run knows only the RUNNABLE HANDLE that invoked it (`lint:complexity`). Those are two
- * vocabularies by design, and comparing them is name-match in a new spelling — it agrees only where
- * the words happen to coincide, which is the single unprefixed check. Resolving the tag HERE, where
- * the registry is already in hand, is what lets the reconciler compare like with like.
- */
 export interface ScriptCitation {
-    /** The BARE check tag this handle runs (`complexity`) — the word an obligation names. */
-    readonly checkTag: string;
-    /** The `@SCN` of the fitness scenario carrying that check — the row the credit posts to. */
     readonly scnId: string;
 }
-/**
- * THE CONSUMER'S OWN CITATION — the configured row a code written on a CI check step names, read
- * back as what that step's run cites.
- *
- * NOT A HOP, AND THE DIFFERENCE IS WHERE IT STARTS — the same point the file's own docblock makes,
- * repeated here because this function is where it is proved. The retired hops resolved a runnable
- * script HANDLE into a scenario, because a handle does not know what it is for. An `id:` is not a
- * handle: it is the consumer SAYING which row this check answers — a citation, never a declaration
- * — so there is nothing to resolve. The row keyed by that code carries the characteristic, and both
- * terms come off one configured row rather than one being recovered from the other.
- *
- * IT REFINES, IT DOES NOT MANUFACTURE (@SCN-LNT-031, and 3F-3261's rule kept whole). A code no
- * configured row answers returns `null` rather than a citation half-assembled from the handle that
- * ran: an `id:` names a ROW and never a characteristic, and reaching for the script's name for the
- * missing half is the name-match this axis retired, in a new spelling. A step carrying no code at
- * all is the same answer for the same reason — the target has said nothing about that check, so its
- * run cites nothing and posts to suspense, which is the state a consumer starts in.
- *
- * BARED ON THE WAY IN, because a manifest's `scn` is stored bare and a workflow is hand-authored:
- * the one spelling rule this repository has (`lib/bareTerm`) is what keeps a code written with a
- * sigil or a stray space from being looked up under a key no row is filed at.
- */
-export declare function citationOfCitedRow(citedScn: string | undefined, fitnessChecks: FitnessCheckIndex): ScriptCitation | null;
+export declare function citationOfCitedRow(citedScn: string | undefined): ScriptCitation | null;
 //# sourceMappingURL=fitnessCitations.d.ts.map

package/dist/parse/fitnessCitations.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"fitnessCitations.d.ts","sourceRoot":"","sources":["../../src/parse/fitnessCitations.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA6BG;AAEH,OAAO,KAAK,EAAE,iBAAiB,EAAE,MAAM,4BAA4B,CAAC;AAGpE;;;;;;;;;;;;;;GAcG;AACH,MAAM,WAAW,cAAc;IAC7B,yFAAyF;IACzF,QAAQ,CAAC,QAAQ,EAAE,MAAM,CAAC;IAC1B,4FAA4F;IAC5F,QAAQ,CAAC,KAAK,EAAE,MAAM,CAAC;CACxB;AAED;;;;;;;;;;;;;;;;;;;;;GAqBG;AACH,wBAAgB,kBAAkB,CAChC,QAAQ,EAAE,MAAM,GAAG,SAAS,EAC5B,aAAa,EAAE,iBAAiB,GAC/B,cAAc,GAAG,IAAI,CAKvB"}
+{"version":3,"file":"fitnessCitations.d.ts","sourceRoot":"","sources":["../../src/parse/fitnessCitations.ts"],"names":[],"mappings":"AAGA,MAAM,WAAW,cAAc;IAC7B,QAAQ,CAAC,KAAK,EAAE,MAAM,CAAC;CACxB;AAED,wBAAgB,kBAAkB,CAAC,QAAQ,EAAE,MAAM,GAAG,SAAS,GAAG,cAAc,GAAG,IAAI,CAItF"}

package/dist/parse/fitnessCitations.js

@@ -1,61 +1,9 @@
-/**
- * THE CITATION SEAM'S SURVIVING ROUTE — a consumer's own CI step states the code of the configured
- * row it answers, and this reads that row back as what the run cites.
- *
- * THE TWO-HOP REGISTRY ROUTE THIS FILE ONCE ALSO HELD IS RETIRED (3F-3161, @SCN-LNT-017 — the last
- * registry-`scn` scenario: a registry entry naming a scenario that carries a different
- * characteristic cited nothing, and no scenario is left needing that resolution at all).
- * The retired registry module (hop 1, script handle → bare check tag) and this module's own
- * `fitnessCitations` / `citationOfScript` (hop 2, bare check tag → the corpus's `@SCN`) went with
- * it. Every check now either states its own row's code on its CI step, or is a converted
- * `@fitness` row read through `domain/fitnessChecks` directly. `citationOfCitedRow` — the `id:`
- * route (@SCN-LNT-031) — is the whole of what is left.
- *
- * NOT A HOP, AND THE DIFFERENCE IS WHERE IT STARTS. The retired hops resolved a runnable script
- * HANDLE into a scenario, because a handle does not know what it is for. An `id:` is not a handle:
- * it is the consumer SAYING which row this check answers — a citation, never a declaration — so
- * there is nothing to resolve. The row keyed by that code carries the characteristic, and both
- * terms come off one configured row rather than one being recovered from the other.
- *
- * IT REFINES, IT DOES NOT MANUFACTURE (@SCN-LNT-031, and 3F-3261's rule kept whole). A code no
- * configured row answers returns `null` rather than a citation half-assembled from the handle that
- * ran: an `id:` names a ROW and never a characteristic, and reaching for the script's name for the
- * missing half is the name-match this axis retired, in a new spelling. A step carrying no code at
- * all is the same answer for the same reason — the target has said nothing about that check, so its
- * run cites nothing and posts to suspense, which is the state a consumer starts in.
- *
- * BARED ON THE WAY IN, because a manifest's `scn` is stored bare and a workflow is hand-authored:
- * the one spelling rule this repository has (`lib/bareTerm`) is what keeps a code written with a
- * sigil or a stray space from being looked up under a key no row is filed at.
- */
 import { bareTerm } from "../lib/bareTerm.js";
-/**
- * THE CONSUMER'S OWN CITATION — the configured row a code written on a CI check step names, read
- * back as what that step's run cites.
- *
- * NOT A HOP, AND THE DIFFERENCE IS WHERE IT STARTS — the same point the file's own docblock makes,
- * repeated here because this function is where it is proved. The retired hops resolved a runnable
- * script HANDLE into a scenario, because a handle does not know what it is for. An `id:` is not a
- * handle: it is the consumer SAYING which row this check answers — a citation, never a declaration
- * — so there is nothing to resolve. The row keyed by that code carries the characteristic, and both
- * terms come off one configured row rather than one being recovered from the other.
- *
- * IT REFINES, IT DOES NOT MANUFACTURE (@SCN-LNT-031, and 3F-3261's rule kept whole). A code no
- * configured row answers returns `null` rather than a citation half-assembled from the handle that
- * ran: an `id:` names a ROW and never a characteristic, and reaching for the script's name for the
- * missing half is the name-match this axis retired, in a new spelling. A step carrying no code at
- * all is the same answer for the same reason — the target has said nothing about that check, so its
- * run cites nothing and posts to suspense, which is the state a consumer starts in.
- *
- * BARED ON THE WAY IN, because a manifest's `scn` is stored bare and a workflow is hand-authored:
- * the one spelling rule this repository has (`lib/bareTerm`) is what keeps a code written with a
- * sigil or a stray space from being looked up under a key no row is filed at.
- */
-export function citationOfCitedRow(citedScn, fitnessChecks) {
+import { SCN_CODE } from "./scenarios.js";
+export function citationOfCitedRow(citedScn) {
     if (citedScn === undefined)
         return null;
     const scnId = bareTerm(citedScn);
-    const row = fitnessChecks.get(scnId);
-    return row === undefined ? null : { checkTag: row.characteristic, scnId };
+    return SCN_CODE.test(scnId) ? { scnId } : null;
 }
 //# sourceMappingURL=fitnessCitations.js.map

package/dist/parse/fitnessCitations.js.map

@@ -1 +1 @@
-{"version":3,"file":"fitnessCitations.js","sourceRoot":"","sources":["../../src/parse/fitnessCitations.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA6BG;AAGH,OAAO,EAAE,QAAQ,EAAE,MAAM,oBAAoB,CAAC;AAwB9C;;;;;;;;;;;;;;;;;;;;;GAqBG;AACH,MAAM,UAAU,kBAAkB,CAChC,QAA4B,EAC5B,aAAgC;IAEhC,IAAI,QAAQ,KAAK,SAAS;QAAE,OAAO,IAAI,CAAC;IACxC,MAAM,KAAK,GAAG,QAAQ,CAAC,QAAQ,CAAC,CAAC;IACjC,MAAM,GAAG,GAAG,aAAa,CAAC,GAAG,CAAC,KAAK,CAAC,CAAC;IACrC,OAAO,GAAG,KAAK,SAAS,CAAC,CAAC,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,QAAQ,EAAE,GAAG,CAAC,cAAc,EAAE,KAAK,EAAE,CAAC;AAC5E,CAAC"}
+{"version":3,"file":"fitnessCitations.js","sourceRoot":"","sources":["../../src/parse/fitnessCitations.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,QAAQ,EAAE,MAAM,oBAAoB,CAAC;AAC9C,OAAO,EAAE,QAAQ,EAAE,MAAM,gBAAgB,CAAC;AAM1C,MAAM,UAAU,kBAAkB,CAAC,QAA4B;IAC7D,IAAI,QAAQ,KAAK,SAAS;QAAE,OAAO,IAAI,CAAC;IACxC,MAAM,KAAK,GAAG,QAAQ,CAAC,QAAQ,CAAC,CAAC;IACjC,OAAO,QAAQ,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC,CAAC,CAAC,EAAE,KAAK,EAAE,CAAC,CAAC,CAAC,IAAI,CAAC;AACjD,CAAC"}

package/dist/parse/reconcilerSteps.d.ts

@@ -1,53 +1,7 @@
-/**
- * THE RECONCILER'S OWN STEPS (@SCN-USG-014, 3F-3343) — which steps of a target's pipeline are this
- * reconciliation rather than something it reconciles, and how the report says so.
- *
- * THE SECOND EXCLUSION, AND THE ONLY ONE NOBODY CONFIGURES. A behavioural runner is excluded by a
- * rule over what the target named and a non-check by the consumer's own list; this one is excluded
- * BY CONSTRUCTION, because the run that computes the books cannot be a row in them. The
- * distinction is not a nicety: a `notChecks` pair produces the identical report over the identical
- * pipeline, and the two answers part company only at the consumer who has written nothing — whose
- * very first run would otherwise report their own reconciler as an uncited fitness check, and go
- * on doing so until they learned to configure it away.
- *
- * A CITATION ON EITHER IS UNSATISFIABLE, WHICH IS WHAT MAKES IT CONSTRUCTION RATHER THAN JUDGEMENT.
- * The step record is written BEFORE the reconciliation reads it — necessarily, since that record
- * is its input — so no run's record can ever carry the reconciling step's own outcome, and no
- * scenario can ever be shown to have been answered by it. A demand nothing could satisfy is not a
- * check somebody failed to cite. It is not a check.
- *
- * TWO HALVES, RECOGNISED TWO WAYS, AND NEITHER IS A LIST OF NAMES.
- *
- *   - THE RUN: a step whose command runs this tool's own reconciling invocation, compared as whole
- *     adjacent shell tokens and followed through the manifest scripts a step invokes — the runner
- *     rule's own comparison (`parse/commandRuns`), because a pipeline invokes a binary through a
- *     script alias far more often than it writes its name. ADJACENT is what keeps the same binary
- *     run for another purpose a candidate: this repository's own pipeline runs `spec-controller
- *     tags` beside its balance step, and that is an ordinary step of the pipeline being reconciled.
- *   - THE RECORD: a step carrying GitHub's own step-record expression, which is the only way that
- *     record can be produced. Read off the step's `env:` and its command, wherever the consumer
- *     wrote it, and not off its title — a step called `Dump this run's step record` that produces
- *     no record is an ordinary step, and one called anything at all that produces the record is
- *     the dump.
- *
- * THE INVOCATION IS INJECTED, NEVER ASSUMED. How this product is invoked at a consumer's command
- * line is a fact the application edge holds (`ingest/ingestQualityChecks.ts`), like the script
- * prefixes and the workflow names beside it; the core is handed it as data. A run told no
- * invocation recognises no reconciling step, which is the safe direction — a candidate too many,
- * visible on the report, rather than a step taken off the books by a rule nobody supplied.
- *
- * THE ACCOUNT AND THE SEAM COME OFF ONE RULE. `isReconciler` re-asks the same question of a single
- * step rather than consulting the list this module built, so the account the report prints and the
- * steps discovery skipped cannot come to disagree — a step named on the report as the reconciler
- * while its check sits on the books is a report that contradicts itself in one page.
- */
 import { type CiWorkflowStep } from "./checkScriptsRunInCI.js";
 import type { ReconcilerStep } from "../domain/evidenceReconciliation.js";
-/** What a run's pipeline yielded of the reconciler — the account, and the one answer per step. */
 export interface ReconcilerSteps {
-    /** The steps that are the reconciler, in the order the pipeline runs them. */
     readonly steps: readonly ReconcilerStep[];
-    /** Whether this step is the reconciler rather than a step of the pipeline it reconciles. */
     readonly isReconciler: (step: CiWorkflowStep) => boolean;
 }
 export declare function reconcilerSteps(ciSources: readonly string[], ciSourceNames: readonly string[], invocation: string, packageJson: {

package/dist/parse/reconcilerSteps.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"reconcilerSteps.d.ts","sourceRoot":"","sources":["../../src/parse/reconcilerSteps.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA0CG;AAEH,OAAO,EAAmB,KAAK,cAAc,EAAE,MAAM,0BAA0B,CAAC;AAGhF,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,qCAAqC,CAAC;AAE1E,kGAAkG;AAClG,MAAM,WAAW,eAAe;IAC9B,8EAA8E;IAC9E,QAAQ,CAAC,KAAK,EAAE,SAAS,cAAc,EAAE,CAAC;IAC1C,4FAA4F;IAC5F,QAAQ,CAAC,YAAY,EAAE,CAAC,IAAI,EAAE,cAAc,KAAK,OAAO,CAAC;CAC1D;AAiCD,wBAAgB,eAAe,CAC7B,SAAS,EAAE,SAAS,MAAM,EAAE,EAC5B,aAAa,EAAE,SAAS,MAAM,EAAE,EAChC,UAAU,EAAE,MAAM,EAClB,WAAW,EAAE;IAAE,OAAO,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAA;CAAE,GAChD,eAAe,CAiBjB"}
+{"version":3,"file":"reconcilerSteps.d.ts","sourceRoot":"","sources":["../../src/parse/reconcilerSteps.ts"],"names":[],"mappings":"AAAA,OAAO,EAAmB,KAAK,cAAc,EAAE,MAAM,0BAA0B,CAAC;AAGhF,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,qCAAqC,CAAC;AAE1E,MAAM,WAAW,eAAe;IAC9B,QAAQ,CAAC,KAAK,EAAE,SAAS,cAAc,EAAE,CAAC;IAC1C,QAAQ,CAAC,YAAY,EAAE,CAAC,IAAI,EAAE,cAAc,KAAK,OAAO,CAAC;CAC1D;AAmBD,wBAAgB,eAAe,CAC7B,SAAS,EAAE,SAAS,MAAM,EAAE,EAC5B,aAAa,EAAE,SAAS,MAAM,EAAE,EAChC,UAAU,EAAE,MAAM,EAClB,WAAW,EAAE;IAAE,OAAO,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAA;CAAE,GAChD,eAAe,CAWjB"}