@openwop/openwop-conformance 1.136.6 → 1.136.7
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -1,5 +1,5 @@
|
|
|
1
1
|
{
|
|
2
2
|
"_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.",
|
|
3
|
-
"suiteVersion": "1.136.
|
|
4
|
-
"corpusCommit": "
|
|
3
|
+
"suiteVersion": "1.136.7",
|
|
4
|
+
"corpusCommit": "b71c4c7c3a3d368c98ef97fd4bed097d16a3fbdd"
|
|
5
5
|
}
|
|
@@ -3,8 +3,26 @@
|
|
|
3
3
|
* immutable recorded fact: a `replay`-mode fork MUST NOT mint a new
|
|
4
4
|
* `memoryId` for a write the source run already recorded. This asserts the
|
|
5
5
|
* "MUST NOT regenerate" half — every `memory.written` on a replayed run
|
|
6
|
-
* reuses a `memoryId` the source run recorded
|
|
7
|
-
*
|
|
6
|
+
* reuses a `memoryId` the source run recorded.
|
|
7
|
+
*
|
|
8
|
+
* H2 (2026-08-18): this file used to say, in this docstring, that "a
|
|
9
|
+
* compliant host that suppresses re-mint on replay satisfies this vacuously
|
|
10
|
+
* with zero events" — and it did: the assertion is a `for` loop over the
|
|
11
|
+
* replayed events, so a host that emits NONE passed trivially. Two hosts
|
|
12
|
+
* diverged under it and both stayed green (openwop-app re-emits the source's
|
|
13
|
+
* events; a tier-2 host suppressed them, which leaves the replayed log SHORT
|
|
14
|
+
* of the source's and breaks RFC 0041 §C byte-equivalence).
|
|
15
|
+
*
|
|
16
|
+
* The divergence is the spec's, not the hosts': RFC 0057 §D says the host
|
|
17
|
+
* "MUST re-emit the recorded events from the log" and then, in a
|
|
18
|
+
* non-normative implementation note in the same section, blesses the
|
|
19
|
+
* reference host for "suppress[ing] rather than re-emit[ting]". Resolving
|
|
20
|
+
* that contradiction is a normative decision (it plausibly makes one shipped
|
|
21
|
+
* host non-conformant), so this leg does NOT pick a side. What it stops
|
|
22
|
+
* doing is passing silently: an empty replay now records `blocked` naming
|
|
23
|
+
* the contradiction, per RFC 0148 §A — a leg that cannot observe MUST NOT
|
|
24
|
+
* read as a pass. Once §D is resolved, the winning side becomes an assertion
|
|
25
|
+
* here.
|
|
8
26
|
*
|
|
9
27
|
* Gated on `capabilities.memory.attribution.emitsWriteEvents`; soft-skips
|
|
10
28
|
* when unadvertised, when the seeded run wrote no memory, or when the host
|
|
@@ -50,6 +68,19 @@ describe('memory-attribution-replay-stable (RFC 0057 §D)', () => {
|
|
|
50
68
|
}
|
|
51
69
|
|
|
52
70
|
const replayed = await memoryWrittenEvents(forkId);
|
|
71
|
+
if (replayed.length === 0) {
|
|
72
|
+
// NOT a pass. The source run recorded `memory.written` events and the
|
|
73
|
+
// replay carries none, so this host is on the "suppress" side of the
|
|
74
|
+
// RFC 0057 §D contradiction. Whether that is conformant is undecided;
|
|
75
|
+
// that it is unobserved here is not (RFC 0148 §A).
|
|
76
|
+
return softSkip(
|
|
77
|
+
'blocked',
|
|
78
|
+
`replay emitted no memory.written while the source recorded ${recordedIds.size} — ` +
|
|
79
|
+
'the host suppresses rather than re-emits. RFC 0057 §D requires re-emission in its ' +
|
|
80
|
+
'normative half and blesses suppression in its implementation note; until that ' +
|
|
81
|
+
'contradiction is resolved this leg records the divergence instead of passing on it.',
|
|
82
|
+
);
|
|
83
|
+
}
|
|
53
84
|
for (const e of replayed) {
|
|
54
85
|
const id = memoryIdOf(e.payload);
|
|
55
86
|
expect(
|