app: protocol status and public metrics page

[joelpeace48-cell]

Problem

There is no public evidence the protocol is alive. Grant reviewers and pilot
partners want traction numbers, and the README itself defines success as
"sustained on-chain attested inference volume" — with no way to see it.

What to do

• /status showing service health (API, indexer lag, RPC connectivity) and
  protocol metrics: attestations recorded over time, active models and payers,
  settlement volume, disputes raised and resolved.
• Sourced from the indexer, cached, degrading gracefully.
• Be honest during the pilot phase: label testnet data clearly and do not
  present small numbers as larger ones. A reviewer who catches inflated framing
  discounts everything else on the site.
• Publish incident history once there is any.

Acceptance criteria

• Health and protocol metrics displayed
• Charts legible in both themes and on mobile
• Testnet versus mainnet unambiguously labelled
• Graceful degradation when the indexer is unavailable

Notes

Honest small numbers with a visible trend are more persuasive than impressive
numbers a reviewer cannot reconcile with the repository's commit history.

[Josetic224]

Application for Protocol Status & Public Metrics Page

I’d like to take on this issue and build the /status page as a transparent, reliable public view of the protocol’s current health and activity.

I’ll implement the page to surface service health information such as API availability, indexer lag, and RPC connectivity, alongside protocol metrics including attestations over time, active models and payers, settlement volume, and disputes raised and resolved.

The metrics will be sourced from the indexer and cached where appropriate, with graceful degradation when the indexer is unavailable so the page remains useful instead of failing completely.

I’ll also make sure the presentation is honest and easy to verify. Testnet and mainnet data will be clearly distinguished, and I’ll avoid any inflated or misleading framing of the protocol’s activity. Where there is insufficient data, the UI will communicate that clearly rather than manufacture a stronger impression.

For the frontend, I’ll make the charts readable across both light and dark themes and responsive on mobile. I’ll also structure the page so an incident history can be introduced cleanly as incidents begin to occur.

The goal is to give grant reviewers, pilot partners, and other visitors a straightforward way to verify that the protocol is active and understand its growth over time.

May I be assigned this issue?