@integraledger/lcp-placement-x402 0.9.0 → 0.10.1

package/CHANGELOG.md

@@ -1,5 +1,24 @@
 # @integraledger/lcp-placement-x402
 
+## 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. One number describes the set that was built,
+tested and sealed together, so a consumer never has to work out which combination of versions was verified.
+
+This package has no source change of its own in this release. What moved across the suite: three exported
+names were corrected before anyone depends on them — `USDC_DECIMALS` became rail-qualified after it was
+found to mean 6 on three rails and 7 on Stellar under one name, `VISA_TAP_PLACEMENT_TIER_A` lost the tier
+it had baked into an identifier, and the memo codecs were named for the carrier they encode. Two wire
+identities were respelled to match the vocabulary they are written into. Five gates were added or widened,
+and a large number of documentation claims were corrected against the host specifications at HEAD.
+
 ## 0.9.0
 
 First public release.

package/README.md

@@ -61,12 +61,14 @@ and the PaymentRequirements table), four facts were confirmed and each one decid
 Extension identifiers are implementation-defined strings — no registry, no reverse-domain rule — so the
 `legalContext` key is available today and this placement is Tier A on the wire.
 
-### Drift from LCP v1.37 §C.4, recorded rather than absorbed
+### Drift from LCP v1.37 §C.4 — recorded then adopted by v1.38
 
 The host governs: its live specification is binding and LCP's Appendix C is an illustration.
 Two differences, neither of which changes the design:
 
-- v1.37 renders the echo rule in RFC-2119 capitals ("MAY append to but **MUST NOT** delete or overwrite")
+- v1.37 rendered the echo rule in RFC-2119 capitals ("MAY append to but **MUST NOT** delete or overwrite")
+  where the host states it in lower case and about the data rather than the map. **v1.38 §C.4 now says
+  exactly that**, so this item is discharged; it is kept because it is why the package reads the way it does
   and states it about the extensions map. The live spec states it in lower case and about the `info` payload.
   Same rule, weaker modality, one level lower.
 - The live spec also carries `extra` on `PaymentPayload.accepted`, which §C.4 does not mention.
@@ -181,16 +183,19 @@ the same defect as a carrier nobody can find.
   x402 defines only `info` and `schema` for an entry and the `legalContext` key is ours, so owning the entry is
   the point for the *seller* direction; entries *beside* ours in the `extensions` map are preserved
   unconditionally.
-- **`LEGAL_CONTEXT_SCHEMA_REF` points at a document the LCP TSC has not published yet**
-  (`https://legalcontextprotocol.org/schemas/lcp-extension.json`). It is byte-identical to what emitters
-  emits, and it is never fetched by anything in x402. Publishing it — or repointing it — is a **wire change
-  and must be made in both repos at once**; repointing it here alone would recreate the drift this package
-  exists to close.
+- **`LEGAL_CONTEXT_SCHEMA` is INLINED, not a reference.** It was a `$ref` at
+  `https://legalcontextprotocol.org/schemas/lcp-extension.json`, which returns 404 — re-measured
+  2026-08-11 — and x402 makes `schema` a REQUIRED member of every extension entry, so that shipped a
+  required member no counterparty could resolve. All nine extensions published in the x402 repository inline
+  a complete JSON Schema, and one of them, Bazaar, forbids an external `$ref` outright. The exported value is
+  now a frozen literal that is byte-identical to what the placement emits. Changing it is a **wire change**:
+  it appears in every challenge.
 
 ## Provenance
 
 Cut against x402 v2 (`x402-foundation/x402@1fec3aa04e41`, `specs/x402-specification-v2.md`, read 2026-07-30) and reconciled
-against LCP v1.37 §C.4 the same day. The **paths and shapes** are matched field-for-field against the shipped
+against LCP v1.37 §C.4 the same day, and re-read against **v1.38 §C.4** on 2026-08-12 — which adopted the
+drift items below and added §6.1's reserved keys. The **paths and shapes** are matched field-for-field against the
 shipped seller carrier and the buyer parsers that read it; the **resolution semantics diverge from a strict
 buyer gate in three recorded ways**, and *Drift from a strict buyer-side reader*
 above states each one and who closes it. Both drift sections are the disclosure, not a to-do list — a

package/dist/manifest.d.ts

@@ -8,10 +8,22 @@ import type { PlacementManifest } from "@integraledger/lcp-binding-core";
  * that does not break, not a reason to ship it. (`https://legalcontextprotocol.org/schemas/lcp-extension.json`
  * returns **404**, measured 2026-08-08 — the schema is inlined instead.)
  *
