@pam-ai/pam-ordo-contracts 3.10.1 → 3.10.2
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/README.md +12 -6
- package/fixtures/dash-273/manifest.v2.json +1416 -0
- package/fixtures/dash-273/manifest.v2.schema.json +200 -0
- package/openapi/openapi.json +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -9,7 +9,7 @@ Pin consumers to an exact npm version:
|
|
|
9
9
|
```json
|
|
10
10
|
{
|
|
11
11
|
"dependencies": {
|
|
12
|
-
"@pam-ai/pam-ordo-contracts": "3.10.
|
|
12
|
+
"@pam-ai/pam-ordo-contracts": "3.10.2"
|
|
13
13
|
}
|
|
14
14
|
}
|
|
15
15
|
```
|
|
@@ -38,11 +38,17 @@ legacy timed-escalation fields.
|
|
|
38
38
|
|
|
39
39
|
The public npm artifact contains compiled TypeScript declarations, bundled OpenAPI, and shared fixtures. Consumers do not need GitHub repository credentials.
|
|
40
40
|
|
|
41
|
-
|
|
42
|
-
`@pam-ai/pam-ordo-contracts/fixtures/dash-273/manifest.json
|
|
43
|
-
|
|
44
|
-
|
|
45
|
-
consumer-only.
|
|
41
|
+
New DASH-273 verification runners must use the canonical v2 manifest exported at
|
|
42
|
+
`@pam-ai/pam-ordo-contracts/fixtures/dash-273/manifest.v2.json` with
|
|
43
|
+
`manifest.v2.schema.json`. Resolve each shared command fixture relative to the manifest file.
|
|
44
|
+
The v2 manifest records exact command and FIFO identities, the truthful starting boundary, and
|
|
45
|
+
whether coverage is projection-only, producer-only, or consumer-only. Conflict references are
|
|
46
|
+
typed as `{ "kind": "command" | "step", "id": "..." }`; command IDs resolve against the global
|
|
47
|
+
command catalog and step IDs resolve within their scenario.
|
|
48
|
+
|
|
49
|
+
The original `manifest.json` and `manifest.schema.json` exports remain byte-for-byte compatible
|
|
50
|
+
with published 3.10.1 for legacy readers. They retain ambiguous string conflict references and
|
|
51
|
+
must not be used by new runners that validate conflict semantics.
|
|
46
52
|
|
|
47
53
|
## Contract development
|
|
48
54
|
|