[PRICING][DOCS] Keep canonical pricing HTML/spec aligned with package-credit launch contract

[replynodes-ai]

Parent tracker: https://github.com/replynodes/replynodes-app/issues/238

Goal

Make replynodes-pricing.html a versioned, reviewable canonical product artifact for the package-credit launch, not an independent page that can drift from app/backend/fetcher enforcement.

Scope

• Keep the embedded replynodes-pricing-spec JSON and rendered HTML synchronized.
• Include stable version/effective date, plan IDs, USD amounts, credit grants, annual discount, overage terms, endpoint/provider credit-cost matrix, and billing rules.
• Mark any route not actually live/supported as deferred or remove it from the launch claim; do not advertise future providers as available.
• Add explicit note that x402/wallet/top-up is disabled for this package launch and link to the authenticated subscription entry point.
• Preserve mobile/accessibility/basic HTML validation and a deterministic check that rendered rows equal the embedded JSON.

Acceptance criteria

• The HTML and embedded JSON contain the same Free/Developer/Pro plans: 500 one-time, 10,000/month at $19, 100,000/month at $99.
• Annual two-month discount and paid overage prices match the reviewed contract.
• Credit-cost rows are complete only for supported launch routes and have no contradictory duplicate prices.
• Canonical rules include exactly-once successful-request charging, zero charge for failures, billable empty success/pagination/cache-hit semantics, monthly reset, and no rollover.
• No x402, wallet, chain, or top-up launch CTA remains.
• A validation script/test fails on JSON-vs-rendered-table drift and malformed/negative prices.

Non-goals

No app deployment, backend billing, payment-provider integration, or fetcher code.