feat: Implement core application structure with new dashboard, settings, and help pages, and enhance opportunities management with persistence and filtering.

docs/phase-4-settings-help-reliability.md

@@ -0,0 +1,44 @@
+# Phase 4 — Settings, Help, Reliability, QA
+
+## Goals
+- Provide basic Settings and Help pages.
+- Improve reliability for long-running operations.
+- Add verification steps and basic test coverage.
+
+## Scope
+- Implement `/settings` and `/help` pages.
+- Add progress and error handling improvements for analysis/search.
+- Document manual QA checklist.
+
+## Detailed Tasks
+1. **Settings page**
+   - Account info display (name/email).
+   - API key setup instructions (OpenAI, Serper).
+   - Placeholder billing section (if needed).
+
+2. **Help page**
+   - Quickstart steps.
+   - Outreach best practices.
+   - FAQ for common errors (scrape failures, auth, API keys).
+
+3. **Reliability improvements**
+   - Move long-running tasks to Convex actions or background jobs.
+   - Track job status: pending → running → completed/failed.
+   - Provide progress UI and retry on failure.
+
+4. **QA checklist**
+   - Auth flow: sign up, sign in, sign out.
+   - Onboarding: URL analysis + manual analysis.
+   - Dashboard: correct rendering for project switch.
+   - Opportunities: search, save, status change.
+
+## Dependencies
+- Depends on Phases 1–3 to stabilize core flows.
+
+## Acceptance Criteria
+- `/settings` and `/help` routes exist and are linked.
+- Background tasks reduce timeouts and improve UX.
+- QA checklist is documented and executable.
+
+## Notes
+- Keep Settings minimal until billing/teams are defined.