@integraledger/lcp-placement-x402 0.15.0 → 0.16.0

package/CHANGELOG.md

@@ -1,5 +1,18 @@
 # @integraledger/lcp-placement-x402
 
+## 0.16.0
+
+### Patch Changes
+
+- @integraledger/lcp-binding-core@0.16.0
+
+## 0.15.1
+
+### Patch Changes
+
+- Updated dependencies [431b8ec]
+  - @integraledger/lcp-binding-core@0.15.1
+
 ## 0.15.0
 
 ### Patch Changes
@@ -73,7 +86,7 @@
   `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
+  being wholly scheme-private when x402 §6.1 reserved names inside it, and LCP §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
@@ -166,7 +179,7 @@ and a large number of documentation claims were corrected against the host speci
 First public release.
 
 `0.9.0` is deliberate: this is a release candidate for 1.0, not a preview. The implementation is complete
-against LCP v1.38 and certified by the conformance corpus, and the remaining distance to 1.0 is the
+against the published LCP specification and certified by the conformance corpus, and the remaining distance to 1.0 is the
 specification's own — the standard is still moving through its steering committee, and this package will not
 claim a stability its protocol has not yet promised.
 

package/README.md

@@ -64,16 +64,16 @@ 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 then adopted by v1.38
+### Drift from LCP §C.4 — recorded then adopted by LCP
 
 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 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 appendix once 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. **LCP §C.4 now
+  says exactly that** — it records the rule "in lower case and about the `info` payload rather than the
+  map" — 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. Same rule, weaker modality, one level lower.
 - The live spec also carries `extra` on `PaymentPayload.accepted`, which §C.4 does not mention.
 
 ### Drift from a strict buyer-side reader, recorded for the same reason
@@ -188,7 +188,7 @@ needs a content-addressed value says so — it checks the decoded type as well a
 
 ## Provenance
 
-Cut against x402 v2 and reconciled against LCP v1.37 §C.4 on 2026-07-30, and re-read against **v1.38 §C.4**
+Cut against x402 v2 and reconciled against LCP §C.4 on 2026-07-30, and re-read against **LCP §C.4**
 on 2026-08-12 — which adopted the drift items below and added §6.1's reserved keys. The host revision is
 `x402-foundation/x402@db5da2e65952` (`specs/x402-specification-v2.md`), which is what `spec-pins.json`
 records this tree read on 2026-08-11 and what `pnpm spec-drift` watches. The **paths and shapes** are

package/dist/manifest.d.ts

@@ -18,7 +18,7 @@ import type { PlacementManifest } from "@integraledger/lcp-binding-core";
  * fragments (starting with `#`); external references … are not allowed", and says a facilitator "must not
  * resolve external `$ref`/`$id` values … when validating an untrusted `schema`". So an external `$ref`
  * here would not merely be unresolvable to a counterparty that declines to fetch — wherever Bazaar