- * **Both extensions published in the x402 repository inline a complete JSON Schema** rather than
- * referencing an external document, and LCP v1.38 §C.4 says to do one or the other: "Because `schema` is a
- * REQUIRED member, publish a resolvable schema or inline it." Inlining also removes a hosting dependency
- * the deployment does not currently meet — the same dependency the UCP capability still owes.
+ * **All nine extensions published in the x402 repository inline a complete JSON Schema** rather than
+ * referencing an external document — `bazaar`, `builder-code`, `eip2612GasSponsoring`,
+ * `erc20ApprovalGasSponsoring`, `auth-hints`, `offer-receipt`, `http-message-signatures`,
+ * `payment-identifier`, `sign-in-with-x`, read at `x402-foundation/x402` HEAD 2026-08-11. Note that two of
+ * the nine are camelCase, so this package's `legalContext` key follows an established minority spelling
+ * rather than diverging from a unanimous one. LCP v1.38 §C.4 says to do one or the other — "Because
+ * `schema` is a REQUIRED member, publish a resolvable schema or inline it" — and adds that inlining is the
+ * safer of the two. Inlining also removes a hosting
+ * dependency the deployment does not currently meet — the same dependency the UCP capability still owes.
+ *
+ * **One of the nine makes it a rule, which settles the question.** The Bazaar extension requires a
+ * `schema`'s `$ref`/`$id` values to be "same-document JSON Pointer fragments (starting with `#`); external
+ * references (`http(s)://`, `file://`, or any other absolute/relative URI) are not allowed", and says a
+ * facilitator "must not resolve external `$ref`/`$id` values … when validating an untrusted `schema`". So a
+ * `$ref` here would not merely be unresolvable to a counterparty — it would be rejected outright by any
+ * facilitator cataloguing this extension.
  *
  * The shape is the §8.1 reference object this placement writes into `info`, and nothing more: it describes
  * the carrier, not the terms behind it.

