smoke-testinglisted

# Smoke Testing > **Style:** Mode-B-lite. Outcome-first smoke discipline for Product Owner definition and AI Developer execution. ## Purpose Prevent pre-outcome signals from being mislabeled as smoke success. A smoke test passes only when the operator-visible action works on the deployed surface and the system's ground-truth diagnostics show no hidden failure. ## When to invoke - Product Owner drafts `verification-gate.md` for a user-facing or operator-facing change. - Product Owner drafts `docs/tmp/handoff/<date>-<slug>-deploy.md` and includes S1..Sn smoke prompts. - AI Developer / Deploy phase runs post-deploy smoke prompts. - A previous smoke missed a production bug and the smoke method must be corrected. - Operator asks whether smoke evidence is sufficient. ## Do not invoke when - The task is only pre-deploy source validation: lint, typecheck, unit tests, static bundle checks, file hash checks. - No deployed or runtime behavior exists to exercise. - A live user session is required but consent/session handling is not available; invoke `workflows/live-user-verification.md` first. ## Required inputs | Input | Where it lives | If missing | |---|---|---| | Operator-visible success criterion | `verification-gate.md` smoke section | PO must write it before designing checks | | Smoke prompts S1..Sn | `docs/specs/<slug>/verification-gate.md` | Stop; smoke cannot be improvised after deploy | | Deployed surface / base URL / command | deploy handoff | Stop; ask PO to amend h