perf: add bounded oracle HTTP client

[findolor]

Why

Oracle-backed quote preparation currently creates a fresh HTTP client for every
pair and has no reusable bounded execution primitive. This adds connection-pool
reuse and a conservative per-origin limit before the quote sweep is made
concurrent.

What changed

• add a reusable OracleClient backed by one native/WASM-compatible reqwest
  connection pool
• cap oracle POSTs at eight in flight per origin across independently created clients
• add ordered bounded execution that avoids head-of-line blocking
• route the existing single and batch APIs through the shared client without
  changing their signatures, timeout, response validation, or status handling
• add deterministic tests for the concurrency bound, shared limiter, positional
  stability, partial failure isolation, and slow-leading-request behavior

Intentionally unchanged

• configured oracle URLs are not assumed to support batch request bodies
• no retries are added for 429/503 or other failures because the endpoint
  contract does not declare POST idempotency
• signed-context and chain quote behavior are unchanged in this prerequisite PR

Local verification

• cargo test -p raindex_quote --lib — 63 passed
• cargo clippy -p raindex_quote --all-targets --all-features -- -D warnings -D clippy::all
• cargo fmt --all -- --check
• nix develop .#wasm-shell -c bash -c 'CARGO_TARGET_WASM32_UNKNOWN_UNKNOWN_RUNNER=wasm-bindgen-test-runner cargo test --target wasm32-unknown-unknown --lib -p raindex_quote'
• rainix-rs-static

Review focus

Please pay particular attention to the per-origin limit of eight, indexed
buffer_unordered ordering restoration, and native/WASM client reuse.

Summary by CodeRabbit

• Performance

  • Oracle requests now reuse shared HTTP resources for improved efficiency.
  • Concurrent requests are bounded, with configurable limits for improved stability under load.

• Reliability

  • Batch results preserve their original request order.
  • Individual request errors are reported without blocking other requests.
  • Requests now validate endpoints, apply timeouts, and redact sensitive URL details from errors.
  • Response handling and request validation are more consistent.

[findolor]

• perf: prepare oracle quote contexts concurrently #2826
• perf: add bounded oracle HTTP client #2825 👈 (View in Graphite)
• main

---

How to use the Graphite Merge Queue

Add the label Raindex-queue to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[coderabbitai]

📝 Walkthrough

Walkthrough

Oracle request handling now uses a reusable OracleClient with shared HTTP and per-origin concurrency limits. Single, batch, and multi-request APIs use common validation, decoding, timeout, and bounded execution logic. Tests cover ordering, error isolation, and shared limits.

Changes

Oracle client concurrency

Layer / File(s)	Summary
Shared request infrastructure crates/quote/src/oracle.rs	Adds OracleClient, OracleRequest, shared HTTP client and per-origin semaphore state, URL validation, configurable limits, and sanitized request errors.
Request execution and API delegation crates/quote/src/oracle.rs	Adds timed POST execution, response decoding, single, batch, and bounded multi-request methods, and routes existing fetch functions through OracleClient.
Concurrency validation crates/quote/src/oracle.rs	Adds tests for request validation, error redaction, ordered failures, bounded execution, slow-task progress, shared limits, and caller-specific limits.

Estimated code review effort: 4 (Complex) | ~45 minutes

Sequence Diagram(s)

sequenceDiagram
  participant Caller
  participant OracleClient
  participant OriginSemaphore
  participant ReqwestClient
  Caller->>OracleClient: fetch_signed_contexts(requests)
  OracleClient->>OriginSemaphore: acquire bounded origin permits
  OracleClient->>ReqwestClient: send oracle POST requests
  ReqwestClient-->>OracleClient: return response bodies
  OracleClient-->>Caller: ordered SignedContextV1 results

Loading

Suggested reviewers: juanirios

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main change: adding a bounded Oracle HTTP client for performance.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch arda/oracle-http-primitives

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@crates/quote/src/oracle.rs`:
- Around line 195-200: Move timeout configuration out of build_http_client and
apply it to each request in fetch_responses using RequestBuilder::timeout,
ensuring wasm and non-wasm requests both enforce the 10-second limit; remove the
cfg-gated ClientBuilder timeout.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 40732961-24eb-438b-ad73-2f0df163ebed

📥 Commits

Reviewing files that changed from the base of the PR and between a665ea9 and 29be9b8.

📒 Files selected for processing (1)

• crates/quote/src/oracle.rs

[coderabbitai]

Note

GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer.

[0xgleb]

minor: acquire() waits outside the 10s reqwest timeout, so under same-origin contention a call can sit in the semaphore queue for much longer than ORACLE_REQUEST_TIMEOUT before send() even starts. Cancellation still works if the parent drops, and other origins stay isolated, but the constant is not an end-to-end bound. Worth documenting that, or giving acquire its own deadline once the concurrent sweep lands.

[graphite-app]

Merge activity

• Aug 11, 11:13 AM UTC: findolor added this pull request to the Graphite merge queue.
• Aug 11, 11:26 AM UTC: Merged by the Graphite merge queue.

[github-actions]

@coderabbitai assess this PR size classification for the totality of the PR with the following criterias and report it in your comment:

S/M/L PR Classification Guidelines:

This guide helps classify merged pull requests by effort and complexity rather than just line count. The goal is to assess the difficulty and scope of changes after they have been completed.

Small (S)

Characteristics:

• Simple bug fixes, typos, or minor refactoring
• Single-purpose changes affecting 1-2 files
• Documentation updates
• Configuration tweaks
• Changes that require minimal context to review

Review Effort: Would have taken 5-10 minutes

Examples:

• Fix typo in variable name
• Update README with new instructions
• Adjust configuration values
• Simple one-line bug fixes
• Import statement cleanup

Medium (M)

Characteristics:

• Feature additions or enhancements
• Refactoring that touches multiple files but maintains existing behavior
• Breaking changes with backward compatibility
• Changes requiring some domain knowledge to review

Review Effort: Would have taken 15-30 minutes

Examples:

• Add new feature or component
• Refactor common utility functions
• Update dependencies with minor breaking changes
• Add new component with tests
• Performance optimizations
• More complex bug fixes

Large (L)

Characteristics:

• Major feature implementations
• Breaking changes or API redesigns
• Complex refactoring across multiple modules
• New architectural patterns or significant design changes
• Changes requiring deep context and multiple review rounds

Review Effort: Would have taken 45+ minutes

Examples:

• Complete new feature with frontend/backend changes
• Protocol upgrades or breaking changes
• Major architectural refactoring
• Framework or technology upgrades

Additional Factors to Consider

When deciding between sizes, also consider:

• Test coverage impact: More comprehensive test changes lean toward larger classification
• Risk level: Changes to critical systems bump up a size category
• Team familiarity: Novel patterns or technologies increase complexity

Notes:

• the assessment must be for the totality of the PR, that means comparing the base branch to the last commit of the PR
• the assessment output must be exactly one of: S, M or L (single-line comment) in format of: SIZE={S/M/L}
• do not include any additional text, only the size classification
• your assessment comment must not include tips or additional sections
• do NOT tag me or anyone else on your comment

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

SIZE=L

_{You are interacting with an AI system.}