Problem: The miner-ui's portfolio view re-implements its own narrower, global-only aggregation instead of reusing the CLI's own richer, per-repo queue dashboard — a real functional regression, not just duplicated code.
Area: AMS / Performance
Proposal: Have the miner-ui's portfolio view consume the same per-repo dashboard data the CLI already computes, rather than maintaining a separate, narrower aggregation.
Deliverables:
- One shared data path for portfolio/queue-health data, consumed by both the CLI and the UI.
Acceptance criteria:
Problem: The miner-ui's portfolio view re-implements its own narrower, global-only aggregation instead of reusing the CLI's own richer, per-repo
queue dashboard— a real functional regression, not just duplicated code.Area: AMS / Performance
Proposal: Have the miner-ui's portfolio view consume the same per-repo dashboard data the CLI already computes, rather than maintaining a separate, narrower aggregation.
Deliverables:
Acceptance criteria:
queue dashboardshows, not just a global aggregate.