feat(ui): redesign dashboard, model market and sharing views (PR 4/6)

[argszero]

Summary

Adapts the dashboard, model market and sharing views to the new prototype — PR 4 of 6 of the full console UI redesign requested in rant 2026-09-11T16:23:43 ("按新原型完整适配前端 UI（全站视觉重设计 + 8 视图结构对齐）", section 六 "建议实施顺序").

Pure front-end change: no backend API contract is altered, no build tooling is introduced (still plain HTML/CSS/JS), and the existing behaviour conventions are preserved (zero-mock in signed-in state — never fall back to D. static data; inline expansion over modals; theme remembered in localStorage; data-i18n coverage).

The prototype is the single design source and is already committed in this repo as a baseline at docs/prototype/aitokenpool-console.html (landed in PR #152).

Related Issue

Refers to the host rant of 2026-09-11T16:23:43.625143+08:00 (project aitokenpool). No GitHub issue exists for this work — the repo currently has no open issues.

Changes

Dashboard (rant §3)

• page-head gains the .crumb breadcrumb + a right-aligned "call a model in the market" action (data-goto).
• New 14-day consumption-vs-earnings two-colour bar chart (.trend, consumption = accent / sharing earnings = ok, .legend included, bars normalised to that day's max, 2% minimum height).
• "My sharings" moved into its own full-width card with a card-sub description and a "manage sharing" ghost button.
• "Month point changes" gains its card-sub and keeps the existing mini-list/sparkline.

Model market (rant §4)

• Toolbar: new availability filter (all / available only) and the count pushed right via .grow.
• Provider + model columns merged into one .provider-cell (status dot + small-caps provider + .model-name).
• New capabilities column rendering only fields the backend actually returns: a Vision tag when vision is set, a tag-accent peak-pricing tag when peak rates exist.
• Availability pill is now three-state and carries the real key count: >=2 → "available · N keys" (pill-ok), ==1 → "tight" (pill-warn), 0 → "no key" (pill-muted), with the "use" button disabled when there is no key.
• Existing dynamic provider options and the recent-models chips are untouched.

Sharing (rant §5)

• "List a new key" promoted into page-head as a primary action; the form is now a sibling card instead of a grid cell.
• New availability time-window column fed by the real available_days / available_start / available_end fields.
• Used / quota now renders a progress bar alongside the numbers (.bar-track / .bar-fill, alt variant at 100%).

Shared

• Define .mt16 / .mb16 — the new layout uses them but the stylesheet never declared them (same class of gap the component audit caught in PR feat(ui): redesign login page as two-column layout + rework sidebar (rant 2026-09-11, PR2) #153).
• style.css / i18n.js only; no token changes (those landed in PR feat(ui): migrate design tokens to OKLCH system + prototype baseline (rant 2026-09-11, PR1) #152).

Correctness fix worth calling out

The dashboard chart reuses /api/transactions/trend rather than the 7-day series from /api/dashboard, so the dashboard and the transactions page cannot disagree on the same numbers. That endpoint aggregates with GROUP BY, so days with no transactions are returned as absent rows, not as zero rows. Rendering that raw would shift the bars left and mislabel the axis, so dashTrendDays() now densifies the window to a fixed DASH_TREND_DAYS (14) with 0-height columns for empty days, and the request start is anchored to UTC midnight so it lines up with the backend's UTC day buckets (a now - 13d start truncated the first bucket once the clock passed midnight).

i18n

Every new label ships with zh + en entries: dash.crumb, dash.gotoMarket, dash.trend*, dash.month.sub, dash.sharings.sub, dash.manageSharing, mk.crumb, mk.avail.*, mk.col.providerModel, mk.col.caps, mk.cap.*, share.crumb, share.col.avail. Entries orphaned by the column changes (mk.col.provider, mk.col.model, mk.avail, mk.busy, share.col.time) were removed from both languages. ZH/EN dictionaries remain in exact parity and every data-i18n attribute and T() call resolves.

No config or data-structure change is involved, so no example file needed updating.

Tests

• cargo test passes — 148 passed; 0 failed (14.62s)
• cargo fmt --check passes
• cargo clippy --all-targets -- -D warnings passes
• node --check passes on all four JS files (api.js, data.js, i18n.js, app.js)
• No new Rust unit tests: this PR is front-end only and touches no Rust code. I18n coverage was instead verified by script (ZH/EN key sets compared for exact parity; every data-i18n value and every T() key in app.js checked to resolve). Visual verification was done by loading the real ui/ in headless Chrome against stubbed API responses and rendering all three views in both light and dark themes, confirming real data (14 trend columns, 4 stat cards, 4 marketplace rows with 4 availability pills, 3 sharing rows with the availability column) rather than empty fallback states.

Checklist

• Branch naming follows the convention (feat/)
• Commit message uses Conventional Commits (feat(ui): …)
• Single responsibility — scoped to the three views named for this batch; the deliberately deferred cleanups (e.g. the now-stale .search-box reference in ui/README.md) were left out to keep the diff reviewable