[Backend] Add Request Correlation IDs

[Abd-Standard]

Description

Improve debugging by attaching unique correlation IDs to every incoming request.

Tasks
Generate IDs per request.
Include IDs in logs.
Return IDs in API responses.
Update documentation.

Acceptance Criteria
All requests have correlation IDs.
Logs can be traced end-to-end.
Documentation reflects implementation.

[naninu123]

Hi, I'd love to work on this.

My background includes merged GrantFox PRs across Core-Foundry, Flux-DeFi, StellarLend, and aid-linkk. I'm comfortable across Rust/Soroban, TypeScript, and backend stacks.

Process:

1. Clone and review the relevant code paths
2. Implement clean, minimal changes
3. Test thoroughly and open a PR

I'm ready to begin now.

[barry01-hash]

My chief, i will love to work on this issue

[MoscowDev]

I'd like to take this issue.

This is primarily an observability and operational debugging improvement rather than a simple middleware addition. My goal would be to ensure a correlation ID follows a request throughout its entire lifecycle so engineers can trace failures and behavior across logs consistently.

My implementation approach would be:

• Add request-level correlation ID generation using a UUID-based strategy.

• Support propagation of an existing incoming correlation ID header when present, generating a new one only when absent.

• Attach the correlation ID to the request context so downstream handlers and services can access it consistently.

• Ensure all application logs include the correlation ID to enable end-to-end request tracing.

• Return the correlation ID in API responses (and optionally expose it through a response header) so clients can reference it when reporting issues.

• Review error-handling paths to ensure correlation IDs remain available for both successful and failed requests.

• Add automated coverage verifying:

  • IDs are generated when absent
  • Existing IDs are propagated correctly
  • Response payloads/headers include the ID
  • Log context contains the expected correlation ID

• Update developer documentation with:

  • correlation ID format
  • request/response behavior
  • logging examples
  • troubleshooting workflow using correlation IDs

The goal is to make every request traceable from ingress through application logs and back to the client, improving debugging, incident response, and operational visibility.

[DavisVT]

studied the task at hand and i can say i have a clear understanding
pls assign me so i can begin implementation

[grantfox-oss]

🦊 GrantFox — @DavisVT has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #127)
2. Your PR will be reviewed by the Core-Foundry maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

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

@DavisVT's PR #160 was approved and merged by @Abd-Standard.

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

👏 Great work, @DavisVT! Keep contributing to Core-Foundry.