Task 1
Local development
Run the locked Node and pnpm toolchain with local database and authentication configuration.
Steps
- 1Use Node 24 and pnpm 10.27.0.
- 2Install from the lockfile and configure the required local environment variables.
- 3Start Postgres, apply existing migrations, then run the Next.js development server.
Local commands
pnpm install --frozen-lockfile
pnpm db:up
pnpm db:migrate
pnpm devDo not run seed or migration commands against production without an explicit, reviewed data operation.
Task 2
Validation commands
Check types, lint, unit behavior, contracts, Storybook, browser flows, and the production build in proportion to the change.
Steps
- 1Run focused tests while editing.
- 2Run static analysis and the full unit project before opening a PR.
- 3For UI work, validate component contracts and inspect the rendered desktop and mobile flow.
- 4Require database, browser, Storybook, and production-build CI before merge.
Core local validation
pnpm typecheck
pnpm lint
pnpm test:unit
pnpm components:validate
pnpm test:browser
pnpm buildTask 3
Release readiness
Tie the merged commit, provider deployment, database readiness, authenticated flow, and runtime logs into one release decision.
Steps
- 1Confirm the PR head is current and every required check passed.
- 2Merge through the repository's PR workflow.
- 3Verify Vercel built the exact merge commit for the production target.
- 4Check /api/ready, the changed user journey, and deployment-scoped runtime errors.
Required evidence
GitHub: merged PR + green checks
Vercel: production target + READY + matching commit SHA
Runtime: /api/ready returns database status ok
Flow: changed behavior exercised without inventing production proof