Error code reference (tabular + SDK / CLI / indexer coverage)

[truthixify]

Tier: S (1-2 days) | Type: reference

Context. guides/stellar-troubleshooting.mdx already documents 20 failure modes across 6 categories (Account & Balance, Network, Signing, Stealth-Specific, Soroban Contract, plus more) as narrative subheadings. Two things are missing: (a) a normative tabular view suitable for grep and citation, and (b) coverage of SDK Error subclasses, CLI errors, and indexer errors, which the troubleshooting page does not touch. Support keeps re-typing SDK error explanations in Discord because they are not linkable.

Scope.

• New reference/error-codes.mdx as a normative flat table.
• One table per source: Stellar contract errors, SDK errors, indexer errors, CLI errors.
• Each row: code, symbolic name, human meaning, most common cause, fix, cross-link to stellar-troubleshooting.mdx where the narrative version exists.
• Cross-link back from every entry in stellar-troubleshooting.mdx to the corresponding tabular row.
• Auto-generation note in scripts/ if source-of-truth lives in a repo constant.

Acceptance.

• Every Error subclass exported from @wraith-protocol/sdk appears
• Every contract Error variant in reference/stellar/contracts/ appears
• Every category / subheading in stellar-troubleshooting.mdx is cross-linked to a matching row
• Renders in mint dev
• Passes Compile docs snippets CI
• Nav entry under Reference

Files. reference/error-codes.mdx (new), guides/stellar-troubleshooting.mdx, docs.json (nav).

[Andrewosazzy]

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

I’ve thoroughly reviewed the requirements and acceptance criteria. I’m ready to investigate and resolve the issue, ensuring the implementation fully aligns with the specified requirements and passes all acceptance criteria.

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

[Mathew2k-hash]

@Mathew2k-hash has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I'd like to work on this issue because it provides high value to both users and support teams while having a well-defined scope. I can systematically map SDK, contract, CLI, and indexer errors into a single reference page, verify coverage against exported error types, and add bidirectional links with the existing troubleshooting guide. This would make error handling easier to search, cite, and maintain while meeting all documentation and CI requirements.

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

[drips-wave]

Congratulations, @Mathew2k-hash! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @Mathew2k-hash: 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 @Mathew2k-hash as part of the Stellar Wave Program's 8th Wave 🥳

😎 @Mathew2k-hash: 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.