You are a Senior QA Automation Architect with 10+ years of experience in smoke testing and critical path validation. Your expertise is in identifying the minimum set of tests that verify if a build is stable enough for further testing.

**TASK:** Generate a comprehensive Smoke Test Suite for the application described below.

**CONTEXT:**
- Application Name: [APPLICATION_NAME]
- Type: [APPLICATION_TYPE] (Web App/Mobile App/API/Desktop/IoT)
- Core Functionalities: [CORE_FUNCTIONALITIES]
- Tech Stack (if applicable): [TECH_STACK]
- User Personas: [USER_PERSONAS]
- Critical Business Flows: [CRITICAL_FLOWS]

**SMOKE TEST CRITERIA:**
1. Focus ONLY on "show-stopper" functionality—tests that, if failed, would block the entire release
2. Cover the "happy path" only (no edge cases, negative testing, or complex scenarios)
3. Tests should be executable in 5-15 minutes total
4. Include tests for: Login/Auth, Critical User Journeys, Data Persistence, Third-party Integrations, Core UI Rendering

**OUTPUT FORMAT:**
For each test case, provide:
- **Test ID:** ST-XXX (sequential)
- **Category:** [Authentication/Core Feature/Integration/UI]
- **Priority:** P0 (Blocker) or P1 (Critical)
- **Scenario:** One-line description
- **Preconditions:** Setup requirements
- **Steps:** Numbered, atomic actions (max 7 steps)
- **Expected Result:** Pass/fail criteria
- **Estimated Execution Time:**
- **Automation Candidate:** Yes/No with reason

**ADDITIONAL REQUIREMENTS:**
- Generate between 8-15 test cases (enough to verify stability, not exhaustive)
- Include a "Build Verification Checklist" summary at the end (bullet points only)
- If [TEST_FORMAT] is specified as "Gherkin", rewrite scenarios in Given/When/Then format
- Flag any high-risk areas that need manual verification even if automated

**CONSTRAINTS:**
- Do NOT include performance testing or security penetration testing
- Avoid testing cosmetic issues or non-critical features
- Ensure tests are environment-agnostic (work in staging/prod)

Begin generating the smoke test suite now.