Logs estructurados y trazas

[Kalebtron1]

Why this matters

Visibility into request failures and tracing makes production debugging faster and less painful.

Problem

Logs are inconsistent across services and do not make incident triage easy.

Scope

• Standardize structured logging in the API layer.
• Add request IDs and log context for the affected flows.
• Keep the output readable for local development and production.

Implementation guidance

• Use the existing API handlers in api/calculate-score.js, api/evaluate-and-mint.js, api/get-available-credit.js, and api/get-user-data.js as the main touch points.
• Reuse shared error mapping where possible.
• Keep the message tone actionable and concise.

Out of scope

• Redesigning the application telemetry stack.
• Adding a full observability platform integration.

Acceptance criteria

• PR includes the logging changes in the listed API files.
• Reviewer can reproduce the flow with npm run dev and observe consistent logs.
• A production build still passes and the PR description includes sample log output or screenshots.

Validation

• Run npm run dev and exercise the affected flow.
• Run npm run build before opening the PR.
• Confirm logs contain the request context for the touched endpoint.

PR requirements

• Include Closes #34.
• Include before/after behavior notes.
• Mention any log format assumptions that reviewers should know.

Complexity

• Medium (100 points)

[oncleweynom]

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

gm mainatainer would love to work on this

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

[Escelit]

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

I’d like to work on this issue because it contributes to improving the project's functionality, reliability, and overall user experience. I enjoy working on open-source projects and collaborating with maintainers to deliver clean, maintainable solutions.

I have experience with software development across frontend, backend, testing, and debugging tasks. I’m comfortable working with existing codebases, following project guidelines, writing tests, and ensuring changes are well-documented. I can investigate the current implementation, propose a clear solution, and deliver a high-quality contribution that meets the acceptance criteria.

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

[drips-wave]

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

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