interactive-testing

# Interactive Testing — Poracode Test the real Electron renderer, preload bridge, main process, and supervisor integration. Treat unit tests as complementary; do not substitute them for this workflow when the skill triggers. ## Required workflow 1. Inspect `git status --short` and the relevant diff. 2. Choose the validation shape below before launching anything. 3. For an ordinary quick or full smoke, run its one-command runner directly; it creates the isolated fixture, boots the app, derives the scope plan, runs the checks, and tears the app down. 4. For a manual live check, generate the plan, then start or reuse one managed debug session: ```sh node .agents/skills/interactive-testing/scripts/poracode-integration-smoke.mjs plan --scope changed node .agents/skills/interactive-testing/scripts/run-poracode-smoke.mjs --launch-only --mode mock ``` 5. Audit the functional inventory only when changing `scripts/smoke-scenarios.mjs`, adding a production surface, or investigating coverage selection: ```sh node .agents/skills/interactive-testing/scripts/poracode-integration-smoke.mjs audit ``` 6. Use fixture projects, deterministic store state, and mocked provider/auth/runtime data for local regression coverage. The runner executes these gates automatically and reports them as `mocked`. 7. Use `--mode real` only when real credentials, devices, or external services are intentionally available; complete and acknowledge those gates with `--ack-manual`. 8. Reset...