Description
Git history (git log) shows a full rebuild from Express to NestJS happened (commit history references "Nest rebuild complete"), which is a significant architectural decision, but there's no ADR or written record of why it happened or what alternatives were considered — that context currently only lives in commit messages.
Requirements and context
- This is worth capturing now while the reasoning is still fresh among the team, before it becomes tribal knowledge that's lost
Suggested execution
- Fork the repo and create a branch
git checkout -b docs/backfill-nestjs-rebuild-adr
- Implement changes
Relevant files:
docs/adr/0000-express-to-nestjs-rebuild.md
-
Test and commit
- Run
npm run lint && npm run typecheck && npm test && npm run test:e2e
- Include test output / screenshots or logs demonstrating the fix in the PR
Example commit message:
docs: backfill ADR for the Express to NestJS rebuild
Guidelines
- Assignment required before starting — comment to claim this issue
- PR description must include:
Closes #[this issue's number]
- Timeframe: 96 hours from assignment
- Complexity: High (200 points)
Part of the Drips Wave for vortex-backend.
Description
Git history (
git log) shows a full rebuild from Express to NestJS happened (commit history references "Nest rebuild complete"), which is a significant architectural decision, but there's no ADR or written record of why it happened or what alternatives were considered — that context currently only lives in commit messages.Requirements and context
Suggested execution
Relevant files:
docs/adr/0000-express-to-nestjs-rebuild.mdTest and commit
npm run lint && npm run typecheck && npm test && npm run test:e2eExample commit message:
Guidelines
Closes #[this issue's number]Part of the Drips Wave for vortex-backend.