roadmap(phase 1): miner command center

[JSONbored]

Parent roadmap: #127

Goal

Make the miner path feel obvious from first install through PR packet generation: install, authenticate, doctor, plan, preflight, understand why recommendations changed, and copy the right MCP/API commands from the app.

Existing tracked work

• feat(control-panel): add miner command center #129: miner command center.
• feat(mcp): add public-safe PR body drafting command #98: public-safe PR body drafting.
• feat(mcp): add multi-account profile support #99: multi-account profile support.
• feat(mcp): cache last-good decision packs for offline fallback #100: last-good decision packs for offline fallback.

Done when

• A miner can install and run doctor without needing tribal setup knowledge.
• The dashboard exposes the same useful next actions as the MCP flow.
• Recommendation changes and rerun reasons are inspectable enough that miners can trust the next action.

Cross-cutting acceptance criteria

• Preserve the repo quality gate: npm run test:ci, 97%+ global coverage, and the local branch coverage target for touched code.
• Keep public/private boundaries explicit. Public GitHub output must not expose wallets, hotkeys, reward estimates, raw trust scores, public score predictions, private reviewability, private scoreability context, or farming language.
• Add/update focused tests for the changed behavior instead of relying on green checks alone.

MCP/CLI acceptance criteria

• Machine-readable JSON output is available where automation needs it.
• Token, wallet/hotkey, and local absolute-path redaction are covered by tests.
• Source-upload behavior remains explicit and fails closed where upload is unsupported.

Public-output safety criteria

• Public text is sanitized before reaching GitHub comments, issue bodies, PR bodies, extension-visible public panels, or copied public snippets.
• Tests cover forbidden wallet/hotkey, reward-estimate, trust-score, public-score-prediction, private-reviewability, private-scoreability, and farming-language leakage.

UI evidence gate

Any visible web, browser-extension, or GitHub-overlay change must include maintainer-reviewable screenshots or a short recording covering the changed states. A checked template box without actual visual evidence is not enough.