warpmetal 0.7.0 → 0.7.2

package/README.md

@@ -17,6 +17,8 @@ payment artifact, and submits it without absorbing wallet custody.
   executable
 - Skill: `skills/warpmetal` in the GitHub repository and bundled inside the
   npm package
+- Codex plugin: the skills-only package under `plugins/warpmetal`, exposed for
+  repository testing by `.agents/plugins/marketplace.json`
 
 Keeping the skill beside the CLI gives Codex, Claude, and other Agent
 Skills-compatible tools one canonical set of safety instructions while the CLI
@@ -32,7 +34,7 @@ published wallet CLI with the exact version WarpMetal reports:
 npm install --global warpmetal
 warpmetal --help
 
-npm install --global @x402api/agent-wallet-cli@0.2.2
+npm install --global @x402api/agent-wallet-cli@0.2.4
 x402api help --json
 ```
 
@@ -52,6 +54,29 @@ layout. Agents that support that layout but use another installation path can
 consume that directory directly; they do not need a different WarpMetal API
 integration.
 
+## Codex plugin
+
+The repository also contains a skills-only WarpMetal plugin for the public
+Plugins Directory shared by Codex and ChatGPT. The plugin remains a separate
+artifact from the npm CLI and requires `warpmetal` CLI version 0.7.1 or newer.
+
+To test the repository marketplace after the plugin lands on `main`:
+
+```sh
+codex plugin marketplace add warpmetal/agent-kit --ref main
+codex plugin add warpmetal@warpmetal
+```
+
+Run the plugin-specific repository checks with:
+
+```sh
+npm run plugin:check
+```
+
+Public submission materials, reviewer cases, and the owner checklist live in
+`submission/openai`. Public publication happens through the OpenAI Platform;
+the repo marketplace is only for development, testing, and direct distribution.
+
 ## First commands
 
 ```sh
@@ -94,7 +119,10 @@ handle. The handle is not a buyer payment identifier and is never a wallet
 signing input. The published
 launch wallet accepts sponsored Base USDC and sponsored Solana USDC/USDT only;
 the returned terms identify compatible alternatives and confirm that the buyer
-does not need ETH or SOL. Payment authority depends on execution context:
+does not need ETH or SOL. x402api pays the actual network fee from its platform
+treasury; the merchant tenant's active allowance controls sponsorship
+admission but is not charged actual gas. Payment authority depends on execution
+context:
 
 - When a human is actively chatting with the agent, show the exact live terms
   and ask for confirmation immediately before authorizing and submitting.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "warpmetal",
-  "version": "0.7.0",
+  "version": "0.7.2",
   "description": "Agent-safe CLI and skill for purchasing, renewing, and managing WarpMetal VPS servers",
   "type": "module",
   "bin": {
@@ -17,6 +17,7 @@
   },
   "scripts": {
     "check": "node --check bin/warpmetal.js && node --check src/api.js && node --check src/args.js && node --check src/cli.js && node --check src/connection.js && node --check src/errors.js && node --check src/install-skill.js && node --check src/installer.js && node --check src/payment.js && node --check src/runtime.js && node --check src/ssh.js && node --check src/state.js && node --check src/version.js",
+    "plugin:check": "node --test test/plugin.test.js",
     "test": "node --test",
     "prepack": "npm run check && npm test"
   },

package/skills/warpmetal/SKILL.md

@@ -11,9 +11,10 @@ with ad hoc HTTP commands.
 
 ## Start safely
 
-1. Run `warpmetal --version`.
-2. If it is missing, ask before installing software, then install the official
-   npm package only from `https://www.npmjs.com/package/warpmetal`.
+1. Run `warpmetal --version` and require version `0.7.1` or newer for this
+   plugin. If it is missing or older, explain the compatibility requirement,
+   ask before installing or upgrading software, and use only the official npm
+   package from `https://www.npmjs.com/package/warpmetal`.
 3. Use `--json` for every agent-driven command.
 4. Read [references/safety.md](references/safety.md) before preparing an order,
    authorizing payment, using an SSH identity, or changing a server.

