chore: initial project scaffold

[casualzach]

What

Scaffolds the full project harness: Next.js 16, Supabase clients, Sentry, health endpoint, landing page, CI, devcontainer, agent knowledge base, and product spec. Ready for Vercel deployment.

How

• create-next-app with TypeScript, Tailwind, App Router, and src/ directory
• Supabase SSR clients (browser, server, middleware) for auth session management
• Sentry integration via @sentry/nextjs with instrumentation hooks and global error boundary
• /api/health endpoint with DB connectivity check
• CI workflow: lint → typecheck → test on every PR
• Agent knowledge base (.agents/) with architecture, conventions, and quality tracking
• Product spec defining scope, priorities, and technical direction

Testing

• pnpm lint ✅
• pnpm typecheck ✅
• pnpm build ✅
• Dev server verified with curl

Checklist

• CI passes
• No any types
• Tests added for new logic (framework configured, no app logic yet)
• Screenshots attached (if UI changes) — N/A, landing page only

[vercel]

@casualzach must be a member of the Ona team on Vercel to deploy.
- Click here to add @casualzach to the team.
- If you initiated this build, request access.

Learn more about collaboration on Vercel and other options here.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
memo	Error		Apr 14, 2026 2:37pm

[casualzach]

Reviewed the full diff against AGENTS.md conventions. No blocking issues.

Correctness — Health endpoint handles missing tables gracefully, Supabase SSR clients follow the official pattern, middleware matcher is correct, Sentry integration is properly wired.

Security — No hardcoded secrets, .env* excluded via .gitignore, .env.example has placeholders only.

Conventions — Strict TypeScript, server components by default, "use client" only on global-error.tsx (required), Tailwind-only styling, conventional commit format. Default exports used only where Next.js requires them.

Testing — Vitest and Playwright configured. No app logic yet, so no tests needed.

Scope — All changes are scaffold-related. No unrelated modifications.

Approving.