Configure Convex Cloud for the MVP and define the core persistence model for campaigns, leads, audits, outreach records, blacklist entries, run logs, and screenshot/file storage. The goal is a typed backend foundation that can support the dashboard, agent pipeline, and public audit pages.
Acceptance Criteria
#1 Convex is connected to the Next.js app with generated types available
#2 Core tables exist for campaigns, leads, audits, outreach, blacklist, run logs, and settings metadata
#3 Convex File Storage is ready for desktop and mobile screenshots
#4 Run-status and error-log concepts are represented so background jobs are observable
#5 No API keys or secrets are stored in user-editable database records
Implementation Plan
Add Convex project configuration and connect it to the app.
Define schemas for Campaign, Lead, Audit, Outreach, BlacklistEntry, and AgentRun.
Add storage conventions for screenshot files and audit assets.
Add basic queries/mutations for creating and reading core records.
Verify Convex generation and typechecking work locally.
