[Wave 6 15/15] Structured failure catalog for cross-chain order lifecycle

[karagozemin]

Stellar Wave #6 - Apply via the Stellar Wave Program on Drips. Use the Wave application flow. Maintainers review applicants on the Drips maintainer dashboard.
Wave window: 2026-06-23 09:00 UTC -> 2026-06-30 09:00 UTC.

Summary

Cross-chain order failures should use stable error codes so the coordinator, resolver, frontend, and docs can speak the same language.

Context

Relevant areas:

• coordinator error responses
• resolver errors
• frontend status rendering
• SDK types and docs

Scope

• Define a small shared failure-code catalog for common lifecycle failures.
• Map coordinator/resolver errors into those codes without hiding original details from logs.
• Update frontend status rendering to use the codes for user-facing messages.
• Add tests for at least five mapped failure cases.
• Document the catalog and when each code is emitted.

Acceptance criteria

• Common order lifecycle failures have stable machine-readable codes.
• API responses keep safe details while logs retain debugging context.
• Frontend renders useful messages from the catalog.
• Tests cover at least five failure-code mappings.
• PR links to this issue.

Wave complexity (maintainer)

High - 200 points

[dhareymu]

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

Maintainer, abeg gimme this project 🙏🙏😭😭

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

[akinboyewaSamson]

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

Hi, I'm Samson - a Full-Stack & Blockchain Developer with 3+ years of experience. I've reviewed this issue and I'm confident I can handle it. I'll submit a clean PR within 4-6 hours max. Please assign it to me!

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

[edehvalentine236-jpg]

@edehvalentine236-jpg has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hello maintainer, I would do good resolving this issue. Kindly assign.

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

[dotmantissa]

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

Please, assign this issue to me.

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

[Amas-01]

@Amas-01 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hello Maintainer
I'll like to work on this Issue. Please Assign me

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

[K1NGD4VID]

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

Hello maintainer, i would like to work on this issue

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

[drips-wave]

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

🧑‍💻 @K1NGD4VID: 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 marked as completed by a Drips Wave moderator for @K1NGD4VID as part of the Stellar Wave Program's 6th Wave 🥳

Moderator's reason: [Auto-assessed] The contributor has addressed all issue requirements and resolved every maintainer objection, including the owner's last request to 'rebase/merge the latest main' and resolve conflicts. The technical issues regarding SDK exports and Vitest resolution are addressed in the code, and the PR is now in a clean mergeable state.

😎 @K1NGD4VID: You earned 400 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.

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

ℹ️ Note: This issue was marked complete via moderation. Points were issued even though the GitHub issue remains open.