Set up dev environment + document DB bootstrap

[DealPatrol]

Summary

Set up and verified the RepoFuse development environment end-to-end, and added two durable, non-obvious notes to AGENTS.md for future agents.

What was done

• Installed dependencies with pnpm install (Node 22, pnpm 10.33).
• Ran static checks: npx tsc --noEmit passes; pnpm lint has only pre-existing errors/warnings.
• Started the dev server (pnpm dev) and confirmed the app boots and the homepage renders.
• Provisioned an isolated Neon branch, initialized the schema via /api/setup/init-db, and exercised the core product flow: authenticated via the cookie bypass → dashboard → created an analysis ("My First RepoFuse Analysis") against a seeded repository, with data persisting to Postgres.

AGENTS.md additions

• /api/setup/init-db is the idempotent way to bootstrap the schema (the psql path in README.md does not work with the Neon HTTP driver).
• Clarified how the github_user_id / github_access_token cookie bypass authenticates when DATABASE_URL is set (a matching user_auth row must exist).

Notes

• No source/runtime code was changed.
• The local .env.local (gitignored) and the provisioned Neon branch were used only for the setup demo; full GitHub OAuth and AI blueprint generation still require user-provided secrets.

  

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
repo-app-architect	Ready	Preview, Comment	Jun 21, 2026 11:10pm
repofuse	Ready	Preview, Comment, Open in v0	Jun 21, 2026 11:10pm
v0-repo-app-architect	Ready	Preview, Comment, Open in v0	Jun 21, 2026 11:10pm