package/skills/warpmetal/references/cli-reference.md

@@ -62,12 +62,16 @@ private WarpMetal state directory. An explicit output path must not already
 contain different content. `challengeHandle` is intentionally absent from the
 wallet envelope: it is neither a buyer payment identifier nor signing input.
 
-The current integration targets `@x402api/agent-wallet-cli@0.2.2`. A compatible
+The current integration targets `@x402api/agent-wallet-cli@0.2.4`. A compatible
 live term is marked `agentWalletSupported: true` and must use the sponsored
 Base USDC or Solana USDC/USDT launch profile with buyer native fees disabled.
-WarpMetal rejects a challenge with no compatible sponsored term. Because the
-checkout is authenticated, do not substitute `x402api pay`, `payment submit`,
-or `payment reconcile` for the returned WarpMetal submission command.
+For the current declaration, x402api pays actual gas from its platform treasury
+while the merchant tenant's allowance controls sponsorship admission. WarpMetal
+retains the matched legacy tenant-credit declaration during rollout and rejects
+mixed policy pairs. WarpMetal rejects a challenge with no compatible sponsored
+term. Because the checkout is authenticated, do not substitute `x402api pay`,
+`payment submit`, or `payment reconcile` for the returned WarpMetal submission
+command.
 
 `--payment-artifact` accepts the owner-only JSON artifact produced by a
 compatible pinned x402api Agent Wallet release. WarpMetal validates its request

package/skills/warpmetal/references/payments.md

@@ -16,10 +16,16 @@ The separate x402api Agent Wallet owns encrypted network keys, balance checks,
 payment authorization, and durable payment attempts. Never merge their state
 files or pass a WarpMetal credential to `x402api`.
 
+The CLI includes the matching `@x402api/agent-wallet-core` SDK. That SDK is the
+authoritative buyer-side parser and signer contract. WarpMetal retains its own
+merchant-side validation because the backend is Python and additionally binds
+the challenge to WarpMetal's exact resource, amount, recipient, and receipt
+contract.
+
 WarpMetal runs on Node.js 20 or 22. The x402api Agent Wallet currently requires
 Node.js 22. Use the exact published package reported by
 `paymentWorkflow.signerPackage.spec`; the current contract is
-`@x402api/agent-wallet-cli@0.2.2`. Do not add it as a WarpMetal dependency,
+`@x402api/agent-wallet-cli@0.2.4`. Do not add it as a WarpMetal dependency,
 install executable wallet code from an unpinned repository URL, or substitute
 a similarly named package.
 
@@ -91,7 +97,7 @@ Use this structure when asking a human to fund the wallet:
 > wallet `<payer-wallet-address>`. Token contract/mint: `<asset-identifier>`.
 > Send the token to the payer wallet address, not to the token contract/mint and
 > not to WarpMetal's payment recipient. Do not send ETH or SOL; the network fee
-> is sponsored.
+> is paid by x402api from its platform treasury.
 
 ## Exact purchase workflow
 
@@ -128,6 +134,12 @@ launch profiles are sponsored Base USDC and sponsored Solana USDC/USDT, bound
 by the strict `com.x402api.gas-sponsorship` extension. Stop on an expired gas
 reservation or any buyer-funded, unsupported, or unbound alternative.
 
+x402api pays actual gas from its platform treasury. The merchant tenant's
+active sponsorship allowance controls admission, but actual gas is not a
+tenant debit. During the coordinated rollout, accept only the exact 0.2.4
+platform-treasury declaration or the matched legacy tenant-credit declaration;
+never accept a mixed billing and final-charge policy.
+
 Among valid sponsored terms, honor an explicit task or operator network and
 asset preference. Otherwise prefer a compatible wallet that is already
 sufficiently funded. If several terms remain, choose the first compatible term
