clawbot
5af89a1b63
All checks were successful
check / check (push) Successful in 38s
ConfirmTx -- the screen that decides what gets signed -- had no automated coverage of its own behaviour. The arithmetic underneath was well tested; the wiring was not, so a mutant making the spend gate read the displayed fee estimate instead of the reserve would have reintroduced the #154 overspend with the suite still green. Nine end-to-end tests now drive it for both the native and ERC-20 paths, covering the pending, funded, over-balance and estimate-failed states, and asserting that the gate reads the reserve rather than the estimate. Swapping the two makes the suite fail. The view height is asserted constant across every state transition rather than merely printed. Reaching the screen needs a funded balance and a gas estimate, so the route interception gains fixtures for both. Testing the estimate-failed state means provoking the console error the code is supposed to emit, which the harness otherwise fails a run on; an expectation mechanism consumes exactly one matching record, is scoped to the declaring test, and fails that test if nothing matched, so it cannot mask an unrelated error.