eval-quality 1.4.0 → 1.4.1

package/dist/core/schemas/evidence-artifact.js

@@ -231,7 +231,7 @@ const evidenceCommonFields = {
     runId: z.string().min(1),
     scoringVersion: Digest.describe('AD-11: computed by the scorer over the six named inputs below and never caller-supplied.'),
     scoringVersionInputs: ScoringVersionInputs,
-    comparabilityKey: Digest.describe("AD-7's declared key: the scoring policy digest plus the corpus digest restricted to the probes both results cover. Deliberately weaker than the scoring version, so adding a probe narrows a comparison rather than voiding every prior result."),
+    comparabilityKey: Digest.describe("AD-7's declared key, computed by `emit` over the scoring policy digest and the sorted list of admitted probe identifiers. AD-7 words it as the scoring policy digest plus the corpus digest restricted to the probes both results cover, and that identifier list is what the restriction resolves to: the corpus digest bytes are not an input, so two results over one scoring policy and one admitted set share a key whatever corpus each was attested against. Deliberately weaker than the scoring version, so adding a probe narrows a comparison rather than voiding every prior result."),
     excludedProbeIds: z
         .array(ProbeId)
         .describe('The probes a narrowed comparison excluded, per AD-7. Empty is the ordinary case.'),

package/dist/core/schemas/sensitivity-witness.d.ts

@@ -56,13 +56,16 @@ export type CommandWitnessInputs = z.infer<typeof CommandWitnessInputs>;
  * interface declaring it lives in another subtree, so no discriminator is
  * available to the schema and the agreement is a compile-time check.
  *
- * Only the sensitivity leg takes the union. `ManifestationWitness` and
- * `FixtureReset` keep the transport spelling, which keeps the probe artifact
- * byte-identical and keeps this shape's widening inside the eval contract's own
- * version bump. That is truthful rather than merely convenient: both of those
- * legs are issued through the environment-probe port, whose `ProbeRequest`
- * carries a method, a path template, and the four transport channels, and
- * pre-flight rejects a non-api interface for exactly that reason.
+ * All three leg shapes take it: `SensitivityWitnessLeg.inputs`,
+ * `ManifestationWitness.inputs`, and `FixtureReset.inputs`. The sensitivity leg
+ * took it from 0.3.0 and the other two followed in 1.3.0, since the transport
+ * spelling left a seeded defect against a command-line system under test
+ * unrepresentable. The reach is the port's: all three legs are issued through
+ * the environment-probe port, whose `ProbeRequest` is itself a union of
+ * `ApiProbeRequest` and `CommandProbeRequest`, and `preflight/plan.ts` admits
+ * `api` and `cli`, rejecting `web` and `mcp` under `unsupported-interface-kind`.
+ * A leg shape narrower than the port it feeds leaves a kind the adapter can run
+ * with no way to declare a leg for it.
  */
 export declare const WitnessInputs: z.ZodUnion<readonly [z.ZodObject<{
     path: z.ZodType<import("./primitives.ts").JsonObject, unknown, z.core.$ZodTypeInternals<import("./primitives.ts").JsonObject, unknown>>;

package/dist/core/schemas/sensitivity-witness.js

@@ -55,13 +55,16 @@ export const CommandWitnessInputs = z.strictObject({
  * interface declaring it lives in another subtree, so no discriminator is
  * available to the schema and the agreement is a compile-time check.
  *
- * Only the sensitivity leg takes the union. `ManifestationWitness` and
- * `FixtureReset` keep the transport spelling, which keeps the probe artifact
- * byte-identical and keeps this shape's widening inside the eval contract's own
- * version bump. That is truthful rather than merely convenient: both of those
- * legs are issued through the environment-probe port, whose `ProbeRequest`
- * carries a method, a path template, and the four transport channels, and
- * pre-flight rejects a non-api interface for exactly that reason.
+ * All three leg shapes take it: `SensitivityWitnessLeg.inputs`,
+ * `ManifestationWitness.inputs`, and `FixtureReset.inputs`. The sensitivity leg
+ * took it from 0.3.0 and the other two followed in 1.3.0, since the transport
+ * spelling left a seeded defect against a command-line system under test
+ * unrepresentable. The reach is the port's: all three legs are issued through
+ * the environment-probe port, whose `ProbeRequest` is itself a union of
+ * `ApiProbeRequest` and `CommandProbeRequest`, and `preflight/plan.ts` admits
+ * `api` and `cli`, rejecting `web` and `mcp` under `unsupported-interface-kind`.
+ * A leg shape narrower than the port it feeds leaves a kind the adapter can run
+ * with no way to declare a leg for it.
  */
 export const WitnessInputs = z.union([ApiWitnessInputs, CommandWitnessInputs]);
 /**

package/dist/index.d.ts

@@ -12,4 +12,4 @@ export type { ScoringPolicy } from './core/schemas/scoring-policy.ts';
 export type { SealedEvaluatorBrief } from './core/schemas/sealed-evaluator-brief.ts';
 export type { SealedRunRecord } from './core/schemas/sealed-run-record.ts';
 export type { FixtureReset, ManifestationWitness, SensitivityWitness, SensitivityWitnessLeg, WitnessChannel, WitnessInputs, } from './core/schemas/sensitivity-witness.ts';
-export declare const VERSION = "1.4.0";
+export declare const VERSION = "1.4.1";

package/dist/index.js

@@ -19,4 +19,4 @@
 // subpath, where AD-37 puts the conformance definition an adapter author
 // reads; the reference adapters stay at `eval-quality/adapters`.
 export * from './application/index.js';
-export const VERSION = '1.4.0';
+export const VERSION = '1.4.1';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "eval-quality",
-  "version": "1.4.0",
+  "version": "1.4.1",
   "description": "Compile disciplined Behavioral Evaluation Contracts and score their ability to catch known defects.",
   "author": "Murat Ozcan",
   "license": "Apache-2.0",

package/schemas/evidence-artifact.schema.json

@@ -86,7 +86,7 @@
         "comparabilityKey": {
           "type": "string",
           "pattern": "^sha256:[0-9a-f]{64}$",
-          "description": "AD-7's declared key: the scoring policy digest plus the corpus digest restricted to the probes both results cover. Deliberately weaker than the scoring version, so adding a probe narrows a comparison rather than voiding every prior result."
+          "description": "AD-7's declared key, computed by `emit` over the scoring policy digest and the sorted list of admitted probe identifiers. AD-7 words it as the scoring policy digest plus the corpus digest restricted to the probes both results cover, and that identifier list is what the restriction resolves to: the corpus digest bytes are not an input, so two results over one scoring policy and one admitted set share a key whatever corpus each was attested against. Deliberately weaker than the scoring version, so adding a probe narrows a comparison rather than voiding every prior result."
         },
         "excludedProbeIds": {
           "type": "array",
@@ -666,7 +666,7 @@
         "comparabilityKey": {
           "type": "string",
           "pattern": "^sha256:[0-9a-f]{64}$",
-          "description": "AD-7's declared key: the scoring policy digest plus the corpus digest restricted to the probes both results cover. Deliberately weaker than the scoring version, so adding a probe narrows a comparison rather than voiding every prior result."
+          "description": "AD-7's declared key, computed by `emit` over the scoring policy digest and the sorted list of admitted probe identifiers. AD-7 words it as the scoring policy digest plus the corpus digest restricted to the probes both results cover, and that identifier list is what the restriction resolves to: the corpus digest bytes are not an input, so two results over one scoring policy and one admitted set share a key whatever corpus each was attested against. Deliberately weaker than the scoring version, so adding a probe narrows a comparison rather than voiding every prior result."
         },
         "excludedProbeIds": {
           "type": "array",