@openwop/openwop-conformance 2.0.0-rc.64 → 2.0.0-rc.66

package/CHANGELOG.md

@@ -1,5 +1,27 @@
 # `@openwop/openwop-conformance` Changelog
 
+## [2.0.0-rc.66] — 2026-09-05 — the changelog you are reading had not mentioned this major
+
+**This file went un-updated from `1.156.0` (2026-09-02) through `2.0.0-rc.65`** — twenty-one published releases, and zero mentions of any `2.0.0-rc` in the changelog that ships inside the tarball. If you installed `2.0.0-rc.65` and read its CHANGELOG, you read a document that ended three days before the v2 release series began.
+
+**Why it rotted, and why nobody noticed.** `conformance/package.json` `files` lists `CHANGELOG.md`, which resolves *inside the package* — so the shipped file is `conformance/CHANGELOG.md`. The corpus changelog at the repo root is a **different file with the same name**, it was current the whole time, and every release wrote to it. The file being edited and the file being shipped were not the same file, and nothing compared either to the version being published. `scripts/check-shipped-changelog.mjs` now fails the corpus gate whenever a packed CHANGELOG's newest heading does not equal its own package's `version`, so this cannot recur.
+
+**Where the 2.0.0 release notes actually are.** The full per-release record for `2.0.0-rc.1` … `2.0.0-rc.65` is the corpus changelog: <https://github.com/openwop/openwop/blob/main/CHANGELOG.md>. It is not reproduced here — it is ~180 KB and would be most of the tarball. What the v2 series changed, in one paragraph: the suite gained `--target-major`, a per-`it` requirement ledger with `req()` as the only assertion form, bundle v3 with signing and verification, the three v2 profiles and their floors, and the RFC 0148 §A disposition vocabulary (`executed-pass` / `executed-fail` / `skipped` / `inapplicable` / `blocked`) under which a bundle carrying any `blocked` row does not certify. `@openwop/spec-artifacts` became a required exact-pinned peer.
+
+**This entry exists because a release should say what it shipped.** The gate requires one on every future version, including versions that change nothing worth recording — which then record exactly that.
+
+
+## [2.0.0-rc.66] — 2026-09-05 — the changelog you are reading had not mentioned this major
+
+**This file went un-updated from `1.156.0` (2026-09-02) through `2.0.0-rc.65`** — twenty-one published releases, and zero mentions of any `2.0.0-rc` in the changelog that ships inside the tarball. If you installed `2.0.0-rc.65` and read its CHANGELOG, you read a document that ended three days before the v2 release series began.
+
+**Why it rotted, and why nobody noticed.** `conformance/package.json` `files` lists `CHANGELOG.md`, which resolves *inside the package* — so the shipped file is `conformance/CHANGELOG.md`. The corpus changelog at the repo root is a **different file with the same name**, it was current the whole time, and every release wrote to it. The file being edited and the file being shipped were not the same file, and nothing compared either to the version being published. `scripts/check-shipped-changelog.mjs` now fails the corpus gate whenever a packed CHANGELOG's newest heading does not equal its own package's `version`, so this cannot recur.
+
+**Where the 2.0.0 release notes actually are.** The full per-release record for `2.0.0-rc.1` … `2.0.0-rc.65` is the corpus changelog: <https://github.com/openwop/openwop/blob/main/CHANGELOG.md>. It is not reproduced here — it is ~180 KB and would be most of the tarball. What the v2 series changed, in one paragraph: the suite gained `--target-major`, a per-`it` requirement ledger with `req()` as the only assertion form, bundle v3 with signing and verification, the three v2 profiles and their floors, and the RFC 0148 §A disposition vocabulary (`executed-pass` / `executed-fail` / `skipped` / `inapplicable` / `blocked`) under which a bundle carrying any `blocked` row does not certify. `@openwop/spec-artifacts` became a required exact-pinned peer.
+
+**This entry exists because a release should say what it shipped.** The gate will require one on every future version, including versions that change nothing worth recording — which then record exactly that.
+
+
 ## [1.156.0] — 2026-09-02 — the event codemap as data (v2 charter Phase 1, tranche 5)
 
 One new corpus-coherence scenario file (471 → 472), not packed:

