Make request logging, correlation IDs, and PII redaction idempotent in `src/middleware/access-log.ts`

[Jagadeeshftw]

Description

Repeated delivery or retrying the same request can currently produce ambiguous outcomes. src/middleware/access-log.ts owns request logging, correlation IDs, and PII redaction, but the current behavior does not yet define the contract tightly enough for safe maintenance. Design the change so the runtime path, tests, and docs all describe the same behavior.

Requirements and context

• Keep the contract specific to src/middleware/access-log.ts and its existing callers.
• Add coverage for the success path and the failure or boundary path relevant to this issue.
• Preserve compatibility where older callers or existing tests already rely on the current shape.
• Keep the change easy to review and small enough for one focused PR.

Suggested execution

Fork the repo and create a branch

git checkout -b access-log-redaction-idempotency-169

Implement changes

• Update/Write: src/middleware/access-log.ts
• Write comprehensive tests: src/middleware/access-log.test.ts
• Add documentation: docs/middleware/access-log.md
• Keep any new helper names consistent with the rest of src/

Test and commit

• Run pnpm test
• Run pnpm lint
• Add a note for any edge cases that are intentionally out of scope

Example commit message

fix: add idempotency and duplicate-request protection

Guidelines

• WCAG 2.1 AA is not relevant here; keep the focus on correctness and maintainability.
• Prefer a narrow, well-documented fix over a broad refactor.
• Timeframe: 96 hours

[ojuotimi932]

@ojuotimi932 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi Maintainer Can I resolve this kindly assign
ETA one hour

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

[Jagadeeshftw]

Thanks for applying here. Please also join our Telegram group here: https://t.me/+vTbe0hOUKrFhNTJl. It helps us keep communication clear while we review contributions.

[drips-wave]

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

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

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign | FWC26 campaign!

@ojuotimi932's PR #525 was approved and merged by @Jagadeeshftw.

🏆 @ojuotimi932: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (153 total points). Track your full progress on GrantFox.

👏 Great work, @ojuotimi932! Keep contributing to Stellopay.

[drips-wave]

This issue has been completed by @ojuotimi932 as part of the Stellar Wave Program's 7th Wave 🥳

😎 @ojuotimi932: You earned 100 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.