feat(control-panel): add usage and value analytics dashboard

[JSONbored]

Background

Gittensory needs to prove adoption and ecosystem value. Operators should see whether miners and maintainers are actually using MCP, GitHub commands, and control-panel workflows.

Goal

Add operator-facing analytics for active miners, maintainers, installs, MCP commands, GitHub commands, PR packets, quiet skips, decision packs, and drift incidents.

Current Behavior

Security audit and operational events exist, but product usage and value reporting are not yet a first-class dashboard.

Desired Behavior

Operators can measure usage, activation, retention, and value without exposing private user/source data.

Implementation Requirements

• Read from product usage rollups, not raw secrets or source data.
• Separate product analytics from security audit events.
• Show stale/degraded data warnings for metrics.
• Support weekly value report generation.
• Restrict operator-only metrics appropriately.

Public/Private Output Boundaries

Public GitHub output must never include wallets, hotkeys, payout/reward estimates, raw trust scores, public score estimates, private reviewability, private scoreability context, or farming language. Private API/MCP/control-panel surfaces may show authenticated scoreability, blockers, projections, and evidence, but must not claim guaranteed payout outcomes.

Acceptance Criteria

• Shows adoption and usage without exposing secrets/source.
• Separates product usage from security audit logs.
• Supports weekly value report generation.
• Tests cover aggregation and redaction.

Testing Requirements

• npm run test:ci must pass.
• Global coverage must remain at or above 97% for lines, statements, functions, and branches.
• Aim for 98%+ branch coverage locally.
• Add tests for every new branch, fallback path, sanitizer rule, and regression.
• Add invariant/property-style tests when behavior depends on sorting, gating, scoring, source-upload safety, public/private boundaries, or telemetry privacy.
• MCP/local tooling must prove source contents are not uploaded when local metadata is involved.
• Public GitHub output must be tested against forbidden language: wallet, hotkey, raw trust score, payout, reward estimate, farming, private reviewability, and public score estimate.