Miner dashboard: run-history route skeleton and pagination adoption

[JSONbored]

Context

Part of epic #6504's visual/ui-kit track. apps/loopover-miner-ui/src/routes/run-history.tsx:26-42 hand-duplicates a 4-branch loading/error/empty/data JSX literal with a plain-text loading state ("Loading local run state…") and a static full-dump table (lines 44-63) with no pagination, despite packages/loopover-ui-kit/src/components/skeleton.tsx and pagination.tsx shipping unused.

Requirements

• Adopt Skeleton for the loading state, matching the real table layout.
• Adopt pagination.tsx for the run-history table instead of a static full dump.
• Adopt the shared async-state primitives from the ui-kit-port child issue of this same epic instead of the hand-rolled 4-branch JSX.

Deliverables

• run-history.tsx restyled with skeleton + pagination
• Shared async-state primitives adopted
• Before/after screenshots

Test Coverage Requirements

99%+ Codecov patch coverage on every changed line and branch, plus a regression test for the new/changed behavior (note: apps/** UI code may fall outside the strict Codecov patch gate — check coverage.include — but a before/after screenshot table per this repo's UI-PR convention is still required for any visual change).

Expected Outcome

The run-history route has a content-shaped loading state and paginated results instead of an unbounded static dump.

Links & Resources

Epic: #6504. apps/loopover-miner-ui/src/routes/run-history.tsx:26-42,44-63.

[linear-code]

JSO-4713

[JSONbored]

Already done — via #6510. apps/loopover-miner-ui/src/routes/run-history.tsx already imports Skeleton, StateBoundary, and the full Pagination* set from ui-kit; RunHistorySkeleton is table-shaped, and RunHistoryView already paginates client-side. Closing as already resolved.