Add distributed tracing and dependency readiness probes across core services

[Viky207]

Objective

Deliver add distributed tracing and dependency readiness probes across core services as a production-ready capability for QuickEx. This is an advanced issue: preserve self-custody, the documented API contracts, and the financial invariants while handling failure and rollback paths.

Scope

• Trace the owning implementation across app/frontend, app/backend, app/mobile, and app/contract as applicable.
• Replace mocks or placeholders with the smallest maintainable production design.
• Define authorization, idempotency, validation, observability, and degraded-mode behavior.
• Update the relevant capability map, contract map, or release documentation.

Acceptance criteria

• The behavior is implemented end to end for the supported network and is explicitly feature-gated where it is not ready for mainnet.
• Unauthorized, duplicate, expired, malformed, and dependency-failure cases are covered with stable errors.
• Tests cover the happy path, boundary conditions, retries, and recovery or rollback behavior.
• Metrics and structured logs make success, latency, and failure diagnosable without exposing secrets or unnecessary personal data.
• Documentation names the changed contract, configuration, migration, and operational procedure.

Workstream

Notifications, webhooks, observability, and operations

References

Start with docs/CAPABILITY-MAP.md, docs/BACKEND-CLIENT-CONTRACT-MAP.md, and docs/INVARIANTS.md; use the owning module and neighboring tests as the implementation authority.

Contributor notes

Before opening a PR, record assumptions about network, custody, and backward compatibility. Include test commands and any follow-up migration or rollout issue in the PR description.

[paulolubanwo391-cloud]

@paulolubanwo391-cloud has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

Hi, I’d like to take this issue.

I’ll start from the capability, contract map, and invariants docs to trace the owning implementations across the core services. I’ll then add production-safe tracing and dependency readiness checks with feature-gating where required, covering failure, retry, and degraded-mode behavior.

I’ll also add focused tests and update the relevant operational documentation without exposing secrets or changing financial invariants.

Please assign it to me.

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

[NoahJoseph-ux]

@NoahJoseph-ux has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

I’ve thoroughly reviewed the requirements and will implement a clean, well-structured solution that satisfies the acceptance criteria.

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

[CryptoverseOG]

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

Hi Maintainer, I’d like to contribute to this issue. I’ve reviewed the requirements and believe I can implement the necessary changes in a clean and maintainable way.

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

[orsar-rita]

@orsar-rita has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

can i work on this issue please, thank you

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

[drips-wave]

Congratulations, @orsar-rita! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on September 30, 2026.

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

[drips-wave]

This issue has been completed by @orsar-rita as part of the Stellar Wave Program's 9th Wave 🥳

😎 @orsar-rita: You earned 200 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.