Miner dashboard chat: read-only backend grounding on the existing 11 MCP tools

[JSONbored]

Context

Part of epic #6504's chat track. The chat backend must ground its responses on the miner's already-existing, entirely read-only 11-tool MCP surface (packages/loopover-miner/bin/loopover-miner-mcp.js: ping, get_portfolio_dashboard, get_manage_status, list_claims, get_audit_feed, get_run_state, list_plans, get_plan, get_governor_decisions, status, get_calibration_report) — no new tool surface. Per the epic's explicit boundary: no new API wiring for calibration, ranked-candidates, or track-record data beyond what these 11 tools already expose.

Requirements

• Wire the chat backend to call the 11 existing loopover_miner_* MCP tools to ground its responses in real local miner state.
• This issue is read-only end to end — no write/action capability (that's the separate action-dispatch scaffolding child issue and its 3 action-family children).
• Do not add any new tool beyond the 11 already listed.

Deliverables

• Chat backend grounded on the 11 existing read-only MCP tools
• Test coverage for the grounding logic

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

Chat can answer questions about real local miner state (portfolio, claims, run state, plans, governor decisions, calibration) using only already-existing, read-only tools.

Links & Resources

Epic: #6504. packages/loopover-miner/bin/loopover-miner-mcp.js.

[linear-code]

JSO-4718

[JSONbored]

Already done — via #6517. packages/loopover-engine/src/miner/chat-grounding.ts already defines exactly the 11 allowlisted read-only loopover_miner_* tools this issue asks for, with a comment stating the session may only reach those 11 tools. apps/loopover-miner-ui/vite-chat-api.ts is already the transport-only SSE bridge to runChatGrounding. Closing as already resolved.