@3f-consulting/spec-controller-core 0.1.0-alpha.7 → 0.1.0-alpha.70

package/dist/render/scenarioCodeErrorsSection.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"scenarioCodeErrorsSection.js","sourceRoot":"","sources":["../../src/render/scenarioCodeErrorsSection.ts"],"names":[],"mappings":"AAEA,OAAO,EAAE,aAAa,EAAE,WAAW,EAAE,MAAM,uBAAuB,CAAC;AAEnE,SAAS,OAAO,CAAC,CAAS,EAAE,IAAY;IACtC,OAAO,GAAG,CAAC,IAAI,IAAI,GAAG,CAAC,KAAK,CAAC,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,GAAG,EAAE,CAAC;AAC7C,CAAC;AAED,SAAS,cAAc,CAAC,UAA8C;IACpE,IAAI,UAAU,KAAK,SAAS;QAAE,OAAO,aAAa,CAAC,WAAW,CAAC,kBAAkB,CAAC,CAAC;IACnF,MAAM,EAAE,YAAY,EAAE,YAAY,EAAE,GAAG,UAAU,CAAC;IAClD,IAAI,YAAY,KAAK,CAAC;QAAE,OAAO,aAAa,CAAC,WAAW,CAAC,mBAAmB,CAAC,CAAC;IAC9E,MAAM,IAAI,GAAG,aAAa,CAAC,WAAW,CAAC,sBAAsB,CAAC,CAC5D,OAAO,CAAC,YAAY,EAAE,aAAa,CAAC,WAAW,CAAC,eAAe,CAAC,CAAC,EACjE,OAAO,CAAC,YAAY,EAAE,aAAa,CAAC,WAAW,CAAC,eAAe,CAAC,CAAC,CAClE,CAAC;IACF,IAAI,YAAY,KAAK,CAAC,EAAE,CAAC;QACvB,MAAM,IAAI,GAAG,YAAY,KAAK,CAAC,CAAC,CAAC,CAAC,aAAa,CAAC,WAAW,CAAC,SAAS,CAAC,CAAC,CAAC,CAAC,aAAa,CAAC,WAAW,CAAC,WAAW,CAAC,CAAC;QAChH,OAAO,aAAa,CAAC,WAAW,CAAC,oBAAoB,CAAC,CAAC,IAAI,EAAE,IAAI,CAAC,CAAC;IACrE,CAAC;IACD,IAAI,YAAY,KAAK,YAAY;QAAE,OAAO,aAAa,CAAC,WAAW,CAAC,oBAAoB,CAAC,CAAC,IAAI,CAAC,CAAC;IAChG,MAAM,aAAa,GAAG,YAAY,GAAG,YAAY,CAAC;IAClD,MAAM,IAAI,GAAG,aAAa,KAAK,CAAC,CAAC,CAAC,CAAC,aAAa,CAAC,WAAW,CAAC,SAAS,CAAC,CAAC,CAAC,CAAC,aAAa,CAAC,WAAW,CAAC,QAAQ,CAAC,CAAC;IAC9G,OAAO,aAAa,CAAC,WAAW,CAAC,wBAAwB,CAAC,CAAC,IAAI,EAAE,aAAa,EAAE,IAAI,CAAC,CAAC;AACxF,CAAC;AAED,MAAM,CAAC,MAAM,yBAAyB,GAAG,CAAC,MAAmB,EAAY,EAAE;IACzE,IAAI,MAAM,CAAC,kBAAkB,KAAK,SAAS;QAAE,OAAO,EAAE,CAAC;IACvD,MAAM,MAAM,GAAG,MAAM,CAAC,kBAAkB,CAAC;IACzC,MAAM,OAAO,GAAG,aAAa,CAAC,WAAW,CAAC,yBAAyB,CAAC,CAAC;IACrE,MAAM,aAAa,GAAG,aAAa,CAAC,WAAW,CAAC,yBAAyB,CAAC,CAAC;IAC3E,IAAI,MAAM,CAAC,MAAM,KAAK,CAAC,EAAE,CAAC;QACxB,OAAO,CAAC,OAAO,EAAE,EAAE,EAAE,cAAc,CAAC,MAAM,CAAC,sBAAsB,CAAC,EAAE,EAAE,EAAE,aAAa,EAAE,EAAE,CAAC,CAAC;IAC7F,CAAC;IACD,MAAM,KAAK,GACT,MAAM,CAAC,MAAM,KAAK,CAAC;QACjB,CAAC,CAAC,aAAa,CAAC,WAAW,CAAC,oBAAoB,CAAC;QACjD,CAAC,CAAC,aAAa,CAAC,WAAW,CAAC,sBAAsB,CAAC,CAAC,MAAM,CAAC,MAAM,CAAC,CAAC;IACvE,OAAO;QACL,OAAO;QACP,EAAE;QACF,aAAa,CAAC,WAAW,CAAC,yBAAyB,CAAC,CAAC,KAAK,CAAC;QAC3D,EAAE;QACF,GAAG,MAAM,CAAC,GAAG,CAAC,CAAC,KAAK,EAAE,EAAE,CAAC,OAAO,KAAK,CAAC,IAAI,QAAQ,KAAK,CAAC,OAAO,EAAE,CAAC;QAClE,EAAE;QACF,aAAa;QACb,EAAE;KACH,CAAC;AACJ,CAAC,CAAC"}

package/dist/render/stepAccounting.d.ts

@@ -1,39 +1,3 @@
-/**
- * WHAT BECAME OF EVERY STEP THIS RUN READ (@SCN-USG-018) — the population, the four dispositions,
- * and whether they add back up to it.
- *
- * THE SECTION IS THIS AXIS'S FIRST NON-NEGOTIABLE MADE CHECKABLE. Nothing seen is dropped: a step
- * that reaches the reader leaves it as a candidate fitness check, as one of the runners the target
- * named, as the reconciler, or as a step the consumer called a non-check, and there is no fifth
- * outcome. Every section above this one names what a step BECAME, so a step that became nothing is
- * missing from none of them and every one reads exactly as it would have read had the step never
- * existed. This is the only cut of the report that can see an absence, and seeing absences is what
- * the whole axis is for.
- *
- * BOTH TOTALS, SIDE BY SIDE, AND THE SUM IS NOT THE READER'S TO MAKE. `Accounted for` is the
- * figure the count itself arrived at; a reader adding the four dispositions up for themselves
- * would be checking their own arithmetic against nothing, and would go on agreeing with a report
- * whose four figures had lost a step between them. Stated as a pair, the identity is something a
- * consumer reads rather than derives.
- *
- * A TABLE AND THEN A SENTENCE, because the two answer different readers. The row is what a
- * consumer compares against their own pipeline — four candidates and three non-checks is a claim
- * about their file they can check. The line under it is the verdict, and where the figures
- * disagree it names both of them, because a bare "does not balance" over numbers a reader has to
- * subtract for themselves is the report withholding the one thing it knows.
- *
- * Its own module rather than a further section in `markdown.ts`, which sits at a `max-lines`
- * exception — and an exception excuses existing debt, never headroom. The precedent is
- * `runVerdict.ts` and, along this axis, `discoveryScope.ts`, `behaviouralRunners.ts`,
- * `excludedSteps.ts` and `reconcilerSteps.ts`.
- */
 import type { RenderInput } from "../assemble/renderInput.js";
