Run Smoke Tests

Execute a broad user journey against a real build and leave enough evidence for a person to audit the judgment. Understand the host project before starting the product or touching its state.

Operating contract

• Treat the Markdown as runtime instructions, not source to compile into code.
• Test through a supported user-facing surface: web UI, API, CLI, desktop, mobile, or a documented combination.
• Separate execution from repair. Do not edit the product, tests, or journey during a run. Finish the report before starting any requested fix.
• Default to local, test, preview, or staging environments. Never mutate production, spend money, send real invitations, or change real user data without explicit authorization.
• Make every pass or fail claim traceable to captured evidence.
• Keep the first failed run. Do not erase evidence by retrying until green.