# Agent-Built App Before Deploy Checklist

This checklist is for apps built or heavily modified by AI agents. A local demo is not a launch signal. VibeRaven turns repo evidence into a production-readiness tasklist before the app reaches real users.

## Original Angle

Most deploy checklists assume a human already knows what was wired and what was guessed. This checklist starts from the AI-built-app failure mode: the app may look complete while auth, RLS, billing, env vars, webhooks, and monitoring are only partly evidenced.

## Unique Contribution

Treat every item as an evidence request to the agent. The useful answer is not "yes, implemented"; it is a file path, config name, migration, policy, webhook handler, or VibeRaven gap artifact that proves the claim.

## Not A Generic SEO Page

This page is intentionally scoped to agent-built apps before deploy. It is not a broad launch checklist for every startup, and it separates repo-code fixes from provider dashboard work.

## Start Here

```bash
npx -y viberaven init --agents all
npx -y viberaven --agent-mode
```

Use the install command to add agent rules, then run the canonical production gate. Agents should read `.viberaven/agent-tasklist.md`, `.viberaven/gate-result.json`, and `.viberaven/context-map.json` before editing.

## Before Deploy

- Confirm auth is enforced on server routes, API handlers, and user-owned data.
- Confirm database migrations, RLS policies, backups, and data ownership are represented by repo evidence.
- Confirm billing and webhook code verifies signatures and handles subscription state.
- Confirm environment variables and deployment config are documented without secrets.
- Confirm monitoring, logging, and first-user paths have evidence.
- Fix one VibeRaven repo-code gap at a time, then verify in batches.

## Provider Boundary

Provider dashboard checks are not fixed by repo edits alone. Repo edits can document expected settings and add validation, but production billing, DNS, webhook registration, live credentials, quotas, and dashboard-only toggles need provider-side confirmation.

## MCP Note

If VibeRaven MCP tools are available through the MCP registry, agents can use them for readiness checks and verification. If not, run the CLI commands above.