feat(launch): handle the mandatory 1M $CLAWNCH burn across all launch surfaces (v0.19.0)

[clawnchdev]

Why

The Clawnch launchpad now requires a verified 1,000,000+ $CLAWNCH burn for every launch (clawnchdev/clawnch#7). /api/prepare/deploy and /api/deploy reject no-burn deploys with HTTP 402:

{"ok":false,"code":"burn_required","meta":{"minBurnTokens":"1000000","burnAddress":"0x000000000000000000000000000000000000dEaD"}}

clawmes still treated the burn as an optional vault-allocation perk. The failure mode today:

1. A burn-less /launch confirm gets the 402, which lib/http's tenacity predicate retries 3× with backoff (despite the module docstring promising 4xx is never retried)
2. _reclassify has no 402/burn_required mapping, so the raw httpx.HTTPStatusError bubbles up
3. The user sees Prepare failed: Client error '402 Payment Required' — no mention of the burn, the amount, or the address
4. The clawnch_launch LLM tool has no burn_tx_hash param at all, so that surface can't launch under the new rules, period

What changed

services/clawnch.py

• ClawnchError gains a meta dict (carries minBurnTokens / burnAddress from upstream)
• _reclassify maps HTTP 402 / burn_required / BURN_PAYMENT_REQUIRED → burn_required with meta
• prepare_deploy's ok:false map handles burn_required on 2xx bodies too

commands/launch.py — burn_required renders exact burn instructions on all four surfaces (confirm non-custodial + custodial, check, export): required amount, dead address, the /launch burn <amount|tx_hash> next step, and the vault % the same burn earns. Help text reframed (burn = required, vault = bonus).

tools/clawnch_launch.py — new burn_tx_hash schema param forwarded to deploy(); burn_required errors include retry instructions; bypass copy corrected 0.001 → 0.005 ETH (the actual default).

lib/http.py — retry predicate now skips all 4xx (5xx + transport errors keep the existing backoff). A burn-less prepare fails in one request instead of three.

Docs — README launch section, clawnch-launch skill (drops "free deploys", adds a Launch cost section + burn_required/invalid_burn recovery), plugin.yaml (both copies), /burn + /launch usage text.

Tests

• burn_required mapping with + without meta, BURN_PAYMENT_REQUIRED legacy hint, bare-402 fallback (test_clawnch.py)
• Command rendering on confirm/check/export (test_launch.py)
• Tool burn_tx_hash passthrough + error copy (test_clawnch_launch.py)
• 4xx-never-retried (400/402/404/429) + 5xx-still-retried (test_http_request.py)

4658 passed, 8 skipped · ruff clean · verified live: GET /api/prepare/deploy without burnTxHash → 402 burn_required with the documented meta shape.

Version

0.18.2 → 0.19.0 (_version.py + both plugin.yaml copies + pyproject.toml, changelog entry under Keep-a-Changelog format).