-/**
- * The accounting, or nothing at all.
- *
- * OMITTED WHERE THE RUN READ NO STEP, which is the only way the count can be empty: the section
- * appears wherever there is a pipeline to account for, and a run handed no CI configuration
- * renders byte-identically to before.
- */
 export declare const stepAccountingSection: (report: RenderInput) => string[];
 //# sourceMappingURL=stepAccounting.d.ts.map

package/dist/render/stepAccounting.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"stepAccounting.d.ts","sourceRoot":"","sources":["../../src/render/stepAccounting.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA4BG;AAEH,OAAO,KAAK,EAAE,WAAW,EAAE,MAAM,4BAA4B,CAAC;AAiB9D;;;;;;GAMG;AACH,eAAO,MAAM,qBAAqB,GAAI,QAAQ,WAAW,KAAG,MAAM,EAcjE,CAAC"}
+{"version":3,"file":"stepAccounting.d.ts","sourceRoot":"","sources":["../../src/render/stepAccounting.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,WAAW,EAAE,MAAM,4BAA4B,CAAC;AAS9D,eAAO,MAAM,qBAAqB,GAAI,QAAQ,WAAW,KAAG,MAAM,EAcjE,CAAC"}

package/dist/render/stepAccounting.js

@@ -1,60 +1,16 @@
-/**
- * WHAT BECAME OF EVERY STEP THIS RUN READ (@SCN-USG-018) — the population, the four dispositions,
- * and whether they add back up to it.
- *
- * THE SECTION IS THIS AXIS'S FIRST NON-NEGOTIABLE MADE CHECKABLE. Nothing seen is dropped: a step
- * that reaches the reader leaves it as a candidate fitness check, as one of the runners the target
- * named, as the reconciler, or as a step the consumer called a non-check, and there is no fifth
- * outcome. Every section above this one names what a step BECAME, so a step that became nothing is
- * missing from none of them and every one reads exactly as it would have read had the step never
- * existed. This is the only cut of the report that can see an absence, and seeing absences is what
- * the whole axis is for.
- *
- * BOTH TOTALS, SIDE BY SIDE, AND THE SUM IS NOT THE READER'S TO MAKE. `Accounted for` is the
- * figure the count itself arrived at; a reader adding the four dispositions up for themselves
- * would be checking their own arithmetic against nothing, and would go on agreeing with a report
- * whose four figures had lost a step between them. Stated as a pair, the identity is something a
- * consumer reads rather than derives.
- *
- * A TABLE AND THEN A SENTENCE, because the two answer different readers. The row is what a
- * consumer compares against their own pipeline — four candidates and three non-checks is a claim
- * about their file they can check. The line under it is the verdict, and where the figures
- * disagree it names both of them, because a bare "does not balance" over numbers a reader has to
- * subtract for themselves is the report withholding the one thing it knows.
- *
- * Its own module rather than a further section in `markdown.ts`, which sits at a `max-lines`
- * exception — and an exception excuses existing debt, never headroom. The precedent is
- * `runVerdict.ts` and, along this axis, `discoveryScope.ts`, `behaviouralRunners.ts`,
- * `excludedSteps.ts` and `reconcilerSteps.ts`.
- */
-/**
- * The verdict line — one sentence, and where the two totals disagree it states both.
- *
- * ONE SENTENCE FOR EITHER DISAGREEMENT, deliberately. A step accounted for as nothing and a step
- * accounted for twice are opposite faults, but the reader's next move is the same in both cases
- * and the figures already say which it is: a second sentence would be a branch nothing in this
- * repository can reach, kept alive to describe a case the guards on the count forbid.
- */
+import { CORE_MESSAGES, CoreMessage } from "../domain/messages.js";
 const verdictOf = ({ stepsRead, accountedFor }) => accountedFor === stepsRead
-    ? "- every step this run read is accounted for."
-    : `- ${stepsRead} step(s) read, ${accountedFor} accounted for — the four dispositions do not ` +
-        `add up to the steps this run read.`;
-/**
- * The accounting, or nothing at all.
- *
- * OMITTED WHERE THE RUN READ NO STEP, which is the only way the count can be empty: the section
- * appears wherever there is a pipeline to account for, and a run handed no CI configuration
- * renders byte-identically to before.
- */
+    ? `- ${CORE_MESSAGES[CoreMessage.EveryStepAccountedFor]}`
+    : `- ${CORE_MESSAGES[CoreMessage.StepsNotAccountedFor](stepsRead, accountedFor)}`;
 export const stepAccountingSection = (report) => {
     const accounting = report.summary.stepAccounting;
     if (accounting === undefined)
         return [];
     const { stepsRead, candidates, runners, reconciler, excluded, accountedFor } = accounting;
     return [
-        "### Step accounting",
+        CORE_MESSAGES[CoreMessage.StepAccountingHeading],
         "",
-        "| Steps read | Candidates | Runners | Reconciler | Excluded | Accounted for |",
+        CORE_MESSAGES[CoreMessage.StepAccountingTableHeader],
         "| --- | --- | --- | --- | --- | --- |",
         `| ${stepsRead} | ${candidates} | ${runners} | ${reconciler} | ${excluded} | ${accountedFor} |`,
         "",

package/dist/render/stepAccounting.js.map

@@ -1 +1 @@
-{"version":3,"file":"stepAccounting.js","sourceRoot":"","sources":["../../src/render/stepAccounting.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA4BG;AAKH;;;;;;;GAOG;AACH,MAAM,SAAS,GAAG,CAAC,EAAE,SAAS,EAAE,YAAY,EAAkB,EAAU,EAAE,CACxE,YAAY,KAAK,SAAS;IACxB,CAAC,CAAC,8CAA8C;IAChD,CAAC,CAAC,KAAK,SAAS,kBAAkB,YAAY,gDAAgD;QAC5F,oCAAoC,CAAC;AAE3C;;;;;;GAMG;AACH,MAAM,CAAC,MAAM,qBAAqB,GAAG,CAAC,MAAmB,EAAY,EAAE;IACrE,MAAM,UAAU,GAAG,MAAM,CAAC,OAAO,CAAC,cAAc,CAAC;IACjD,IAAI,UAAU,KAAK,SAAS;QAAE,OAAO,EAAE,CAAC;IACxC,MAAM,EAAE,SAAS,EAAE,UAAU,EAAE,OAAO,EAAE,UAAU,EAAE,QAAQ,EAAE,YAAY,EAAE,GAAG,UAAU,CAAC;IAC1F,OAAO;QACL,qBAAqB;QACrB,EAAE;QACF,+EAA+E;QAC/E,uCAAuC;QACvC,KAAK,SAAS,MAAM,UAAU,MAAM,OAAO,MAAM,UAAU,MAAM,QAAQ,MAAM,YAAY,IAAI;QAC/F,EAAE;QACF,SAAS,CAAC,UAAU,CAAC;QACrB,EAAE;KACH,CAAC;AACJ,CAAC,CAAC"}
+{"version":3,"file":"stepAccounting.js","sourceRoot":"","sources":["../../src/render/stepAccounting.ts"],"names":[],"mappings":"AAEA,OAAO,EAAE,aAAa,EAAE,WAAW,EAAE,MAAM,uBAAuB,CAAC;AAEnE,MAAM,SAAS,GAAG,CAAC,EAAE,SAAS,EAAE,YAAY,EAAkB,EAAU,EAAE,CACxE,YAAY,KAAK,SAAS;IACxB,CAAC,CAAC,KAAK,aAAa,CAAC,WAAW,CAAC,qBAAqB,CAAC,EAAE;IACzD,CAAC,CAAC,KAAK,aAAa,CAAC,WAAW,CAAC,oBAAoB,CAAC,CAAC,SAAS,EAAE,YAAY,CAAC,EAAE,CAAC;AAEtF,MAAM,CAAC,MAAM,qBAAqB,GAAG,CAAC,MAAmB,EAAY,EAAE;IACrE,MAAM,UAAU,GAAG,MAAM,CAAC,OAAO,CAAC,cAAc,CAAC;IACjD,IAAI,UAAU,KAAK,SAAS;QAAE,OAAO,EAAE,CAAC;IACxC,MAAM,EAAE,SAAS,EAAE,UAAU,EAAE,OAAO,EAAE,UAAU,EAAE,QAAQ,EAAE,YAAY,EAAE,GAAG,UAAU,CAAC;IAC1F,OAAO;QACL,aAAa,CAAC,WAAW,CAAC,qBAAqB,CAAC;QAChD,EAAE;QACF,aAAa,CAAC,WAAW,CAAC,yBAAyB,CAAC;QACpD,uCAAuC;QACvC,KAAK,SAAS,MAAM,UAAU,MAAM,OAAO,MAAM,UAAU,MAAM,QAAQ,MAAM,YAAY,IAAI;QAC/F,EAAE;QACF,SAAS,CAAC,UAAU,CAAC;QACrB,EAAE;KACH,CAAC;AACJ,CAAC,CAAC"}

package/dist/render/testVolume.d.ts

@@ -1,28 +1,3 @@
-/**
- * THE RUNTIME TEST-VOLUME CENSUS a run banked — the `### Test volume` cut under Summary views.
- *
- * Its own module rather than a section in `markdown.ts`, which sits at a `max-lines` exception —
- * and an exception excuses existing debt, never headroom. Moved out whole at @SCN-USG-015, when
- * the excluded-step cut beside it needed the room; `runVerdict.ts`, `staticChecks.ts` and
- * `behaviouralRunners.ts` are the precedent, each moved for exactly this reason. It goes out
- * BESIDE `staticChecks.ts` deliberately: that module's own header already calls this section its
- * mirror on the runtime axis, and the two now sit where a reader looking for either finds both.
- * NOTHING about the section changed in the move: same emitter, same lines, same omit-when-absent.
- */
 import type { RenderInput } from "../assemble/renderInput.js";
-/**
- * Test volume (@SCN-RPT-010) — the evidence-observation side under Summary views, the
- * counterpart to the Evidence reconciliation' evidence-obligation side. Renders the balancing identity
- * (`N evidence observations = a on scenarios + b on phantom scenarios + c on the suspense scenario`,
- * a DERIVED view of the retained aggregate, grouped by the SCENARIO-KIND each credit posted to)
- * then the per-quality-check evidence observation table
- * (all four runtime quality-checks, zeros shown — a fixed tally like Evidence reconciliation).
- * Omitted only when no evidence-observation read is threaded (the 3-arg back-compat path). The
- * identity holds BY CONSTRUCTION (one shared pass in src/evidenceObservations.ts); the renderer
- * only sums what the aggregate already counted by kind. Quality-checks read as their tag words,
- * lowercase (the label-=-tag rule). The numbers read off the report's materialised
- * `summary.testVolume` + `summary.rawByRuntimeQualityCheck` (both Ledger folds, 3F-2103 — the
- * `evidenceObservations` section retired).
- */
 export declare const testVolumeSection: (report: RenderInput) => string[];
 //# sourceMappingURL=testVolume.d.ts.map

package/dist/render/testVolume.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"testVolume.d.ts","sourceRoot":"","sources":["../../src/render/testVolume.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;GAUG;AAGH,OAAO,KAAK,EAAE,WAAW,EAAE,MAAM,4BAA4B,CAAC;AAE9D;;;;;;;;;;;;;GAaG;AACH,eAAO,MAAM,iBAAiB,GAAI,QAAQ,WAAW,KAAG,MAAM,EAyB7D,CAAC"}
+{"version":3,"file":"testVolume.d.ts","sourceRoot":"","sources":["../../src/render/testVolume.ts"],"names":[],"mappings":"AACA,OAAO,KAAK,EAAE,WAAW,EAAE,MAAM,4BAA4B,CAAC;AAG9D,eAAO,MAAM,iBAAiB,GAAI,QAAQ,WAAW,KAAG,MAAM,EAkB7D,CAAC"}

package/dist/render/testVolume.js

@@ -1,48 +1,17 @@
-/**
- * THE RUNTIME TEST-VOLUME CENSUS a run banked — the `### Test volume` cut under Summary views.
- *
- * Its own module rather than a section in `markdown.ts`, which sits at a `max-lines` exception —
- * and an exception excuses existing debt, never headroom. Moved out whole at @SCN-USG-015, when
- * the excluded-step cut beside it needed the room; `runVerdict.ts`, `staticChecks.ts` and
- * `behaviouralRunners.ts` are the precedent, each moved for exactly this reason. It goes out
- * BESIDE `staticChecks.ts` deliberately: that module's own header already calls this section its
- * mirror on the runtime axis, and the two now sit where a reader looking for either finds both.
- * NOTHING about the section changed in the move: same emitter, same lines, same omit-when-absent.
- */
 import { RUNTIME_QUALITY_CHECKS } from "../domain/ledger.js";
-/**
- * Test volume (@SCN-RPT-010) — the evidence-observation side under Summary views, the
- * counterpart to the Evidence reconciliation' evidence-obligation side. Renders the balancing identity
- * (`N evidence observations = a on scenarios + b on phantom scenarios + c on the suspense scenario`,
- * a DERIVED view of the retained aggregate, grouped by the SCENARIO-KIND each credit posted to)
- * then the per-quality-check evidence observation table
- * (all four runtime quality-checks, zeros shown — a fixed tally like Evidence reconciliation).
- * Omitted only when no evidence-observation read is threaded (the 3-arg back-compat path). The
- * identity holds BY CONSTRUCTION (one shared pass in src/evidenceObservations.ts); the renderer
- * only sums what the aggregate already counted by kind. Quality-checks read as their tag words,
- * lowercase (the label-=-tag rule). The numbers read off the report's materialised
- * `summary.testVolume` + `summary.rawByRuntimeQualityCheck` (both Ledger folds, 3F-2103 — the
- * `evidenceObservations` section retired).
- */
+import { CORE_MESSAGES, CoreMessage } from "../domain/messages.js";
 export const testVolumeSection = (report) => {
     const volume = report.summary.testVolume;
     const raw = report.summary.rawByRuntimeQualityCheck;
     if (!volume || !raw)
         return [];
     const total = volume.totalEvidenceObservations;
-    // Three DIRECT reads off the materialised kind-counts — the renderer does no arithmetic on this
-    // line. The three terms are grouped by the SCENARIO-KIND each credit posted to (the canon
-    // grouping): on scenarios (a scenario's account), on phantom scenarios (invented
-    // phantom-scenario accounts — many can exist, hence the plural) and on the suspense scenario (the
-    // one suspense account, singular — includes broken). The identity total = onScenario +
-    // onPhantomScenario + onSuspenseScenario holds BY CONSTRUCTION (one shared runtimeObservationTally
-    // fold), so the three printed terms cannot drift from the total.
     const lines = [
-        "### Test volume",
+        CORE_MESSAGES[CoreMessage.TestVolumeHeading],
         "",
-        `${total} evidence observations = ${volume.onScenario} on scenarios + ${volume.onPhantomScenario} on phantom scenarios + ${volume.onSuspenseScenario} on the suspense scenario.`,
+        CORE_MESSAGES[CoreMessage.TestVolumeSum](total, volume.onScenario, volume.onPhantomScenario, volume.onSuspenseScenario),
         "",
-        "| Quality-check | Evidence observations |",
+        CORE_MESSAGES[CoreMessage.TestVolumeTableHeader],
         "| --- | --- |",
     ];
     for (const qualityCheck of RUNTIME_QUALITY_CHECKS) {

package/dist/render/testVolume.js.map

@@ -1 +1 @@
-{"version":3,"file":"testVolume.js","sourceRoot":"","sources":["../../src/render/testVolume.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;GAUG;AAEH,OAAO,EAAE,sBAAsB,EAAE,MAAM,qBAAqB,CAAC;AAG7D;;;;;;;;;;;;;GAaG;AACH,MAAM,CAAC,MAAM,iBAAiB,GAAG,CAAC,MAAmB,EAAY,EAAE;IACjE,MAAM,MAAM,GAAG,MAAM,CAAC,OAAO,CAAC,UAAU,CAAC;IACzC,MAAM,GAAG,GAAG,MAAM,CAAC,OAAO,CAAC,wBAAwB,CAAC;IACpD,IAAI,CAAC,MAAM,IAAI,CAAC,GAAG;QAAE,OAAO,EAAE,CAAC;IAC/B,MAAM,KAAK,GAAG,MAAM,CAAC,yBAAyB,CAAC;IAC/C,gGAAgG;IAChG,0FAA0F;IAC1F,iFAAiF;IACjF,kGAAkG;IAClG,uFAAuF;IACvF,mGAAmG;IACnG,iEAAiE;IACjE,MAAM,KAAK,GAAG;QACZ,iBAAiB;QACjB,EAAE;QACF,GAAG,KAAK,4BAA4B,MAAM,CAAC,UAAU,mBAAmB,MAAM,CAAC,iBAAiB,2BAA2B,MAAM,CAAC,kBAAkB,4BAA4B;QAChL,EAAE;QACF,2CAA2C;QAC3C,eAAe;KAChB,CAAC;IACF,KAAK,MAAM,YAAY,IAAI,sBAAsB,EAAE,CAAC;QAClD,KAAK,CAAC,IAAI,CAAC,KAAK,YAAY,MAAM,GAAG,CAAC,YAAY,CAAC,IAAI,CAAC,CAAC;IAC3D,CAAC;IACD,KAAK,CAAC,IAAI,CAAC,EAAE,CAAC,CAAC;IACf,OAAO,KAAK,CAAC;AACf,CAAC,CAAC"}
+{"version":3,"file":"testVolume.js","sourceRoot":"","sources":["../../src/render/testVolume.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,sBAAsB,EAAE,MAAM,qBAAqB,CAAC;AAE7D,OAAO,EAAE,aAAa,EAAE,WAAW,EAAE,MAAM,uBAAuB,CAAC;AAEnE,MAAM,CAAC,MAAM,iBAAiB,GAAG,CAAC,MAAmB,EAAY,EAAE;IACjE,MAAM,MAAM,GAAG,MAAM,CAAC,OAAO,CAAC,UAAU,CAAC;IACzC,MAAM,GAAG,GAAG,MAAM,CAAC,OAAO,CAAC,wBAAwB,CAAC;IACpD,IAAI,CAAC,MAAM,IAAI,CAAC,GAAG;QAAE,OAAO,EAAE,CAAC;IAC/B,MAAM,KAAK,GAAG,MAAM,CAAC,yBAAyB,CAAC;IAC/C,MAAM,KAAK,GAAG;QACZ,aAAa,CAAC,WAAW,CAAC,iBAAiB,CAAC;QAC5C,EAAE;QACF,aAAa,CAAC,WAAW,CAAC,aAAa,CAAC,CAAC,KAAK,EAAE,MAAM,CAAC,UAAU,EAAE,MAAM,CAAC,iBAAiB,EAAE,MAAM,CAAC,kBAAkB,CAAC;QACvH,EAAE;QACF,aAAa,CAAC,WAAW,CAAC,qBAAqB,CAAC;QAChD,eAAe;KAChB,CAAC;IACF,KAAK,MAAM,YAAY,IAAI,sBAAsB,EAAE,CAAC;QAClD,KAAK,CAAC,IAAI,CAAC,KAAK,YAAY,MAAM,GAAG,CAAC,YAAY,CAAC,IAAI,CAAC,CAAC;IAC3D,CAAC;IACD,KAAK,CAAC,IAAI,CAAC,EAAE,CAAC,CAAC;IACf,OAAO,KAAK,CAAC;AACf,CAAC,CAAC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@3f-consulting/spec-controller-core",
-  "version": "0.1.0-alpha.7",
+  "version": "0.1.0-alpha.70",
   "description": "The pure, embeddable reconciliation core behind spec-controller — Gherkin/@SCN parse, the evidence model, reconcile primitives, and renderers. No CLI, no I/O.",
   "keywords": [
     "reconciliation",
@@ -32,6 +32,9 @@
   "publishConfig": {
     "access": "public"
   },
+  "devDependencies": {
+    "fast-check": "4.10.1"
+  },
   "scripts": {
     "build": "tsc -p tsconfig.build.json"
   },

package/dist/domain/checkCharacteristics.d.ts

@@ -1,88 +0,0 @@
-/**
- * THE PORTFOLIO'S CHECK CHARACTERISTICS — the words that may name what a fitness check asserts.
- *
- * WHAT THIS IS FOR NOW — A ROLL-UP VOCABULARY, NOT A GATE (3F-3167). A fitness scenario carries
- * one tag, `@fitness`, and names its characteristic as a FIELD on its configured row. The word is
- * therefore a REPORTING LABEL: it is what a report groups its fitness rows by and what the
- * portfolio says out loud about where a product is weak. Nothing parses it, and no check in this
- * repository holds a manifest to this list any more.
- *
- * THE GATE THAT USED TO (3F-2996, retired 3F-3167). The set of words that could name a
- * characteristic was once read out of the target's own check registry and
- * `specController.thresholds`, so adding a registry entry was simultaneously the act that MINTED
- * a characteristic and the act that CERTIFIED it. Fourteen tags for seven characteristics were
- * built over a month in a repository that reconciles its own tree on every push, and nothing
- * redded once (3F-2994). `lint:check-characteristics` closed that, along with a minting ceremony
- * for words canon had not named — and both left when the tag stopped doing two jobs. A word that
- * only labels a roll-up cannot be minted into the parser by a typo, because the parser does not
- * read it. Whether the portfolio SHOULD carry a given word is a canon question, asked of people.
- *
- * THE ROSTER IS STILL THE PORTFOLIO'S, AND IT STILL ARRIVES BY VERSION. Canon names this package
- * as the machine-readable form's home — *"a `spec-controller-core` export or its own shared
- * package … from which each product DERIVES its legal set via its pinned version, refreshed on a
- * bump — never a hand-typed roster"* (`fitness-functions.md` → *Static checks*). Every reconciled
- * product already installs this package to run `balance`, so the export is the smaller of the two
- * shapes canon offers: nothing is published that was not published before, and no consumer gains
- * a dependency. What changed at 3F-3167 is what a consumer DOES with it — group a report, not
- * refuse a build.
- *
- * ON THE PUBLIC `.` BARREL, NEVER `./internal`. A roster only the monorepo can import is
- * reachable by exactly the one product that does not need it.
- *
- * AND THE BARREL ENTRY IS NOT A FROZEN CONTRACT — it stays on its merits (3F-3410). This used to
- * say the entry was a "v1 contract change", reconciled against a hand-written surface updated in
- * the same act. Both halves are gone: that surface left at 3F-3449, and a 0.x package does not
- * freeze its exports, it drops the dead ones in a prerelease (operator, 2026-09-16). So nothing
- * keeps this export here by inertia, and 3F-3410 — which deleted the obligation-side observer from
- * this same barrel for having no caller — asked directly whether this one had one. It does, and not
- * in this repository: canon names it (below), and a sibling product holds a vendored copy naming
- * this module as its source, to be replaced by the import. A shared vocabulary's consumers are
- * outside the repository that publishes it, so a grep of this tree is the wrong population to
- * measure it by.
- *
- * ═══ THIS FILE IS A VENDORED COPY, AND SAYS SO ═══
- *
- * Canon lives in the `strategy` repository, which this one's CI never checks out and a public
- * consumer of an MIT-licensed tool would not have at all — the arrangement the operator ruled
- * for exactly this case (2026-08-03, 3F-2296). So this list is transcribed, and
- * holding it to canon belongs to the strategy repository's CI, where every product is visible. It
- * says so on its face rather than leaving a reader to wonder whether the reconciliation was
- * forgotten.
- *
- * PURE DATA AND ONE PREDICATE — no I/O, nothing imported, so it sits in `domain/` beside
- * the fitness-row readers, and `pnpm lint:boundaries` stays green by construction — the whole of
- * what asks that question, now that `domainPurity` has gone at 3F-3438.
- */
-/**
- * The characteristics the portfolio carries, transcribed from `fitness-functions.md`.
- *
- * THE WORDS ONLY — WHICH CHECKS SIT UNDER EACH IS NOT RECORDED HERE, AND THAT IS THE POINT
- * (3F-3410). This docblock used to carry canon's grouped-by-characteristic sentence, naming the
- * member checks per word. Canon removed that column on 2026-09-16 and said why in terms: the list
- * had been transcribed HERE, so one unread list had become two drifting ones, and by then most of
- * the checks it named had been deleted from this repository. Membership is recorded once, on each
- * product's own `specController.fitnessChecks` rows — the only place the answer is true and the
- * only place any reconciliation reads it (`dry`: the rows are the fact).
- *
- * TWO GROUPS, WHICH IS CANON'S OWN SPLIT AND NOT A MEMBERSHIP CLAIM. The static checks read the
- * source (or, for `self-balance`, the PRODUCED EVIDENCE rather than the source); the measured ones
- * are assessed by running the suite and measuring it (canon, *Runtime fitness functions*).
- *
- * BARE, AND SORTED BY NEITHER. The words carry no `@` because every reader hands this list bare
- * terms (`bareTerm`, 3F-2976), and the order is canon's own so a reader diffing the two documents
- * reads them in the same sequence.
- */
-export declare const PORTFOLIO_CHECK_CHARACTERISTICS: readonly string[];
-/**
- * Whether the portfolio roster carries this characteristic.
- *
- * EXACT, AND NEVER A NEAR-MATCH COURTESY. A word the roster does not carry is not resolved to the
- * roster word it resembles: the mint is the act being surfaced, and quietly reading `complexty`
- * as `complexity` would hide exactly what a caller reads this to make visible.
- *
- * The term arrives BARE. Every reader in this repository reaches the roster through the resolvers
- * that already store both terms bare, so stripping a sigil here would be a second reading of what
- * a term bare is — the disagreement between readers that 3F-2976 spent a slice removing.
- */
-export declare function isPortfolioCharacteristic(characteristic: string): boolean;
-//# sourceMappingURL=checkCharacteristics.d.ts.map

package/dist/domain/checkCharacteristics.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"checkCharacteristics.d.ts","sourceRoot":"","sources":["../../src/domain/checkCharacteristics.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAsDG;AAEH;;;;;;;;;;;;;;;;;;GAkBG;AACH,eAAO,MAAM,+BAA+B,EAAE,SAAS,MAAM,EAmB5D,CAAC;AAEF;;;;;;;;;;GAUG;AACH,wBAAgB,yBAAyB,CAAC,cAAc,EAAE,MAAM,GAAG,OAAO,CAEzE"}

package/dist/domain/checkCharacteristics.js

@@ -1,109 +0,0 @@
-/**
- * THE PORTFOLIO'S CHECK CHARACTERISTICS — the words that may name what a fitness check asserts.
- *
- * WHAT THIS IS FOR NOW — A ROLL-UP VOCABULARY, NOT A GATE (3F-3167). A fitness scenario carries
- * one tag, `@fitness`, and names its characteristic as a FIELD on its configured row. The word is
- * therefore a REPORTING LABEL: it is what a report groups its fitness rows by and what the
- * portfolio says out loud about where a product is weak. Nothing parses it, and no check in this
- * repository holds a manifest to this list any more.
- *
- * THE GATE THAT USED TO (3F-2996, retired 3F-3167). The set of words that could name a
- * characteristic was once read out of the target's own check registry and
- * `specController.thresholds`, so adding a registry entry was simultaneously the act that MINTED
- * a characteristic and the act that CERTIFIED it. Fourteen tags for seven characteristics were
- * built over a month in a repository that reconciles its own tree on every push, and nothing
- * redded once (3F-2994). `lint:check-characteristics` closed that, along with a minting ceremony
- * for words canon had not named — and both left when the tag stopped doing two jobs. A word that
- * only labels a roll-up cannot be minted into the parser by a typo, because the parser does not
- * read it. Whether the portfolio SHOULD carry a given word is a canon question, asked of people.
- *
- * THE ROSTER IS STILL THE PORTFOLIO'S, AND IT STILL ARRIVES BY VERSION. Canon names this package
- * as the machine-readable form's home — *"a `spec-controller-core` export or its own shared
- * package … from which each product DERIVES its legal set via its pinned version, refreshed on a
- * bump — never a hand-typed roster"* (`fitness-functions.md` → *Static checks*). Every reconciled
- * product already installs this package to run `balance`, so the export is the smaller of the two
- * shapes canon offers: nothing is published that was not published before, and no consumer gains
- * a dependency. What changed at 3F-3167 is what a consumer DOES with it — group a report, not
- * refuse a build.
- *
- * ON THE PUBLIC `.` BARREL, NEVER `./internal`. A roster only the monorepo can import is
- * reachable by exactly the one product that does not need it.
- *
- * AND THE BARREL ENTRY IS NOT A FROZEN CONTRACT — it stays on its merits (3F-3410). This used to
- * say the entry was a "v1 contract change", reconciled against a hand-written surface updated in
- * the same act. Both halves are gone: that surface left at 3F-3449, and a 0.x package does not
- * freeze its exports, it drops the dead ones in a prerelease (operator, 2026-09-16). So nothing
- * keeps this export here by inertia, and 3F-3410 — which deleted the obligation-side observer from
- * this same barrel for having no caller — asked directly whether this one had one. It does, and not
- * in this repository: canon names it (below), and a sibling product holds a vendored copy naming
- * this module as its source, to be replaced by the import. A shared vocabulary's consumers are
- * outside the repository that publishes it, so a grep of this tree is the wrong population to
- * measure it by.
- *
- * ═══ THIS FILE IS A VENDORED COPY, AND SAYS SO ═══
- *
- * Canon lives in the `strategy` repository, which this one's CI never checks out and a public
- * consumer of an MIT-licensed tool would not have at all — the arrangement the operator ruled
- * for exactly this case (2026-08-03, 3F-2296). So this list is transcribed, and
- * holding it to canon belongs to the strategy repository's CI, where every product is visible. It
- * says so on its face rather than leaving a reader to wonder whether the reconciliation was
- * forgotten.
- *
- * PURE DATA AND ONE PREDICATE — no I/O, nothing imported, so it sits in `domain/` beside
- * the fitness-row readers, and `pnpm lint:boundaries` stays green by construction — the whole of
- * what asks that question, now that `domainPurity` has gone at 3F-3438.
- */
-/**
- * The characteristics the portfolio carries, transcribed from `fitness-functions.md`.
- *
- * THE WORDS ONLY — WHICH CHECKS SIT UNDER EACH IS NOT RECORDED HERE, AND THAT IS THE POINT
- * (3F-3410). This docblock used to carry canon's grouped-by-characteristic sentence, naming the
- * member checks per word. Canon removed that column on 2026-09-16 and said why in terms: the list
- * had been transcribed HERE, so one unread list had become two drifting ones, and by then most of
- * the checks it named had been deleted from this repository. Membership is recorded once, on each
- * product's own `specController.fitnessChecks` rows — the only place the answer is true and the
- * only place any reconciliation reads it (`dry`: the rows are the fact).
- *
- * TWO GROUPS, WHICH IS CANON'S OWN SPLIT AND NOT A MEMBERSHIP CLAIM. The static checks read the
- * source (or, for `self-balance`, the PRODUCED EVIDENCE rather than the source); the measured ones
- * are assessed by running the suite and measuring it (canon, *Runtime fitness functions*).
- *
- * BARE, AND SORTED BY NEITHER. The words carry no `@` because every reader hands this list bare
- * terms (`bareTerm`, 3F-2976), and the order is canon's own so a reader diffing the two documents
- * reads them in the same sequence.
- */
-export const PORTFOLIO_CHECK_CHARACTERISTICS = [
-    // Static checks
-    "complexity",
-    "function-length",
-    "tech-conformance",
-    "vocab",
-    "traceability",
-    "lint",
-    "flag-hygiene",
-    "doc-accuracy",
-    "typecheck",
-    "security",
-    "licence",
-    "bundle-size",
-    "self-balance",
-    // Measured
-    "ci-run-time",
-    "coverage",
-    "mutation",
-];
-/**
- * Whether the portfolio roster carries this characteristic.
- *
- * EXACT, AND NEVER A NEAR-MATCH COURTESY. A word the roster does not carry is not resolved to the
- * roster word it resembles: the mint is the act being surfaced, and quietly reading `complexty`
- * as `complexity` would hide exactly what a caller reads this to make visible.
- *
- * The term arrives BARE. Every reader in this repository reaches the roster through the resolvers
- * that already store both terms bare, so stripping a sigil here would be a second reading of what
- * a term bare is — the disagreement between readers that 3F-2976 spent a slice removing.
- */
-export function isPortfolioCharacteristic(characteristic) {
-    return PORTFOLIO_CHECK_CHARACTERISTICS.includes(characteristic);
-}
-//# sourceMappingURL=checkCharacteristics.js.map

package/dist/domain/checkCharacteristics.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"checkCharacteristics.js","sourceRoot":"","sources":["../../src/domain/checkCharacteristics.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAsDG;AAEH;;;;;;;;;;;;;;;;;;GAkBG;AACH,MAAM,CAAC,MAAM,+BAA+B,GAAsB;IAChE,gBAAgB;IAChB,YAAY;IACZ,iBAAiB;IACjB,kBAAkB;IAClB,OAAO;IACP,cAAc;IACd,MAAM;IACN,cAAc;IACd,cAAc;IACd,WAAW;IACX,UAAU;IACV,SAAS;IACT,aAAa;IACb,cAAc;IACd,WAAW;IACX,aAAa;IACb,UAAU;IACV,UAAU;CACX,CAAC;AAEF;;;;;;;;;;GAUG;AACH,MAAM,UAAU,yBAAyB,CAAC,cAAsB;IAC9D,OAAO,+BAA+B,CAAC,QAAQ,CAAC,cAAc,CAAC,CAAC;AAClE,CAAC"}

package/dist/domain/fitnessChecks.d.ts

@@ -1,79 +0,0 @@
-/**
- * THE FITNESS CHECK ROWS — what a CONVERTED check says about itself, keyed by the `@SCN` it is
- * about.
- *
- *     @SCN          the row                       what the corpus then reads
- *     SCN-FIT-001   { characteristic: complexity } a @fitness scenario owes `complexity`
- *
- * THE TAG NAMES THE AXIS AND THE ROW NAMES THE SUBJECT. A bare characteristic tag answered two
- * questions at once — how a claim is proved, and what it is about — and the tier tags answer only
- * the first. So a converted scenario carries `@fitness` alone, and the characteristic moves here,
- * where it stays a first-class word the roll-up still groups by.
- *
- * NOT A SECOND OBLIGATION SHAPE. What a `@fitness` scenario raises is the same
- * `{ qualityCheck: "lint", staticCheck: <characteristic> }` a registered bare tag raises today, so
- * the pair key, the reconciler's static arm and the report's roll-up are all untouched. What
- * changed is only where the word came from.
- *
- * NOT THE (RETIRED) CHECK REGISTRY, AND THE DIFFERENCE IS THE SEAM THIS RETIRES. That registry
- * answered "which check is this runnable script handle", because a handle does not know what it
- * is for; the `@SCN`
- * is then resolved through the corpus, a second hop. A converted check is never discovered as a
- * handle — it is a scenario that ran, carrying its own tag line — so the `@SCN` is the KEY here
- * rather than something a lookup has to recover.
- *
- * PURE AND INJECTED — the rows arrive as data, read from the TARGET's own manifest at the app edge
- * (`specController.fitnessChecks`), the stance the retired `thresholdsOf` took. A target that
- * configures nothing raises nothing, so the reading is inert on a corpus
- * nobody has converted.
- */
-/**
- * ONE CONFIGURED ROW as the obligation rule reads it.
- *
- * The `scn` a row states is not a member here: it is this index's KEY, so a row cannot name one
- * scenario and be filed under another. The command a row states is not a member either — it is the
- * COMMAND half of the row and nothing on the debit side reads it. Every row is credited by its own
- * step's outcome in the run's record, so the characteristic is the whole of what the ledger reads.
- */
-export interface FitnessCheck {
-    /** The bare characteristic this check asserts (`complexity`). */
-    readonly characteristic: string;
-}
-/** The rows as the rule reads them — bare `@SCN` → the row naming that scenario's check. */
-export type FitnessCheckIndex = ReadonlyMap<string, FitnessCheck>;
-/**
- * Build the index from the rows a manifest holds.
- *
- * A LIST, NOT A BLOCK KEYED BY `@SCN`, and the shape is the row's own argument: a row is what a
- * check says about ITSELF — its `@SCN`, its characteristic, its command — so no one of those three
- * is promoted above the others by being the key somebody has to write it under. The `@SCN` becomes
- * the key HERE, where a lookup needs one.
- *
- * A MALFORMED ROW IS DROPPED, NOT TRUSTED AND NOT THROWN ON — the defensive stance the whole
- * `specController.*` family takes. Config is data from outside, and a reader that throws on a typo
- * turns one bad character into a run that produces no verdict at all, which is loud nowhere; a
- * dropped row leaves its scenario naming no characteristic, which the corpus reports.
- */
-export declare function fitnessChecksOf(entries: unknown): FitnessCheckIndex;
-/**
- * ONE CONFIGURED ROW THE TARGET'S CORPUS CARRIES NO SCENARIO FOR (3F-3472) — a check the manifest
- * declares and nothing in the corpus specifies.
- *
- * THE MIRROR OF `unconfiguredFitnessScenarios`, AND THE HALF THE BOOKS COULD NOT SEE. That one
- * reads a `@fitness` scenario no row names; this reads a row no scenario names. The asymmetry
- * between what each EARNS is the two facts' own: a scenario naming no row names no characteristic,
- * so there is nothing to put on the books and the census says who — a row names one, so there IS a
- * debit, and `features/fitness-checks.feature` promises it as "an Evidence Obligation nothing
- * observed".
- *
- * IT CARRIES THE CHARACTERISTIC BECAUSE THE OBLIGATION IT RAISES NAMES ONE. The `@SCN` alone would
- * leave the reader of this reading to go back to the index for the other half, which is the second
- * read `readTargetCorpus` composes its readings together to foreclose.
- */
-export interface UnspecifiedFitnessRow {
-    /** The `@SCN` the row states, which no scenario in the target's corpus carries. */
-    readonly scnId: string;
-    /** The bare characteristic the row asserts (`complexity`) — what its debit is owed at. */
-    readonly characteristic: string;
-}
-//# sourceMappingURL=fitnessChecks.d.ts.map

package/dist/domain/fitnessChecks.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"fitnessChecks.d.ts","sourceRoot":"","sources":["../../src/domain/fitnessChecks.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA4BG;AAIH;;;;;;;GAOG;AACH,MAAM,WAAW,YAAY;IAC3B,iEAAiE;IACjE,QAAQ,CAAC,cAAc,EAAE,MAAM,CAAC;CACjC;AAED,4FAA4F;AAC5F,MAAM,MAAM,iBAAiB,GAAG,WAAW,CAAC,MAAM,EAAE,YAAY,CAAC,CAAC;AA2BlE;;;;;;;;;;;;GAYG;AACH,wBAAgB,eAAe,CAAC,OAAO,EAAE,OAAO,GAAG,iBAAiB,CAQnE;AAED;;;;;;;;;;;;;;GAcG;AACH,MAAM,WAAW,qBAAqB;IACpC,mFAAmF;IACnF,QAAQ,CAAC,KAAK,EAAE,MAAM,CAAC;IACvB,0FAA0F;IAC1F,QAAQ,CAAC,cAAc,EAAE,MAAM,CAAC;CACjC"}

package/dist/domain/fitnessChecks.js

@@ -1,81 +0,0 @@
-/**
- * THE FITNESS CHECK ROWS — what a CONVERTED check says about itself, keyed by the `@SCN` it is
- * about.
- *
- *     @SCN          the row                       what the corpus then reads
- *     SCN-FIT-001   { characteristic: complexity } a @fitness scenario owes `complexity`
- *
- * THE TAG NAMES THE AXIS AND THE ROW NAMES THE SUBJECT. A bare characteristic tag answered two
- * questions at once — how a claim is proved, and what it is about — and the tier tags answer only
- * the first. So a converted scenario carries `@fitness` alone, and the characteristic moves here,
- * where it stays a first-class word the roll-up still groups by.
- *
- * NOT A SECOND OBLIGATION SHAPE. What a `@fitness` scenario raises is the same
- * `{ qualityCheck: "lint", staticCheck: <characteristic> }` a registered bare tag raises today, so
- * the pair key, the reconciler's static arm and the report's roll-up are all untouched. What
- * changed is only where the word came from.
- *
- * NOT THE (RETIRED) CHECK REGISTRY, AND THE DIFFERENCE IS THE SEAM THIS RETIRES. That registry
- * answered "which check is this runnable script handle", because a handle does not know what it
- * is for; the `@SCN`
- * is then resolved through the corpus, a second hop. A converted check is never discovered as a
- * handle — it is a scenario that ran, carrying its own tag line — so the `@SCN` is the KEY here
- * rather than something a lookup has to recover.
- *
- * PURE AND INJECTED — the rows arrive as data, read from the TARGET's own manifest at the app edge
- * (`specController.fitnessChecks`), the stance the retired `thresholdsOf` took. A target that
- * configures nothing raises nothing, so the reading is inert on a corpus
- * nobody has converted.
- */
-import { bareTerm } from "../lib/bareTerm.js";
-/**
- * One entry as a manifest spells it, read into the pair a lookup can use, or `null` where it names
- * nothing one can.
- *
- * BOTH TERMS ARE STORED BARE. A manifest written by hand will sooner or later spell an `@SCN` — and
- * a characteristic — the way a feature file does, and both lookups match bare; stripping once here
- * rather than at every call site is the stance the retired `thresholdsOf` took.
- *
- * A ROW NAMING NEITHER TERM IS DROPPED WHOLE, never half-read. The two terms make one claim
- * together — THIS scenario asserts THIS characteristic — so a row missing either says nothing a
- * lookup can act on, and there is no lenient reading that does not invent one of them.
- */
-function fitnessCheckOf(entry) {
-    // THE TWO STRING READS ARE THE WHOLE GUARD, and a shape test ahead of them would add no teeth: a
-    // string, a number, a list and a function all answer `undefined` here, so each is refused by the
-    // read that matters rather than by a clause restating it. The optional chain is what covers the
-    // two values a property read would throw on.
-    const named = entry;
-    if (typeof named?.scn !== "string" || typeof named.characteristic !== "string")
-        return null;
-    const scnId = bareTerm(named.scn);
-    const characteristic = bareTerm(named.characteristic);
-    if (scnId === "" || characteristic === "")
-        return null;
-    return [scnId, { characteristic }];
-}
-/**
- * Build the index from the rows a manifest holds.
- *
- * A LIST, NOT A BLOCK KEYED BY `@SCN`, and the shape is the row's own argument: a row is what a
- * check says about ITSELF — its `@SCN`, its characteristic, its command — so no one of those three
- * is promoted above the others by being the key somebody has to write it under. The `@SCN` becomes
- * the key HERE, where a lookup needs one.
- *
- * A MALFORMED ROW IS DROPPED, NOT TRUSTED AND NOT THROWN ON — the defensive stance the whole
- * `specController.*` family takes. Config is data from outside, and a reader that throws on a typo
- * turns one bad character into a run that produces no verdict at all, which is loud nowhere; a
- * dropped row leaves its scenario naming no characteristic, which the corpus reports.
- */
-export function fitnessChecksOf(entries) {
-    if (!Array.isArray(entries))
-        return new Map();
-    const index = new Map();
-    for (const entry of entries) {
-        const row = fitnessCheckOf(entry);
-        if (row !== null)
-            index.set(row[0], row[1]);
-    }
-    return index;
-}
-//# sourceMappingURL=fitnessChecks.js.map

package/dist/domain/fitnessChecks.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"fitnessChecks.js","sourceRoot":"","sources":["../../src/domain/fitnessChecks.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA4BG;AAEH,OAAO,EAAE,QAAQ,EAAE,MAAM,oBAAoB,CAAC;AAkB9C;;;;;;;;;;;GAWG;AACH,SAAS,cAAc,CAAC,KAAc;IACpC,iGAAiG;IACjG,iGAAiG;IACjG,gGAAgG;IAChG,6CAA6C;IAC7C,MAAM,KAAK,GAAG,KAAuE,CAAC;IACtF,IAAI,OAAO,KAAK,EAAE,GAAG,KAAK,QAAQ,IAAI,OAAO,KAAK,CAAC,cAAc,KAAK,QAAQ;QAAE,OAAO,IAAI,CAAC;IAC5F,MAAM,KAAK,GAAG,QAAQ,CAAC,KAAK,CAAC,GAAG,CAAC,CAAC;IAClC,MAAM,cAAc,GAAG,QAAQ,CAAC,KAAK,CAAC,cAAc,CAAC,CAAC;IACtD,IAAI,KAAK,KAAK,EAAE,IAAI,cAAc,KAAK,EAAE;QAAE,OAAO,IAAI,CAAC;IACvD,OAAO,CAAC,KAAK,EAAE,EAAE,cAAc,EAAE,CAAC,CAAC;AACrC,CAAC;AAED;;;;;;;;;;;;GAYG;AACH,MAAM,UAAU,eAAe,CAAC,OAAgB;IAC9C,IAAI,CAAC,KAAK,CAAC,OAAO,CAAC,OAAO,CAAC;QAAE,OAAO,IAAI,GAAG,EAAE,CAAC;IAC9C,MAAM,KAAK,GAAG,IAAI,GAAG,EAAwB,CAAC;IAC9C,KAAK,MAAM,KAAK,IAAI,OAA6B,EAAE,CAAC;QAClD,MAAM,GAAG,GAAG,cAAc,CAAC,KAAK,CAAC,CAAC;QAClC,IAAI,GAAG,KAAK,IAAI;YAAE,KAAK,CAAC,GAAG,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,GAAG,CAAC,CAAC,CAAC,CAAC,CAAC;IAC9C,CAAC;IACD,OAAO,KAAK,CAAC;AACf,CAAC"}