A key that fails verification is replaced from the wizard and the connection becomes Active

Verification Boundary

This browser suite exercises the console journey for a key that fails verification is replaced from the wizard and the connection becomes active. Its registration records the executable definition; no run result is asserted.

What This Suite Proves

The suite contains executable checks, but no detailed scenario binding is verified in this pass.

What It Does Not Prove

A mock run does not establish deployed persistence, provider effects or service authorization. The suite does not establish a complete feature sequence merely because it visits several screens.

Real Dependencies and Test Doubles

The deployed mode uses the console and acceptance service clients. The mock mode substitutes responses through the harness. Run records and the suite definition identify any live-only or unavailable step.

Must Not Be Doubled

The console interactions and assertions for a claimed browser outcome must execute. A deployed claim also requires the service and persistence effects checked by that step.