@integraledger/lcp-placements 0.9.0 → 0.11.0

package/CHANGELOG.md

@@ -1,5 +1,92 @@
 # @integraledger/lcp-placements
 
+## 0.11.0
+
+### Minor Changes
+
+- 822190a: Give the terms URL the write path the published set never had, and certify the composition that broke
+  without it (integra-protocol#8).
+
+  A third party assembling a seller from published parts emitted a 402 the published buyer refuses: every
+  published reader demanded `legalContextUrl` and no published writer placed it, and the schema
+  `placement-x402` inlined onto the wire (`required: ["type","value"]`, closed) contradicted the authority
+  document integraledger.com serves (`required: ["type","value","legalContextUrl"]`, closed) — two
+  definitions of one `info`, no document valid against both, each package self-consistent. Three structural
+  gaps let it ship: the manifest's `termsUrlField` was singular and read-only (declared, hygiene-checked,
+  never written — and x402's wire carries the URL in two slots, so one path could not even name the shape),
+  nothing compared the inlined schema to the authority document, and the corpus certified `place` and
+  `extract` separately but never fed one to the other.
+
+  `binding-core` — the placement seam now moves an ADVERTISEMENT, not a bare reference. `place` takes
+  `{ ref, termsUrl? }` and writes the URL at every slot the manifest's new `termsUrlFields` (plural,
+  replacing `termsUrlField`) declares; it REFUSES an integrity-bearing advertisement with no URL where slots
+  are declared (a hash no counterparty can resolve is unverifiable by construction), a URL where no slot
+  exists (silent dropping is fail-open), and a non-https URL on either side of the seam. `extract` returns
+  `{ ref, termsUrl }` with absence as a typed value — `no-field-declared` is a fact about the protocol,
+  `declared-fields-empty` a fact about the document, and the gate decides what an absence means — while two
+  slots that disagree, or a malformed value in either, refuse. The object-path writer learned to descend
+  into an EXISTING array element (never minting one, never extending a list, refusing an index segment it
+  would have to create), which is what lets x402's `accepts[0].extra` mirrors land.
+
+  `placement-x402` — the inlined wire schema now IS the authority document minus `$id` and `$defs`
+  (Bazaar forbids both on the wire), drift-gated in `lcp-conformance` where the two packages meet.
+  `termsUrlFields` declares both slots the wire carries; the bare-hash alias is written (`extra` stopped
+  being wholly scheme-private when x402 §6.1 reserved names inside it, and LCP v1.38 §C.4's own Tier A
+  illustration carries the pair there); the `url` carrier admission is withdrawn (`carrierTypes` is
+  `sha256` alone — the schema on the wire is `const: "sha256"`, and no shipped reader ever accepted a url
+  in this slot). The `place` override shrinks to composition: the kit performs the whole placement and the
+  override adds only the `{info, schema}` wrapper.
+
+  `placement-mpp` / `placement-acp` — the singular member becomes the one-entry `termsUrlFields`; the kit
+  now writes the slot their buyer parsers always demanded and refuses first at the seller.
+
+  `lcp-conformance` — the corpus grows 812 → 844: a `roundtrip` op (place then extract in one case, the
+  composition certification whose absence let two separately-conformant halves ship jointly broken),
+  advertisement-rule refusals for every manifest, and the authority↔wire drift gate. Extract expectations
+  across every placement area become the extracted advertisement.
+
+  `lcp-verify` — `referencePlacementStep` reads the advertisement (`extracted.ref.value`) and deliberately
+  ignores `termsUrl`: where the terms live is the gate's fetch concern, not a fact the record can
+  contradict.
+
+  `lcp-discovery` — the x402 authority document restates the atrHash pattern inline in both definitions
+  (no `$defs` indirection the wire copy would have to rewrite) and moves the two-definitions rationale into
+  `$defs.receipt`, so the challenge-time root is byte-derivable for the wire.
+
+### Patch Changes
+
+- Updated dependencies [b2ffecc]
+- Updated dependencies [822190a]
+  - @integraledger/lcp-binding-core@0.11.0
+  - @integraledger/lcp-placement-ucp@0.11.0
+  - @integraledger/lcp-placement-x402@0.11.0
+  - @integraledger/lcp-placement-mastercard-vi@0.11.0
+  - @integraledger/lcp-placement-mpp@0.11.0
+  - @integraledger/lcp-placement-acp@0.11.0
+  - @integraledger/lcp-placement-a2a@0.11.0
+  - @integraledger/lcp-placement-ack@0.11.0
+  - @integraledger/lcp-placement-ap2@0.11.0
+  - @integraledger/lcp-placement-visa-tap@0.11.0
+
+## 0.10.1
+
+**0.10.0 was staged and withdrawn before approval; this is that release, re-cut.** The conformance corpus
+was re-sealed after 0.10.0 was staged — its root moved `32fa90a6…` → `28bbf4ef…` when the vector tree was
+brought inside the prose gates — so the staged `lcp-conformance` tarball carried a seal that no longer
+matched the repository. The seal is what proves corpus authenticity to an independent implementer, and a
+published version cannot be replaced, so the whole set was rejected and re-cut rather than shipping one
+package that disagreed with its own source. No version 0.10.0 exists on the registry.
+
+Released as part of a flat `0.10.1` across the whole suite, so this package carries the suite version even
+though its own change is dependency-level: two placements it re-exports renamed an export, and the registry
+itself is unchanged.
+
+### Patch Changes
+
+- Updated dependencies [3f2d2e3]
+  - @integraledger/lcp-placement-mastercard-vi@0.10.0
+  - @integraledger/lcp-placement-visa-tap@0.10.0
+
 ## 0.9.0
 
 First public release.

