feat(metrics): expose Redis GitHub response cache counters

[oktofeesh1]

Summary

• Adds Prometheus counters for the self-host Redis GitHub response cache so operators can see hit, miss, set, and Redis-error outcomes.
• Preserves existing cache behavior: malformed entries still miss, successful entries replay, and Redis failures still propagate to the caller-level fallback path.
• Closes feat(metrics): emit hit/miss/error counters for the Redis GitHub-response cache #2073.

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; codecov/patch requires >=99% coverage of the lines AND branches you changed (aim for 100% on your diff so CI variance does not fail near the threshold). Global coverage is a non-blocking trend with a loose 90% backstop, not the gate.
• 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. Also ran npx vitest run test/unit/selfhost-redis-response-cache.test.ts --coverage.enabled true --coverage.include src/selfhost/redis-response-cache.ts after rebasing; the touched source file reported 100% statements, branches, functions, and lines.

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 changes.

Notes

• The new metric is gittensory_redis_gh_response_cache_total{result="hit|miss|set|error"} with a fixed, low-cardinality label set.
• Rebased on the latest upstream/main before opening.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 0.00%. Comparing base (a52c3b0) to head (bbb1ae9).
⚠️ Report is 9 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #2118       +/-   ##
==========================================
- Coverage   95.71%       0   -95.72%     
==========================================
  Files         222       0      -222     
  Lines       24653       0    -24653     
  Branches     8945       0     -8945     
==========================================
- Hits        23597       0    -23597     
+ Misses        433       0      -433     
+ Partials      623       0      -623     

see 222 files with indirect coverage changes

🚀 New features to boost your workflow:

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

[loopover-orb]

Warning

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

⏸️ Gittensory review result - manual review recommended

_{Review updated: 2026-07-01 17:55:39 UTC}

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

⏸️ Suggested Action - Manual Review

Review summary
The change adds Prometheus counters around the Redis-backed GitHub response cache without changing the cache contract: read failures and write failures still rethrow, cache misses still return null, malformed entries still miss, and successful writes/hits are counted. The tests cover the newly observable hit, miss, set, and Redis-error paths, and the full changed file shows the metrics helper is imported and used consistently.

Nits — 4 non-blocking

• nit: test/unit/selfhost-redis-response-cache.test.ts:119 does not assert the new miss metric for the non-replayable cached-response case, so that changed false branch is only indirectly covered through malformed shape cases.
• test/unit/selfhost-redis-response-cache.test.ts:119: add a direct assertion that a stored 500 response increments `gittensory_redis_gh_response_cache_total{result="miss"}` to document that valid-but-non-replayable cache entries are counted as misses.
• Pull request duplicates other open work — Check for an existing pull request or issue covering this change and coordinate or consolidate before continuing.
• Readiness score is below the configured threshold — Use the readiness panel as advisory maintainer context; the score does not block this PR.

Signal	Result	Evidence
Code review	✅ No blockers	1 reviewer
Linked issue	✅ Linked	#2073
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:M; 1 linked issue).
Validation posture	❌ 5/25	Preflight is holding this PR: the review lane is unavailable, so it is not ready for automated review.
Contributor workload	✅ 10/10	Author activity: 68 registered-repo PR(s), 56 merged, 4 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	oktofeesh1; Gittensor profile; 68 PR(s), 4 issue(s).
Gate result	✅ Passing	No configured blocker found.

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: 68 PR(s), 4 issue(s).
• Related work: Items reference the same linked issue feat(metrics): emit hit/miss/error counters for the Redis GitHub-response cache #2073. (issue #2073)
• Related work: Titles/paths share 9 meaningful terms. (PR #2123)
• Related work: Open PR work references issue feat(metrics): emit hit/miss/error counters for the Redis GitHub-response cache #2073. (issue #2073)
• Additional title-only matches omitted; title-only overlap does not block.

Contributor next steps

• Review top overlaps.
• Add a concise scope and risk note.
• Await review-lane availability.
• Triage stale or unlinked PRs.
• Refresh registry data or choose a registered active repo.
• 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