smoke-testlisted

# SKILL: smoke-test — "done" includes that it STARTS (automated smoke) **Principle (P-10 · any stack/domain).** "Done" is not just that it compiles and unit tests pass: it includes an **artifact that STARTS**, proven by an **automated smoke** with a clear **pass/fail**. The studio **AUTHORS** the smoke; the PO/CI runs it with **ONE command**. Applies to any domain and any stack (desktop, web, CLI, service): the smoke confirms the binary/process boots and shows/exposes the essentials. > Why it exists: headless QA and unit tests do NOT catch **startup/integration failures of the packaged artifact** (init order, production paths, bundle load, handler registration). An automated smoke does — and it runs **with no human watching**. ## What it tests (and what it does NOT) - **YES:** the artifact STARTS + renders/exposes the ESSENTIALS (window/root + 2-3 key points). - **NO:** business logic — that's unit tests. Nor exhaustive coverage. The smoke is about STARTUP. - **P-11:** whatever can't be validated without a real environment (hardware, live data, network) is **DECLARED deferred**, not faked. ## Contract (invariant, any stack) - **ONE command** (`smoke` script) → **exit 0 = pass / exit 1 = fail**. CI-ready. - **Machine-readable evidence:** on finish it writes **`tests/smoke-result.json`** = `{ "pass": true|false, "ts": <epoch>, "screenshot": "tests/smoke.png" }`. The **RELEASE gate verifies it mechanically** (DoD): without a recent `smoke-result.json` with `pass:true`, r