blockrun-debug

# Debugging BlockRun MCP Find the row, run the fix, stop. Most "broken" reports are one of the first three rows. ## Rules before touching anything 1. **A 402 / "Insufficient balance" is a funding state, not a bug.** Call `blockrun_wallet` first. Never retry the failing tool in a loop — it will 402 identically every time and the failed attempts cost nothing, but they burn turns. 2. **Never delete or regenerate `~/.blockrun/.session`.** It is the only copy of the key that holds the user's USDC and their Polymarket deposit wallet. There is no recovery. 3. **Never advise withdrawing from Polymarket to "start over".** Every post-funding trade failure seen so far was a missing approval; a withdraw does not fix it and costs a round trip. 4. Reproduce with the **free** call `blockrun_wallet` before anything paid. ## Run these first (read-only, 10 seconds) ```bash node -v && which npx # runtime present, ≥ 20.19? claude mcp get blockrun # registered command, env, AND scope (-s user / project / local) npx -y @blockrun/mcp@latest --version # does the package itself run? (prints e.g. 0.43.0) ``` Use the scope `claude mcp get` reports in every `remove`/`add` below — the examples say `-s user` because that is the documented install, but a project-scoped install re-added at user scope leaves a duplicate. Then, in the session: `blockrun_wallet` (free) → `blockrun_models` (free) → the tool that failed, **once**. ## Symptom → cause →...