feat(analytics): generate weekly value reports

[oktofeesh1]

Summary

• add a rollup-backed weekly value report for public-safe and operator views
• wire the report into the operator dashboard, app API, internal job queue, and Monday scheduled generation
• add privacy/auth regression coverage for public-safe output, internal guards, queue processing, and scheduler behavior

What changed

• builds weekly adoption, MCP usage, GitHub command, PR packet, quiet-skip, drift, and maintainer-value metrics from daily product usage rollups
• keeps public reports aggregate-only and genericizes public warning text while preserving detailed warning context for operator reports
• exposes an authenticated app report endpoint and protected internal queue/run endpoints
• updates the UI OpenAPI artifact and operator dashboard card to display report freshness and warnings

Why

Weekly operator text was static and could not reflect product usage or maintainer value. This gives operators a generated report while keeping public-safe variants free of source, token, local-path, wallet, trust, payout, and private scoring leakage.

Validation

• npm run test:unit -- test/unit/weekly-value-report.test.ts
• npm run test:integration -- test/integration/api.test.ts test/integration/routes-errors.test.ts
• npm run test:ci
• Codex Security diff scan: no reportable findings; 13/13 worklist rows completed; report format validated and rendered locally.

Notes

• Stacked after the analytics usage-event spine and daily-rollup branches; the weekly report delta is commit 2046ed8.
• Closes feat(analytics): add weekly Gittensory value report #138.
• Advances feat(control-panel): add usage and value analytics dashboard #134.

[superagent-security]

Superagent found 1 security concern(s).

[JSONbored]

@oktofeesh1 This is ready from my side. Weekly value reports are green and merge-clean against current main.

A few notes:

• The report service has focused unit coverage.
• The API, OpenAPI, analytics UI, and operator UI surfaces are wired together.
• Empty-data and scheduled queue paths are covered, which is the right shape for this feature.