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

package/dist/domain/qualityCheckReconciliation.js

@@ -1,146 +1,43 @@
-/**
- * THE QUALITY CHECK RECONCILIATION — one reconciling item in the accounting frame: the
- * per-evidence-obligation line explaining why obligation and observation disagree. This module
- * co-locates the concept's type with its OWN behaviour — the outcome vocabulary, the canon
- * descriptions, and `reconcileEvidenceObligation`, the pure derivation that computes a single
- * obligation's outcome from the observed evidence (module, not class; the rule lives WITH the
- * concept, not in the reconcile orchestration that folds it).
- */
-import { isStaticCheckObservation, evidenceObligationPairKey, } from "./journal.js";
+import { isFitnessObservation, evidenceObligationPairKey, } from "./journal.js";
 import { QualityCheckFaultCode } from "./qualityCheckFault.js";
 import { QualityCheckReconciliationFault } from "./qualityCheckReconciliationFault.js";
-// evidence obligation AND no citing evidence observation) — the ONE degenerate Quality Check Reconciliation it
-// posts, blank on both sides (label: "Evidence Obligation and Evidence Observation are both
-// missing — the Scenario is untagged and uncited"). Detected by the reconciler emitting NOTHING either way (NOT a
-// hard evidenceObligations.length === 0 map — a zero-evidence obligation scenario cited by a stray
-// credit is `no-evidence-obligation`, @SCN-LDG-010). Retires the zero-evidence-scenario warning (@SCN-WRN-001
-// Update): the zero-evidence scenario is now this out-of-balance row, never a separate axis.
-// The verdict stays two-valued (out-of-balance VIA this reconciling item, never a third verdict).
-/**
- * The canon description for each reconciling-item Outcome — the human-readable gloss a
- * markdown reader needs (the bare handle means nothing in a CI log). SINGLE SOURCE: the
- * markdown renderer renders this description in place of the handle EVERYWHERE an outcome
- * surfaces to a reader — the Evidence-reconciliation summary's `↳` decomposition rows, the
- * per-scenario reconciling-items list, and the lint-obligation table's Outcome column. The
- * JSON keeps the bare handle (the machine axis; a programmatic consumer uses it).
- *
- * Keyed by EVERY `Outcome` (a `Record<Outcome, …>`), so a new outcome cannot be added to the
- * union without a description here — the description can never silently diverge from the
- * outcome it names (the drift class this project has been burned by: the census, the views).
- * These phrasings ARE the original canon — later abbreviated to the handles; 3F-1626 restores
- * them. `satisfied` (the balanced outcome, excluded from the out-of-balance decomposition)
- * carries one for totality's sake.
- *
- * ⚠ KEY ORDER IS LOAD-BEARING (3F-1806). `OUT_OF_BALANCE_OUTCOMES` is DERIVED from these keys,
- * and the renderer walks that list to emit the decomposition rows — so this map's key order IS
- * the report's row order (`missing` first: the headline cause, the one carrying the bare-level
- * split as Detail). Reordering these keys is a REPORT CHANGE, not a cosmetic tidy. The order
- * follows canon, grouped by reconciling-item shape: a DEBIT block (missing, failing, watermelon,
- * no-scn-code), a CREDIT block (cites-unknown-scenario, cites-no-scenario, no-evidence-obligation), then
- * NEITHER (broken, both-missing). @SCN-RPT-019 now pins this SEQUENCE against the rendered `↳`
- * rows (3F-1926), so a reorder reds — the exhaustiveness guard alone proved MEMBERSHIP, not
- * order, and used not to catch one (which is how the order drifted before it was pinned).
- */
 export const OUTCOME_DESCRIPTION = {
     satisfied: "Evidence Observation satisfies its Evidence Obligation",
     missing: "Evidence Observation is missing",
     failing: "Evidence Observation is failing",
     watermelon: "Evidence Observation is passing but fabricated",
-    // The DEBIT TWIN of `cites-no-scenario` (@SCN-LDG-021): same missing LINK, opposite side — the
-    // scenario is real and ORDINARY, but carries no @SCN for an observation to link to.
     "no-scn-code": "Evidence Obligation has no @SCN code for an Evidence Observation to link to",
+    "duplicate-scn-code": "Evidence Obligation's @SCN code is carried by another Scenario",
     "cites-unknown-scenario": "Evidence Observation cites an unknown Scenario",
     "cites-no-scenario": "Evidence Observation cites no Scenario",
-    // CANON VERBATIM — double-entry-manifesto.md:42, the Outcome column. The gloss is the outcome
-    // SENTENCE, canon's checkably-true half where the handle is only a label, so it states the
-    // credit-side fact rather than echoing the handle's root. 3F-2308 landed the sentence; 3F-2300
-    // then renamed the HANDLE to match it — the old one was the last survivor of a word canon has
-    // retired — moving the emitted `byOutcome` key and every @SCN-LDG scenario that reads it.
     "no-evidence-obligation": "Evidence Observation cites a Scenario with no matching Evidence Obligation",
-    // GENERIC over its producers (@SCN-LDG-017 + @SCN-LDG-019, 3F-1654): `broken` has two instances
-    // — a vitest suite that failed to COLLECT, and a cucumber step two or more step definitions
-    // match, which therefore never ran. An ambiguous step is neither a "suite" nor a "collection
-    // error", so the gloss names what BOTH have in common: the proof exists and did not run.
-    // REMEDY-NEUTRAL by design: what broke is equally a missing dependency, a syntax error, a bad
-    // import, a top-level throw, or two colliding step definitions — the gloss names the FACT, not a
-    // guessed cure. Contrast `missing`, whose remedy is "write the test": conflating the two is
-    // exactly the false-`missing` this outcome retires.
     broken: "Evidence Observation ATTEMPT errored before it could cite a Scenario (the proving suite failed to collect; behaviour never exercised)",
     "both-missing": "Evidence Obligation and Evidence Observation are both missing — the Scenario is untagged and uncited",
 };
