feat: scaffold next-postgres-shadcn full stack developer harness

[ryaneggz]

Summary

• Scaffolds a Full Stack Developer agent workspace with Next.js + TypeScript + PostgreSQL + shadcn/ui
• Project isolated in workspace/next-app/ keeping agent harness files (SOUL.md, MEMORY.md, heartbeats) at workspace root
• Docker Compose override adds PostgreSQL 16 on an isolated bridge network (${NAME}-devnet)

Stack & Tooling

• Next.js 15+ (App Router, TypeScript strict, src/ directory)
• PostgreSQL 16 + Prisma ORM
• shadcn/ui + Tailwind CSS + next-themes (light/dark/system)
• PWA via next-pwa
• Testing: Vitest + React Testing Library + Playwright
• Linting: ESLint + Prettier + lint-staged
• Hooks: Husky pre-commit (lint + format + type-check + tests)
• CI: GitHub Actions mirrors pre-commit with Postgres service container
• Infrastructure: cloudflared tunnel (next-postgres-shadcn.ruska.dev), agent-browser + Chromium for QA
• Ralph: Autonomous agent orchestrator

Files Changed

• docker/docker-compose.nextjs.yml — PostgreSQL + isolated network + port 3000
• workspace/SOUL.md — Full Stack Developer persona
• workspace/MEMORY.md — Seeded stack decisions
• workspace/AGENTS.md — Stack-specific guidance (DB, shadcn, testing, CI, tunnel, QA)
• workspace/next-app/ — Scaffolded Next.js project with all tooling configured
• workspace/heartbeats/build-health.md — Periodic build + test health check
• .github/workflows/ci.yml — CI pipeline with Postgres service
• .github/ISSUE_TEMPLATE/{feature,bug}.md — Stack-tailored templates
• README.md — Setup guide with post-provisioning auth steps

Test plan

• Container starts and workspace files are accessible
• cd next-app && npm run build succeeds
• npm test passes (Vitest)
• npm run lint && npm run format:check && npm run type-check all clean
• PostgreSQL reachable via psql -c "SELECT 1" (requires compose nextjs override)
• Cloudflared tunnel connects to next-postgres-shadcn.ruska.dev (requires auth)
• Git commit triggers Husky pre-commit hooks
• CI workflow runs on push

Closes #22

🤖 Generated with Claude Code

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
29850720	Triggered	Generic High Entropy Secret	389861c	workspace/startup.sh	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}