Engineering System

Every project includes unit, integration, and end-to-end tests. TypeScript strict mode catches type-level regressions at build time. Vitest runs fast feedback on business logic, and Playwright smoke tests verify the public, admin, and private-room flows from the user's perspective.

All services run in Docker — the database, the application, and CI steps. A single `docker compose up` starts a production-like environment with zero manual setup. The Dockerfile is multi-stage, producing the same image that Railway deploys to production.

GitHub Actions enforces linting, formatting, typechecking, unit tests, database migration checks, and a production build on every branch. Main is the deployable branch — Railway deploys from main after the quality gate passes, so the live site always reflects reviewed, tested code.

The codebase uses feature-first organization with thin routes. Business logic lives in `src/features/*` or `src/lib/*`, not inside page files. Next.js App Router pages compose tested feature modules, keeping the surface area small and the behavior easy to change.

Every significant technical decision is documented as an ADR in `docs/adr/`. Each record describes the context, the decision, and the trade-offs — so a new engineer (or my future self) can understand why the system is shaped the way it is, not just what was built.

Projects ship in visible milestones — completed, current, and upcoming work is public. The Build Log captures dated progress updates, and private client rooms expose curated milestone views so clients always know where their project stands.