Dev nodes wiped — HTTP 401 on every battery tx, funded addresses now empty

[linear]

What

dev.node2.demos.sh:53650 is reachable and producing blocks (chain head was 8898+ at probe time), but every confirm-then-broadcast call from scripts/dev-node-battery.ts and scripts/governance-diag.ts returns HTTP 401 immediately.

Underlying cause: the previously-funded test address now reports balance: 0, nonce: 0. The full clean wipe + restart procedure that landed on #890 on 2026-06-13 left the genesis-baked balances live on the funded address. Some intervention between then and 2026-06-15 cleared that state — either another wipe, a chain re-genesis, or a different snapshot was loaded.

Symptoms

Probe (works):

POST http://dev.node2.demos.sh:53650/  body={"method":"nodeCall","params":[{"message":"getLastBlockNumber","data":{},"muid":"x"}]}
→ HTTP 200  {"result":200,"response":8898,"require_reply":false,"extra":null}

getAddressInfo for the funded test address:

balance: 0
nonce:   0

demos.confirm(tx) for any tx type (native pay, governance propose):

HTTP 401 — TransportError: Demos RPC POST … failed after 1 attempt(s): ERR_BAD_REQUEST

Acceptance

• Confirm what changed between 2026-06-13 and 2026-06-15 (likely a redeploy / wipe). Capture the dev-node boot.log head for the most recent restart.
• Re-fund the test address from genesis OR provide a new funded address + matching mnemonic for the battery / diag scripts to use.
• Once funded, re-run scripts/dev-node-battery.ts — confirm 401s clear and we're back to the governance hash mismatch (Governance propose Transaction hash mismatch — separate code path from PR #926 #941) as the only failing stage.
• Add a one-line guard to dev-node-battery.ts that fails fast with a clear "address has 0 balance — fund $ADDR before running" message instead of going through the whole confirm round-trip on every stage.

Source / context

• Funded mnemonic used by the battery: ./stress-test-mnemonic (gitignored)
• Funded address: 0x742e15a60e3a9400c9b890518a1cb0a38f978f77bc69826f559a76e7f44e85b5
• Blocks the governance hash-mismatch repro on Governance propose Transaction hash mismatch — separate code path from PR #926 #941 — without funding I cannot reach the confirmTx path that produces the actual divergence.
• Related: Re-validate dev environment after reboot #890 (dev environment recovery procedure that worked on 2026-06-13).