Todo

README.md

@@ -1,5 +1,7 @@
 # CMS Monorepo (Bun + Biome + Next.js)
 
+Roadmap and progress are tracked in `TODO.md` (also visible in admin at `/todo`).
+
 A baseline monorepo with:
 
 - `apps/web`: public frontend app
@@ -56,6 +58,10 @@ bun run dev
 - `bun run dev`
 - `bun run dev:web`
 - `bun run dev:admin`
+- `bun run test`
+- `bun run test:watch`
+- `bun run test:coverage`
+- `bun run test:e2e`
 - `bun run lint`
 - `bun run typecheck`
 - `bun run check`
@@ -66,6 +72,47 @@ bun run dev
 - `bun run db:studio`
 - `bun run db:seed`
 
+## Testing
+
+- Unit/integration/component: Vitest + Testing Library + MSW
+- E2E: Playwright (separate projects for `web` and `admin`)
+- Use `bun run test` and `bun run test:e2e` (not plain `bun test`, which uses Bun's runner)
+
+One-time Playwright browser install:
+
+```bash
+bunx playwright install
+```
+
+## Delivery Scaffolding
+
+The repo includes a theoretical CI/CD and deployment baseline:
+
+- Gitea workflow: `.gitea/workflows/ci-cd-theoretical.yml`
+- App images:
+  - `apps/web/Dockerfile`
+  - `apps/admin/Dockerfile`
+- Runtime stacks:
+  - `docker-compose.staging.yml`
+  - `docker-compose.production.yml`
+
+Compose helper scripts:
+
+- `bun run docker:staging:up`
+- `bun run docker:staging:down`
+- `bun run docker:production:up`
+- `bun run docker:production:down`
+
+Environment examples:
+
+- `.env.staging.example`
+- `.env.production.example`
+
+Notes:
+
+- `dev` remains your local non-docker Bun workflow.
+- Staging and production compose files are templates and still require real secrets, registry strategy, and deployment host wiring.
+
 ## Recommended next packages
 
 - Auth: `better-auth` or `next-auth`