feat: add correlation-id propagation on /api/logs handlers

[Faree-code]

Overview

This PR creates a new /api/logs router that applies correlationMiddleware to all routes, ensuring the X-Correlation-Id header is propagated through every log handler and any outbound calls they make. The router is mounted at /api/logs in the main Express app.

Related Issue

Closes #917

Changes

• [ADD] src/routes/logs.ts

  • GET /api/logs — lists audit log entries for the authenticated developer (max 50), includes correlationId in response
  • GET /api/logs/:id — fetches a single log entry by ID, owned by the authenticated developer (cross-user access returns 404)
  • Both routes apply correlationMiddleware for X-Correlation-Id propagation and requireAuth for authentication
  • Dependency injection via LogsRouterDeps interface for testability

• [MODIFY] src/app.ts

  • Imported createLogsRouter and mounted at /api/logs

Verification Results

npx jest --no-coverage src/middleware/correlation.test.ts
✅ 27/27 passed

npx tsc --noEmit
✅ No compilation errors

Acceptance Criteria	Status
X-Correlation-Id propagated through /api/logs	✅ correlationMiddleware applied router-wide
GET /api/logs returns audit entries	✅ Backed by PgAuditLogRepository
GET /api/logs/:id returns single entry	✅ With ownership check (404 for cross-user)
Existing correlation tests still pass	✅ 27/27 passing
TypeScript compilation	✅ No errors

[drips-wave]

@Faree-code Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[greatest0fallt1me]

Merged into main via admin resolver (-X theirs).

[greatest0fallt1me]

All checks green — merging. Nice job! 🚀