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

package/dist/render/staticChecks.d.ts

@@ -1,23 +1,3 @@
-/**
- * THE STATIC-CHECK CENSUS a run banked — the counts line under Summary views, and the corpus's
- * half-converted checks beside it.
- *
- * 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 3F-3353, when the
- * behavioural-runner cut beside it needed the room; `runVerdict.ts` is the precedent, moved for
- * exactly this reason. NOTHING about the section changed in the move: same emitter, same lines,
- * same omit-when-absent.
- */
 import type { RenderInput } from "../assemble/renderInput.js";
-/**
- * Static checks (@SCN-USG-001) — the STATIC-check evidence observation side under
- * Summary views, the mirror of `### Test volume` on the runtime axis. Renders the counts line
- * (`N static check(s) run, K uncited static check(s)`) alone — a pure counts summary, symmetric with
- * `### Test volume` (2.4). The named count is implicit (`running − uncited`), so it
- * is no longer printed. The per-guard member detail lives in the rows (named → each
- * scenario's `@lint` sub-row; no-evidence-obligation → the suspense row's `cites-no-scenario` credit items), so
- * no list renders here. Omitted only when no static-check census is threaded (the back-compat path).
- * The counts read off the report's materialised `summary.staticChecks`.
- */
 export declare const staticChecksSection: (report: RenderInput) => string[];
 //# sourceMappingURL=staticChecks.d.ts.map

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

