Parent phase: #234
Parent roadmap: #127
Problem
The miner dashboard should bridge directly into the MCP/CLI flow by exposing copy-ready commands that match the user state, instead of forcing miners to hunt through docs.
Acceptance criteria
- Dashboard shows copy actions for install/status/doctor/plan/preflight/packet where appropriate.
- Commands are role/state-aware and avoid leaking local absolute paths into shared/public UI.
- Copy feedback is visible and accessible.
- Empty/error/API-unreachable states still provide safe next steps.
Validation expected
- UI tests or component tests cover visible command states.
- Screenshots or recording show desktop and narrow viewport command-copy behavior.
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.
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.
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.
Parent phase: #234
Parent roadmap: #127
Problem
The miner dashboard should bridge directly into the MCP/CLI flow by exposing copy-ready commands that match the user state, instead of forcing miners to hunt through docs.
Acceptance criteria
Validation expected
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.
MCP/CLI acceptance criteria
Cross-cutting acceptance criteria
npm run test:ci, 97%+ global coverage, and the local branch coverage target for touched code.