[M5] Deploy vibeDeploy itself to DigitalOcean

[ComBba]

Overview

Deploy vibeDeploy itself: Agent to Gradient ADK, Frontend to App Platform.

Acceptance Criteria

• Agent deployed via `gradient agent deploy`
  • Agent URL accessible: `https://agents.do-ai.run/v1/{ws}/vibedeploy-agent/run\`
  • Health check passes: `GET /health`
  • All secrets set: DIGITALOCEAN_INFERENCE_KEY, GITHUB_TOKEN, DIGITALOCEAN_API_TOKEN
• Frontend deployed via App Platform
  • `NEXT_PUBLIC_AGENT_URL` points to deployed agent URL
  • Static site builds and serves correctly
  • Custom subdomain if possible
• Managed PostgreSQL provisioned (if DB features implemented)
• End-to-end test: submit idea → see meeting → get deployed app URL
• Error handling verified: bad input, API failures, deployment failures

Deploy Commands

```bash

Agent

cd agent/
gradient secret set DIGITALOCEAN_INFERENCE_KEY=
gradient agent deploy

Frontend

doctl apps create --spec .do/app.yaml
```

Dependencies

• [M2] LangGraph StateGraph: wire all nodes + SSE streaming entrypoint #15 (complete graph wiring)
• [M4] Frontend: Landing page with input form #12, [M4] Frontend: Live Meeting View with SSE streaming #13, [M4] Frontend: Result Dashboard (GO + NO-GO views) #14 (frontend pages)

Reference

• `docs/reference/10-technical-plan.md` — Deploy Commands

[ComBba]

Superseded by #74 and the pivot documents in docs/reference/15-18. This legacy hackathon-era issue is archived to keep the tracker aligned with the current product direction.