provider-chat-smoke

# Provider Chat Smoke Use this skill with `interactive-testing`. Run the ordinary isolated-app workflow from that skill first; use real provider credentials only for the safe live gates below. Keep the scope to a disposable project, never approve a write, and preserve the smoke profile for inspection. ## Plan coverage before launch 1. Inspect the diff, generate the integration smoke plan, and record every provider/presentation surface in scope. 2. Separate gates into **live** (an authenticated provider and its real ACP server) and **deterministic** (mock/unit coverage for protocol branches that cannot safely be driven against an external provider). 3. Create a fresh thread per provider. Use short marker prompts such as `QWEN_SMOKE_OK` and `KIMI_SMOKE_OK`; never use repository-changing prompts. 4. Capture screenshots, runtime items, final thread state, and the first three console/runtime errors. Do not call the suite successful while a required gate is unresolved. ## Required live chat matrix Run each applicable row for every requested provider. Retry a timing-sensitive row with a longer harmless response if the provider finishes before the control can be used. | Gate | Drive through the real UI | Required evidence | | ----------------------- | -----------------------------------------...