fix(github): guard backfill GraphQL helpers' repoFullName parsing

[philluiz2323]

Summary

fetchLiveCiAggregateViaGraphQl, fetchLivePullRequestReviewDecision, and fetchLiveReviewThreadBlockers in src/github/backfill.ts parsed repoFullName with a bare split(/) + truthiness check. Extra path segments (owner/repo/extra) and whitespace-padded slugs (owner/ repo, owner/repo) therefore reached GraphQL query strings — the same failure mode #8311 closed for app.ts/comments.ts.

Adds a local parseBackfillRepoFullName helper mirroring the segment-count + whitespace guard used in labels.ts/assignees.ts/pr-actions.ts, reused by all three call sites. Each function keeps its existing fail-soft return contract (null / undefined / []).

Test plan

• test/unit/graphql-status-rollup.test.ts: fetchLiveCiAggregateViaGraphQl rejects extra-segment and whitespace-padded slugs before any GraphQL call
• test/unit/backfill-2.test.ts: fetchLivePullRequestReviewDecision returns undefined for the same malformed shapes
• test/unit/backfill-2.test.ts: fetchLiveReviewThreadBlockers returns [] for the same malformed shapes
• Targeted vitest + main regression suites (salvageability, selfhost-pg-retention) pass locally

Closes #9317

[superagent-security]

Superagent didn't find any vulnerabilities or security issues in this PR.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 75.91%. Comparing base (f7dda79) to head (0e7c9d9).
⚠️ Report is 11 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #9351      +/-   ##
==========================================
+ Coverage   75.38%   75.91%   +0.53%     
==========================================
  Files         275      277       +2     
  Lines       58023    59546    +1523     
  Branches     6181     8758    +2577     
==========================================
+ Hits        43739    45206    +1467     
- Misses      14014    14021       +7     
- Partials      270      319      +49     

Flag	Coverage Δ
backend	96.32% <100.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
src/github/backfill.ts	96.06% <100.00%> (ø)
src/selfhost/metrics.ts	100.00% <ø> (ø)

[loopover-orb]

Tip

✅ LoopOver review result - approve/merge recommended

_{Review updated: 2026-07-27 14:30:19 UTC}

7 files · 1 AI reviewer · no blockers · readiness 98/100 · CI green · clean

✅ Suggested Action - Approve/Merge

• safe to merge

Review summary
Adds a local parseBackfillRepoFullName helper (segment-count + whitespace guard) reused across the three GraphQL read helpers in backfill.ts, closing the same repoFullName-parsing gap #8311 fixed elsewhere. The fix is correctly placed at the source (before any query string interpolation or fetch call), each call site's existing fail-soft contract is preserved, and each new guard is backed by a real unit test asserting fetchSpy is never called for malformed slugs. The PR also carries unrelated but small, well-justified bundled changes (metrics additions, a worker-entry-boundary test narrowing, a salvageability semantics fix, a pg-retention regex update) that are all pure test/observability changes rather than new feature surface.

Nits — 4 non-blocking

• The bundled unrelated changes (metrics.ts additions, worker-entry-boundary.test.ts rewrite, salvageability.test.ts semantics fix, selfhost-pg-retention.test.ts regex update) are not mentioned in the PR description/summary at all — worth calling out explicitly in the PR body so reviewers aren't surprised by scope beyond the stated repoFullName-guard fix.
• src/github/backfill.ts: parseBackfillRepoFullName duplicates logic already shared via a helper in labels.ts/assignees.ts/pr-actions.ts per the PR's own description — consider extracting a single shared util instead of a fourth copy, though the comment explains the intentional non-import choice.
• Confirm the PR body is updated to disclose the four bundled non-backfill changes, since maintainers reviewing only the stated summary would miss them.
• If a shared repoFullName-parsing utility doesn't already exist across labels.ts/assignees.ts/pr-actions.ts/backfill.ts, this would be a good follow-up issue to consolidate the now four near-identical copies.

Decision drivers

• ✅ Code review — No blockers (1 reviewer)
• ✅ Gate result — Passing (No configured blocker found.)

Context & advisory signals — never blocks the verdict

Signal	Result	Evidence
Linked issue	✅ Linked	#9317
Related work	✅ No active overlap found	No same-issue or scoped active PR overlap found.
Change scope	✅ 20/20	Low review scope from cached public metadata (1 linked issue).
Validation posture	✅ 25/25	PR body includes validation/test evidence.
Contributor workload	✅ 10/10	Author activity: 986 registered-repo PR(s), 563 merged, 125 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	philluiz2323; Gittensor profile; 986 PR(s), 125 issue(s).
Improvement	✅ Minor	risk: clean · value: minor

Linked issue satisfaction

Addressed
The diff adds a single local parseBackfillRepoFullName helper in backfill.ts applying the segment-count + whitespace guard, reused by all three call sites (fetchLiveCiAggregateViaGraphQl, fetchLivePullRequestReviewDecision, fetchLiveReviewThreadBlockers) while preserving each function's existing null/undefined/[] return contract, and adds matching regression tests for extra-segment and whitespace-

Review context

• Author: philluiz2323
• Role context: outside_contributor
• Public audience mode: oss maintainer
• Lane context: Repository is configured for direct PR review.
• Public profile languages: Python, JavaScript, MDX, TypeScript, CSS, Cuda, HTML, Kotlin
• Official Gittensor activity: 986 PR(s), 125 issue(s).
• PR-specific overlap: none found.

Contributor next steps

• Keep the PR focused and include validation evidence before maintainer review.

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.

🧪 Chat with LoopOver

Ask LoopOver a question about this PR directly in a comment — grounded only in the same cached, public-safe facts shown above, never a new claim.

• @loopover ask <question> answers contribution-quality Q&A with source citations and freshness.
• @loopover chat <question> answers in natural prose from cached decision-pack facts via local inference (maintainer/collaborator; read-only).
• A plain-language @loopover mention with a real question is routed to the closest matching read-only command automatically — no exact syntax required.

Full command reference: https://loopover.ai/docs/loopover-commands

🧪 Experimental — new and may change.

Decision record

• action: merge · clause: success
• config: 03a7f8b529a9 · pack: oss-anti-slop
• record: fee57401c534 (schema v3, head f27a356)

_{🟩 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 LoopOver, a quiet PR intelligence layer for OSS maintainers.

• Re-run LoopOver review

[loopover-orb]

LoopOver approves — the gate is satisfied and CI is green.

[loopover-orb]

LoopOver approves — the gate is satisfied and CI is green.