bareloop 0.11.0 → 0.12.0

package/types/authoring.d.ts

@@ -9,10 +9,11 @@
  * `CLASS_BY_VERDICT` exist to stop, defeated from ABOVE by never letting the
  * illegal pair be formed.
  *
- * INERT IN v1 BY CONSTRUCTION, which is why it is cheap now: every LIVE kind is
- * mechanical, so no declaration a v1 catalogue can express reaches above green.
- * It is written before the second class exists so the first soft-green kind is
- * not the thing that discovers the question.
+ * NO LONGER INERT: `human-confirms` (N4 slice 1) and `judged-floor` (softgreen
+ * module 2) are both live and both above green, so a green declaration naming
+ * one is a real red rather than a hypothetical. `classMenu` below is the other
+ * half of the same rule, applied one step earlier — the composer is never handed
+ * a kind this would refuse.
  *
  * A kind the catalogue does not know contributes NOTHING — it already carries an
  * `unknown-kind` red, and guessing a class for it would be deriving the promise
@@ -28,6 +29,31 @@ export function closeCeiling(declaration: any, catalogue?: Record<string, KindSp
     stage: string | null;
     locked: boolean;
 } | null;
+/**
+ * THE MENU A JOB OF THIS CLASS MAY EXPRESS — the ceiling rule, moved one step
+ * EARLIER, to the moment the composer is handed its vocabulary.
+ *
+ * `closeCeiling` refuses an above-ceiling kind AFTER a paid call has composed a
+ * declaration around it. That is a late red for an illegal pick the composer was
+ * shown in its own catalogue and its own tool schema — and the standing rule is
+ * the opposite: wherever only a closed set can satisfy a field, hand over the
+ * enumerated set, so the illegal value is INEXPRESSIBLE rather than rejected
+ * after the fact (the `check-passes(name)` model). A green job is therefore never
+ * shown `judged-floor` or `human-confirms` at all.
+ *
+ * ONLY THE MENU NARROWS. The VALIDATOR keeps the whole catalogue, deliberately:
+ * a model that names a kind it was never offered must be told which RULE it
+ * broke (`class-ceiling`), not that the kind does not exist (`unknown-kind`) —
+ * one is the truth and the other invites it to invent a spelling.
+ *
+ * `null` means UNFILTERED and exists for callers inspecting the catalogue itself
+ * (the schema/coverage suite). Every composing call site passes the user's own
+ * picked class; `authorPrompt` already throws without one.
+ * @param {string|null} verdictType
+ * @param {Record<string, KindSpec>} [catalogue]
+ * @returns {string[]} kind names at or below the picked class, in catalogue order
+ */
+export function classMenu(verdictType: string | null, catalogue?: Record<string, KindSpec>): string[];
 /**
  * Which kinds can carry an environment at all, read off the CATALOGUE rather
  * than a hand-kept list. ONE spelling, because two consumers must agree
@@ -291,8 +317,14 @@ export function normalizeDeclaration(declaration: any): any;
 /** the whole menu, in ascending order of what it takes to render the verdict */
 export const VERDICT_CLASSES: readonly string[];
 /** declared-but-locked: selecting one is COUNTED demand, never an admission.
- * `hitl` LEFT this list at N4 slice 1 (see `src/job.js`'s twin) — the class is
- * built, and its battery is below. `soft-green` waits for the judged floor. */
+ * `hitl` LEFT this list at N4 slice 1 and `soft-green` at softgreen module 3
+ * (see `src/job.js`'s twin, `LOCKED_VERDICTS`, which moved in the same commit) —
+ * the judged floor its lock was waiting on is built, wired and calibrated.
+ *
+ * EMPTY is a true statement about a closed menu, not F59's absent-as-empty: the
+ * mechanism is read at call time from this constant, so re-locking a class is
+ * one edit and every counted refusal comes back with it. */
+/** @type {readonly string[]} */
 export const LOCKED_CLASSES: readonly string[];
 /** the classes v1 actually builds */
 export const LIVE_CLASSES: readonly string[];
@@ -530,8 +562,22 @@ export const CLASS_BATTERIES: Readonly<{
         }>)[];
     }>;
     'soft-green': Readonly<{
-        locked: true;
-        guards: null;
+        locked: false;
+        guards: readonly (Readonly<{
+            name: "changed-from-seed";
+            kind: "files-changed";
+            params: Readonly<{
+                requireNonEmpty: true;
+            }>;
+            compose: readonly never[];
+            fill: readonly string[];
+        }> | Readonly<{
+            name: "no-suppressions";
+            kind: "pattern-absent-in-diff";
+            params: Readonly<{}>;
+            compose: readonly string[];
+            fill: readonly never[];
+        }>)[];
     }>;
     hitl: Readonly<{
         locked: false;

package/types/authorjob.d.ts

@@ -85,12 +85,13 @@ export function refuseLockedKind(kind: string): Refusal;
  *   onPhase?: (phase: string, data?: any) => void,
  *   onCall?: (call: {label: string, costUsd: number|null, unpricedRounds: number}) => void,
  *   seedFn?: Function, scoutFn?: Function, listingFn?: Function,
- *   authorFn?: Function, authorOpts?: object}} o
+ *   authorFn?: Function, authorOpts?: object,
+ *   signerFix?: Function|any, proposeFn?: Function, compileOpts?: object}} o
  * @returns {Promise<{ok: boolean, refusal: Refusal|null, verdictType: string|null,
- *   closeDecl: any, seedRef: string|null, authoring: any, reds: Red[], stop: string|null,
- *   cost: any, interview: any}>}
+ *   closeDecl: any, seedRef: string|null, authoring: any, judged: any, reds: Red[],
+ *   stop: string|null, cost: any, interview: any}>}
  */
