Propagate correlation_id and stream_id through all stream lifecycle route logs

[greatest0fallt1me]

Description

Several routes import getCorrelationContext from app/lib/logger.ts but never use it (e.g. start, pause, settle import it yet log nothing structured), so logs lack the correlation_id/stream_id propagation the project's logging story promises. Wire structured, correlated logging through every lifecycle route. This is a backend observability task.

Requirements and Context

• Emit structured logger.info/warn/error entries on each lifecycle action with correlation_id, stream_id, action, and resulting status.
• Remove the unused getCorrelationContext imports or actually consume them; ensure correlation-middleware.ts context is in scope.
• Redact secrets/PII per app/lib/privacy.ts and the README secret-redaction policy.
• Must be secure, tested, and documented
• Should be efficient and easy to review

Suggested Execution

1. Fork the repo and create a branch

   git checkout -b task/correlated-lifecycle-logging

2. Implement changes
   • app/api/streams/[id]/{start,pause,stop,settle,withdraw}/route.ts
   • Reuse app/lib/logger.ts and app/lib/correlation-middleware.ts
3. Test and commit
   • npm test -- app/lib/logger.test.ts app/lib/correlation-middleware.test.ts
   • Cover edge cases: correlation_id present in logs, redaction of recipient PII
   • Include test output and notes in the PR

Example commit message

task: propagate correlation and stream ids in lifecycle logs

Acceptance Criteria

• Every lifecycle action logs correlation_id + stream_id
• No unused logger imports remain
• PII/secrets redacted in logged fields
• Coverage ≥ 90% for logger/correlation libs

Guidelines

• Minimum 90% test coverage including redaction
• Clear documentation and inline comments
• Timeframe: 96 hours

[greatKhalifa-code]

@greatKhalifa-code has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Hello maintainer i'll like to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @greatKhalifa-code to this issue.

[drips-wave]

Congratulations, @greatKhalifa-code! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

🧑‍💻 @greatKhalifa-code: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