[Suggestion] MCP server + local web dashboard (backlog) #13

Is your feature request related to a problem? Please describe.
Tracking backlog ambitions for the plugin: making the collected usage data consumable outside the TUI (by other agents or in a browser). Explicitly LOW priority — parked until the core feature set (dialog fix, leaderboard, trends, projections, export, config) is shipped.

Describe the solution you'd like

1. MCP server (model-usage-mcp/ directory, bun entrypoint): expose tools like get_usage(period), get_session_cost(sessionID), get_quota(), get_top_sessions(period) — reusing model-usage/db.ts and wlib readers as the single source of truth
2. Local web dashboard: tiny bun HTTP server on localhost serving JSON + an inline no-dependency HTML chart page, opened via a /usage-web command

Describe alternatives you've considered

• Bigger full dashboard framework — rejected, no dependencies, keep it ~150 lines

Additional context
This is the "bigger" stretch goal. Do NOT start before the core roadmap is done. Share pure query logic with the TUI side so behavior never drifts.

Media
N/A