package/dist/spec-artifacts.lock.json

@@ -1,5 +1,5 @@
 {
   "package": "@openwop/spec-artifacts",
-  "version": "2.0.0-rc.64",
-  "stampSha256": "5c29710dc65214cae16f4698cec6f2ca4646efa1e9bb472bfcf55e15183f0518"
+  "version": "2.0.0-rc.66",
+  "stampSha256": "66b1abcf0f47532edff60ffce799e180a79bd21924cc3c44c294c3a7d48823ec"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@openwop/openwop-conformance",
-  "version": "2.0.0-rc.64",
+  "version": "2.0.0-rc.66",
   "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.0.0-rc.64"
+    "@openwop/spec-artifacts": "2.0.0-rc.66"
   }
 }

package/requirements.json

@@ -28363,7 +28363,7 @@
     {
       "id": "openwop.it.v2-run-fork-prefix.a-replay-fork-inherits-exactly-0-fromseq-the-event-at-fromseq-is-re-executed-nev",
       "file": "v2-run-fork-prefix.test.ts",
-      "line": 86,
+      "line": 106,
       "title": "a replay fork inherits exactly [0, fromSeq): the event at fromSeq is re-executed, never carried over",
       "explicitId": null,
       "citations": [

package/schemas/CORPUS-STAMP.json

@@ -1,7 +1,7 @@
 {
   "_comment": "Provenance of @openwop/spec-artifacts (RFC 0168 §D.2). files: SHA-256 per file; the conformance suite compares the installed peer against dist/spec-artifacts.lock.json at start.",
   "package": "@openwop/spec-artifacts",
-  "version": "2.0.0-rc.64",
+  "version": "2.0.0-rc.66",
   "corpusTag": null,
   "files": {
     "api/.redocly.lint-ignore.yaml": "bf5a8350b88a72fa43f59605ed8d903ed24b6cfccda5e45509c9f6ed9ee4e712",
@@ -9,9 +9,9 @@
     "api/grpc/openwop.proto": "c3e72bb17cba514ee98feb6434e6c9b6ea6795bfd086489ec69fd882dd1ad977",
     "api/openapi.yaml": "39081c59fb696159806b0f2f9a42e7e9ff830d622fcf2ad4159b21357580a955",
     "api/redocly.yaml": "b0604c89b2ca6d5076ec25725c539dad44a741a811fe524439ee6daef8baa09f",
-    "api/seams-v2.yaml": "620fa28e241d3936fd6b9aac6d6d85c440e9d20baa3c37544c4d6dbdfc403b60",
-    "api/v2/asyncapi.yaml": "51b177f3135d573af563a2985fa36efaa82ae7d64e19b1c80bd755b4229f0e0d",
-    "api/v2/openapi.yaml": "f3a3cf2c0ad275fa0b847df1ceedcb15caf5283e89a3dcd87b1e296f74d58ce6",
+    "api/seams-v2.yaml": "039b73ef681bc1aba9b2dd1a29ccc29e45ea5ee881ce3902797a36413e052a8a",
+    "api/v2/asyncapi.yaml": "2e509275b37a636961a2aca52d51d27b4e439cf751232783238e08a12d7f6f40",
+    "api/v2/openapi.yaml": "cdfdb3c268c9e7daddc1e8c115788b5cd2812d7e950c071822c0f85cde733022",
     "api/v2/redocly.yaml": "1e66b60e6118ad11a823bb620678be464d99dfe50a40e3e6f93ec9429b88b34c",
     "schemas/README.md": "0c0b737ffcf8f30e7d2809cec8a498232de710f41443212922ad8337cdde0b51",
     "schemas/a2a-task-state.schema.json": "c9365918f993f943b4b619d42551eb066a1ed33a08d895d51b395432a5b1f1bc",
@@ -199,7 +199,7 @@
     "schemas/workspace-file.schema.json": "464de85c2a068243084ee9c1d969bc7cd5d8f7948574e58450d6493c38a0e1e4",
     "spec/v1/alias-detectors.json": "fee4594ef49953953ffcd0b3813300067d16b3e65ebff2aac722034ac9b3f545",
     "spec/v1/capability-declaration-classes.json": "e7729aed5c4b4e1dd02abab0530f14cc95f5d4070fe51fb139e7f5cccefa00c6",
-    "spec/v1/core-standard-manifest.json": "281d29c567eb67e38a229f083fa7c33cc5a3ec4307f745a7d8617a12bd4216e8",
+    "spec/v1/core-standard-manifest.json": "314be9c18684aff3c1d25f6f9633dc7185fb335f27775344f0a0aa0b23431538",
     "spec/v1/deprecations.json": "1d5acb69a9b8ccb57275a95605f74aef1d920685f8407c9d382a46b59dc803bb",
     "spec/v1/deprecations.schema.json": "18c87e78bedc210431f795ae44c5b5d202f2f3317850d5cf86867d4f1fa1cdfb",
     "spec/v1/event-codemap.json": "3da60d884157793a360da532a9fcbbfb5285636db325a74cec94b34622186d97",
@@ -230,8 +230,8 @@
     "spec/v2/path-manifest.json": "034152e09b1458c66810d4050e20a273b2b9b8fe2d92b66e8b819477de58a1be",
     "spec/v2/peer-dependency-aliases.json": "d10299280abee08258502925bc327293ee413e0108cd6e6ec75ff6110653308d",
     "spec/v2/profiles.json": "0636f19fceae625390003a347e70ef4797d84766b5c24ce8a02cea52aadebca4",
-    "spec/v2/release.json": "3fb60f16863dce06f3fe38e538e1d5214dfdd57532b865ca626ebc8d1504368d",
+    "spec/v2/release.json": "6b75f2b9d9ed2e217482d9b1be41ded1cf367abc47a1478c97770070a8764e7a",
     "spec/v2/retention-floors.json": "eaf3722d95c79947af1d4269ef85117e126518c588cfcf1a2b21b97269f51624"
   },
-  "corpusCommit": "bd32391b7d99df7545b832d365c05e0907ff5013"
+  "corpusCommit": "ec9ad85dc5eb930605e797b45072dc7707b92b72"
 }

package/src/scenarios/v2-run-fork-prefix.test.ts

@@ -32,6 +32,26 @@
  * re-executed. Length is therefore not the discriminator and this file does not
  * assert on it; the event at the boundary is.
  *
+ * Floor membership: RULED OUT (rc.65), and the reasoning generalises. Rule 10
+ * admits this file mechanically — it gates only on `replay`, which IS in the
+ * core-standard predicate, and carries no seam token. But rule 10's stated
+ * intent is that a floor file be "witnessable by an honest holder of the
+ * predicate", and this file is not: it is a SINGLE `it` gated entirely on
+ * `isFixtureAdvertised(conformance-multi-node)`, and no spec text makes that
+ * fixture mandatory. An honest `replay` holder without it records the whole
+ * file `inapplicable` and contributes zero witness. Contrast the eleven of
+ * thirteen current core-standard members with no fixture gate at all, and the
+ * two that have one (`v2-run-cancel`, `v2-run-pause-resume`) gating only SOME
+ * legs of a multi-`it` file, so the file still witnesses — the rc.59
+ * `partial-witness:` pattern.
+ *
+ * The test for any future floor candidate, then: CAN THE FILE STILL WITNESS
+ * FOR A PREDICATE HOLDER THAT ADVERTISES NO OPTIONAL FIXTURE? If the answer is
+ * no because it is single-leg and fixture-gated, it is a valid scenario and not
+ * a floor member. That is a statement about the floor's promise, not about this
+ * file's worth: the boundary it checks is real and a tier-1 host shipped the
+ * bug it catches.
+ *
  * What this file deliberately does NOT assert: the CONTENT of the re-executed
  * tail, determinism across two forks, timing, and effect re-fire suppression.
  * Those are `replay.md` §Replay determinism and the seams floor's, witnessed in