Observability: request ID middleware coverage (`requestId`)

[greatest0fallt1me]

Description

Verify request IDs propagate to logs and error responses consistently.

Requirements and context

• Ensure IDs are unguessable enough for correlation (UUID/etc.).
• No PII in IDs.

Suggested execution

• Fork the repo and create a branch: git checkout -b test/request-id-middleware
• Work in Callora-Backend (TypeScript / Express).

Primary paths

src/middleware/requestId.ts, src/middleware/logging.ts

• Run npm run lint, npm run typecheck, and npm test.

Deliverables

• Middleware tests.

Test and commit

• Add or extend unit and/or integration tests (src/**/*.test.ts, tests/integration/**).
• Paste summarized test output in the PR; call out security or data-integrity notes.

Example commit message

test(observability): requestId propagation

Guidelines

• Tests should cover new behavior and important edge cases.
• Keep changes focused; follow existing patterns in the codebase.
• Timeframe: 96 hours from assignment unless agreed otherwise.

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 200 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[Banx17]

@Banx17 has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

I’m a backend developer with strong experience in JavaScript, TypeScript, Node.js, and Express, especially around observability and middleware testing. I’ve worked on request correlation flows, structured logging, and ensuring error responses consistently include traceable request IDs without exposing sensitive data.

I would love to work on this issue by adding focused middleware tests to verify UUID-based request ID propagation across logs and error responses, including edge cases and security checks. My ETA is 5 hour.

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

[drips-wave]

Congratulations, @Banx17! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on March 30, 2026.

🧑‍💻 @Banx17: 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 🌊