# Agent instructions ## Simulation test suite - `cargo run --features testing` is the simulation test-suite entry point. It must run named scenarios and print a pass/fail summary. - The `testing` feature must route authorization, browser opening, credential storage, and Git configuration through fake implementations. Simulation runs must never contact Twig, open a real browser, access the OS keyring, invoke Git, or modify machine credentials/configuration. - Do not compile production adapters into a testing-feature binary; normal `cargo test` covers those adapters, while `cargo test --features testing` must remain isolated too. - Keep simulation credentials fake and in memory. Do not add hidden fallback to real services when a fake operation fails. - When changing authentication or credential-helper behavior, run `cargo run --features testing` as well as the relevant Rust tests.