feat: show Raindex market data

[findolor]

Chained PRs

• Depends on feat: replace REST API with Raindex market service #2847, which provides the public cached market API.
• feat: replace REST API with Raindex market service #2847 depends on feat: add Raindex market SDK #2845, which provides active-order discovery and the shared SDK market read model.

Summary

• Add a dedicated /markets Raindex market page that consumes only the public REST market service.
• Show every active direct quote-token pair discovered from Raindex orders, with API-backed 24-hour statistics, token artwork when available, and on-demand executable depth.
• Source market content from the public REST service while retaining the application shared layout and initialization behavior.

Key decisions

• Present the route as a Raindex-level market view and link it immediately after Vaults in permanent navigation.
• Refresh the cached overview each minute and quote only the selected market. TanStack Query cancellation prevents superseded requests from accumulating.
• Render registry-provided token images when available and retain token initials as the missing-image fallback.
• Treat 200 [] as healthy: counters render as zero and the page explains that no active Raindex orders currently provide a direct pair with the configured quote token.
• Preserve the last successful overview or detail when a background refresh fails and surface a compact freshness status.
• Keep scanning values concise while exposing unrounded API decimal strings in selected-market verification details.
• Support search by symbol, token name/address, ticker ID, quote symbol, and chain ID without product category, ISIN, or market-enabled hardcoding.

Validation

• npm run check: 0 errors and 0 warnings
• npm run lint
• Focused market/navigation/component tests: 8 passed
• Full webapp suite: 32 files and 224 runnable tests passed; the existing network-dependent fullDeployment.test.ts could not fetch its remote registry and skipped 9 tests
• npm run build
• git diff --check
• Manual local integration against the local API and index: 48 active markets rendered, including non-stock tokens; search, refresh, token artwork, empty executable depth, populated depth, exact values, and recent trades were verified.

Build output retains the repository existing sourcemap, large-chunk, and optional dependency warnings.

No issue is linked per the implementation scope.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 3d655c2c-6bb1-497e-955a-6227438f3596

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

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.}

[findolor]

• feat: show Raindex market data #2848 👈 (View in Graphite)
• feat: replace REST API with Raindex market service #2847
• feat: add Raindex market SDK #2845
• 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.

[findolor]

Updated Raindex market UI

Captured from the current Vercel preview: open the live markets page.

Desktop overview

Executable market detail

Exact API values

Search across active-order tokens

The example below filters the Raindex-wide market list to WETH; discovery is not limited to stock tokens.

Mobile overview

Mobile executable detail

[agryaznov]

LGTM

[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