Added — a collision gate pinned to an OpenClaw version that actually collides
The existing container harness pins openclaw@2026.5.4 — the release before OpenClaw began bundling its own clawrouter plugin — so the id collision from #305 cannot occur there, and every other harness floats on @latest, which cannot hold a version-specific regression still. The unit tests mock homedir and never see the installer, while both production failures were installer-shaped.
npm run test:e2e:openclaw-collision drives the real installer against a pinned 2026.8.2. Opt-in, not wired into CI; it sandboxes HOME and strips BLOCKRUN_WALLET_KEY and the OPENCLAW_* overrides from the child environment, so it cannot touch a real wallet or config. From #320 by @twzrd-sol.
Fixed — the wallet rails never said which gateway they were using
Three rails, three gateways: an API key goes to api.blockrun.ai, a Solana wallet to sol.blockrun.ai, a Base wallet to blockrun.ai. Only two of them said so. /health reported gateway in API-key mode only, and startup logged the chain for Solana but printed nothing at all for Base — so the default rail was the one that never announced itself.
Which gateway a request went to is the single most useful fact when a paid call fails, and its absence cost a round trip on every report that needed it. All three now name it, in both /health and the startup log.