xytara 3.6.1 → 3.7.0

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.1 fixes the delegation log not surviving a runtime restart.
1
+ `xytara` 3.7.0 puts open-network provider tools in front of every MCP client.
2
2
 
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.
3
+ - **Provider tools on the MCP server** — the MCP executor lists each active provider's offered tool (`provider_offers` with a `tool_name`) in `tools/list` after its built-in tools (a colliding name is skipped; built-in tools win) and proxies a `tools/call` for it to the runtime's paid execute route. The runtime quotes at the provider's price, challenges / verifies / settles the x402 payment (or debits the spend key's credits equivalent), routes the job to the provider, attributes the revenue share and issues the delivery receipt. The MCP result carries the provider's output as `structuredContent`, `_meta["naxytra.com/provider"]` (provider, price, runtime transaction and receipt ids), the runtime's settlement in `_meta["x402/payment-response"]` (and the `PAYMENT-RESPONSE` header), and the runtime's signed delivery receipt. Provider tools are never covered by the free allowance; `MCP_EXECUTOR_PROVIDER_TOOLS=0` hides them; `/health` reports `provider_tools`.
4
+ - **Payout sweep preview** — `POST /v1/provider-network/payouts/sweep { dry_run: true }` returns the payable providers, the total and whether a signer is configured, without creating or sending anything.
5
+ - The provider contract (`/v1/provider-network/contract`) states the MCP distribution.
6
6
  - Client package (thin): unchanged.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "xytara",
3
- "version": "3.6.1",
3
+ "version": "3.7.0",
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": {