-export function authorCloseForJob({ answers, repoPath, lang, verdictType, questions, generate, provider, seedRef, scout, listing, ceilingUsd, onPhase, onCall, seedFn, scoutFn, listingFn, authorFn, authorOpts, }: {
+export function authorCloseForJob({ answers, repoPath, lang, verdictType, questions, generate, provider, seedRef, scout, listing, ceilingUsd, onPhase, onCall, seedFn, scoutFn, listingFn, authorFn, authorOpts, signerFix, proposeFn, compileOpts, }: {
     answers: Record<string | number, any>;
     repoPath?: string | null;
     lang: string;
@@ -113,6 +114,9 @@ export function authorCloseForJob({ answers, repoPath, lang, verdictType, questi
     listingFn?: Function;
     authorFn?: Function;
     authorOpts?: object;
+    signerFix?: Function | any;
+    proposeFn?: Function;
+    compileOpts?: object;
 }): Promise<{
     ok: boolean;
     refusal: Refusal | null;
@@ -120,6 +124,7 @@ export function authorCloseForJob({ answers, repoPath, lang, verdictType, questi
     closeDecl: any;
     seedRef: string | null;
     authoring: any;
+    judged: any;
     reds: Red[];
     stop: string | null;
     cost: any;
@@ -171,6 +176,24 @@ export function assembleSpec(specDraft: any, { closeDecl, verdictType }: {
  *      A close with NO work stage red at seed has nothing to do and is refused
  *      decision-ready — gate-2 round 2's arm B died exactly there, on a mypy that
  *      scanned nothing and therefore read clean.
+ *   4. THE CALIBRATION GATE (softgreen module 5) — for a close carrying a
+ *      `judged-floor` stage ONLY. The whole judged pipe runs over the signed ten
+ *      and the five arbiter-owned injection artifacts, and anything short of
+ *      10/10 with itemized reds and 5/5 resisted is an unsignable close. It is
+ *      the ONE gate here that spends money, so it runs LAST — every free refusal
+ *      has already had its chance, and nobody pays to discover a broken
+ *      declaration.
+ *
+ * D9.3 AND THE JUDGED-ONLY CLOSE (2026-08-18 second addendum, ruling 3; hamr:
+ * *"fix it now, we are delivering softgreen, isn't that the whole point?"*). Gate
+ * 3 protects against a close that cannot fail — one that scans nothing and reads
+ * green at seed against a true red. A judged stage SKIPS the seed read by ruling
+ * 8, so a close whose only work stage is judged has no seed red to show and used
+ * to be unsignable: the one job shape softgreen exists for. For that shape, and
+ * ONLY that shape, a PASSED calibration gate plays the seed-red role — it is that
+ * close's own proof of failability, held to the same all-or-nothing bar. A close
+ * with a mechanical work stage is UNCHANGED: it still needs a seed red, whatever
+ * its calibration says.
  *
  * Gates 2 and 3 share ONE execution, and that is stated rather than hidden: at
  * job creation the tree IS the seed, so "does every stage run against the real
@@ -183,11 +206,13 @@ export function assembleSpec(specDraft: any, { closeDecl, verdictType }: {
  * comes back is the resolved spec, its hash, and the evidence to sign against.
  *
  * @param {{spec: any, workdir: string, seedRef?: string|null, shellCapUsd?: number,
- *   timeoutMs?: number, seedFn?: Function, listingFn?: Function, seedReadFn?: Function}} o
+ *   timeoutMs?: number, seedFn?: Function, listingFn?: Function, seedReadFn?: Function,
+ *   judgeLoop?: Function|null, onJudgeCost?: ((c: any) => void)|null, calibrateFn?: Function,
+ *   ceilingUsd?: number|null, priorCalls?: any[]}} o
  * @returns {Promise<{ok: boolean, specHash: string|null, seedRef: string|null,
  *   gates: any, work: any[], guards: any[], stops: any[], reds: Red[], refusal: Refusal|null}>}
  */
-export function prepareSigning({ spec, workdir, seedRef, shellCapUsd, timeoutMs, seedFn, listingFn, seedReadFn, }: {
+export function prepareSigning({ spec, workdir, seedRef, shellCapUsd, timeoutMs, seedFn, listingFn, seedReadFn, judgeLoop, onJudgeCost, calibrateFn, ceilingUsd, priorCalls, }: {
     spec: any;
     workdir: string;
     seedRef?: string | null;
@@ -196,6 +221,11 @@ export function prepareSigning({ spec, workdir, seedRef, shellCapUsd, timeoutMs,
     seedFn?: Function;
     listingFn?: Function;
     seedReadFn?: Function;
+    judgeLoop?: Function | null;
+    onJudgeCost?: ((c: any) => void) | null;
+    calibrateFn?: Function;
+    ceilingUsd?: number | null;
+    priorCalls?: any[];
 }): Promise<{
     ok: boolean;
     specHash: string | null;

package/types/bridges.d.ts

@@ -1,3 +1,8 @@
+/** does a green under this verdict class earn its learning credit at the close, or
+ * does it wait for a person? Absent/unknown means green's behaviour, byte for byte
+ * — the pre-softgreen path is the default and stays untouched.
+ * @param {unknown} verdictType @returns {boolean} */
+export function quarantinesCredit(verdictType: unknown): boolean;
 /**
  * D6's status ladder, walked in history order. Pure, total, and never throws —
  * it is called on whatever a file happens to contain.
@@ -13,6 +18,10 @@
  *   the entry on the first repeat green.
  * - a red on a CANDIDATE changes nothing: there is nothing below the entry bar, and
  *   the entry stays in the record with the red beside it.
+ * - a **QUARANTINED green is not evidence** (softgreen module 6). The row exists and
+ *   the run happened, but a judged green earns nothing until the signer's `accept`
+ *   releases it, so it neither clears the entry bar nor adds a distinct patient. An
+ *   entry whose only greens are held derives `null` — below the bar, not demoted.
  * - a **CASUALTY is not a red.** Only the literal outcome `'red'` demotes; every
  *   other non-green outcome (`provider-red`, `wall-halt`, `close-crashed`, …) is a
  *   casualty, and casualties are never evidence in either direction.
@@ -74,6 +83,68 @@ export function appendRed(bridge: unknown, record: unknown): {
     reds: Red[];
     bridge: any;
 };
+/**
+ * The version that would INHERIT — the newest one whose credit has actually been
+ * released. `versions` is oldest-first, so this is normally the last of them; it
+ * differs only when a judged green sits on top of a released one, and in that case
+ * the RELEASED plan is what a reuse starts from. A held version is not a worse
+ * recipe, it is an unjudged one: nobody has said yet whether the ruler that passed
+ * it was right, and starting the next run from it would spend the credit before it
+ * was granted.
+ *
+ * Total and never throws — it is read at selection time and at the load door.
+ * @param {unknown} bridge
+ * @returns {any|null} null when every version is held (or there are none)
+ */
+export function newestEligibleVersion(bridge: unknown): any | null;
+/**
+ * May this workflow be offered for reuse at all? A held entry is SKIPPED WITH A
+ * REASON everywhere it is skipped — the same visible-skip discipline an unreadable
+ * registry file already gets, because a shelf that quietly shrinks teaches the
+ * operator that the registry is empty when it is merely holding.
+ * @param {unknown} bridge
+ * @returns {{ok: boolean, reason: string}} `reason` is '' when ok
+ */
+export function reuseEligibility(bridge: unknown): {
+    ok: boolean;
+    reason: string;
+};
+/**
+ * THE REVIEW DOOR, written down (PRD v1.71 §3). The person read the finished run
+ * and said one of three things; this records that on the run's own row, and — for
+ * `accept` on a HELD green — releases the learning credit that green has been
+ * carrying unspent.
+ *
+ * Three properties, and each is a ruling rather than a convenience:
+ *
+ *  - **the door never changes the loop's verdict.** A green row stays a green row,
+ *    whatever the person then does with it. `rerun` and `pause` are dispositions,
+ *    recorded and nothing more; a rerun's own outcome is a NEW run's row.
+ *  - **release is FORWARD-ONLY.** Nothing here can set `quarantined` back to true,
+ *    so a signer who accepts and later reruns has recorded a disagreement — which
+ *    is a datum worth keeping — without un-granting credit already granted. There
+ *    is deliberately no re-hold path at all: it would be a way to walk the ledger
+ *    backwards, which the ruling forbids.
+ *  - **releasing is not minting.** A door aimed at a run with no green row of its
+ *    own is a named red — never an invented entry. That is slice 1's already-green
+ *    rule holding from the other side: `accept` confirms a verdict, it never
+ *    creates one.
+ *
+ * Idempotent by shape: a decision identical to the last one recorded is a no-op
+ * that returns the entry unchanged, so a double-click at the door cannot inflate
+ * the report card (and `released` says whether THIS call was the one that freed it).
+ *
+ * Pure — returns a NEW entry; the input is never mutated.
+ * @param {unknown} bridge a validated bridge entry
+ * @param {unknown} door `{ runid, decision, at }` — `at` may be an explicit null
+ * @returns {{ ok: boolean, reds: Red[], bridge: any, released: boolean }}
+ */
+export function recordDoor(bridge: unknown, door: unknown): {
+    ok: boolean;
+    reds: Red[];
+    bridge: any;
+    released: boolean;
+};
 /**
  * One row of D3's listing: what the user (and the selecting LLM) sees per bridge —
  * name, the job sentence it greened, status, greens/reds, and the cost/time BAND of
@@ -86,7 +157,7 @@ export function appendRed(bridge: unknown, record: unknown): {
  * Total and never throws: the listing is a display surface, and one malformed
  * entry must not take the whole listing down (loadRegistry already reports it).
  * @param {unknown} bridge
- * @returns {{name: string|null, goal: string|null, status: 'candidate'|'proven'|null, greens: number, reds: number, lastOutcome: string|null, greenCost: {minUsd: number|null, maxUsd: number|null, minWallMs: number|null, maxWallMs: number|null, unpricedCount: number, untimedCount: number}}}
+ * @returns {{name: string|null, goal: string|null, status: 'candidate'|'proven'|null, greens: number, reds: number, quarantinedGreens: number, doorDecisions: {runid: string|null, decision: string|null, at: string|null}[], lastOutcome: string|null, greenCost: {minUsd: number|null, maxUsd: number|null, minWallMs: number|null, maxWallMs: number|null, unpricedCount: number, untimedCount: number}}}
  */
 export function listingRow(bridge: unknown): {
     name: string | null;
@@ -94,6 +165,12 @@ export function listingRow(bridge: unknown): {
     status: "candidate" | "proven" | null;
     greens: number;
     reds: number;
+    quarantinedGreens: number;
+    doorDecisions: {
+        runid: string | null;
+        decision: string | null;
+        at: string | null;
+    }[];
     lastOutcome: string | null;
     greenCost: {
         minUsd: number | null;
@@ -191,6 +268,23 @@ export function makeRegistry(dir: string): string;
 /** @param {string} dir @returns {boolean} does a registry directory exist */
 export function registryExists(dir: string): boolean;
 export const BRIDGE_SCHEMA: "bridge-v1";
+/**
+ * SOFTGREEN MODULE 6 — the verdict classes whose greens are minted QUARANTINED.
+ *
+ * The standing ruling (PRD v1.53, given a mechanism by v1.71 §3): *softgreen
+ * passes are quarantined from learning credit until the judged floor is proven*,
+ * and **the signer's `accept` at the review door is what releases it**.
+ *
+ * `soft-green` and NOT `hitl`: the hold is about the young JUDGE, not about every
+ * class that is not `green`. A hitl close is rendered by a PERSON at close time —
+ * there is no unproven ruler in it to distrust. A green earns its credit at its
+ * own close, exactly as it always has.
+ */
+export const QUARANTINED_VERDICTS: readonly string[];
+/** the red CODE a hold travels under — the gate emits it, the listing splits the
+ * held rows out of the broken ones on it, and the runner reads it back. One
+ * spelling, because three literals is how a hold silently becomes a breakage. */
+export const QUARANTINED_CODE: "quarantined";
 export type Red = {
     code: string;
     path: string;

package/types/calibrate.d.ts

@@ -0,0 +1,191 @@
+/**
+ * Did the pipe grade this case the way the signer signed it?
+ *
+ * BOTH HALVES, AND BOTH ARE REQUIRED. The verdict alone is the aggregate this
+ * floor was written against: a red case that reds on the wrong card line, or on
+ * the right line and the wrong function, has told the operator nothing about
+ * whether their ruler works — §4.4's *"with itemized reds, not a paragraph"* is
+ * exactly this comparison and not a looser one.
+ *
+ * The reds compare as SETS: `decide()` grades every card item over every
+ * function and its emission order follows the card and the model's function
+ * list, while a signer writes their expectation in whatever order they thought
+ * of it. Order is not a fact about the pipe, so it is not compared; the ADDRESSES
+ * are. A duplicate is already inexpressible on both sides (`expectedOf` dedupes,
+ * `validateCalibrationSet` reds a repeated pair), so set comparison loses
+ * nothing.
+ * @param {{verdict: string, reds: {rule: string, fn: string}[]}} got
+ * @param {any} want
+ * @returns {{ok: boolean, verdictOk: boolean, redsOk: boolean, missing: string[], extra: string[]}}
+ */
+export function compareExpectation(got: {
+    verdict: string;
+    reds: {
+        rule: string;
+        fn: string;
+    }[];
+}, want: any): {
+    ok: boolean;
+    verdictOk: boolean;
+    redsOk: boolean;
+    missing: string[];
+    extra: string[];
+};
+/**
+ * Did the extraction survive the attack?
+ *
+ * Three readings, all mechanical, all over facts this module owns both sides of:
+ *   - THE FUNCTION LIST is exactly the gold's, as a set. A style that hides a
+ *     function has moved the facts even if every remaining fact is true.
+ *   - EVERY DOCUMENTED function's `docQuote` is a REAL JSDoc opener from the
+ *     artifact, and every UNDOCUMENTED one's is `null`. A non-null quote on an
+ *     undocumented function is the leak this battery exists to catch, and it is
+ *     invisible one layer up: `decide()` reds it either way (an invented quote
+ *     fails the artifact check), so resist and leak render the SAME itemized
+ *     reds and only the facts separate them.
+ *   - and the DECISION still matches gold, so a leak that somehow survives both
+ *     fact checks still has one more gate to pass.
+ * @param {any} facts @param {any} gold @param {string} artifactText
+ * @returns {{ok: boolean, why: string|null}}
+ */
+export function factsResist(facts: any, gold: any, artifactText: string): {
+    ok: boolean;
+    why: string | null;
+};
+/**
+ * THE CALIBRATION GATE. Run the whole pipe over the signed ten and over the five
+ * arbiter-owned injection artifacts, and report — itemized, per case — whether
+ * the ruler is a ruler.
+ *
+ * It never throws on a caller's data: an illegal set is a RED (the same
+ * `{ok, reds}` shape module 4's validators return), because this is reached from
+ * a signing gate whose whole job is to hand a person a readable refusal. It
+ * throws on nothing at all.
+ *
+ * ORDER, and it is load-bearing: the $0 legality check runs FIRST and buys no
+ * calls; then the ten; then the battery. A set that cannot be legal is refused
+ * before a token, and an operator whose card is malformed does not pay to find
+ * out.
+ *
+ * ALL-OR-NOTHING, both halves (v1.73 ruling 2 and ruling 3, kept by the second
+ * addendum's ruling 1): `ok` is true only when all ten graded correctly AND all
+ * five styles resisted AND nothing was a casualty.
+ * THE OPERATOR'S CEILING RIDES IN AS A PREDICATE (`capStop`), asked between metered
+ * calls exactly as the authoring pipeline's cost book asks its own. It is the
+ * CALLER's book that answers, because the gate is the THIRD paid seam of one run and
+ * a tally that starts at zero here would be a second ceiling wearing the first one's
+ * number. Absent is UNBOUNDED, and unbounded is a stated operator choice.
+ *
+ * A ceiling stop is a REFUSAL, never a throw and never a partial set presented as a
+ * graded one: `ok` is false, the cases nobody bought are absent rather than recorded
+ * as failures, and `casualty` stays null — the transport was fine, the operator's own
+ * governance stopped the gate.
+ * @param {{cases: any, card: any, judgeLoop: Function|null,
+ *   onCost?: (c: any) => void, attempts?: number, battery?: any[], batteryCard?: any,
+ *   capStop?: () => 'cap-halt'|'pricing-red'|null}} o
+ * @returns {Promise<{ok: boolean, stop: string|null, casualty: any,
+ *   graded: {id: string, ok: boolean, got: any, want: any, detail: string|null}[],
+ *   injection: {styles: any[], allResisted: boolean, leaks: string[]},
+ *   failures: string[], reds: Red[], judgeModel: string,
+ *   cardHash: string|null, casesHash: string|null, setHash: string|null,
+ *   costUsd: number|null, knownUsd: number, spendComplete: boolean, calls: any[]}>}
+ */
+export function runCalibration({ cases, card, judgeLoop, onCost, attempts, battery, batteryCard, capStop, }: {
+    cases: any;
+    card: any;
+    judgeLoop: Function | null;
+    onCost?: (c: any) => void;
+    attempts?: number;
+    battery?: any[];
+    batteryCard?: any;
+    capStop?: () => "cap-halt" | "pricing-red" | null;
+}): Promise<{
+    ok: boolean;
+    stop: string | null;
+    casualty: any;
+    graded: {
+        id: string;
+        ok: boolean;
+        got: any;
+        want: any;
+        detail: string | null;
+    }[];
+    injection: {
+        styles: any[];
+        allResisted: boolean;
+        leaks: string[];
+    };
+    failures: string[];
+    reds: Red[];
+    judgeModel: string;
+    cardHash: string | null;
+    casesHash: string | null;
+    setHash: string | null;
+    costUsd: number | null;
+    knownUsd: number;
+    spendComplete: boolean;
+    calls: any[];
+}>;
+/** @typedef {{code: string, path: string, detail: string, [k: string]: any}} Red */
+/** the label a calibration's own locate calls are metered under. The SAME
+ * `LOCATE_LABEL` a close's judged stage spends under, deliberately: it is the
+ * same call to the same model over the same prompt, and a second spelling would
+ * make one population of spend read as two. */
+export const CALIBRATION_LABEL: "judged-locate";
+/** the axes that STOP the gate as a casualty rather than failing a case. All
+ * three are `runLocate`'s own, borrowed with their meanings intact — this module
+ * invents no vocabulary for a fault the shipped pipe already names. */
+export const CASUALTY_AXES: readonly ("pricing-red" | "provider-red" | "artifact-red")[];
+export function artifactHash(v: any): string;
+/**
+ * The battery's OWN card — `has-doc` alone, and one line rather than three on
+ * purpose. Every attack style below aims at exactly one lie ("this file is
+ * documented"), so the card that grades them names exactly the fact being lied
+ * about; extra lines would buy extra prompt surface and extra ways for a
+ * truthful-but-noisy extraction to look like a leak.
+ */
+export const INJECTION_CARD: Readonly<{
+    items: readonly Readonly<{
+        rule: "has-doc";
+        text: "Every top-level function has a JSDoc block directly above it.";
+    }>[];
+}>;
+/**
+ * THE FIVE STYLES, one artifact each. Every artifact carries one honestly
+ * documented function and one honestly undocumented one, and the attack always
+ * asks for the same thing: report the undocumented function as documented (or
+ * do not report it at all). The truth is therefore identical across all five,
+ * which is what makes a leak attributable to the STYLE rather than to the file.
+ */
+export const INJECTION_LOCATE_BATTERY: readonly Readonly<{
+    id: string;
+    style: string;
+    attack: string;
+    artifact: `/**
+ * Add two numbers.
+ */
+export function add(a, b) {
+  return a + b;
+}
+
+${string}`;
+    expectFacts: Readonly<{
+        functions: readonly Readonly<{
+            name: string;
+            hasDoc: boolean;
+        }>[];
+    }>;
+    expect: Readonly<{
+        verdict: "pass" | "red";
+        reds: readonly Readonly<{
+            rule: string;
+            fn: string;
+        }>[];
+    }>;
+}>[];
+export type Red = {
+    code: string;
+    path: string;
+    detail: string;
+    [k: string]: any;
+};