feat(analytics): add role-aware recommendation quality rollups

[mkdev5]

Summary

• Closes feat(analytics): add role-aware recommendation quality rollups #303.
• Add private recommendation quality rollup rows keyed by role, surface, lane, outcome category, and report time bucket.
• Keep maintainer-lane and contributor-lane outcomes separated in the authenticated operator quality report.

Scope Summary

This PR only enhances the existing private recommendation quality report and its tests. It does not add migrations, product-usage rollup storage, visible UI behavior, dependencies, or release notes.

Scope

• The PR title follows type(scope): short summary Conventional Commit format, for example fix(api): restore profile access checks.
• 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

• 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. npm run test:ci passed locally.

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 a UI Evidence section below with JPG/JPEG or PNG screenshots arranged as organized, captioned, clickable thumbnails. SVG screenshots are not used as review evidence. Review-only screenshots or recordings are not committed to the repository.
• Public docs/changelogs are updated where needed; changelogs are only edited for release-prep PRs.

UI Evidence

No visible UI, frontend, docs, or extension behavior changed. The private operator payload shape is covered by integration tests; screenshots are not applicable.

State / title	JPG/PNG evidence
Not applicable	No visible UI change

Notes

• This avoids the stale migration-numbering and unrelated extension artifact problems that blocked the previous closed feat(analytics): add role-aware recommendation quality rollups #303 attempt.
• Rollups are computed from already-private recommendation outcome records and remain operator_only.
• The operator-dashboard integration assertion verifies authenticated access to the new rollup rows and sanitizer coverage remains in place.

[ghost]

Note

Gittensory Gate skipped

PR closed before full evaluation. No late first comment was created.

Signal	Result	Evidence	Action
Gate result	⚠️ Skipped	#470 is no longer open.	No action.

---

Checked by Gittensory, a quiet PR intelligence layer for OSS maintainers.

[JSONbored]

@MkDev11 this is ready from my side.

A few notes:

• The rollup dimensions match #303: role, surface, lane, outcome category, and time bucket.
• Maintainer-lane and contributor-lane outcomes stay separated.
• The API integration assertion covers the private operator payload shape.
• No code changes requested.