package/README.md

@@ -43,7 +43,8 @@ which unit landed first.
 
 ## `mcp` is absent because MCP has no field carrier
 
-Not a pending `placement-mcp`. LCP v1.37 §C.9 and §10 describe an LCP-aware MCP **server** — tools,
+Not a pending `placement-mcp`. LCP §C.9 and §10 — v1.38, and unchanged on this point from v1.37 — describe
+an LCP-aware MCP **server** — tools,
 resources and prompts, plus a `capabilities.extensions` negotiation map keyed by a reverse domain — and no
 document field for a reference to ride in. MCP is a delivery surface, not a placement, so `mcp`'s absence
 from this registry is the correct terminal state. The corpus pins it: `placement.dispatch` asserts that a

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@integraledger/lcp-placements",
-  "version": "0.9.0",
+  "version": "0.11.0",
   "description": "The LCP placement registry — the one place a protocol is registered.",
   "keywords": [
     "lcp",
@@ -40,16 +40,16 @@
   },
   "homepage": "https://github.com/IntegraLedger/integra-protocol/tree/main/packages/placements#readme",
   "dependencies": {
-    "@integraledger/lcp-binding-core": "0.9.0",
-    "@integraledger/lcp-placement-a2a": "0.9.0",
-    "@integraledger/lcp-placement-ack": "0.9.0",
-    "@integraledger/lcp-placement-acp": "0.9.0",
-    "@integraledger/lcp-placement-ap2": "0.9.0",
-    "@integraledger/lcp-placement-mastercard-vi": "0.9.0",
-    "@integraledger/lcp-placement-mpp": "0.9.0",
-    "@integraledger/lcp-placement-ucp": "0.9.0",
-    "@integraledger/lcp-placement-visa-tap": "0.9.0",
-    "@integraledger/lcp-placement-x402": "0.9.0"
+    "@integraledger/lcp-binding-core": "0.11.0",
+    "@integraledger/lcp-placement-a2a": "0.11.0",
+    "@integraledger/lcp-placement-ack": "0.11.0",
+    "@integraledger/lcp-placement-acp": "0.11.0",
+    "@integraledger/lcp-placement-ap2": "0.11.0",
+    "@integraledger/lcp-placement-mastercard-vi": "0.11.0",
+    "@integraledger/lcp-placement-mpp": "0.11.0",
+    "@integraledger/lcp-placement-ucp": "0.11.0",
+    "@integraledger/lcp-placement-visa-tap": "0.11.0",
+    "@integraledger/lcp-placement-x402": "0.11.0"
   },
   "devDependencies": {
     "@types/node": "24.13.3",