@openwop/openwop-conformance 2.45.0 → 2.45.2

package/CHANGELOG.md

@@ -1,5 +1,42 @@
 # `@openwop/openwop-conformance` Changelog
 
+## [2.45.2] — 2026-09-30 — a run-failure code must be registered or a vendor code (no longer advisory)
+
+- **`errors.event-code-registered` is required** (#1698). The leg in `v2-error-registry` shipped ADVISORY in 2.43.1: an unregistered, non-vendor code on `run.failed`, `node.failed` or the snapshot's `error` recorded a partial witness naming the codes, while hosts remapped. That branch is removed, so such a code now fails the row, which names each `where=code`.
+  - **Evidence.** All three hosts' latest certified bundles record it as a clean `executed-pass` (2 assertions, no partial-witness detail), each verified under the key its host serves:
+    - the v2 reference host at 2.44.6 (witness `188a23d56886`);
+    - MyndHyve at 2.44.3 (`58da9407e616`);
+    - openwop-app at 2.44.5 (build `ab77c3aa`, `cb16716e1be6`).
+  - **Negative control.** A stub host whose failed run carries `totally_unregistered_code` passed the advisory leg and now fails it. A vendor code (`example.conformance_failure`) still passes.
+  - **Ids.** The title drops "(advisory in 2.43.1)". The per-`it` id is unchanged, since the slug is capped before those words.
+
+## [2.45.1] — 2026-09-29 — the run-list legs stop walking once they find their runs, and no scenario skips every test at describe level
+
+- **No scenario file skips every test at describe level any more, and the guard is a hard rule** (patch; no requirement added or removed; the gates are identical, and only their placement moves).
+  - **Background.** `describe-level-skip.test.ts` (2.44.9, #1686) ratcheted 56 non-floor files in which every test sat under `describe.skipIf`. vitest runs no setup hook for such a file, so it recorded no disposition when its gate held, and the runner resolved it to a report-derived `blocked` naming no reason.
+  - **The conversion.** Each file now un-gates its `describe`s and opens every test with `if (GATE) return softSkip(...GATE_WHY)`, done by an AST codemod over the unchanged predicates. `GATE_WHY` is a module constant naming the RFC 0148 §A disposition, checked in this order:
+    - `inapplicable` for a capability the host does not advertise (`isAgentSupported()`, `hasLongTermMemory()`, `isConversationPrimitiveSupported()`, `isOrchestratorSupported()`, reasoning verbosity `off`, and the like), and for no target or a published package without the scenario sources;
+    - `skipped` for an operator opt-in that is not set (`OPENWOP_RUN_RESTART_DURING_RUN`, `OPENWOP_SKIP_SCALE_PRODUCTION`);
+    - `blocked` for a withheld fixture, naming it.
+
+    A capability that is absent wins over a missing fixture, because then the requirement does not apply at all. `durability-poison-exhaustion` keeps the `inapplicable` its module-scope record already gives a missing fixture. `agentPackHandoffSchemaValidation`'s nested `describe.skipIf(!hasHandoffValidation())` is converted too.
+  - **Measured.** Against a stub host that advertises no fixtures and no capabilities, with the ledger on: before, 4 of the 56 files wrote a row; after, all 56 do, and none carries the unclassified-return detail (31 `blocked`, 23 `inapplicable`, 1 `skipped`, and 1 `executed-pass` for the corpus check `host-callback-declaration`, which passes both before and after).
+  - **The guard.** The ratchet (ceiling 56) is replaced by a hard rule: no scenario file, floor or not, may skip every test at describe level. Adding such a file fails with the offender named.
+
+- **`v2-run-list`: a bounded walk instead of a full-history walk** (patch; no requirement added or removed).
+  - **Defect.** `walk()` followed `nextCursor` to the end of the list or `MAX_PAGES` (50), although the list is newest first (`runs.md` §List) and the two runs the leg had just created sit on page 1. A long-lived host's conformance tenant gains hundreds of runs per cut, so the walk grew with the tenant's age. On openwop-app's b29427fef major-2 cut it outran the 30 s test timeout, and `0182.run-list.tenant-scoped` failed on the tenant's history, not on host behaviour.
+  - **Fix.** New pure helper `lib/run-list-walk.ts` (`walkRunList`). It stops once every created id is seen, then follows a two-page tail, so a host-minted cursor is still exercised. A created id that never appears within the 50-page cap fails the leg; it is never a silent pass.
+  - **Unchanged checks.** Every page walked is still validated against `run-list-response.schema.json`, checked against `maxPageSize`, and every id seen is checked for the caller's tenant (identity.md §5).
+  - **New check.** The unfiltered leg asserts newest-first: the second created run is listed before the first. The filtered leg uses the same walk.
+  - **Proof.**
+    - Server-free self-test `run-list-walk.test.ts` (6). Removing the early stop fails it (51 fetches, not 3), and so does dropping the tail.
+    - Measured on a stub host with 40 prior runs, 3 per page:
+      - created runs on page 1: pass.
+      - created runs on pages 3–4: pass (the walk finds them).
+      - one created run omitted: fail.
+      - another tenant's run interleaved: fail on the tenant check.
+      - created runs listed oldest first: fail on the new order check.
+
 ## [2.45.0] — 2026-09-29 — a host that grants an origin admits the contract's request headers in preflight
 
 - **New scenario `v2-cors-preflight`: `openwop.requirement.headers.cors-preflight-admits`** (#1763; minor, since a scenario is added). It witnesses the new `headers.md` §Cross-origin preflight (Class 3).

package/dist/spec-artifacts.lock.json

@@ -1,5 +1,5 @@
 {
   "package": "@openwop/spec-artifacts",
-  "version": "2.45.0",
-  "stampSha256": "f4646a61110c8c6132dfc23c78868cdfaaa6e18cda1d8247fac0b123f29c693e"
+  "version": "2.45.2",
+  "stampSha256": "30b580360e19f8ecdc72c058e20bdca2ba5cd054b5c6b98145b4086871ac73de"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@openwop/openwop-conformance",
-  "version": "2.45.0",
+  "version": "2.45.2",
   "description": "Production-ready black-box conformance suite for OpenWOP v1.0 compliant servers.",
   "repository": {
     "type": "git",
@@ -56,6 +56,6 @@
     "@openwop/spec-artifacts": "file:../spec-artifacts"
   },
   "peerDependencies": {
-    "@openwop/spec-artifacts": "2.45.0"
+    "@openwop/spec-artifacts": "2.45.2"
   }
 }