feat(control-panel): add miner command center

[JSONbored]

Background

Miners need a practical command center that answers what to do next, not another list of repos. This surface should make MCP and agent recommendations understandable from the web app.

Goal

Create a miner dashboard for next actions, cleanup-first guidance, scoreability blockers, pending-merge projections, MCP setup, and PR packet history.

Current Behavior

Miner intelligence exists across MCP/API outputs, but it is not presented as a guided web workflow.

Desired Behavior

A miner can open the control panel and immediately see what to work on, what to avoid, what to clean up, and which MCP commands to run locally.

Implementation Requirements

• Use decision-pack and agent planning outputs as source of truth.
• Show open PR pressure, pending merge scenarios, stale data warnings, and rerun conditions.
• Surface MCP install/status/doctor guidance without uploading source contents.
• Show generated PR packet history when available.
• Separate account/queue blockers from branch-quality blockers.

Public/Private Output Boundaries

Public GitHub output must never include wallets, hotkeys, payout/reward estimates, raw trust scores, public score estimates, private reviewability, private scoreability context, or farming language. Private API/MCP/control-panel surfaces may show authenticated scoreability, blockers, projections, and evidence, but must not claim guaranteed payout outcomes.

Acceptance Criteria

• Miner can see what should I work on next and why.
• Shows current blockers, stale data warnings, and rerun conditions.
• Links to MCP install and relevant commands.
• No source upload or public reward claims.
• Tests cover role gating and response redaction.

Testing Requirements

• npm run test:ci must pass.
• Global coverage must remain at or above 97% for lines, statements, functions, and branches.
• Aim for 98%+ branch coverage locally.
• Add tests for every new branch, fallback path, sanitizer rule, and regression.
• Add invariant/property-style tests when behavior depends on sorting, gating, scoring, source-upload safety, public/private boundaries, or telemetry privacy.
• MCP/local tooling must prove source contents are not uploaded when local metadata is involved.
• Public GitHub output must be tested against forbidden language: wallet, hotkey, raw trust score, payout, reward estimate, farming, private reviewability, and public score estimate.