xytara 3.6.0 → 3.6.1

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.
Files changed (2) hide show
  1. package/RELEASE_NOTES.md +4 -4
  2. package/package.json +1 -1
package/RELEASE_NOTES.md CHANGED
@@ -1,6 +1,6 @@
1
- `xytara` 3.6.0 lets open-network providers price what they sell.
1
+ `xytara` 3.6.1 fixes the delegation log not surviving a runtime restart.
2
2
 
3
- - **Provider offers** — a provider registers `offers: [{ tool_name | task_ref, title, description?, price_usd }]` (whole cents, $0.01–$100.00, up to 50, selectors it declared). A call routed to that provider for an offered capability is quoted at the offer: the x402 challenge advertises the offer amount on every configured network (`acceptsForQuote`), the payment is verified against it (a base-price payment is `payment_requirements_mismatch` before the facilitator), a `credits_first` call is debited the offer's credits equivalent (price ÷ credit value, rounded up), and the provider's revenue share accrues on its own price. Offers are metadata: repricing never reverts an active provider to pending; omitting `offers` on an update keeps them, `[]` clears them. An operator-pinned execution target for a call disables offer pricing for it (the registry would not route it).
4
- - **Catalog** — `GET /v1/catalog` gains `provider_offers`: every active provider's offers with `purchase.x402_per_call` (re-priced amounts) and `credits_per_call`. Quotes carry `price_source` (`provider_offer` | `catalog`), `provider_offer` and `catalog_amount_minor`.
5
- - **Contract** — `/v1/provider-network/contract` documents `offers` and the pricing rule; the public provider view includes `offers`; `register-provider.sh` takes `OFFERS_JSON` and `PAYOUT_ADDRESS`.
3
+ - **Fix: delegation log restored from the durable snapshot** — the initial runtime state now declares `delegationEventLog`, so a restored snapshot carries the log over (the restore copies only collections the initial state already has; the log was being re-created empty on every restart). Events recorded on the live runtime between a restart and this fix were lost from memory; the hash chain restarts from genesis on the live log, which the public head reports honestly.
4
+ - **Fix: buyer event log restored too** — the same gap applied to the buyer event log and its per-day counters (`buyerEventLog`, `buyerEventDaily`): they were lost on every deploy, so the daily buyer-journey report only ever saw events since the last restart. Both are now declared in the initial state and carried over.
5
+ - The state-guard verifier now asserts every durable collection — provider registry, payouts, settlement ledger, delegation log, buyer event log — is declared in the initial state and survives a restore.
6
6
  - Client package (thin): unchanged.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "xytara",
3
- "version": "3.6.0",
3
+ "version": "3.6.1",
4
4
  "description": "Client for the hosted naxytra runtime: discover a capability, pay per call with x402 (gasless USDC on Base) or credits, get the deliverable and a signed delivery receipt you can verify offline. The runtime is a hosted service; this package is the client.",
5
5
  "main": "client.js",
6
6
  "exports": {