Error handler: `errorHandler` never leaks internal messages; `sanitize` and `lib/errors` parity [RC26Q2-B27]

[thlpkee20-wq]

Description

Error handler: errorHandler never leaks internal messages; sanitize and lib/errors parity — target TypeScript/Express in Revora-Backend (Stellar/Horizon + Soroban on the chain leg). Add tests, structured logging, and lib/errors style responses. Backend scope only, not the React app.

Requirements and context

• ≥95% coverage for new or materially changed lines; follow existing Jest/TS test layout.
• No raw upstream/DB error strings in client-facing JSON; align with security modules.

Suggested execution

• Fork the repo, then:

  • git checkout -b be27-error-handler

• Relevant modules: Per title; src/services/, src/routes/, src/middleware/, src/lib/, src/db/ as applicable.

• Implement and verify

  • Branch: git checkout -b be27-error-handler
  • Touch the listed modules; extend *.test.ts co-located with implementation.
  • If Stellar RPC is involved, document classifyStellarRPCFailure behavior in the PR; link stellar.test and stellarRpcFailure usage.
  • Run full npm test / yarn test as used by the repo; paste summary; add security assumptions note.

• Test and document

  • Add or extend automated tests; cover edge cases and invariants
  • Document security assumptions; include test output summary and a short security / risk note in the PR
  • For Revora-Contracts (Soroban): cargo test, cargo clippy, rustdoc/NatSpec-style entrypoint docs where applicable. Do not implement Solidity; this work targets Rust/WASM in this repository.
  • For Backend / Frontend: follow the repo’s existing Jest/TS/ESLint/Vite setup.
  • Example commit message: fix(backend): error handler

Labels and GitHub label colors

• Create the labels in this issue’s labels: line under Settings → Labels in the target repo.
• Assign distinct colors (avoid all grey): e.g. #0052CC (blue, platform), #B60205 (red, security), #0E8A16 (green, tests), #5319E7 (purple, P1), #F9D0C4 (scope), #1D76DB (api), #BFD4F2 (docs) — pick a non-default palette so issues are scannable in the board.

Guidelines

• Target ≥ 95% test coverage for new or materially changed code paths
• Clear, linked documentation in-repo
• Timeframe: 96 hours from assignment

[Emmo00]

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

I would love to work on this issue.

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

[drips-wave]

Congratulations, @Guddy1-tech! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on April 29, 2026.

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

[Escelit]

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

I'd implement a centralized error handler middleware that catches all errors, maps known error types to safe client-friendly responses using lib/errors parity, and sanitizes unknown errors to generic messages while logging full details server-side. I'd add comprehensive tests covering each error mapping, sanitization of raw database/upstream strings, and edge cases, achieving ≥95% coverage on new lines.

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

[nikkybel]

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

can i be assign this issue?

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

[meshackyaro]

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

Hi, I'd like to work on this. I'd ensure that the errorHandler never leaks internal messages and also write a comprehensive test with up to 95% test coverage

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

[CollinsC1O]

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

I would love to work on this issue and get it resolved

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