v1.0.2 — x402 Spec Compliance

What's changed

x402 Protocol — Full Spec Compliance

AlgoVoi now fully implements the coinbase/x402 specification, while remaining backward-compatible with existing payment flows.

Server (mcp.ilovechicken.co.uk)

• Payment requirements now include maxAmountRequired (spec field) alongside amount (legacy) — third-party x402 clients can now parse the 402 correctly
• Added required spec fields: resource, description, mimeType
• Fixed x402Version: 2 → 1 to match the official spec
• PAYMENT-RESPONSE settlement header returned on all successful paid responses

Extension (mcp-client.ts)

• McpPaymentOption interface accepts both maxAmountRequired (spec) and amount (legacy)
• Payment logic reads maxAmountRequired ?? amount — no behaviour change, works with both old and new server builds

Firefox AMO

• manifest.json now includes browser_specific_settings.gecko (id: [email protected], strict_min_version: 128.0) required for Mozilla Add-ons submission

Store packages

File	Store
algovoi-1.0.1-chrome.zip	Chrome Web Store
algovoi-1.0.1-firefox.zip	Mozilla AMO (patched manifest — sidePanel removed, gecko ID set, scripts fallback added)
algovoi-1.0.1-source.zip	AMO source code submission (required for minified bundles)

Compatibility

All existing x402 payment flows continue to work unchanged. x402 version, field names, and settlement headers now match the coinbase/x402 reference spec.