feat(rees): generate analyzer config metadata

[JSONbored]

Summary

• Fixes feat(rees): generate analyzer config and self-host profiles #1813.
• Generates REES analyzer metadata from runtime descriptors for docs, UI, and self-host env examples.
• Adds profile metadata for fast, balanced, and deep so operators can tune REES without source spelunking.

What changed

• Added review-enrichment/analyzer-metadata.json generated from ANALYZER_DESCRIPTORS and scheduler profile metadata.
• Replaced the hand-maintained UI analyzer list with a generated TypeScript module.
• Updated REES docs to show generated profiles, cost classes, requirements, limits, and analyzer details.
• Added a generated block in .env.example for current analyzer names and profile defaults.
• Added generator/check scripts and a REES test asserting generated metadata matches the runtime registry.

Why

The runtime analyzer registry had already outgrown the hand-maintained docs/env/UI lists. This makes descriptor metadata the source of truth so self-host operators see the same analyzers and profiles the service actually runs.

Validation

• npm --prefix review-enrichment test
• npm --workspace @jsonbored/gittensory-ui run typecheck
• git diff --check

Notes

• Stacked on perf(rees): add cost-aware analyzer scheduling #1833 because profile metadata is exported from the scheduler added there.

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	gittensory-ui	1faaaea	Commit Preview URL Branch Preview URL	Jun 30 2026, 07:11 AM

[loopover-orb]

Warning

🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨

⏸️ Gittensory review result - manual review recommended

_{Review updated: 2026-06-30 07:12:27 UTC}

19 files · 1 AI reviewer · no blockers · readiness 77/100 · CI pending · unknown

⏸️ Suggested Action - Manual Review

Review summary
The change establishes REES analyzer/profile metadata as generated output and updates the UI docs, env sample, telemetry, and request guardrails around that richer descriptor shape. The generator follows the runtime registry/profile metadata in the visible code, and the guardrail additions bound request size and shape without an obvious reachable runtime break. The remaining issues are documentation consistency and generator maintainability rather than blockers.

Nits — 6 non-blocking

• nit: apps/gittensory-ui/src/routes/docs.self-hosting-rees-analyzers.tsx:46 still says `REES_ANALYZERS=all` runs the full registry, but the profile-aware docs now say it uses the selected profile defaults; change that sample text to avoid contradicting the new behavior.
• nit: apps/gittensory-ui/src/routes/docs.self-hosting-rees-analyzers.tsx:113 lists GitHub API analyzers without `docCommentDrift`, even though the generated metadata marks it as `github-light` requiring `github-token` and `head-sha`.
• nit: review-enrichment/scripts/generate-analyzer-metadata.mjs:49 hardcodes the `ReesProfileName` union instead of deriving it from `profiles`, so adding a scheduler profile still requires editing the generated-template code.
• nit: .env.example:68 wraps comma-separated generated analyzer names without commas at line breaks, which makes copying the comment block into `REES_ANALYZERS` error-prone.
• nit: review-enrichment/src/brief.ts:356 captures `new Error(partialReason)` on analyzer failure, which sanitizes the event but loses the original stack; keep the sanitized reason in metadata while passing the original error to Sentry.
• PR author also opened the linked issue — Link an issue that was opened by a different contributor, or provide a rationale for why this self-authored issue represents genuine discovery work.

Signal	Result	Evidence
Code review	✅ No blockers	1 reviewer
Linked issue	✅ Linked	#1813
Related work	⚠️ 3 scoped overlaps	Top overlaps are listed below; lower-confidence bulk is hidden.
Change scope	❌ 8/20	High review scope from cached public metadata (size label size:XXL; 1 linked issue).
Validation posture	✅ 25/25	PR body includes validation/test evidence.
Contributor workload	✅ 10/10	Author activity: 2 registered-repo PR(s), 2 merged, 273 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	JSONbored; Gittensor profile; 2 PR(s), 273 issue(s).
Gate result	✅ Passing	No configured blocker found.

Review context

• Author: JSONbored
• Role context: owner (maintainer lane)
• Public audience mode: oss maintainer
• Lane context: Repository registration is not available in the local Gittensory cache.
• Public profile languages: not available
• Official Gittensor activity: 2 PR(s), 273 issue(s).
• Related work: Items reference the same linked issue feat(rees): generate analyzer config and self-host profiles #1813. (issue #1813)
• Related work: Open PR work references issue feat(rees): generate analyzer config and self-host profiles #1813. (issue #1813)
• Related work: Items reference the same linked issue fix(rees): standardize bounded external fetches #1812. (issue #1812, PR #1831)
• Additional title-only matches omitted; title-only overlap does not block.

Contributor next steps

• Treat this as maintainer-lane context rather than normal contributor-lane activity.
• Review top overlaps.
• Add a concise scope and risk note.
• Triage stale or unlinked PRs.
• No action.
• Check active issues and PRs before submitting.

Signal definitions

• Related work = same linked issue, overlapping active PRs, or title/path similarity.
• Change scope = cached public metadata such as size labels, draft state, and review-burden hints.
• Validation posture = whether the PR provides enough public validation/test evidence for maintainer review.
• Contributor workload = public contributor activity and cleanup pressure, not a repo-wide quality failure.
• Contributor context = public GitHub/Gittensor identity context; non-Gittensor status is not a blocker.

_{🟩 Safe / merged · 🟦 Advisory · 🟨 Held for review · 🟥 Blocked / closed}

---

💰 Earn for open-source contributions like this. Gittensor lets GitHub contributors earn for the work they already do — register to start earning →.

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

• Re-run Gittensory review

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
⚠️ Please upload report for BASE (codex/rees-scheduler-profiles@8f17c83). Learn more about missing BASE report.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@                       Coverage Diff                        @@
##             codex/rees-scheduler-profiles    #1835   +/-   ##
================================================================
  Coverage                                 ?   95.66%           
================================================================
  Files                                    ?      214           
  Lines                                    ?    23342           
  Branches                                 ?     8427           
================================================================
  Hits                                     ?    22331           
  Misses                                   ?      419           
  Partials                                 ?      592           

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.