[GrantFox][Medium] Show stale market data and indexing state

Summary

Show stale market data and indexing state

Why this matters

Users can mistake delayed indexer data for final market state.

Scope

Track freshness, last indexed ledger, pending operations, and authoritative refresh status.

Acceptance criteria

• Stale data is visibly identified.
• Freshness thresholds are configurable.
• Confirmed operations reconcile after indexing.
• Tests cover delayed, missing, and recovered data.

Validation

Add regression coverage for existing behavior, failure modes, authorization boundaries, and compatibility. The implementation must pass the repository CI checks.

Non-goals

• Typo-only, formatting-only, or documentation-only changes.
• Unrelated refactors or dependency upgrades.
• Weakening existing security, authorization, CI, or production safeguards.

Contributor application

Before implementation, comment with relevant experience, a 1–4 bullet approach, and an estimate for opening the first draft PR. Wait for maintainer assignment before coding.

PR requirements

Use a feature branch, include Closes #<issue-number>, check every acceptance criterion, link criteria to code/tests, explain security and failure-mode considerations, and pass CI.

Reward-readiness

This is a substantive GrantFox campaign issue. Merge and CI success do not by themselves guarantee reward eligibility; final reward-readiness is determined by campaign review.

Start by locating the existing market-data and indexing-state entry points and related tests in the repository. Trace how delayed, missing, recovered, and authorized data states are represented, then use the acceptance criteria to define the regression coverage and run the repository CI checks.