package/dist/manifest.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"manifest.d.ts","sourceRoot":"","sources":["../src/manifest.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,iBAAiB,EAAE,MAAM,iCAAiC,CAAC;AAEzE;;;;;;;;;;;;;;;;;;;GAmBG;AACH,eAAO,MAAM,oBAAoB,EAAE,QAAQ,CAAC,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAuB/D,CAAC;AAEL;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA8EG;AACH,eAAO,MAAM,cAAc,EAAE,iBAkB5B,CAAC"}
+{"version":3,"file":"manifest.d.ts","sourceRoot":"","sources":["../src/manifest.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,iBAAiB,EAAE,MAAM,iCAAiC,CAAC;AAEzE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA+BG;AACH,eAAO,MAAM,oBAAoB,EAAE,QAAQ,CAAC,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAuB/D,CAAC;AAEL;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA8EG;AACH,eAAO,MAAM,cAAc,EAAE,iBAkB5B,CAAC"}

package/dist/manifest.js

@@ -7,10 +7,22 @@
  * that does not break, not a reason to ship it. (`https://legalcontextprotocol.org/schemas/lcp-extension.json`
  * returns **404**, measured 2026-08-08 — the schema is inlined instead.)
  *
- * **Both extensions published in the x402 repository inline a complete JSON Schema** rather than
- * referencing an external document, and LCP v1.38 §C.4 says to do one or the other: "Because `schema` is a
- * REQUIRED member, publish a resolvable schema or inline it." Inlining also removes a hosting dependency
- * the deployment does not currently meet — the same dependency the UCP capability still owes.
+ * **All nine extensions published in the x402 repository inline a complete JSON Schema** rather than
+ * referencing an external document — `bazaar`, `builder-code`, `eip2612GasSponsoring`,
+ * `erc20ApprovalGasSponsoring`, `auth-hints`, `offer-receipt`, `http-message-signatures`,
+ * `payment-identifier`, `sign-in-with-x`, read at `x402-foundation/x402` HEAD 2026-08-11. Note that two of
+ * the nine are camelCase, so this package's `legalContext` key follows an established minority spelling
+ * rather than diverging from a unanimous one. LCP v1.38 §C.4 says to do one or the other — "Because
+ * `schema` is a REQUIRED member, publish a resolvable schema or inline it" — and adds that inlining is the
+ * safer of the two. Inlining also removes a hosting
+ * dependency the deployment does not currently meet — the same dependency the UCP capability still owes.
+ *
+ * **One of the nine makes it a rule, which settles the question.** The Bazaar extension requires a
+ * `schema`'s `$ref`/`$id` values to be "same-document JSON Pointer fragments (starting with `#`); external
+ * references (`http(s)://`, `file://`, or any other absolute/relative URI) are not allowed", and says a
+ * facilitator "must not resolve external `$ref`/`$id` values … when validating an untrusted `schema`". So a
+ * `$ref` here would not merely be unresolvable to a counterparty — it would be rejected outright by any
+ * facilitator cataloguing this extension.
  *
  * The shape is the §8.1 reference object this placement writes into `info`, and nothing more: it describes
  * the carrier, not the terms behind it.

package/dist/manifest.js.map

@@ -1 +1 @@
-{"version":3,"file":"manifest.js","sourceRoot":"","sources":["../src/manifest.ts"],"names":[],"mappings":"AAEA;;;;;;;;;;;;;;;;;;;GAmBG;AACH,MAAM,CAAC,MAAM,oBAAoB,GAC/B,MAAM,CAAC,MAAM,CAAC;IACZ,OAAO,EAAE,8CAA8C;IACvD,KAAK,EAAE,6BAA6B;IACpC,WAAW,EACT,qJAAqJ;IACvJ,IAAI,EAAE,QAAQ;IACd,QAAQ,EAAE,CAAC,MAAM,EAAE,OAAO,CAAC;IAC3B,oBAAoB,EAAE,KAAK;IAC3B,UAAU,EAAE;QACV,IAAI,EAAE;YACJ,IAAI,EAAE,QAAQ;YACd,IAAI,EAAE,CAAC,QAAQ,EAAE,KAAK,EAAE,MAAM,EAAE,IAAI,CAAC;YACrC,WAAW,EACT,0GAA0G;SAC7G;QACD,KAAK,EAAE;YACL,IAAI,EAAE,QAAQ;YACd,SAAS,EAAE,CAAC;YACZ,WAAW,EACT,yGAAyG;SAC5G;KACF;CACF,CAAC,CAAC;AAEL;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA8EG;AACH,MAAM,CAAC,MAAM,cAAc,GAAsB;IAC/C,QAAQ,EAAE,MAAM;IAChB,OAAO,EAAE,eAAe;IACxB,IAAI,EAAE,GAAG;IACT,QAAQ,EAAE,kBAAkB;IAC5B,SAAS,EAAE,EAAE,IAAI,EAAE,aAAa,EAAE;IAClC,KAAK,EAAE,8BAA8B;IACrC,QAAQ,EAAE;QACR;YACE,IAAI,EAAE,yBAAyB;YAC/B,QAAQ,EAAE,YAAY;YACtB,QAAQ,EAAE,QAAQ;SACnB;KACF;IACD,aAAa,EAAE,8CAA8C;IAC7D,YAAY,EAAE,CAAC,QAAQ,EAAE,KAAK,CAAC;IAC/B,OAAO,EACL,kRAAkR;CACrR,CAAC"}
+{"version":3,"file":"manifest.js","sourceRoot":"","sources":["../src/manifest.ts"],"names":[],"mappings":"AAEA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA+BG;AACH,MAAM,CAAC,MAAM,oBAAoB,GAC/B,MAAM,CAAC,MAAM,CAAC;IACZ,OAAO,EAAE,8CAA8C;IACvD,KAAK,EAAE,6BAA6B;IACpC,WAAW,EACT,qJAAqJ;IACvJ,IAAI,EAAE,QAAQ;IACd,QAAQ,EAAE,CAAC,MAAM,EAAE,OAAO,CAAC;IAC3B,oBAAoB,EAAE,KAAK;IAC3B,UAAU,EAAE;QACV,IAAI,EAAE;YACJ,IAAI,EAAE,QAAQ;YACd,IAAI,EAAE,CAAC,QAAQ,EAAE,KAAK,EAAE,MAAM,EAAE,IAAI,CAAC;YACrC,WAAW,EACT,0GAA0G;SAC7G;QACD,KAAK,EAAE;YACL,IAAI,EAAE,QAAQ;YACd,SAAS,EAAE,CAAC;YACZ,WAAW,EACT,yGAAyG;SAC5G;KACF;CACF,CAAC,CAAC;AAEL;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA8EG;AACH,MAAM,CAAC,MAAM,cAAc,GAAsB;IAC/C,QAAQ,EAAE,MAAM;IAChB,OAAO,EAAE,eAAe;IACxB,IAAI,EAAE,GAAG;IACT,QAAQ,EAAE,kBAAkB;IAC5B,SAAS,EAAE,EAAE,IAAI,EAAE,aAAa,EAAE;IAClC,KAAK,EAAE,8BAA8B;IACrC,QAAQ,EAAE;QACR;YACE,IAAI,EAAE,yBAAyB;YAC/B,QAAQ,EAAE,YAAY;YACtB,QAAQ,EAAE,QAAQ;SACnB;KACF;IACD,aAAa,EAAE,8CAA8C;IAC7D,YAAY,EAAE,CAAC,QAAQ,EAAE,KAAK,CAAC;IAC/B,OAAO,EACL,kRAAkR;CACrR,CAAC"}

package/dist/placement.d.ts

@@ -9,7 +9,7 @@ import { type ReferencePlacementAdapter } from "@integraledger/lcp-binding-core"
  * a generic enum — the abstraction leaking — so the write half is overridden here, in this package, where it
  * is reviewed like any other code. `extract` is the kit's unchanged: reading `extensions.legalContext.info` is
  * an ordinary object-path read, and the bare-hash alias at `accepts.0.extra.atrHash` is handled by its own
- * declared encoding (S2/S6). One overridden member is composition; a second would mean this package had
+ * declared encoding. One overridden member is composition; a second would mean this package had
  * stopped using the kit, and the test suite says so.
  */
 export declare const x402Placement: ReferencePlacementAdapter;

package/dist/placement.js

@@ -21,7 +21,7 @@ function refuse(code, detail) {
  * a generic enum — the abstraction leaking — so the write half is overridden here, in this package, where it
  * is reviewed like any other code. `extract` is the kit's unchanged: reading `extensions.legalContext.info` is
  * an ordinary object-path read, and the bare-hash alias at `accepts.0.extra.atrHash` is handled by its own
- * declared encoding (S2/S6). One overridden member is composition; a second would mean this package had
+ * declared encoding. One overridden member is composition; a second would mean this package had
  * stopped using the kit, and the test suite says so.
  */
 export const x402Placement = {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@integraledger/lcp-placement-x402",
-  "version": "0.9.0",
+  "version": "0.10.1",
   "description": "Places an LCP reference into an x402 v2 payment challenge, and reads it back.",
   "keywords": [
     "lcp",
@@ -40,7 +40,7 @@
   },
   "homepage": "https://github.com/IntegraLedger/integra-protocol/tree/main/packages/placement-x402#readme",
   "dependencies": {
-    "@integraledger/lcp-binding-core": "0.9.0"
+    "@integraledger/lcp-binding-core": "0.10.1"
   },
   "devDependencies": {
     "@cfworker/json-schema": "4.1.1",

package/src/manifest.ts

@@ -9,10 +9,22 @@ import type { PlacementManifest } from "@integraledger/lcp-binding-core";
  * that does not break, not a reason to ship it. (`https://legalcontextprotocol.org/schemas/lcp-extension.json`
  * returns **404**, measured 2026-08-08 — the schema is inlined instead.)
  *
- * **Both extensions published in the x402 repository inline a complete JSON Schema** rather than
- * referencing an external document, and LCP v1.38 §C.4 says to do one or the other: "Because `schema` is a
- * REQUIRED member, publish a resolvable schema or inline it." Inlining also removes a hosting dependency
- * the deployment does not currently meet — the same dependency the UCP capability still owes.
+ * **All nine extensions published in the x402 repository inline a complete JSON Schema** rather than
+ * referencing an external document — `bazaar`, `builder-code`, `eip2612GasSponsoring`,
+ * `erc20ApprovalGasSponsoring`, `auth-hints`, `offer-receipt`, `http-message-signatures`,
+ * `payment-identifier`, `sign-in-with-x`, read at `x402-foundation/x402` HEAD 2026-08-11. Note that two of
+ * the nine are camelCase, so this package's `legalContext` key follows an established minority spelling
+ * rather than diverging from a unanimous one. LCP v1.38 §C.4 says to do one or the other — "Because
+ * `schema` is a REQUIRED member, publish a resolvable schema or inline it" — and adds that inlining is the
+ * safer of the two. Inlining also removes a hosting
+ * dependency the deployment does not currently meet — the same dependency the UCP capability still owes.
+ *
+ * **One of the nine makes it a rule, which settles the question.** The Bazaar extension requires a
+ * `schema`'s `$ref`/`$id` values to be "same-document JSON Pointer fragments (starting with `#`); external
+ * references (`http(s)://`, `file://`, or any other absolute/relative URI) are not allowed", and says a
+ * facilitator "must not resolve external `$ref`/`$id` values … when validating an untrusted `schema`". So a
+ * `$ref` here would not merely be unresolvable to a counterparty — it would be rejected outright by any
+ * facilitator cataloguing this extension.
  *
  * The shape is the §8.1 reference object this placement writes into `info`, and nothing more: it describes
  * the carrier, not the terms behind it.

package/src/placement.ts

@@ -31,7 +31,7 @@ function refuse(code: string, detail: string): Outcome<never> {
  * a generic enum — the abstraction leaking — so the write half is overridden here, in this package, where it
  * is reviewed like any other code. `extract` is the kit's unchanged: reading `extensions.legalContext.info` is
  * an ordinary object-path read, and the bare-hash alias at `accepts.0.extra.atrHash` is handled by its own
- * declared encoding (S2/S6). One overridden member is composition; a second would mean this package had
+ * declared encoding. One overridden member is composition; a second would mean this package had
  * stopped using the kit, and the test suite says so.
  */
 export const x402Placement: ReferencePlacementAdapter = {