@openwop/openwop-conformance 1.131.0 → 1.132.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@openwop/openwop-conformance",
-  "version": "1.131.0",
+  "version": "1.132.0",
   "description": "Production-ready black-box conformance suite for OpenWOP v1.0 compliant servers.",
   "repository": {
     "type": "git",

package/schemas/CORPUS-STAMP.json

@@ -1,5 +1,5 @@
 {
   "_comment": "Provenance of this vendored schemas/ copy. See conformance/README.md \u00a7\"Resolving the contract\". Compare against the stamp in your installed @openwop/openwop-conformance to detect a stale hand-copied contract.",
-  "suiteVersion": "1.131.0",
-  "corpusCommit": "b2a25cf7013d21838b8b5abeaea7dff12355bfc5"
+  "suiteVersion": "1.132.0",
+  "corpusCommit": "1f702f91558437558816d0e6af251926942d123f"
 }

package/src/scenarios/compensation-recovery.test.ts

@@ -31,24 +31,29 @@
  * (soft-skips without the advert, HARD-FAILS under `OPENWOP_REQUIRE_BEHAVIOR=true`)
  * and records its RFC 0148 §A disposition. The three sub-features are
  * INDEPENDENTLY optional: a host that wires the base seams but not this
- * extension is `blocked` here (named as such via `seamAbsent`) and keeps its
+ * extension is `blocked` here (named as such via `softSkip`) and keeps its
  * `compensation-behavior` witness — the base and the extension are different
  * claims and are recorded separately.
  *
- * Mode matters, and the first host to advertise pointed it out: `seamAbsent`
- * records `blocked` in DEFAULT mode but THROWS under
- * `OPENWOP_REQUIRE_BEHAVIOR=true` (RFC 0148 §B — an advertised capability
- * whose witness seam is missing is a failure in strict certification, not a
- * disposition). So a host that flips `compensation.supported` on without the
- * §21 recovery extension is honest-red here in strict runs. Wire the extension
- * with the advert, or run default mode and read the `blocked` rows.
+ * Mode does NOT change that (S24, corrected 2026-08-16 after the first host to
+ * wire §21 read the contract back to us): the recovery extension has NO advert
+ * flag — `capabilities.compensation` is closed over `supported` /
+ * `profileVersion` / `orderingModels` / `manualIntervention` — so a host cannot
+ * claim or disclaim it, and `seamAbsent` (whose contract is "an ADVERTISED
+ * capability whose observation seam is absent", strict-failing) is the wrong
+ * tool for it. An absent extension is `softSkip('blocked', …)` in both modes,
+ * exactly as §21 says; the ledger still refuses to certify the three §G
+ * invariants, so nothing weakens. The BASE seams (`unwind` / `replay`) are a
+ * different matter: `compensation.supported` promises them, and a 404 there
+ * stays `seamAbsent` (strict-fails) — that is `compensation-behavior`'s wall,
+ * not this file's.
  */
 
 import { describe, it, expect } from 'vitest';
 import { driver } from '../lib/driver.js';
 import { behaviorGate } from '../lib/behavior-gate.js';
 import { capabilityFamily } from '../lib/discovery-capabilities.js';
-import { seamAbsent } from '../lib/soft-skip.js';
+import { seamAbsent, softSkip } from '../lib/soft-skip.js';
 import { readErrorCode, readRetriable } from '../lib/error-envelope.js';
 
 const PROFILE = 'openwop-compensation';
@@ -93,9 +98,14 @@ async function post(path: string, body: Record<string, unknown>): Promise<{ stat
   return { status: r.status, json: r.json };
 }
 
-/** The recovery extension is optional; a base seam that ignores the new fields is `blocked` here, not failed. */
+/**
+ * The recovery extension is optional and has no advert flag, so its absence is
+ * `blocked` in BOTH modes — `softSkip`, never `seamAbsent` (S24). The three §G
+ * invariants stay uncertified either way; strict mode is not entitled to fail
+ * a host for a sub-seam it was never asked to claim.
+ */
 function extensionAbsent(what: string): undefined {
-  return seamAbsent(`the §21 recovery extension is not wired: ${what} (host-sample-test-seams.md §21 "Recovery extension") — retry-stability / operator authority / recorded-facts are unobservable`);
+  return softSkip('blocked', `the §21 recovery extension is not wired: ${what} (host-sample-test-seams.md §21 "Recovery extension") — retry-stability / operator authority / recorded-facts are unobservable`);
 }
 
 describe('RFC 0151 §C — inverse-action identity is retry-stable (capability-gated behavior)', () => {