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

[kiannidev]

Fixes #134

Summary

• Completes the operator Usage & value analytics dashboard at /app/analytics using hashed product_usage_* rollups (not audit_events or raw source).
• Adds shared UI panels for weekly value metrics, product usage breakdown (MCP, GitHub commands, quiet skips, PR packets, decision packs, drift), adoption/retention by role, and command usefulness feedback.
• Extracts buildOperatorDashboardPayload in src/services/operator-dashboard.ts and adds test/unit/operator-dashboard.test.ts for payload shape and redaction.
• Restricts Analytics navigation to operator only so it matches GET /v1/app/operator-dashboard auth.

Scope

• This PR is focused and does not mix unrelated backend, UI, MCP, docs, dependency, and deploy changes.
• This follows CONTRIBUTING.md and does not reintroduce GitHub Pages, VitePress, site/, or CNAME.
• I linked an issue, or this is small enough that the summary explains why an issue is not needed.

Validation

Verified locally with npm run test:ci on Node v24.15.0 (repo requires Node >= 22 per .nvmrc). Fixes CI UI check failure on run 26912190264 (prettier/prettier in usage-analytics-panels.tsx and app.analytics.tsx).

• git diff --check
• npm run actionlint
• npm run typecheck
• npm run test:coverage locally; global coverage stays at or above 97% for lines, statements, functions, and branches (aim for 98%+ branch coverage locally so CI variance does not fail near the threshold)
• npm run test:workers
• npm run build:mcp
• npm run test:mcp-pack
• npm run ui:openapi:check
• npm run ui:lint
• npm run ui:typecheck
• npm run ui:build
• npm audit --audit-level=moderate
• New or changed behavior has unit/integration tests for new branches, fallback paths, and sanitizer boundaries

If any required check was skipped, explain why:

• None.

Coverage summary (npm run test:coverage): statements 99.08%, branches 97.00%, functions 98.40%, lines 99.66%. New tests: test/unit/operator-dashboard.test.ts (2 cases).

Safety

• No secrets, wallet details, hotkeys, coldkeys, user PATs, private keys, raw trust scores, private rankings, or private maintainer evidence are exposed.
• Public GitHub text stays sanitized, low-noise, and does not imply compensation guarantees or optimization tactics.
• Auth, cookie, CORS, GitHub App, Cloudflare, or session changes include negative-path tests.
• API/OpenAPI/MCP behavior is updated and tested where needed.
• UI changes use live API data or real empty/error/loading states, not production mock/demo fallbacks.
• Visible UI changes include screenshots or a short recording.
• Public docs/changelogs are updated where needed; changelogs are only edited for release-prep PRs.

Notes

• Weekly report generation/export remains on /app/operator and existing scheduled/internal jobs; /app/analytics displays rollup-backed metrics from GET /v1/app/operator-dashboard.
• Existing coverage: test/unit/product-usage.test.ts, test/unit/weekly-value-report.test.ts, test/integration/api.test.ts (operator-dashboard paths). New: test/unit/operator-dashboard.test.ts.
• Add a screenshot of /app/analytics (operator session) before merge if reviewers require UI proof.

UI Evidence

Loaded — operator analytics

Empty — no rollup metrics yet

Error — dashboard unavailable

[JSONbored]

@kiannidev this is close.

A few notes:

• The operator dashboard split and redaction-focused tests look directionally right.
• CI is green now.
• The remaining blocker is PR evidence, not the implementation direction.

Required changes:

• Add a clear Screenshots or UI Evidence section to the PR description.
• Include small clickable thumbnails with state labels for the loaded operator analytics view and any empty/error state that renders differently.

Validation expected:

• Keep the current green CI.
• Reconfirm the screenshots match the current /app/analytics implementation.

[kiannidev]

@kiannidev this is close.

A few notes:

• The operator dashboard split and redaction-focused tests look directionally right.
• CI is green now.
• The remaining blocker is PR evidence, not the implementation direction.

Required changes:

• Add a clear Screenshots or UI Evidence section to the PR description.
• Include small clickable thumbnails with state labels for the loaded operator analytics view and any empty/error state that renders differently.

Validation expected:

• Keep the current green CI.
• Reconfirm the screenshots match the current /app/analytics implementation.

Hi, @JSONbored

I added UI Evidence to the description.
Please check it

[JSONbored]

@kiannidev this now looks merge-ready from this pass.

A few notes:

• The operator dashboard extraction is cleaner than keeping the full payload assembly inside the route.
• The analytics UI evidence is in the PR description with loaded, empty, and error states.
• Validation evidence is complete, including UI checks and coverage.

No code changes are requested from this review pass.