-/**
- * The out-of-balance reconciling-item outcomes, in report reading order — every `Outcome`
- * except `satisfied` (the BALANCED outcome, not part of the OUT-of-balance decomposition).
- * The renderer walks this to emit the summary's `↳` leaf rows (@SCN-RPT-019), each reconciling
- * to the out-of-balance total exactly once (a FLAT list: the old debit/credit/neither grouping
- * emitted a `↳ <group>-side` subtotal AND its leaves at the same indent, so a naive column-sum
- * double-counted — the live 170 vs 85).
- *
- * DERIVED from the type-forced `OUTCOME_DESCRIPTION`, never hand-listed (3F-1806). It was a
- * hand-maintained `readonly Outcome[]` in the renderer, which accepted a missing union member
- * SILENTLY: `broken` (@SCN-LDG-017) joined the union, tallied into `byOutcome`, compiled clean,
- * and would have been omitted from the table. Deriving the keys makes that omission IMPOSSIBLE
- * rather than merely CAUGHT — a new `Outcome` cannot compile without a description, and the
- * moment it has one it renders a leaf row with no change to the renderer.
- *
- * Lives in the model, not the renderer: which outcomes are out-of-balance is the model's rule,
- * not a presentation choice (`entity-owns-its-behaviour`). The @SCN-RPT-019 guard remains as the
- * end-to-end backstop — it renders real markdown and reads the rows back, deriving its
- * expectation from its OWN type-forced record (`double-entry`, not a re-read of this source).
- */
 export const OUT_OF_BALANCE_OUTCOMES = Object.keys(OUTCOME_DESCRIPTION).filter((outcome) => outcome !== "satisfied");
-/**
- * THE CANON OUTCOME-SIDE PROFILE (@SCN-LDG-030, 3F-2016) — the (outcome → side-presence) table
- * transcribed from canon (`double-entry-manifesto.md` lines 35-44), keyed by EVERY `Outcome` (a
- * `Record<Outcome, …>`), so a new outcome cannot join the union without STATING its side
- * profile here — the type-forced totality that makes this map the SINGLE SOURCE the invariant is
- * checked against (mirroring `OUTCOME_DESCRIPTION`).
- *
- * `obligation`/`observation` are `"Exists" | "None"` — whether a canon-correct reconciling item
- * of that outcome CARRIES the debit (evidence obligation) and the credit (evidence observation)
- * side respectively. NOT a naive function of side-presence: `missing` and `no-scn-code` share
- * (Exists, None); the three credit outcomes (`cites-unknown-scenario` / `cites-no-scenario` /
- * `no-evidence-obligation`) share (None, Exists). So the invariant `makeQualityCheckReconciliation` enforces
- * is (outcome, side-presence) CONSISTENCY against this row, never a derivation of outcome FROM the
- * sides.
- */
 export const OUTCOME_SIDE_PROFILE = {
     satisfied: { obligation: "Exists", observation: "Exists" },
     missing: { obligation: "Exists", observation: "None" },
     failing: { obligation: "Exists", observation: "Exists" },
     watermelon: { obligation: "Exists", observation: "Exists" },
     "no-scn-code": { obligation: "Exists", observation: "None" },
+    "duplicate-scn-code": { obligation: "Exists", observation: "None" },
     "cites-unknown-scenario": { obligation: "None", observation: "Exists" },
     "cites-no-scenario": { obligation: "None", observation: "Exists" },
     "no-evidence-obligation": { obligation: "None", observation: "Exists" },
     broken: { obligation: "None", observation: "None" },
     "both-missing": { obligation: "None", observation: "None" },
 };
