Dashboard: redesign card layout to prioritize stack-relevant data on top (Simple + Advanced)

[VijitSingh97]

Problem

The dashboard's information hierarchy doesn't match what an operator cares about. Cards render in DOM order (no CSS reordering), and in the Advanced view that order is:

1. Chart
2. My P2Pool Node Stats
3. Global P2Pool Stats ← pool-wide / external
4. XvB Donation Stats
5. XMR Network ← network-wide / external
6. P2Pool Earnings
7. Tari Merge Mining
8. Workers (table)

(web/static/components.mjs DashboardView, ~lines 424-436.)

Less-interesting global/network context (Global P2Pool Stats, XMR Network) sits above and between the things actually relevant to running this stack — your own node performance, your XvB donation status/tier/VIP, your earnings, your workers. The reading order should reflect operator priority, not happen to be the order cards were added.

Goal

A more user-focused information hierarchy for both Simple and Advanced views: surface what's relevant to this stack first; relegate pool-wide and network-wide context toward the bottom as reference.

Proposed priority (Advanced — starting point, refine in discussion)

1. Chart (hashrate over time — the at-a-glance)
2. My P2Pool Node Stats (this stack's performance)
3. XvB Donation Stats (tier / VIP / routed — what the algo is doing for me)
4. Workers (my miners)
5. P2Pool Earnings (my estimate)
6. Tari Merge Mining (my secondary reward)
7. Global P2Pool Stats (pool-wide context — reference)
8. XMR Network (network-wide context — reference)

Roughly: "mine" first, "the world" last.

Simple view

Simple currently shows only the Overview card (the lone card-simple) + chart + workers. Revisit which stats live in Overview and their order so the most decision-relevant numbers (total hashrate, tier, VIP, shares-in-window, routed split, earnings headline) lead, and anything incidental drops off or moves to Advanced.

Notes / relationships

• The HeroBand (Dashboard branding: header logo/wordmark + hero KPI band #81) already surfaces headline KPIs at the very top — this issue is about the cards below it.
• A good layout directly benefits the launch hero screenshot (Launch assets: refreshed hero screenshot + demo GIF + GitHub social preview #80).
• Interacts with the XvB display changes in Dashboard: use *routed* (xmrig-proxy) hashrate everywhere for display; credited (XvB API) only in the swap algorithm + Advanced card #156 (routed vs credited), Dashboard 'Current Tier' uses only the 24h credited avg — overstates tier on a hashrate drop (raffle needs 1h AND 24h) #157 (tier accuracy), Dashboard: surface explicit VIP status (a PPLNS share) — make-or-break for ALL tiers incl. Whale/Mega #158 (explicit VIP) — ideally land those card-content changes and this ordering pass together so the XvB card is both correct and well-placed.
• Partly a design exercise: suggest a quick reordering win first, then a deeper "what belongs where, and what should each view emphasize" pass. Worth a couple of mockups before committing.

Acceptance criteria

• Advanced view orders cards by operator relevance (stack-specific before global/network).
• Simple view's Overview leads with the most decision-relevant stats.
• Global P2Pool Stats and XMR Network are demoted to reference position (lower), not interleaved with stack stats.
• Layout reads well for the launch screenshot (Launch assets: refreshed hero screenshot + demo GIF + GitHub social preview #80).