shelf-smoke — url smoke / headless QA

Each tool targets a distinct resource/action: key tools (issue/verify/rotate/revoke), credit tools (quote/checkout/confirm/balance/events/packs), plus smoke and health are mutually exclusive. Related pairs like checkout/confirm and quote/smoke are clearly separated by explicit intent-versus-confirm and dry-run-versus-debit language.

Most tools follow a recognizable verb_noun pattern such as issue_key, revoke_key, checkout_credits, quote_credits, and list_credit_packs. A few noun-style names like credit_balance, credit_events, health, and smoke break the pattern slightly, but the overall convention is still predictable.

With 12 tools, the server is well-scoped across key management, credit billing, and smoke/health operations. Each tool maps to a meaningful endpoint and none feel redundant or unnecessary for the service's purpose.

The lifecycle is fully covered: keys can be issued, verified, rotated, and revoked; credits can be quoted, purchased, confirmed, checked as balance, and audited via events; smoke and health are both present. The billing workflow even accounts for 401 and 402 failure paths with refresh/buy guidance, so there are no obvious dead ends.