-/**
- * THE SMART CONSTRUCTOR (@SCN-LDG-030, 3F-2016) — the ONLY way to mint a
- * `QualityCheckReconciliation`. It takes `outcome` as GIVEN (a consistency check, NOT a
- * derivation — `missing`/`no-scn-code` share a profile, so the outcome cannot be recovered from
- * side-presence alone), looks up the canon row in `OUTCOME_SIDE_PROFILE`, and THROWS if the
- * carried sides disagree with it: a divergent (outcome, side-presence) pair — the watermelon class
- * this tool exists to catch, in its own output — is UNCONSTRUCTIBLE.
- *
- * Returns `fields` UNCHANGED (cast to the branded type): the producer's own key order is preserved
- * verbatim, so every unchanged row stays byte-identical (no object is reconstructed).
- */
 export function makeQualityCheckReconciliation(fields) {
     const profile = OUTCOME_SIDE_PROFILE[fields.outcome];
-    // The DEBIT-side check: the obligation is carried IFF canon says it Exists for this outcome.
     if ((fields.evidenceObligation !== undefined) !== (profile.obligation === "Exists")) {
         throw new QualityCheckReconciliationFault({
             code: QualityCheckFaultCode.ObligationSideDivergesFromCanon,
             outcome: fields.outcome,
             required: profile.obligation,
-            // The ternary STAYS in code (@SCN-MSG-001): it is parameter logic, not prose, so mutation
-            // still reaches it — and now an assertion does too, which is what kills it.
             actual: fields.evidenceObligation !== undefined ? "Exists" : "None",
         });
     }
-    // The CREDIT-side check: the observation is carried IFF canon says it Exists for this outcome.
     if ((fields.evidenceObservation !== undefined) !== (profile.observation === "Exists")) {
         throw new QualityCheckReconciliationFault({
             code: QualityCheckFaultCode.ObservationSideDivergesFromCanon,
@@ -151,336 +48,82 @@ export function makeQualityCheckReconciliation(fields) {
     }
     return fields;
 }
-/**
- * The where-to-fix a credit carries, for the credit-side items that now see BOTH axes.
- *
- * A static-check observation has no `locator` and never will: it is read from a target's CI
- * config and manifest, not from a test file, so there is no file to send the reader to beyond the
- * check's own handle — which the item already carries. Reading the field off the union rather
- * than off `RuntimeEvidenceObservation` is what let those items widen to the static axis at all
- * (@SCN-LNT-001, since a citing static credit can now post to a real or a phantom row).
- */
 function locatorOf(observation) {
-    return observation.qualityCheck === "lint" ? undefined : observation.locator;
+    return observation.qualityCheck === "fitness" ? undefined : observation.locator;
 }
-/**
- * The static-check observation answering THIS scenario's `lint` obligation — ONE ROUTE, the
- * citation, on both of its terms (@SCN-LNT-001).
- *
- * THE CREDIT CITES, and it is the same rule the runtime arm applies: an observation citing this
- * scenario's `@SCN` answers its obligation. That is what lets a FITNESS obligation reconcile at
- * all — its `staticCheck` is the BARE CHECK TAG the scenario carries (`traceability`), while the
- * run knows only the runnable handle (`lint:feature-codes`), so nothing matches by name and
- * nothing ever could. The citation is the seam that already crossed between them.
- *
- * AND THE CITATION IS NOT AN ADDRESS ON ITS OWN (@SCN-LNT-012). The `@SCN` says which ROW the
- * credit belongs to; it does not say which of that row's obligations it ANSWERS. A stepless
- * scenario may carry more than one bare check tag, so a row can raise two fitness obligations and
- * be cited by two runs — and matching on the `@SCN` alone hands the first credit found to both,
- * silently absorbing the second. Measured: a genuine `typecheck` watermelon read `satisfied` off
- * `lint:complexity`'s credit, and the row read `balanced`. So the observation's own BARE CHECK TAG
- * is compared too, and it is the observation's `checkTag` — NOT its `staticCheck`. `staticCheck` is
- * the runnable handle, a different vocabulary from the obligation's bare tag, and comparing those
- * two is name-match in a new spelling: it agrees only where the words coincide, which is
- * `typecheck`, the one unprefixed check. `checkTag` is what the seam resolved, so the comparison is
- * like with like.
- *
- * NAME-MATCH IS GONE FROM HERE TOO (3F-2625). A by-handle fallback stood second, taken only for a
- * run that cited NOTHING. 3F-2590 retired the by-name route and removed `posting.ts`'s arm, but
- * never touched this file, so this half outlived the retirement it was written to announce — and
- * it was LIVE, not dead code. It compared an uncited observation's RUNNABLE handle against the
- * obligation's BARE tag, which differ for every prefixed check (`lint:feature-codes` vs
- * `traceability`) and are the SAME WORD for a prefix-less one (`typecheck`). On that check an
- * uncited credit both posted to suspense AND answered this obligation: the row read `satisfied` on
- * evidence that cited nothing, and one observation became the credit side of two items on two rows
- * — the exactly-one-posting claim broken by the reconciler rather than by the posting rule.
- *
- * SO A RUN THAT CITES NOTHING NOW ANSWERS NOTHING. It posts to SUSPENSE (`postingOf`), where a
- * check nobody named is meant to surface, and the obligation naming that check reads `missing` —
- * an honest pair, both halves loud. Pinned by plant, not by the absence of a symbol:
- * `uncitedFitnessCredit.test.ts`, @SCN-USG-001.
- *
- * ONE WORD IS PASSED, NOT TWO, and it is the BARE CHECK TAG. Every surviving `lint` obligation
- * names one: the fitness rule raises it from the tag its stepless scenario carries, and the retired
- * `@lint=<handle>` form raises nothing at all (@SCN-LNT-007). The obligation's word is now matched
- * ONLY against the observation's own `checkTag` — never against its `staticCheck`, which is the
- * runnable handle and a different vocabulary. That comparison was the deleted arm's, and it is what
- * made the arm name-match.
- *
- * Lives beside `reconcileEvidenceObligation` rather than inside it: which observation answers an
- * obligation is one idea with a name, and the outcome mapping that follows it is another.
- */
-function staticCheckObservationFor(scnId, checkTag, evidenceObservations) {
-    return evidenceObservations.find((o) => isStaticCheckObservation(o) &&
-        // THE FAIL-SAFE, THE SAME ONE THE RUNTIME MATCH BELOW KEEPS (@SCN-LNT-026). A proof that
-        // never ran can neither discharge an obligation nor fail it, so a broken credit is excluded
-        // from the match entirely and its obligation reconciles `missing` by absence — while the
-        // credit itself posts to suspense, where the reader is told what broke. The exclusion is
-        // STRUCTURAL rather than incidental: this observation carries its `scnId` and its
-        // `checkTag`, exactly as cucumber's broken observation carries the `@SCN` its scenario
-        // cited, so nothing but this clause keeps it out.
+const CREDIT_PRECEDENCE = ["failing", "watermelon", "satisfied"];
+function answerOf(matches, outcomeOf) {
+    for (const outcome of CREDIT_PRECEDENCE) {
+        const credit = matches.find((match) => outcomeOf(match) === outcome);
+        if (credit)
+            return { outcome, credit };
+    }
+    return { outcome: "missing" };
+}
+function fitnessCreditsCiting(scnId, evidenceObservations) {
+    return evidenceObservations.filter((o) => isFitnessObservation(o) &&
         o.broken !== true &&
-        o.scnId === scnId &&
-        o.checkTag === checkTag);
+        o.scnId === scnId);
 }
-/**
- * Reconcile one STATIC-CHECK fitness obligation — the read-over-the-source arm, the fitness
- * axis's one route since its measured twin left (3F-3516). Three mappings on the static check
- * evidence observation:
- *   - wired into CI over the real source → satisfied.
- *   - exists (a package.json script) but NOT wired → THE WATERMELON: green on the surface, red
- *     within — a static check that guards nothing.
- *   - absent (no package.json script) → missing: a required ledger entry never recorded, GENUINELY
- *     DIFFERENT from the watermelon.
- *
- * NAMED FOR WHAT IT HOLDS. Every surviving fitness obligation carries the BARE CHECK TAG its
- * stepless scenario spells (`complexity`), never the runnable handle that invokes it
- * (`lint:complexity`) — the retired `@lint=<handle>` form raises nothing (@SCN-LNT-007). The old
- * name `guard` read as the handle and was the tag, which is exactly the confusion that let an
- * observation's handle be compared against it.
- */
-function reconcileStaticObligation(scnId, req, evidenceObservations) {
-    const checkTag = req.staticCheck; // present by construction for a fitness evidence obligation.
-    const obs = staticCheckObservationFor(scnId, checkTag, evidenceObservations);
-    let outcome;
-    // THE CHECK'S OWN VERDICT FIRST, WHERE THE OBSERVATION CARRIED ONE (@SCN-LNT-028), and the order
-    // is the rule rather than a convenience. `exists` and `enforcedOverRealSource` say a check is
-    // there and is wired, which is exactly what a check that ran and found violations also is — so
-    // asked in the other order the wiring facts would answer `satisfied` over a red and the verdict
-    // would never be reached. It is the same arrangement `broken` takes one function up, for the
-    // same reason: the fact that reds is the one asked about first.
-    if (obs?.status === "failed") {
-        outcome = "failing";
-    }
-    else if (obs && obs.enforcedOverRealSource) {
-        outcome = "satisfied";
-    }
-    else if (obs?.exists) {
-        outcome = "watermelon";
-    }
-    else {
-        outcome = "missing";
-    }
-    // The CREDIT side (@SCN-LDG-027/@SCN-LDG-028): the matched static-check observation, carried
-    // ONLY when it is a REAL observation — `exists:true` (the two-sided `satisfied` / `watermelon`).
-    // A guard absent from both package.json and CI is FOUND as the negative fact
-    // `{exists:false}` — an ABSENCE, not an observed piece of evidence — so `missing` carries
-    // NOTHING on the credit side (Obligation Exists, Observation None; double-entry-manifesto line
-    // 36), uniform with the runtime `missing` path. `obs?.exists` (not `obs`) is the discriminator:
-    // `find` locating the absent-guard record must not be mistaken for an observation existing.
+function staticOutcomeOf(credit) {
+    if (credit.status === "failed")
+        return "failing";
+    if (credit.enforcedOverRealSource)
+        return "satisfied";
+    return credit.exists ? "watermelon" : undefined;
+}
+function reconcileStaticObligation(scnId, obligation, evidenceObservations) {
+    const { outcome, credit } = answerOf(fitnessCreditsCiting(scnId, evidenceObservations), staticOutcomeOf);
     return makeQualityCheckReconciliation({
-        qualityCheck: "lint",
-        staticCheck: checkTag,
+        qualityCheck: "fitness",
         outcome,
-        evidenceObligation: req,
-        ...(obs?.exists ? { evidenceObservation: obs } : {}),
+        evidenceObligation: obligation,
+        ...(credit ? { evidenceObservation: credit } : {}),
     });
 }
-/**
- * Reconcile one evidence obligation against the observed evidence, keyed on the
- * flat `qualityCheck`. `qualityCheck === "lint"` is the watermelon
- * discriminator: it routes to the STATIC-check mapping;
- * every other value routes to the RUNTIME-result mapping.
- */
-export function reconcileEvidenceObligation(scnId, req, evidenceObservations) {
-    if (req.qualityCheck === "lint") {
-        return reconcileStaticObligation(scnId, req, evidenceObservations);
-    }
-    // A runtime evidence obligation — matched by (scnId, quality-check) among the runtime
-    // evidence observations (a static check evidence observation carries qualityCheck "lint" and no scnId, so it
-    // never matches here). present+pass → satisfied; present+fail → failing;
-    // absent → missing (a required ledger entry never recorded).
-    //
-    // THE FAIL-SAFE (@SCN-LDG-017, operator-mandated): `broken` is checked BEFORE `status`. A
-    // broken observation — one whose PROOF NEVER RAN — is excluded from the match entirely, so it
-    // can NEVER reconcile as `satisfied` or `failing`: a proof that never ran can neither discharge
-    // an obligation nor fail it. The obligation then finds no match and reconciles `missing` —
-    // honest at its own resolution (no evidence citing it arrived); the broken evidence itself
-    // posts to the SUSPENSE row below, where the reader is sent to fix the harness. The exclusion
-    // is structural rather than incidental: `broken` rides an OPTIONAL
-    // FLAG on RuntimeEvidenceObservation, so a broken credit CAN carry an scnId and a status — the
-    // guard is what makes the fail-safe hold whatever it carries.
-    const match = evidenceObservations.find((o) => 
-    // TWO SURVIVING MUTANTS LIVE ON THIS CLAUSE, KEPT DELIBERATELY (3F-2237). Stryker has no
-    // equivalence detection, so a mutant no test can kill is indistinguishable from one nobody
-    // has written yet. The argument is recorded here because a reader meeting this line has no
-    // other way to recover that the clause is redundant ON PURPOSE.
-    //
-    // `ConditionalExpression` (this clause → `true`) is redundant FOR ANY INPUT WHATSOEVER.
-    // The arm is reached only when `req.qualityCheck !== "lint"` (the fitness fork above
-    // returns first), and `o.qualityCheck === req.qualityCheck` two lines down entails
-    // `o.qualityCheck !== "lint"` for every `o` that survives the chain. The redundancy is
-    // LOGICAL, not type-based — no input, however constructed, separates mutant from original.
-    //
-    // `StringLiteral` (`"lint"` → `""`) rests on a NARROWER argument, and the difference is the
-    // point. Mutated, the clause reads `o.qualityCheck !== ""`. On the `"lint"` side the logical
-    // argument above still covers it — a `"lint"` observation can never satisfy the third clause
-    // below the fitness fork. The `""` side IS separable: an evidence obligation and a credit
-    // both carrying `""` reconcile `satisfied` here and `missing` under the mutant. But that
-    // input is out of domain — no member of `QualityCheck` spells `""`, and nothing in this
-    // package emits it (every producer is a literal, a closed alternation, or a lookup hit), so
-    // it is reachable only by casting PAST the parameter type. 3F-2879 drew exactly that line: a
-    // shape admitted by width subtyping WITH NO CAST is a real published-surface input and kills
-    // (it killed `locatorOf`, and `fitnessCheckTagOf` with it); an out-of-domain value for a
-    // typed field is not one, and pinning behaviour for it would assert a case no reader of this
-    // model can reach.
-    //
-    // Kept because it is load-bearing for the compiler — delete it and `pnpm typecheck` reds
-    // with `TS2339: Property 'broken' does not exist on type 'EvidenceObservation'`, the `"lint"`
-    // observations never having been narrowed away — and because it states the fail-safe above
-    // at the point the reader meets it.
-    o.qualityCheck !== "lint" &&
-        o.broken !== true &&
-        o.qualityCheck === req.qualityCheck &&
-        o.scnId === scnId);
-    let outcome;
-    if (!match) {
-        outcome = "missing";
-    }
-    else if (match.status === "passed") {
-        outcome = "satisfied";
-    }
-    else {
-        outcome = "failing";
+function runtimeOutcomeOf(credit) {
+    return credit.status === "passed" ? "satisfied" : "failing";
+}
+export function reconcileEvidenceObligation(scnId, obligation, evidenceObservations) {
+    if (obligation.qualityCheck === "fitness") {
+        return reconcileStaticObligation(scnId, obligation, evidenceObservations);
     }
-    // The CREDIT side (@SCN-LDG-027): the matched runtime observation, present for the two-sided
-    // outcomes `satisfied` / `failing` and absent for `missing` — the conditional spread keeps
-    // `missing` observation-free (obligation Exists, observation None).
+    const { outcome, credit } = answerOf(evidenceObservations.filter((o) => o.broken !== true &&
+        o.qualityCheck === obligation.qualityCheck &&
+        o.scnId === scnId), runtimeOutcomeOf);
     return makeQualityCheckReconciliation({
-        qualityCheck: req.qualityCheck,
+        qualityCheck: obligation.qualityCheck,
         outcome,
-        evidenceObligation: req,
-        ...(match ? { evidenceObservation: match } : {}),
+        evidenceObligation: obligation,
+        ...(credit ? { evidenceObservation: credit } : {}),
     });
 }
-// ---------------------------------------------------------------------------
-// THE CREDIT-SIDE AND DEGENERATE ITEM RULES (3F-2204) — co-located here beside
-// `reconcileEvidenceObligation` because they answer the same question it does: what outcome does
-// an entry reconcile to, and which sides does that item carry? `reconcileEvidenceObligation`
-// answers it for a DEBIT matched against the observed evidence; these answer it for the entries
-// that match no obligation at all (the credit-side outcomes) and for the two degenerate rows
-// (no-scn-code, both-missing).
-//
-// They were inline `.map()` bodies in the `reconcile` fold. Posting-destination left in 3F-2202;
-// this is the sibling class — WHAT an entry reconciles to, as opposed to WHERE it lands. Both are
-// domain rules, so neither belongs in the orchestration. `reconcile` keeps the walk and builds the
-// rows; the outcomes are asked for.
-// ---------------------------------------------------------------------------
-/**
- * What a FITNESS credit calls the check that ran — its bare tag where it has one, else the runnable
- * handle that invoked it. `undefined` for a runtime credit, which names a test file instead.
- *
- * The bare tag is preferred because a reconciling item's `staticCheck` holds the bare tag on the
- * debit side, so a reader comparing "the row names complexity" against "a credit for typecheck
- * arrived" is comparing like with like. The handle is a fallback rather than a second choice of
- * vocabulary: a credit with no tag cites nothing and posts to suspense, so it should not reach a
- * real row at all — but if one ever does, naming its handle beats naming nothing.
- */
-function fitnessCheckNameOf(observation) {
-    return isStaticCheckObservation(observation)
-        ? (observation.checkTag ?? observation.staticCheck)
-        : fitnessCheckTagOf(observation);
+function fitnessFunctionNameOf(observation) {
+    return isFitnessObservation(observation)
+        ? observation.fitnessFunction
+        : undefined;
 }
-/**
- * A fitness credit's BARE CHECK TAG, or `undefined` — the term the pair key compares.
- *
- * Deliberately NO handle fallback, unlike `fitnessCheckNameOf` above. The key is matched against an
- * obligation's `staticCheck`, which since the bare-tag unification always holds the BARE tag; a
- * handle substituted here would compare `lint:typecheck` against `typecheck` and miss — name-match
- * in a new spelling. A credit with no tag keys distinctly from every tagged one, which is what
- * stops it matching by having nothing to compare.
- */
-function fitnessCheckTagOf(observation) {
-    return isStaticCheckObservation(observation) ? observation.checkTag : undefined;
-}
-/**
- * The NO-EVIDENCE-OBLIGATION items on a real scenario's row (@SCN-LDG-008) — one per credit citing THIS
- * scenario at a quality-check it never named. The credit posts to a real row against NO
- * evidence obligation, so the item is CREDIT-ONLY (no obligation is in scope).
- *
- * The pair-check is what distinguishes no-evidence-obligation from a matched credit: a credit at a NAMED
- * `(scnId, quality-check)` pair reconciles satisfied/failing via `reconcileEvidenceObligation` and
- * is NOT re-listed here. `evidenceObligationPairs` is the journal's rule (`evidenceObligationPairsOf`),
- * built once and shared — which is what makes a credit citing a PENDING pair land here rather than
- * nowhere (3F-1858: a pending obligation names nothing, so such a credit is no-evidence-obligation exactly
- * as when nothing was raised at all, and the run that used to read balanced over it now fails).
- */
 export function noEvidenceObligationReconciliationsOf(scnId, postedCredits, evidenceObligationPairs) {
     return postedCredits
-        .filter((o) => 
-    // THE CREDIT'S OWN CHECK TAG, not the axis (@SCN-LNT-013). Keyed on `lint` alone, a row's
-    // obligation for one check answered a credit for any other — so a credit the debit match had
-    // already, correctly, refused by tag was ALSO excluded here and reconciled to nothing.
-    // Composed by the model's own `evidenceObligationPairKey`, the same spelling the set is
-    // built with: a key built one way and read another is the same bug in a new spelling.
-    !evidenceObligationPairs.has(evidenceObligationPairKey(scnId, o.qualityCheck, fitnessCheckTagOf(o))))
+        .filter((o) => !evidenceObligationPairs.has(evidenceObligationPairKey(scnId, o.qualityCheck)))
         .map((o) => makeQualityCheckReconciliation({
         qualityCheck: o.qualityCheck,
         outcome: "no-evidence-obligation",
-        // THE CHECK THAT RAN (@SCN-LNT-013) — a fitness credit's whole where-to-fix, since it has no
-        // test file to be sent to. Without it the item reads "lint: no evidence obligation" and a
-        // reader learns only that SOME check arrived uninvited, on a row that may name several.
-        // Preferring the BARE TAG over the runnable handle is what lets it be read against the row's
-        // own obligations, which are named by the bare tag — like compared with like. The handle is
-        // the fallback for a credit that carries no tag, so the item still names something.
-        ...(fitnessCheckNameOf(o) !== undefined ? { staticCheck: fitnessCheckNameOf(o) } : {}),
-        // The CREDIT side (@SCN-LDG-027): the citing observation this item reconciles.
+        ...(fitnessFunctionNameOf(o) !== undefined ? { fitnessFunction: fitnessFunctionNameOf(o) } : {}),
         evidenceObservation: o,
         ...(locatorOf(o) !== undefined ? { locator: locatorOf(o) } : {}),
     }));
 }
-/**
- * The items on a PHANTOM row (@SCN-LDG-006) — one `cites-unknown-scenario` per credit citing an
- * `@SCN` no scenario carries, in citation order. CREDIT-ONLY: a phantom row is minted BY a credit,
- * so nothing can ever have been named of it, and no obligation is in scope.
- *
- * THE WHERE-TO-FIX IS THE WHOLE OF WHAT THIS ITEM CAN OFFER, which is why both halves ride through
- * (ruling Q5): a phantom item has no obligation to point a reader at instead. A runtime credit
- * carries its locator (the test file that cited); a FITNESS credit carries the CHECK THAT RAN —
- * it is read from a target's config, not from a test file, so it has no locator and the handle is
- * all there is. That half became reachable when the fitness axis started citing (@SCN-LNT-009);
- * the suspense arm below already carried it, and the two unmatched-credit destinations must not
- * tell a reader different amounts about the same class of fault.
- */
 export function citesUnknownScenarioReconciliationsOf(credits) {
     return credits.map((o) => makeQualityCheckReconciliation({
         qualityCheck: o.qualityCheck,
-        // THE CHECK THAT RAN is the fitness credit's whole where-to-fix — it has no test file to be
-        // sent to. For a static run that is its runnable handle.
-        ...(isStaticCheckObservation(o) ? { staticCheck: o.staticCheck } : {}),
+        ...(isFitnessObservation(o) ? { fitnessFunction: o.fitnessFunction } : {}),
         outcome: "cites-unknown-scenario",
         evidenceObservation: o,
         ...(locatorOf(o) !== undefined ? { locator: locatorOf(o) } : {}),
     }));
 }
-/**
- * The items on the SUSPENSE row (@SCN-LDG-007) — every entry that names no scenario at all,
- * in the ONE order canon fixes.
- *
- * THE ORDER IS THE RULE, not an accident of assembly. `broken` comes FIRST because a broken run's
- * other suspense items are downstream noise: the reader must be sent to the harness before being
- * asked to read anything the harness failed to produce.
- *
- * THE SPLIT (@SCN-LDG-017) is why `broken` and `cites-no-scenario` are separate arms rather than
- * one map over "everything uncited". Both land here because they name no scenario, but they are
- * distinguished by errored-vs-completed and their remedies differ: a `cites-no-scenario` test RAN
- * and forgot its citation (add the `@SCN`); a `broken` suite never ran at all (fix the harness).
- * Folding the second into the first would hide a collection failure behind the wrong cure.
- *
- * The three arms carry different payloads, each for a stated reason:
- *   - `broken` carries its WHERE-to-fix (locator) and its WHAT-broke (the runner's message), and
- *     NO `evidenceObservation` — a proof that never ran is not an observed piece of evidence.
- *   - an uncited runtime credit carries the observation it reconciles, plus its locator.
- *   - a no-evidence-obligation static check carries its handle and its observation; it has no locator (a
- *     static check is read from config, not from a test file).
- *
- * THE BROKEN STREAM TAKES EITHER AXIS SINCE @SCN-LNT-026, AND THE ARM NEEDED NO BRANCH FOR IT.
- * A converted static check that did not run carries the same two payload halves under the same
- * two names, so the map reads what the observation holds exactly as it does for a vitest suite
- * that failed to collect. What differs is only the `qualityCheck` the item then carries — `lint`
- * rather than a runtime tier — which is read off the observation and not decided here.
- */
-export function suspenseReconciliationsOf(brokenEvidence, uncited, noEvidenceObligationGuards) {
+export function suspenseReconciliationsOf(brokenEvidence, uncited, noEvidenceObligationFitnessFunctions) {
     return [
         ...brokenEvidence.map((o) => makeQualityCheckReconciliation({
             qualityCheck: o.qualityCheck,
@@ -494,73 +137,30 @@ export function suspenseReconciliationsOf(brokenEvidence, uncited, noEvidenceObl
             evidenceObservation: o,
             ...(o.locator !== undefined ? { locator: o.locator } : {}),
         })),
-        ...noEvidenceObligationGuards.map((o) => makeQualityCheckReconciliation({
-            qualityCheck: "lint",
-            // The check that ran: a static run knows its runnable handle.
-            staticCheck: o.staticCheck,
+        ...noEvidenceObligationFitnessFunctions.map((o) => makeQualityCheckReconciliation({
+            qualityCheck: "fitness",
+            fitnessFunction: o.fitnessFunction,
             outcome: "cites-no-scenario",
             evidenceObservation: o,
         })),
     ];
 }
-/**
- * The item on an UNTAGGED scenario's row (@SCN-LDG-021) — the DEBIT twin of `cites-no-scenario`
- * (same missing link, opposite side; suspense stays credit-only).
- *
- * A scenario carrying no `@SCN` is REAL and ORDINARY — cucumber runs it — but its obligation has no
- * CODE for an observation to link to, so it could reconcile NOTHING: not satisfied, not failing,
- * not even `missing`, because an obligation never RAISED cannot be ABSENT. Without this item it
- * contributed nothing to the verdict and the run went green over work nothing proves.
- *
- * It carries NO `qualityCheck`: with no code, no observation can link at ANY tier, so the missing
- * link is SCENARIO-scope, not tier-scope (the shape `both-missing` also uses). The synthesised
- * scenario-scope obligation — an empty `{}` — lives ONLY on this item; the row's own
- * `evidenceObligations` stays empty (canon citation: double-entry-manifesto line 39, Obligation
- * Exists / Observation None).
- */
 export function noScnCodeReconciliations() {
     return [makeQualityCheckReconciliation({ outcome: "no-scn-code", evidenceObligation: {} })];
 }
-/**
- * The degenerate BOTH-MISSING item (@SCN-LDG-009) — the NEITHER-side outcome, blank on both sides:
- * no `qualityCheck` (it is neither a debit obligation nor a credit observation), no carried entry.
- * A scenario that reconciled to zero rows on BOTH sides posts exactly one of these, and is
- * out-of-balance through it.
- *
- * Construction lives here with the item; the rule for WHEN a row carries it instead of its sub-rows
- * is the ROW's, and lives on `scenarioReconciliation` (`qualityCheckReconciliationsOf`).
- */
+export function duplicateScnCodeReconciliationsOf(obligations) {
+    const firstNaming = new Map();
+    for (const obligation of obligations) {
+        if (obligation.qualityCheck !== undefined && !firstNaming.has(obligation.qualityCheck)) {
+            firstNaming.set(obligation.qualityCheck, obligation);
+        }
+    }
+    if (firstNaming.size === 0) {
+        return [makeQualityCheckReconciliation({ outcome: "duplicate-scn-code", evidenceObligation: {} })];
+    }
+    return [...firstNaming].map(([qualityCheck, evidenceObligation]) => makeQualityCheckReconciliation({ qualityCheck, outcome: "duplicate-scn-code", evidenceObligation }));
+}
 export function bothMissingReconciliation() {
     return makeQualityCheckReconciliation({ outcome: "both-missing" });
 }
-/**
- * The item on the row a CONFIGURED ROW WITH NO SCENARIO earns (@SCN-LNT-027, 3F-3472) — canon's
- * `missing`: Obligation Exists, Observation None.
- *
- * NO NEW OUTCOME, AND THAT IS THE ARGUMENT RATHER THAN THE CONVENIENCE. A row the manifest declares
- * and no scenario specifies is a debit nothing observed, which is what `missing` already means and
- * what `features/fitness-checks.feature` promises in those words. Minting a fourth corpus-shape
- * outcome would put a second sentence beside a row canon already has a sentence for.
- *
- * THE OBLIGATION IS THE ROW'S OWN, and it is REAL — `{ qualityCheck: "lint", staticCheck: <the
- * characteristic> }`, the same shape a converted scenario raises. That is what separates this from
- * the uncoded-work item beside it: THAT one synthesises an empty `{}` because an untagged scenario
- * names no check at all, and this row names exactly one. So the row posts it as a debit too, and
- * the summary counts the obligation the manifest raised.
- *
- * NOTHING HERE CAN DISCHARGE IT, and that is structural rather than asserted: no observation is
- * offered to this item at all, and the minted row's `@SCN` is not a member of the set the citation
- * router posts credits against. A credit citing the row's code still mints a phantom row
- * (@SCN-LNT-009); there is no route by which it reaches this one.
- */
-export function unspecifiedRowReconciliations(characteristic) {
-    return [
-        makeQualityCheckReconciliation({
-            qualityCheck: "lint",
-            staticCheck: characteristic,
-            outcome: "missing",
-            evidenceObligation: { qualityCheck: "lint", staticCheck: characteristic },
-        }),
-    ];
-}
 //# sourceMappingURL=qualityCheckReconciliation.js.map