@@ -1 +1 @@
-{"version":3,"file":"staticChecks.d.ts","sourceRoot":"","sources":["../../src/render/staticChecks.ts"],"names":[],"mappings":"AAAA;;;;;;;;;GASG;AAEH,OAAO,KAAK,EAAE,WAAW,EAAE,MAAM,4BAA4B,CAAC;AA+B9D;;;;;;;;;GASG;AACH,eAAO,MAAM,mBAAmB,GAAI,QAAQ,WAAW,KAAG,MAAM,EAyB/D,CAAC"}
+{"version":3,"file":"staticChecks.d.ts","sourceRoot":"","sources":["../../src/render/staticChecks.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,WAAW,EAAE,MAAM,4BAA4B,CAAC;AAE9D,eAAO,MAAM,mBAAmB,GAAI,QAAQ,WAAW,KAAG,MAAM,EAQ/D,CAAC"}

package/dist/render/staticChecks.js

@@ -1,69 +1,11 @@
-/**
- * THE STATIC-CHECK CENSUS a run banked — the counts line under Summary views, and the corpus's
- * half-converted checks beside it.
- *
- * 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 3F-3353, when the
- * behavioural-runner cut beside it needed the room; `runVerdict.ts` is the precedent, moved for
- * exactly this reason. NOTHING about the section changed in the move: same emitter, same lines,
- * same omit-when-absent.
- */
-/**
- * A BAR A CONFIGURED ROW STILL CARRIES (@SCN-LNT-035), named `fitnessChecks[<@SCN>].<key>` by the
- * resolver. Its line says something different from a retired top-level key's, because its
- * consequence is different: the row still reaches the books, credited by its own step's outcome;
- * only the number on it is unread.
- */
-const isRowBar = (key) => key.startsWith("fitnessChecks[");
-/**
- * THE RETIRED-KEY ACCOUNT (@SCN-USG-021) — one line per `specController.*` key this reader has
- * retired that the target's manifest still carries, naming the key and saying what became of it.
- *
- * THE LINE EXISTS BECAUSE THE ALTERNATIVE IS SILENCE, the same argument
- * `behaviouralRunners.ts`'s `unrecognisedKeyAccount` makes for a key the target INVENTED: a
- * consumer who wrote `checkRegistry` in good faith, when it was read, believes it still routes
- * their checks. Nothing reads it now — the entries it names reach no candidate and resolve no
- * citation — so the only remaining question is whether they get to find that out, and this is
- * the answer.
- */
-const retiredKeyAccount = (keys) => (keys ?? []).map((key) => `- specController.${key} — retired: ${isRowBar(key)
-    ? "this reader no longer reads a row's bar, and the row is credited by its step's outcome."
-    : "this reader no longer reads it, and none of its entries reach the books."}`);
-/**
- * Static checks (@SCN-USG-001) — the STATIC-check evidence observation side under
- * Summary views, the mirror of `### Test volume` on the runtime axis. Renders the counts line
- * (`N static check(s) run, K uncited static check(s)`) alone — a pure counts summary, symmetric with
- * `### Test volume` (2.4). The named count is implicit (`running − uncited`), so it
- * is no longer printed. The per-guard member detail lives in the rows (named → each
- * scenario's `@lint` sub-row; no-evidence-obligation → the suspense row's `cites-no-scenario` credit items), so
- * no list renders here. Omitted only when no static-check census is threaded (the back-compat path).
- * The counts read off the report's materialised `summary.staticChecks`.
- */
 export const staticChecksSection = (report) => {
-    // THE HALF-CONVERTED CHECKS (@SCN-LNT-020) render HERE, under the same heading, because they are
-    // the same class of half-entry as an uncited static check — something the run saw and nothing
-    // owed — read off the other side of the books. FACTS ONLY, count and ids: the reader is told what
-    // the corpus said about itself and left with the one remedy there is, which is to write the row.
-    // OMIT-WHEN-EMPTY, so an unconverted corpus renders byte-identically to before.
-    const { staticChecks: counts, unconfiguredFitnessScenarios: halfConverted = [] } = report.summary;
+    const { staticChecks: counts } = report.summary;
     if (!counts)
         return [];
-    // THE RETIRED-KEY ACCOUNT (@SCN-USG-021) renders HERE, under the same heading, because a
-    // retired key is a fact about the STATIC axis: every key this reader has retired so far named
-    // a route onto this axis's books, never the runtime one. OMIT-WHEN-EMPTY, the same as every
-    // account beside it.
-    const retired = retiredKeyAccount(report.summary.retiredKeys);
-    // A pure counts summary off `summary.staticChecks` (2.4) — symmetric with the
-    // runtime `### Test volume` line. There is no census section: the per-guard DETAIL lives in
-    // the rows (named → each scenario's `@lint` sub-row; the no-evidence-obligation static-checks surface
-    // as `cites-no-scenario` credit items on the `(no scenario)` suspense row). Only the running
-    // volume + the uncited count render here; the named count is implicit.
     return [
         "### Static checks", "",
         `${counts.runningStaticCheckCount} static check(s) run, ${counts.uncitedStaticCheckCount} uncited static check(s).`,
         "",
-        ...(halfConverted.length > 0 ? [`${halfConverted.length} @fitness scenario(s) no configured row names: ${halfConverted.join(", ")}.`, ""] : []),
-        ...(retired.length > 0 ? [...retired, ""] : []),
     ];
 };
 //# sourceMappingURL=staticChecks.js.map

package/dist/render/staticChecks.js.map

@@ -1 +1 @@
-{"version":3,"file":"staticChecks.js","sourceRoot":"","sources":["../../src/render/staticChecks.ts"],"names":[],"mappings":"AAAA;;;;;;;;;GASG;AAIH;;;;;GAKG;AACH,MAAM,QAAQ,GAAG,CAAC,GAAW,EAAW,EAAE,CAAC,GAAG,CAAC,UAAU,CAAC,gBAAgB,CAAC,CAAC;AAE5E;;;;;;;;;;GAUG;AACH,MAAM,iBAAiB,GAAG,CAAC,IAAmC,EAAY,EAAE,CAC1E,CAAC,IAAI,IAAI,EAAE,CAAC,CAAC,GAAG,CACd,CAAC,GAAG,EAAE,EAAE,CACN,oBAAoB,GAAG,eACrB,QAAQ,CAAC,GAAG,CAAC;IACX,CAAC,CAAC,yFAAyF;IAC3F,CAAC,CAAC,0EACN,EAAE,CACL,CAAC;AAEJ;;;;;;;;;GASG;AACH,MAAM,CAAC,MAAM,mBAAmB,GAAG,CAAC,MAAmB,EAAY,EAAE;IACnE,iGAAiG;IACjG,8FAA8F;IAC9F,kGAAkG;IAClG,iGAAiG;IACjG,gFAAgF;IAChF,MAAM,EAAE,YAAY,EAAE,MAAM,EAAE,4BAA4B,EAAE,aAAa,GAAG,EAAE,EAAE,GAAG,MAAM,CAAC,OAAO,CAAC;IAClG,IAAI,CAAC,MAAM;QAAE,OAAO,EAAE,CAAC;IACvB,yFAAyF;IACzF,8FAA8F;IAC9F,4FAA4F;IAC5F,qBAAqB;IACrB,MAAM,OAAO,GAAG,iBAAiB,CAAC,MAAM,CAAC,OAAO,CAAC,WAAW,CAAC,CAAC;IAC9D,8EAA8E;IAC9E,4FAA4F;IAC5F,sGAAsG;IACtG,6FAA6F;IAC7F,uEAAuE;IACvE,OAAO;QACL,mBAAmB,EAAE,EAAE;QACvB,GAAG,MAAM,CAAC,uBAAuB,yBAAyB,MAAM,CAAC,uBAAuB,2BAA2B;QACnH,EAAE;QACF,GAAG,CAAC,aAAa,CAAC,MAAM,GAAG,CAAC,CAAC,CAAC,CAAC,CAAC,GAAG,aAAa,CAAC,MAAM,kDAAkD,aAAa,CAAC,IAAI,CAAC,IAAI,CAAC,GAAG,EAAE,EAAE,CAAC,CAAC,CAAC,CAAC,EAAE,CAAC;QAC/I,GAAG,CAAC,OAAO,CAAC,MAAM,GAAG,CAAC,CAAC,CAAC,CAAC,CAAC,GAAG,OAAO,EAAE,EAAE,CAAC,CAAC,CAAC,CAAC,EAAE,CAAC;KAChD,CAAC;AACJ,CAAC,CAAC"}
+{"version":3,"file":"staticChecks.js","sourceRoot":"","sources":["../../src/render/staticChecks.ts"],"names":[],"mappings":"AAEA,MAAM,CAAC,MAAM,mBAAmB,GAAG,CAAC,MAAmB,EAAY,EAAE;IACnE,MAAM,EAAE,YAAY,EAAE,MAAM,EAAE,GAAG,MAAM,CAAC,OAAO,CAAC;IAChD,IAAI,CAAC,MAAM;QAAE,OAAO,EAAE,CAAC;IACvB,OAAO;QACL,mBAAmB,EAAE,EAAE;QACvB,GAAG,MAAM,CAAC,uBAAuB,yBAAyB,MAAM,CAAC,uBAAuB,2BAA2B;QACnH,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,51 +1,7 @@
-/**
- * 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.
- */
 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.
- */
 export const stepAccountingSection = (report) => {
     const accounting = report.summary.stepAccounting;
     if (accounting === undefined)

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":"AAGA,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,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"}

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;AAE9D,eAAO,MAAM,iBAAiB,GAAI,QAAQ,WAAW,KAAG,MAAM,EAkB7D,CAAC"}

package/dist/render/testVolume.js

@@ -1,42 +1,10 @@
-/**
- * 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).
- */
 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",
         "",

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;AAG7D,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,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"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@3f-consulting/spec-controller-core",
-  "version": "0.1.0-alpha.5",
+  "version": "0.1.0-alpha.50",
   "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"}