Error taxonomy aligned with contract Error codes

[greatest0fallt1me]

Description

• Stable machine-readable codes for clients; link to on-chain Error variants.

Requirements and context

• Must be secure, tested, and documented for production operation.
• Should be efficient, observable, and easy to review in PRs.
• Scope is Predictify backend / off-chain services only (no Soroban contract changes, no frontend UI in this issue).

Suggested execution

• Fork the repository and create a branch:
  • git checkout -b feature/error-mapping
• Implement changes:
  1. Service / module: implement in src/errors/codes.rs and related packages as needed.
  2. Tests: add or extend mapping tests (unit + integration where applicable).
  3. Documentation: update or add docs/backend/ERRORS.md (architecture notes, OpenAPI, or runbooks).
  4. Comments & types: document public APIs, config knobs, and failure modes clearly.

Primary touchpoints: src/errors/codes.rs

Test and commit

• Run the project test command (e.g. pytest, cargo test, or npm test — follow repo conventions).
• Cover edge cases listed in the description; add regression tests for any bug found.
• In the PR, include summarized test output and security / ops notes (authn/z, data handling, rate limits).

Example commit message

feat(api): map contract errors to HTTP

Guidelines

• Target ≥ 95% coverage on new or materially changed modules (per language/tooling configured in CI).
• Documentation must allow a new engineer to operate and verify the feature locally.
• Timeframe: 96 hours from assignment.

[nayt9]

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

Hello, my name is Nathan. I’m a fullstack developer and smart contract developer, and I’d love to contribute to this project. I’m comfortable working with modern frontend tools and blockchain technologies, and I can deliver tasks quickly—often within 24 hours.

Please let me know how I can get started or if there are any issues suitable for a first contribution.

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

[wavyboy-build]

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

Please assign me this issue

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