feat(github): memoize live review facts per request

[oktofeesh1]

Summary

• add request-scoped memoization for live GitHub branch-protection, CI aggregate, and PR merge-state reads
• thread the live facts bag through readiness, public PR rendering, manual retriggers, and auto-maintenance
• refresh merge-state after gate publication so post-gate planning never replays pre-approval mergeability
• extend queue tests to pin duplicate-read reduction, public-token fallback, and post-gate merge-state refresh regressions

What changed

• Reuses the sweep resync payload for pre-gate readiness and shares the first live CI/context reads across later consumers in the same job.
• Keeps the memoization strictly in-process for one review/re-gate request, keyed by repo plus token/ref/SHA/PR identity.
• Refreshes merge-state at the public rendering and auto-maintenance boundaries after the gate can publish review/check state.
• Preserves existing fail-open behavior and avoids Redis/cross-job caching for mutable decision reads.

Why

This reduces duplicate GitHub GETs during webhook bursts and re-gate sweeps without risking stale gate decisions from shared cache replay.

No closing issue because the broader retry-storm issue is already claimed by another open PR; this PR is scoped to request-local live fact reuse.

Validation

• npm run test:ci
• npm audit --audit-level=moderate

[loopover-orb]

Warning

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

⏸️ Gittensory review result - manual review recommended

_{Review updated: 2026-06-30 19:04:01 UTC}

2 files · 1 AI reviewer · no blockers · readiness 55/100 · CI green · unknown

⏸️ Suggested Action - Manual Review

• Touches a guarded path — held for manual review

Review summary
The change adds a request-local live facts bag for branch-protection contexts, CI aggregates, and merge-state reads, then threads it through re-review, webhook, public rendering, manual retrigger, and auto-maintenance paths. The visible hot paths refresh CI and mergeability after gate publication where state can change, so the memoization does not replay readiness-era facts into post-gate decisions. The added tests exercise duplicate-read reduction, post-gate refresh, public-token fallback, and required-context failure behavior; the remaining issues are hardening and maintainability, not correctness blockers.

Nits — 7 non-blocking

• nit: src/queue/processors.ts:426 uses a 32-bit token fingerprint for cache keys even though the key is only process-local, so a raw token key part or collision-resistant digest would avoid accidental auth-context aliasing.
• nit: src/queue/processors.ts:481 folds required-context lookup failures to null inside fetchLiveCiAggregateWithRequiredContexts, but the helper name does not make that policy obvious to future callers.
• nit: test/unit/queue.test.ts:870 relies on broad URL/header substring matching for the public-token fallback assertion, which makes the test more coupled to incidental request formatting than necessary.
• src/queue/processors.ts:426: change liveFactTokenPart to use the raw token in the in-memory key or a collision-resistant digest rather than a 32-bit FNV-style fingerprint.
• src/queue/processors.ts:455: add a focused unit test proving evictLiveFactOnReject removes a rejected promise and a later call retries instead of replaying the rejection.
• Readiness score is below the configured threshold — Use the readiness panel as advisory maintainer context; the score does not block this PR.
• Touches a guarded path — held for manual review — A maintainer must review and merge this change.

Signal	Result	Evidence
Code review	✅ No blockers	1 reviewer
Linked issue	✅ No-issue rationale	PR body explains why no issue is linked.
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:L; no linked issue context).
Validation posture	❌ 5/25	Preflight is holding this PR; address the blocker before review.
Contributor workload	✅ 10/10	Author activity: 71 registered-repo PR(s), 60 merged, 7 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	oktofeesh1; Gittensor profile; 71 PR(s), 7 issue(s).
Gate result	⚠️ Not blocking	Advisory; not blocking this PR.

Review context

• Author: oktofeesh1
• Role context: outside_contributor
• Public audience mode: oss maintainer
• Lane context: Repository registration is not available in the local Gittensory cache.
• Public profile languages: JavaScript, MDX, Python, TypeScript
• Official Gittensor activity: 71 PR(s), 7 issue(s).
• Related work: Items reference the same linked issue feat(enrichment): Churn-hotspot + bug-density scorer #1513. (issue #1513, PR #1882)
• Related work: Items reference the same linked issue Reduce duplicate GitHub totals queries during open-data backfill #1855. (issue #1855, PR #1856)
• Related work: Titles/paths share 6 meaningful terms. (PR #1867, PR #1882)
• Additional title-only matches omitted; title-only overlap does not block.

Contributor next steps

• Review top overlaps.
• Add a concise scope and risk note.
• Fix the blocker.
• Triage stale or unlinked PRs.
• Refresh registry data or choose a registered active repo.
• Link the issue being solved, or explicitly explain why this is a no-issue PR.
• 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