Surface sanitized underlying error detail in typed ExecuteAction failures

[outerlook]

Summary

Typed ExecuteAction handlers previously wrapped any thrown exception as an opaque generic status (e.g. INTERNAL "Order Creation failed"), with the underlying ccxt/venue error visible only in the in-enclave logs. In production this converted a transient createOrder rejection into a multi-day misdiagnosis ("pair unsupported") because callers had no error detail to go on — while the pass-through Call path already surfaces raw ccxt messages, so exposing them has established precedent.

• New sanitizeErrorDetail / errorClassName helpers in src/helpers/shared/errors.ts: "<ClassName>: <message>", whitespace collapsed to single spaces, capped at 512 chars. The ccxt class name (InsufficientFunds, OrderNotFound, InvalidOrder, …) is the high-value signal.
• Every typed handler's catch block now appends the sanitized detail to its existing message prefix (Order Creation failed: InsufficientFunds: binance Account has insufficient balance…). All gRPC status codes and message prefixes are preserved, so existing consumer matching is unaffected.
• deposit.ts/treasury-call.ts route through rejectWithGrpcError, which derives the code from the raw message prefix — for those, the class name is appended as a suffix via a new opt-in appendClassName option so code derivation is undisturbed.
• Pass-through handlers and the top-level dispatcher catch-all are unchanged; in-enclave safeLogError logging unchanged.

Testing

bun test: 405 → 413 passed, 0 failed (new: helper unit tests; handler tests asserting code preserved + prefix preserved + class/message appended + single-line + 512-char cap). One existing telemetry test that asserted the old opaque message was updated to the enriched contract. bunx biome check: no new issues (one pre-existing import-ordering error cleared). Husky pre-commit (format + full suite) passed.

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 59 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 9d3d246c-5bee-4606-b0fd-eee0e980328f

📥 Commits

Reviewing files that changed from the base of the PR and between b49a91f and ef9ea38.

📒 Files selected for processing (12)

• src/handlers/execute-action/context.ts
• src/handlers/execute-action/deposit.ts
• src/handlers/execute-action/internal-transfer.ts
• src/handlers/execute-action/order-book-call.ts
• src/handlers/execute-action/orders.ts
• src/handlers/execute-action/perp-config.ts
• src/handlers/execute-action/treasury-call.ts
• src/handlers/execute-action/withdraw.ts
• src/helpers/shared/errors.ts
• test/order-error-detail.test.ts
• test/order-telemetry.test.ts
• test/shared-errors.test.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/typed-error-detail

---

_{Comment @coderabbitai help to get the list of available commands.}