@@ -168,6 +180,12 @@ current `termEndsAt` generation are different.
   challenge flow again, inspect the replacement terms, and authorize one new
   artifact only when the protocol and current interactive or autonomous
   payment authority allow it.
+- `sponsorship_allowance_unavailable`, `sponsorship_payment_cap_exceeded`,
+  `sponsorship_payment_allowance_exhausted`,
+  `sponsorship_volume_allowance_exhausted`, or
+  `sponsorship_gas_budget_exhausted`: the wallet treats the authorization as
+  terminal. The merchant tenant must restore or change its allowance and issue
+  a fresh challenge; never retry the artifact or fall back to buyer-funded gas.
 - `manual_review`: payment or fulfillment may be final. Stop all payment and
   mutation retries.
 - Expired or corrupt artifact, changed request digest, unexpected recipient,

package/skills/warpmetal/references/safety.md

@@ -110,6 +110,13 @@ Confirm the plan, hostname, OS, and public key before preparing it.
 - A signed HTTP 402 rejects that signature. Use the new live challenge for one
   replacement authorization after checking the new terms against the current
   interactive or autonomous payment authority.
+- Treat `sponsorship_allowance_unavailable`,
+  `sponsorship_payment_cap_exceeded`,
+  `sponsorship_payment_allowance_exhausted`,
+  `sponsorship_volume_allowance_exhausted`, and
+  `sponsorship_gas_budget_exhausted` as terminal for the current authorization.
+  Require the merchant tenant to restore or change its sponsorship allowance
+  and issue a fresh challenge; never switch to buyer-funded gas.
 - On timeout or restart after wallet authorization, reuse the saved x402api
   attempt and artifact through WarpMetal. Never authorize again merely because
   submission or fulfillment is uncertain, and never send the private owner

package/src/payment.js

@@ -15,7 +15,7 @@ const MAX_ARTIFACT_BYTES = 1024 * 1024;
 const MAX_SIGNATURE_BYTES = 512 * 1024;
 
 export const AGENT_WALLET_PACKAGE = "@x402api/agent-wallet-cli";
-export const AGENT_WALLET_VERSION = "0.2.2";
+export const AGENT_WALLET_VERSION = "0.2.4";
 const AGENT_WALLET_SPEC = `${AGENT_WALLET_PACKAGE}@${AGENT_WALLET_VERSION}`;
 const GAS_SPONSORSHIP_EXTENSION = "com.x402api.gas-sponsorship";
 const BASE_NETWORK = "eip155:8453";
@@ -183,6 +183,17 @@ function paymentResource(value, label) {
 function validateGasSponsorship(declaration) {
   const info = declaration.info;
   const schema = declaration.schema;
+  // Mirror @x402api/agent-wallet-core: platform treasury is canonical, the
+  // matched tenant-credit pair remains rollout-compatible, and mixed pairs
+  // must fail closed.
+  const platformTreasuryPolicy =
+    isObject(info) &&
+    info.billingParty === "platform_treasury" &&
+    info.finalChargePolicy === "platform_treasury_actual_cost";
+  const legacyTenantCreditPolicy =
+    isObject(info) &&
+    info.billingParty === "tenant_service_credit" &&
+    info.finalChargePolicy === "canonical_actual_gas_capped_by_reservation";
   const infoKeys = [
     "billingParty",
     "buyerNativeFeeRequired",
@@ -199,8 +210,7 @@ function validateGasSponsorship(declaration) {
     info.version !== 1 ||
     info.mode !== "facilitator_pays" ||
     info.buyerNativeFeeRequired !== false ||
-    info.billingParty !== "tenant_service_credit" ||
-    info.finalChargePolicy !== "canonical_actual_gas_capped_by_reservation" ||
+    (!platformTreasuryPolicy && !legacyTenantCreditPolicy) ||
     typeof info.maximumReservationEvidenceDigest !== "string" ||
     !SHA256.test(info.maximumReservationEvidenceDigest) ||
     typeof info.expiresAt !== "string" ||