feat(analytics): add weekly Gittensory value report

[JSONbored]

Background

If the goal is higher Gittensor allocation, Gittensory needs a concise value report showing adoption, maintainer burden reduction, and signal freshness.

Goal

Generate an operator report suitable for explaining Gittensory’s value to the Gittensor team.

Current Behavior

Usage and impact have to be inferred manually from scattered data.

Desired Behavior

Gittensory can produce a weekly value report with public-safe and private operator variants.

Implementation Requirements

• Summarize active users, active repos, MCP usage, GitHub commands, PR packets, quiet skips, drift detections, and maintainer-value signals.
• Separate public-safe aggregate output from private operator details.
• Include freshness and data-quality warnings.
• Support scheduled generation.
• Keep output free of private source and identity leaks.

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, usage, quiet skips, PRs preflighted, packets generated, drift detected, and maintainer value signals.
• Public-safe version excludes private details.
• Private operator version includes deeper metrics.
• Tests cover redaction and stale-data warnings.

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.