docs(roadmap): record backend startup logging

This commit is contained in:
Saravana Achu Mac 2026-05-05 11:00:58 -07:00
parent 7016fc1ad5
commit 45b03c482a

View File

@ -170,7 +170,7 @@ Acceptance criteria:
Goal: backend behavior is production observable, testable, and consistent with common platform service conventions.
- [ ] **P5.1** Replace raw `process.stdout.write` / `process.stderr.write` in backend startup paths with app logger or shared logger-compatible handling. Commit:
- [x] **P5.1** Replace raw `process.stdout.write` / `process.stderr.write` in backend startup paths with app logger or shared logger-compatible handling. Commit: `7016fc1`; Verified: `GITEA_NPM_TOKEN=dummy pnpm --filter @notelett/backend run typecheck`; `GITEA_NPM_TOKEN=dummy pnpm --filter @notelett/backend exec vitest run src/server.test.ts src/modules/note-prompts/scheduler.test.ts`; `rg -n "process\\.(stdout|stderr)\\.write" backend/src --glob '!**/*.test.*'` returned no matches; `git diff --check`. Routed Cosmos startup diagnostics through `@bytelyst/logger`, passed the Fastify app logger into the scheduler loop, and updated server bootstrap coverage to assert logger propagation.
- [ ] **P5.2** Ensure request IDs are propagated to extraction-service, platform-service, blob, LLM, webhook, and MCP calls where supported. Add tests for local propagation helpers. Commit:
- [ ] **P5.3** Add health/dependency readiness coverage for datastore, encryption, platform-service, extraction-service, and MCP. Prefer `@bytelyst/monitoring` patterns if suitable. Commit:
- [ ] **P5.4** Add structured error mapping tests for validation, auth, forbidden, not found, conflict, extraction failure, LLM timeout, and blob failure paths. Commit: