9ce34d8ca49405fba3f62bfd02790b244bca44c8
Phase 0 research resolves module placement (problem-management/problems confirmed dead/unwired, left untouched), Investigation's version-row-per- attempt shape, the strict investigation->root-cause->solution-> implementation->verification existence chain, why Resolution has no solutionId FK (matches doc06 exactly), why verification-failure escalation reuses 003/007's plain HUMAN_ESCALATION transition instead of adding an eleventh trigger type to 008's already-shipped escalation rules, the customer-facing route design (reusing 002's inbound trust boundary rather than fastify.authenticate), and the auto-close sweep design (the already-defined-but-unused CLEANUP queue, mirroring 008's breach-detection job). Phase 1 adds data-model.md, the admin/customer-facing contract, and six quickstart scenarios covering the full sequential workflow through customer confirmation, auto-close, and reopen. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Development
- docker compose --env-file .env.development -f docker-compose.development.yml up -d --build
Test
- docker compose --env-file .env.test -f docker-compose.test.yml up --build
Production
- docker compose --env-file .env.prod -f docker-compose.prod.yml up --build -d
Stop
- docker compose -f docker-compose.prod.yml down
list containers
- docker compose --env-file .env.development -f docker-compose.development.yml ps
logs
- docker compose --env-file .env.development -f docker-compose.development.yml logs -f
Languages
TypeScript
93.2%
PowerShell
6.5%
JavaScript
0.2%