- * governs, it is rejected outright. LCP v1.38 §C.4 draws the same conclusion ("publish a resolvable
+ * governs, it is rejected outright. LCP §C.4 draws the same conclusion ("publish a resolvable
  * schema or inline it — and inlining is the safer of the two"). Dropping `$id` and `$defs` from the
  * inlined form is that rule applied: the authority document's `$id` is an absolute URL, and its `$defs`
  * carries the RECEIPT-time definition, which is not this challenge-time `info` and would bloat every 402.
@@ -42,7 +42,7 @@ export declare const LEGAL_CONTEXT_SCHEMA: Readonly<Record<string, unknown>>;
  *
  * **THE CANONICAL REPOSITORY IS THE FOUNDATION'S, and the citation moved on 2026-08-08.** Every
  * reference here named `coinbase/x402`, which the GitHub API reports as `"fork": true`;
- * `x402-foundation/x402` is `"fork": false` and is what LCP v1.38 §C.4's own *Checked against* line
+ * `x402-foundation/x402` is `"fork": false` and is what LCP §C.4's own *Checked against* line
  * reads. Citing a fork invites a reader to diff against a copy that may lag. The revision is pinned
  * rather than left as a bare repo name, because "the live spec" with no commit is not a claim anyone
  * can re-check.
@@ -71,7 +71,7 @@ export declare const LEGAL_CONTEXT_SCHEMA: Readonly<Record<string, unknown>>;
  *
  * **The extension key is `legalContext`, deliberately not a reverse-domain name.** x402 imposes no namespace
  * rule, and `legalContext` is the spelling emitters put on the wire, the spelling buyer parsers read, and the
- * one LCP v1.38 §C.4's own illustration shows. The `com.integraledger.*` reverse-domain namespace applies to
+ * one LCP §C.4's own illustration shows. The `com.integraledger.*` reverse-domain namespace applies to
  * hosts that REQUIRE one — UCP does; x402 does not — and renaming this key to suit a convention x402 does not
  * have would put a spelling on the wire that no counterparty reads.
  *
@@ -86,7 +86,7 @@ export declare const LEGAL_CONTEXT_SCHEMA: Readonly<Record<string, unknown>>;
  * and writing into another party's namespace is not our act. That reasoning has been overtaken. First, the
  * host itself no longer treats `extra` as wholly scheme-private: §6.1 reserves `assetTransferMethod` and
  * `paymentFlow` inside it as protocol-governed names, so `extra` is a host-managed extension surface with
- * scheme-specific residue, not a foreign namespace. Second, LCP v1.38 §C.4's own Tier A illustration puts
+ * scheme-specific residue, not a foreign namespace. Second, LCP §C.4's own Tier A illustration puts
  * `atrHash` AND `legalContextUrl` in `accepts[].extra` — a third-party reader built from the spec's example
  * reads `extra` first, and a challenge that leaves it empty is invisible to that reader. Third, the shipped
  * buyer parser reads BOTH carriers and reconciles, refusing disagreement — so the mirror cannot drift

package/dist/manifest.js

@@ -17,7 +17,7 @@
  * fragments (starting with `#`); external references … are not allowed", and says a facilitator "must not
  * resolve external `$ref`/`$id` values … when validating an untrusted `schema`". So an external `$ref`
  * here would not merely be unresolvable to a counterparty that declines to fetch — wherever Bazaar
- * governs, it is rejected outright. LCP v1.38 §C.4 draws the same conclusion ("publish a resolvable
+ * governs, it is rejected outright. LCP §C.4 draws the same conclusion ("publish a resolvable
  * schema or inline it — and inlining is the safer of the two"). Dropping `$id` and `$defs` from the
  * inlined form is that rule applied: the authority document's `$id` is an absolute URL, and its `$defs`
  * carries the RECEIPT-time definition, which is not this challenge-time `info` and would bloat every 402.
@@ -65,7 +65,7 @@ export const LEGAL_CONTEXT_SCHEMA = Object.freeze({
  *
  * **THE CANONICAL REPOSITORY IS THE FOUNDATION'S, and the citation moved on 2026-08-08.** Every
  * reference here named `coinbase/x402`, which the GitHub API reports as `"fork": true`;
- * `x402-foundation/x402` is `"fork": false` and is what LCP v1.38 §C.4's own *Checked against* line
+ * `x402-foundation/x402` is `"fork": false` and is what LCP §C.4's own *Checked against* line
  * reads. Citing a fork invites a reader to diff against a copy that may lag. The revision is pinned
  * rather than left as a bare repo name, because "the live spec" with no commit is not a claim anyone
  * can re-check.
@@ -94,7 +94,7 @@ export const LEGAL_CONTEXT_SCHEMA = Object.freeze({
  *
  * **The extension key is `legalContext`, deliberately not a reverse-domain name.** x402 imposes no namespace
  * rule, and `legalContext` is the spelling emitters put on the wire, the spelling buyer parsers read, and the
- * one LCP v1.38 §C.4's own illustration shows. The `com.integraledger.*` reverse-domain namespace applies to
+ * one LCP §C.4's own illustration shows. The `com.integraledger.*` reverse-domain namespace applies to
  * hosts that REQUIRE one — UCP does; x402 does not — and renaming this key to suit a convention x402 does not
  * have would put a spelling on the wire that no counterparty reads.
  *
@@ -109,7 +109,7 @@ export const LEGAL_CONTEXT_SCHEMA = Object.freeze({
  * and writing into another party's namespace is not our act. That reasoning has been overtaken. First, the
  * host itself no longer treats `extra` as wholly scheme-private: §6.1 reserves `assetTransferMethod` and
  * `paymentFlow` inside it as protocol-governed names, so `extra` is a host-managed extension surface with
- * scheme-specific residue, not a foreign namespace. Second, LCP v1.38 §C.4's own Tier A illustration puts
+ * scheme-specific residue, not a foreign namespace. Second, LCP §C.4's own Tier A illustration puts
  * `atrHash` AND `legalContextUrl` in `accepts[].extra` — a third-party reader built from the spec's example
  * reads `extra` first, and a challenge that leaves it empty is invisible to that reader. Third, the shipped
  * buyer parser reads BOTH carriers and reconciles, refusing disagreement — so the mirror cannot drift

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@integraledger/lcp-placement-x402",
-  "version": "0.15.0",
+  "version": "0.16.0",
   "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.15.0"
+    "@integraledger/lcp-binding-core": "0.16.0"
   },
   "devDependencies": {
     "@cfworker/json-schema": "4.1.1",

package/src/manifest.ts

@@ -19,7 +19,7 @@ import type { PlacementManifest } from "@integraledger/lcp-binding-core";
  * fragments (starting with `#`); external references … are not allowed", and says a facilitator "must not
  * resolve external `$ref`/`$id` values … when validating an untrusted `schema`". So an external `$ref`
  * here would not merely be unresolvable to a counterparty that declines to fetch — wherever Bazaar
- * governs, it is rejected outright. LCP v1.38 §C.4 draws the same conclusion ("publish a resolvable
+ * governs, it is rejected outright. LCP §C.4 draws the same conclusion ("publish a resolvable
  * schema or inline it — and inlining is the safer of the two"). Dropping `$id` and `$defs` from the
  * inlined form is that rule applied: the authority document's `$id` is an absolute URL, and its `$defs`
  * carries the RECEIPT-time definition, which is not this challenge-time `info` and would bloat every 402.
@@ -73,7 +73,7 @@ export const LEGAL_CONTEXT_SCHEMA: Readonly<Record<string, unknown>> =
  *
  * **THE CANONICAL REPOSITORY IS THE FOUNDATION'S, and the citation moved on 2026-08-08.** Every
  * reference here named `coinbase/x402`, which the GitHub API reports as `"fork": true`;
- * `x402-foundation/x402` is `"fork": false` and is what LCP v1.38 §C.4's own *Checked against* line
+ * `x402-foundation/x402` is `"fork": false` and is what LCP §C.4's own *Checked against* line
  * reads. Citing a fork invites a reader to diff against a copy that may lag. The revision is pinned
  * rather than left as a bare repo name, because "the live spec" with no commit is not a claim anyone
  * can re-check.
@@ -102,7 +102,7 @@ export const LEGAL_CONTEXT_SCHEMA: Readonly<Record<string, unknown>> =
  *
  * **The extension key is `legalContext`, deliberately not a reverse-domain name.** x402 imposes no namespace
  * rule, and `legalContext` is the spelling emitters put on the wire, the spelling buyer parsers read, and the
- * one LCP v1.38 §C.4's own illustration shows. The `com.integraledger.*` reverse-domain namespace applies to
+ * one LCP §C.4's own illustration shows. The `com.integraledger.*` reverse-domain namespace applies to
  * hosts that REQUIRE one — UCP does; x402 does not — and renaming this key to suit a convention x402 does not
  * have would put a spelling on the wire that no counterparty reads.
  *
@@ -117,7 +117,7 @@ export const LEGAL_CONTEXT_SCHEMA: Readonly<Record<string, unknown>> =
  * and writing into another party's namespace is not our act. That reasoning has been overtaken. First, the
  * host itself no longer treats `extra` as wholly scheme-private: §6.1 reserves `assetTransferMethod` and
  * `paymentFlow` inside it as protocol-governed names, so `extra` is a host-managed extension surface with
- * scheme-specific residue, not a foreign namespace. Second, LCP v1.38 §C.4's own Tier A illustration puts
+ * scheme-specific residue, not a foreign namespace. Second, LCP §C.4's own Tier A illustration puts
  * `atrHash` AND `legalContextUrl` in `accepts[].extra` — a third-party reader built from the spec's example
  * reads `extra` first, and a challenge that leaves it empty is invisible to that reader. Third, the shipped
  * buyer parser reads BOTH carriers and reconciles, refusing disagreement — so the mirror cannot drift