eval-quality 0.2.0 → 0.3.0

package/dist/core/evaluate/operators.d.ts

@@ -31,6 +31,18 @@ export declare function setMembership(value: ResolvedValue, set: JsonValue[], ar
  * single element to search for: this function receives resolved values only,
  * so it cannot tell a `{ literal }` array from a resolved `{ referenceSet }`.
  * Known, accepted limitation.
+ *
+ * A separate property, and a separate limitation: a `{ referenceSet }`
+ * candidate matches **whole declared members** by structural equality. A
+ * container element carrying any field the reference set does not declare
+ * therefore never matches, which is the ordinary case for rows read off a
+ * response body. `set-membership`'s set position projects a reference set to
+ * its single declared key and this position does not, because projecting only
+ * where a container happens to hold objects would make the operand's meaning
+ * depend on the evidence's runtime shape. An author reconciling rows against a
+ * declared set wants `covers-by-key`, which compares on named keys on both
+ * sides, or `for-all(rows, set-membership(@/key, { referenceSet }))`, which
+ * reads the declared key.
  */
 export declare function containment(container: ResolvedValue, candidate: ResolvedValue | JsonValue[], artifactPath: string): boolean;
 /**
@@ -62,6 +74,16 @@ export declare function countTolerance(collection: ResolvedValue, expected: numb
  * that is required and not permitted reaches here and fails every value.
  */
 export declare function shape(value: ResolvedValue, descriptor: KeyedShapeDescriptor, _artifactPath: string): boolean;
+/**
+ * Own-property lookup only, so a key like `__proto__` reads as missing
+ * rather than inherited. Returns `ABSENT`, never throws (AD-4: a missing key
+ * resolves `false`, not an error).
+ *
+ * Exported so `resolution.ts`'s `set-membership` set-operand projection reads
+ * a declared member's key through this one spelling, keeping the own-property
+ * guard in one place.
+ */
+export declare function keyValueOf(element: JsonValue, key: string): JsonValue | typeof ABSENT;
 /**
  * AD-4's bijection: equal cardinality and a distinct `actual` match per
  * `expected` element on the named keys. `ABSENT` on either side resolves

package/dist/core/evaluate/operators.js

@@ -90,6 +90,18 @@ export function setMembership(value, set, artifactPath) {
  * single element to search for: this function receives resolved values only,
  * so it cannot tell a `{ literal }` array from a resolved `{ referenceSet }`.
  * Known, accepted limitation.
+ *
+ * A separate property, and a separate limitation: a `{ referenceSet }`
+ * candidate matches **whole declared members** by structural equality. A
+ * container element carrying any field the reference set does not declare
+ * therefore never matches, which is the ordinary case for rows read off a
+ * response body. `set-membership`'s set position projects a reference set to
+ * its single declared key and this position does not, because projecting only
+ * where a container happens to hold objects would make the operand's meaning
+ * depend on the evidence's runtime shape. An author reconciling rows against a
+ * declared set wants `covers-by-key`, which compares on named keys on both
+ * sides, or `for-all(rows, set-membership(@/key, { referenceSet }))`, which
+ * reads the declared key.
  */
 export function containment(container, candidate, artifactPath) {
     if (container === ABSENT)
@@ -287,8 +299,12 @@ export function shape(value, descriptor, _artifactPath) {
  * Own-property lookup only, so a key like `__proto__` reads as missing
  * rather than inherited. Returns `ABSENT`, never throws (AD-4: a missing key
  * resolves `false`, not an error).
+ *
+ * Exported so `resolution.ts`'s `set-membership` set-operand projection reads
+ * a declared member's key through this one spelling, keeping the own-property
+ * guard in one place.
  */
-function keyValueOf(element, key) {
+export function keyValueOf(element, key) {
     if (!isPlainObject(element) || !Object.hasOwn(element, key))
         return ABSENT;
     // `Object.hasOwn` above already proves the key is present; `noUncheckedIndexedAccess`

package/dist/core/evaluate/resolution.d.ts

@@ -3,8 +3,9 @@
  * that turns an `Expression` into one `CheckResolutionValue`. Leaf operators,
  * `covers-by-key` included, live in `operators.ts`. Operand resolution, every
  * pointer form including the bound-element `@/` form, is injected;
- * `evidence-resolution.ts` supplies it, and `ResolveOperand` and
- * `PointerDenotesCollection` are the consumer-side contract it satisfies.
+ * `evidence-resolution.ts` supplies it, and `ResolveOperand`,
+ * `PointerDenotesCollection`, and `ReferenceSetKeys` are the consumer-side
+ * contract it satisfies.
  */
 import type { CheckResolutionValue } from '../schemas/evidence-artifact.ts';
 import type { Expression, Operand } from '../schemas/expression.ts';
@@ -31,10 +32,20 @@ export type ResolveOperand = (operand: Operand, boundElement: ResolvedValue, art
  * soft-delete agreement pair (AD-4's own worked example).
  */
 export type PointerDenotesCollection = (pointer: string) => boolean;
+/**
+ * The `keys` each declared reference set names, by identifier.
+ * `set-membership`'s set position reads the single declared key off each
+ * member (`reference-set.ts`), and the members map the injected
+ * `ResolveOperand` closes over has already discarded the keys, so they travel
+ * separately. Plain data, because `PreflightPlan` carries this through to
+ * its reducer and is compared by value, which a closure fails.
+ * `evidence-resolution.ts` builds it from a contract.
+ */
+export type ReferenceSetKeys = Readonly<Record<string, readonly string[]>>;
 /**
  * The public entry point. Walks `expression` and produces one
  * `CheckResolutionValue`, exactly what `Outcome.checkResolution` needs,
  * unmodified. `boundElement` starts `ABSENT` at the root, where no quantifier
  * has bound anything yet.
  */
-export declare function resolveCheck(expression: Expression, resolveOperand: ResolveOperand, pointerDenotesCollection: PointerDenotesCollection, regexMatchStepBudget: number, artifactPath: string): CheckResolutionValue;
+export declare function resolveCheck(expression: Expression, resolveOperand: ResolveOperand, pointerDenotesCollection: PointerDenotesCollection, referenceSetKeys: ReferenceSetKeys, regexMatchStepBudget: number, artifactPath: string): CheckResolutionValue;

package/dist/core/evaluate/resolution.js

@@ -1,4 +1,4 @@
-import { absence, containment, countTolerance, coversByKey, deepEquality, equality, existence, ordering, regexMatch, setMembership, shape, } from './operators.js';
+import { absence, containment, countTolerance, coversByKey, deepEquality, equality, existence, keyValueOf, ordering, regexMatch, setMembership, shape, } from './operators.js';
 import { ABSENT } from './resolved-value.js';
 /**
  * AD-4's one closed introduction condition, checked per operand and applied
@@ -242,10 +242,69 @@ function resolveRegexNode(expression, boundElement, ctx) {
     const { pattern } = expression;
     return resolveSingleOperand(operand, boundElement, ctx, (resolved) => regexMatch(resolved, pattern, ctx.regexMatchStepBudget, ctx.artifactPath));
 }
+/**
+ * Reads the single declared key off each member of a `{ referenceSet }` set
+ * operand. `reference-set.ts` declares members as objects so one declaration
+ * serves both operators, and states that "a `set-membership` operand against
+ * the same set reads the single named key". This is where that reading
+ * happens, and without it AD-20 rule 6's injection form can never answer
+ * `true`: the value operand resolves to a scalar, and `setMembership` compares
+ * whole members by digest, so a scalar against an object is always `false`.
+ *
+ * Scoped to this one operator position on purpose. `covers-by-key` projects
+ * both sides itself on `expectedKey` and `actualKey`, and `containment`
+ * matches whole members, so both want the members unprojected. The injected
+ * `ResolveOperand` is handed one operand at a time and cannot see which
+ * operator position it is filling, which is why the projection lives at the
+ * resolution site.
+ *
+ * The option turned down: an explicit `memberKey` field on `set-membership`
+ * mirroring `covers-by-key`'s `expectedKey`. It is symmetric with its sibling
+ * and it carries a multi-key set, at the price of a grammar change to a
+ * published artifact, an eval-contract `schemaVersion` bump, and
+ * published-schema drift, for a case no shipped contract has. Revisit it the
+ * first time a real contract wants a multi-key set in this position.
+ *
+ * Both throws are unreachable for a compiled contract:
+ * `checkOperandLegality` rejects a multi-key reference set in this position,
+ * and a member missing the declared key, under
+ * `malformed-operator-expression`. They throw, because a set this function
+ * cannot project carries no membership answer to give.
+ */
+function projectSetOperand(resolvedSet, setOperand, ctx) {
+    if (!('referenceSet' in setOperand))
+        return resolvedSet;
+    const { referenceSet } = setOperand;
+    // `Object.hasOwn`, the same prototype-chain guard `makeResolveOperand`
+    // applies to its own maps: `Identifier`'s charset admits `constructor`.
+    const keys = Object.hasOwn(ctx.referenceSetKeys, referenceSet)
+        ? ctx.referenceSetKeys[referenceSet]
+        : undefined;
+    // No declared keys means the contract declares no such reference set,
+    // which compilation rejects under `unresolved-reference-set`; a non-array
+    // is the array guard below reporting whatever the resolver returned. Both
+    // pass through so exactly one guard speaks for each.
+    if (keys === undefined || !Array.isArray(resolvedSet))
+        return resolvedSet;
+    if (keys.length !== 1) {
+        throw new Error(`set-membership's set-operand projection: referenceSet "${referenceSet}" declares ${keys.length} keys, and this position reads exactly one. A multi-key set here is malformed-operator-expression, which compilation rejects.`);
+    }
+    const key = keys[0];
+    return resolvedSet.map((member) => {
+        const keyValue = keyValueOf(member, key);
+        if (keyValue === ABSENT) {
+            throw new Error(`set-membership's set-operand projection: a member of referenceSet "${referenceSet}" carries no own property "${key}", the key it declares. That is malformed-operator-expression, which compilation rejects.`);
+        }
+        return keyValue;
+    });
+}
 function resolveSetMembershipNode(expression, boundElement, ctx) {
     const [valueOperand, setOperand] = expression.operands;
     const value = ctx.resolveOperand(valueOperand, boundElement, ctx.artifactPath);
-    const resolvedSet = ctx.resolveOperand(setOperand, boundElement, ctx.artifactPath);
+    // Projected before the empty-collection interception and the array guard
+    // below, so both read the one value the operator will see. Projection
+    // preserves length and array-ness, so neither answer moves.
+    const resolvedSet = projectSetOperand(ctx.resolveOperand(setOperand, boundElement, ctx.artifactPath), setOperand, ctx);
     if (anyOperandEmpty([
         { operand: valueOperand, resolved: value },
         { operand: setOperand, resolved: resolvedSet },
@@ -326,10 +385,11 @@ function resolveNode(expression, boundElement, ctx) {
  * unmodified. `boundElement` starts `ABSENT` at the root, where no quantifier
  * has bound anything yet.
  */
-export function resolveCheck(expression, resolveOperand, pointerDenotesCollection, regexMatchStepBudget, artifactPath) {
+export function resolveCheck(expression, resolveOperand, pointerDenotesCollection, referenceSetKeys, regexMatchStepBudget, artifactPath) {
     return resolveNode(expression, ABSENT, {
         resolveOperand,
         pointerDenotesCollection,
+        referenceSetKeys,
         regexMatchStepBudget,
         artifactPath,
     });

package/dist/core/excluded-content.d.ts

@@ -0,0 +1,65 @@
+/**
+ * AD-18's excluded categories, as patterns that read a value rather than a name.
+ *
+ * AD-18 excludes "credentials, tokens, real names, email addresses, account
+ * identifiers, and transaction content" from every artifact this package
+ * produces or publishes, and binds "published examples and test fixtures as
+ * strictly as real runs". Until this module the whole prohibition was carried by
+ * one test that scans `corpus/dev`, so a contract carrying a live-shaped token
+ * compiled clean and the token travelled into the sealed brief.
+ *
+ * Only the value-shaped half of that scan ships here, and the split is the point
+ * rather than an economy. AD-18's own reading of the rule for the header channel
+ * is that a declaration "names the header and its type and never carries a
+ * credential value", so a name is what an author is supposed to write: an
+ * operation declaring a `password` body key or an `Authorization` header is a
+ * contract for an authentication API, and a gate matching `\bpassword\b` would
+ * reject exactly the systems this package exists to evaluate. The patterns below
+ * therefore match only strings whose shape is decidable without knowing what
+ * field they sit in: a PEM header, a token with an issuer prefix, an address, a
+ * checkable account number, a card-shaped digit run. The name-shaped patterns
+ * stay in `tests/architecture/dev-corpus.test.ts`, where review rather than a
+ * compiler decides.
+ *
+ * Each pattern carries a string it must fire on, and a test asserts every one
+ * still does. A pattern that has rotted into a regex matching nothing is worse
+ * than no pattern: it reports clean forever.
+ */
+/** AD-18's six categories, in the rule's own order. */
+export declare const EXCLUDED_CATEGORIES: readonly ['credentials', 'tokens', 'real names', 'email addresses', 'account identifiers', 'transaction content'];
+export type ExcludedCategory = (typeof EXCLUDED_CATEGORIES)[number];
+export type ExcludedContentPattern = {
+    readonly category: ExcludedCategory;
+    readonly regex: RegExp;
+    /** a string the pattern must match, so a rotted pattern fails its own test. */
+    readonly fires: string;
+};
+/**
+ * `real names` has no member here and never will: a personal name has no surface
+ * form, so every pattern that reaches one reads the field that carries it, which
+ * is a name-shaped test. The category stays in the tuple above because AD-18
+ * names six and dropping one from the vocabulary would make the gate look total.
+ */
+export declare const EXCLUDED_VALUE_PATTERNS: readonly ExcludedContentPattern[];
+export type ExcludedContentHit = {
+    readonly category: ExcludedCategory;
+    /** the artifact-rooted path of the string that matched. */
+    readonly path: string;
+    /** the matched run, which is short by construction and is what a caller redacts. */
+    readonly match: string;
+};
+/**
+ * Every string anywhere inside one value, against every value-shaped pattern.
+ *
+ * Object keys are walked as paths and never scanned as content: a key is a name
+ * by construction, which is the same line the pattern set is drawn on. The walk
+ * is total over JSON and stops at nothing, so a token nested under a body
+ * example twelve levels down is found; the first matching category per string
+ * wins, since one string reported six times says nothing more than once.
+ *
+ * Order is the walk's order, which for an object is its own key order. A caller
+ * that needs a stable report over two spellings of the same object sorts what
+ * comes back; the compile gate below reads only the first hit and never the
+ * order.
+ */
+export declare function scanExcludedContent(value: unknown, path: string): readonly ExcludedContentHit[];

package/dist/core/excluded-content.js

@@ -0,0 +1,113 @@
+/**
+ * AD-18's excluded categories, as patterns that read a value rather than a name.
+ *
+ * AD-18 excludes "credentials, tokens, real names, email addresses, account
+ * identifiers, and transaction content" from every artifact this package
+ * produces or publishes, and binds "published examples and test fixtures as
+ * strictly as real runs". Until this module the whole prohibition was carried by
+ * one test that scans `corpus/dev`, so a contract carrying a live-shaped token
+ * compiled clean and the token travelled into the sealed brief.
+ *
+ * Only the value-shaped half of that scan ships here, and the split is the point
+ * rather than an economy. AD-18's own reading of the rule for the header channel
+ * is that a declaration "names the header and its type and never carries a
+ * credential value", so a name is what an author is supposed to write: an
+ * operation declaring a `password` body key or an `Authorization` header is a
+ * contract for an authentication API, and a gate matching `\bpassword\b` would
+ * reject exactly the systems this package exists to evaluate. The patterns below
+ * therefore match only strings whose shape is decidable without knowing what
+ * field they sit in: a PEM header, a token with an issuer prefix, an address, a
+ * checkable account number, a card-shaped digit run. The name-shaped patterns
+ * stay in `tests/architecture/dev-corpus.test.ts`, where review rather than a
+ * compiler decides.
+ *
+ * Each pattern carries a string it must fire on, and a test asserts every one
+ * still does. A pattern that has rotted into a regex matching nothing is worse
+ * than no pattern: it reports clean forever.
+ */
+/** AD-18's six categories, in the rule's own order. */
+export const EXCLUDED_CATEGORIES = [
+    'credentials',
+    'tokens',
+    'real names',
+    'email addresses',
+    'account identifiers',
+    'transaction content',
+];
+/**
+ * `real names` has no member here and never will: a personal name has no surface
+ * form, so every pattern that reaches one reads the field that carries it, which
+ * is a name-shaped test. The category stays in the tuple above because AD-18
+ * names six and dropping one from the vocabulary would make the gate look total.
+ */
+export const EXCLUDED_VALUE_PATTERNS = [
+    {
+        category: 'credentials',
+        regex: /-----BEGIN [A-Z ]*PRIVATE KEY-----/,
+        fires: '-----BEGIN RSA PRIVATE KEY-----',
+    },
+    {
+        category: 'tokens',
+        regex: /(?<![A-Za-z])(?:[Bb]earer\s+[\w.~+/-]{16,}|eyJ[\w-]{8,}\.[\w-]{8,}|sk-[A-Za-z0-9]{16,}|gh[pousr]_[A-Za-z0-9]{16,}|AKIA[0-9A-Z]{16})/,
+        fires: 'Authorization: Bearer abcdefghijklmnopqrstuv',
+    },
+    {
+        category: 'email addresses',
+        regex: /[A-Za-z0-9._%+-]+@[A-Za-z0-9.-]+\.[A-Za-z]{2,}/,
+        fires: '{"contact":"ada@example.com"}',
+    },
+    {
+        // Case-sensitive: an IBAN is upper case, and a case-insensitive form
+        // matches a run inside a lower-case hex digest.
+        category: 'account identifiers',
+        regex: /\b[A-Z]{2}\d{2}[A-Z0-9]{11,30}\b|\b\d{3}-\d{2}-\d{4}\b/,
+        fires: 'GB29NWBK60161331926819',
+    },
+    {
+        category: 'transaction content',
+        regex: /(?<![0-9A-Za-z])\d{4}(?:[ -]\d{4}){3}(?![0-9A-Za-z])/,
+        fires: 'charged 4111 1111 1111 1111',
+    },
+];
+const step = (path, key) => typeof key === 'number' ? `${path}[${key}]` : `${path}.${key}`;
+/**
+ * Every string anywhere inside one value, against every value-shaped pattern.
+ *
+ * Object keys are walked as paths and never scanned as content: a key is a name
+ * by construction, which is the same line the pattern set is drawn on. The walk
+ * is total over JSON and stops at nothing, so a token nested under a body
+ * example twelve levels down is found; the first matching category per string
+ * wins, since one string reported six times says nothing more than once.
+ *
+ * Order is the walk's order, which for an object is its own key order. A caller
+ * that needs a stable report over two spellings of the same object sorts what
+ * comes back; the compile gate below reads only the first hit and never the
+ * order.
+ */
+export function scanExcludedContent(value, path) {
+    const hits = [];
+    const visit = (node, at) => {
+        if (typeof node === 'string') {
+            for (const { category, regex } of EXCLUDED_VALUE_PATTERNS) {
+                const match = regex.exec(node);
+                if (match === null)
+                    continue;
+                hits.push({ category, path: at, match: match[0] });
+                return;
+            }
+            return;
+        }
+        if (Array.isArray(node)) {
+            node.forEach((element, index) => {
+                visit(element, step(at, index));
+            });
+            return;
+        }
+        if (node === null || typeof node !== 'object')
+            return;
+        for (const [key, child] of Object.entries(node))
+            visit(child, step(at, key));
+    };
+    visit(value, path);
+    return hits;
+}

package/dist/core/failure-codes.d.ts

@@ -1,5 +1,5 @@
-/** AD-5's twenty-three compile-time failure codes, as data, in the table's order. */
-export declare const FAILURE_CODES: readonly ['missing-requirement-linkage', 'no-observable-success-criterion', 'unreachable-check-evidence', 'malformed-operator-expression', 'quantifier-over-non-collection', 'quantifier-nesting-exceeded', 'unresolved-reference-set', 'duplicate-operation-signature', 'undeclared-mandatory-input', 'oracle-missing-channel', 'direction-check-misaligned', 'unsupported-interface-kind', 'nested-temporal-clause', 'plan-exceeds-scripting-bound', 'binding-cycle', 'captured-channel-undeclared', 'rubric-scores-reasoning-prose', 'rubric-unanchored', 'rubric-evidence-unreachable', 'forbidden-input-floor-incomplete', 'scoped-reference-resolves-forbidden', 'waiver-incomplete', 'brief-exceeds-scripting-bound'];
+/** AD-5's twenty-six compile-time failure codes, as data, in the table's order. */
+export declare const FAILURE_CODES: readonly ['missing-requirement-linkage', 'no-observable-success-criterion', 'unreachable-check-evidence', 'malformed-operator-expression', 'quantifier-over-non-collection', 'quantifier-nesting-exceeded', 'unresolved-reference-set', 'duplicate-operation-signature', 'undeclared-mandatory-input', 'oracle-missing-channel', 'direction-check-misaligned', 'unsupported-interface-kind', 'nested-temporal-clause', 'plan-exceeds-scripting-bound', 'binding-cycle', 'captured-channel-undeclared', 'rubric-scores-reasoning-prose', 'rubric-unanchored', 'rubric-evidence-unreachable', 'forbidden-input-floor-incomplete', 'scoped-reference-resolves-forbidden', 'waiver-incomplete', 'brief-exceeds-scripting-bound', 'unresolved-artifact-reference', 'irreducible-step-reference', 'excluded-content-in-declaration'];
 export type FailureCode = (typeof FAILURE_CODES)[number];
 /**
  * AD-5's compile-time failure registry: thrown when a structural error fails

package/dist/core/failure-codes.js

@@ -1,11 +1,11 @@
-/** AD-5's twenty-three compile-time failure codes, as data, in the table's order. */
+/** AD-5's twenty-six compile-time failure codes, as data, in the table's order. */
 // This lives in `core/`, since it's a plain data tuple and `core/schemas/`
 // is reserved for Zod definitions. The compiler that emits these codes lives
 // in `core/compile/`, one directory over.
 //
 // `scripts/check-ad5-registry.ts` checks this tuple against AD-5's own
 // registry table under `npm run validate`; the tuple's own invariants
-// (twenty-three members, unique, kebab-case) are locked in
+// (twenty-six members, unique, kebab-case) are locked in
 // tests/schemas/failure-codes.test.ts.
 export const FAILURE_CODES = [
     'missing-requirement-linkage',
@@ -31,6 +31,9 @@ export const FAILURE_CODES = [
     'scoped-reference-resolves-forbidden',
     'waiver-incomplete',
     'brief-exceeds-scripting-bound',
+    'unresolved-artifact-reference',
+    'irreducible-step-reference',
+    'excluded-content-in-declaration',
 ];
 /**
  * AD-5's compile-time failure registry: thrown when a structural error fails

package/dist/core/ingest/conditions.d.ts

@@ -67,7 +67,7 @@ export type AgreementField = (typeof AGREEMENT_FIELDS)[number];
  */
 export type DuplicateRecordIdentifier = {
     readonly kind: Extract<IngestConditionKind, 'duplicate-record-identifier'>;
-    readonly subject: 'observation' | 'finding' | 'oracle-disposition';
+    readonly subject: 'observation' | 'finding' | 'oracle-disposition' | 'judge-result';
     readonly identifier: string;
     readonly occurrences: number;
 };

package/dist/core/ingest/ingest.js

@@ -106,6 +106,14 @@ export const ingest = (record, manifest, configuration) => {
             'oracle-disposition',
             record.oracleDispositions.map((disposition) => disposition.oracleId),
         ],
+        // AD-17's "one judge call scoring all named criteria", read as far as
+        // one record can be read: a criterion scored twice is not one call's
+        // product whatever the rest of the record says. Keyed by the pair,
+        // since two rubrics may each declare a criterion of the same name.
+        [
+            'judge-result',
+            record.judgeResults.map((result) => `${result.rubricId}/${result.criterionId}`),
+        ],
     ]) {
         const counts = new Map();
         for (const identifier of identifiers) {

package/dist/core/preflight/plan.d.ts

@@ -1,5 +1,6 @@
+import type { ReferenceSetKeys } from '../evaluate/resolution.ts';
 import type { EvalContract } from '../schemas/eval-contract.ts';
-import type { Operation } from '../schemas/interface.ts';
+import type { AnyOperation } from '../schemas/interface.ts';
 import type { ProbeRequest } from '../schemas/port-messages.ts';
 import type { JsonValue } from '../schemas/primitives.ts';
 import type { Probe } from '../schemas/probe.ts';
@@ -15,7 +16,7 @@ export type PlannedLeg = {
     readonly legId: string;
     readonly purpose: PlannedLegPurpose;
     readonly request: ProbeRequest;
-    readonly operation: Operation;
+    readonly operation: AnyOperation;
     readonly inputs: WitnessInputs;
 };
 export type PlannedCheck = {
@@ -28,7 +29,7 @@ export type PlannedCheck = {
     readonly interfaceId: string;
     readonly operationId: string;
     readonly witness: SensitivityWitness | null;
-    readonly operation: Operation;
+    readonly operation: AnyOperation;
 } | {
     readonly kind: 'state-reset';
     readonly legIds: readonly [string, string];
@@ -39,19 +40,20 @@ export type PlannedCheck = {
     readonly kind: 'seeded-faults-scoped';
     readonly defectId: string;
     readonly witness: ManifestationWitness;
-    readonly operation: Operation;
+    readonly operation: AnyOperation;
     readonly cleanLegIds: readonly string[];
 } | {
     readonly kind: 'seeded-fault-fired';
     readonly defectId: string;
     readonly witness: ManifestationWitness | null;
-    readonly operation: Operation | null;
+    readonly operation: AnyOperation | null;
 };
 export type PreflightPlan = {
     readonly runId: string;
     readonly legs: readonly PlannedLeg[];
     readonly checks: readonly PlannedCheck[];
     readonly referenceSets: Readonly<Record<string, JsonValue[]>>;
+    readonly referenceSetKeys: ReferenceSetKeys;
 };
 /**
  * AD-10's plan, derived from the interfaces the contract's probes exercise.