roadmap(phase 4): adoption analytics and launch system

[JSONbored]

Parent roadmap: #127

Goal

Prove adoption and value without becoming a public reward predictor: privacy-safe usage events, activation/retention rollups, operator-facing value reports, and launch metrics for miners, maintainers, repo owners, and operators.

Existing tracked work

• feat(control-panel): add usage and value analytics dashboard #134: usage and value analytics dashboard.

Completed foundation to verify before claiming done

• feat(analytics): add privacy-safe product usage event spine #136, feat(analytics): add daily rollups and retention funnels #137, feat(analytics): add weekly Gittensory value report #138, feat(analytics): add MCP package and API compatibility adoption tracking #139, feat(pwa): make the control panel notification-ready #149, docs(launch): add role-based beta onboarding journeys #153.

Current gap signal

The current codebase exposes analytics UI routes and an ai_usage_events table, but does not obviously expose a durable product-usage event table by that name. Treat the closed analytics foundation as something to verify against current schema and migrations before claiming v1 analytics complete.

Done when

• Product usage is captured with privacy-safe, role-aware event names.
• Activation and retention are measurable by role/surface without exposing private scoreability or payout implications.
• Weekly value reports can be exported for operators and maintainers.

Cross-cutting acceptance criteria

• Preserve the repo quality gate: npm run test:ci, 97%+ global coverage, and the local branch coverage target for touched code.
• Keep public/private boundaries explicit. Public GitHub output must not expose wallets, hotkeys, reward estimates, raw trust scores, public score predictions, private reviewability, private scoreability context, or farming language.
• Add/update focused tests for the changed behavior instead of relying on green checks alone.

Public-output safety criteria

• Public text is sanitized before reaching GitHub comments, issue bodies, PR bodies, extension-visible public panels, or copied public snippets.
• Tests cover forbidden wallet/hotkey, reward-estimate, trust-score, public-score-prediction, private-reviewability, private-scoreability, and farming-language leakage.

UI evidence gate

Any visible web, browser-extension, or GitHub-overlay change must include maintainer-reviewable screenshots or a short recording covering the changed states. A checked template box without actual visual evidence is not enough.