fix(github): log discarded review-files fetch warnings, clear npm audit findings

[JSONbored]

Summary

• fetchAndStorePullRequestFilesForReview (src/github/backfill.ts) built a warnings array from
  fetchPullRequestFiles but never read it, so a REST+GraphQL double failure during the live-review
  inline file fetch degraded to an empty file list with zero observability — no log, no metric, no
  audit row. Now logs a structured review_files_fetch_failed warning (matching the
  console.error(JSON.stringify({level, event, ...})) convention used elsewhere in src/, e.g.
  review_files_inline_fetch_failed in src/queue/processors.ts) when warnings.length > 0, without
  changing the fail-safe return-[] behavior itself. Rebased on top of fix(review): retry an empty inline files fetch before trusting it #7601's just-merged retry logic;
  the log now fires after both fetch attempts, capturing whichever attempt(s) hit the double-failure path.
• Also clears the two remaining npm audit --audit-level=moderate findings left after fix(deps): brace-expansion <1.1.16 has a high-severity ReDoS advisory (GHSA-3jxr-9vmj-r5cp) #7568/fix(deps): update brace-expansion to 1.1.16 to clear GHSA-3jxr-9vmj-r5cp #7569
  fixed brace-expansion: adm-zip <0.6.0 (high, GHSA-xcpc-8h2w-3j85) via a package.json overrides
  entry forcing ^0.6.0 (same mechanism already used here for tar/esbuild/ws/js-yaml; verified
  against a cleared ~/.github-actionlint binary cache so npm run actionlint genuinely re-extracts
  through the new adm-zip code path rather than reusing a stale cache hit), and body-parser 2.0.0-2.2.2 (low, GHSA-v422-hmwv-36x6) via npm update body-parser (lockfile-only, same shape as
  fix(deps): update brace-expansion to 1.1.16 to clear GHSA-3jxr-9vmj-r5cp #7569) — the same bump Dependabot PR chore(deps): bump body-parser from 2.2.2 to 2.3.0 #7605 already carries, whose only failing check is the
  Codecov-upload step that fails on every Dependabot PR here because Dependabot runs don't get repo
  secrets, unrelated to the dependency itself.

Closes #7602, Closes #7607

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 a currently open issue this PR resolves (e.g. Closes #123) — a linked open issue is required for every contributor PR.

Validation

• git diff --check
• npm run actionlint (re-verified against a cleared ~/.github-actionlint cache after the adm-zip override, forcing a real re-extraction)
• 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. — the two new lines/branches in fetchAndStorePullRequestFilesForReview are 100% branch-covered (verified via the raw v8 coverage JSON: both sides of the new if (warnings.length > 0) branch are exercised).
• 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 — 0 vulnerabilities (was 2: adm-zip high, body-parser low)
• New or changed behavior has unit/integration tests for new branches, fallback paths, and sanitizer boundaries — added a positive test (log fires with the right JSON shape on a real REST+GraphQL double failure) and a negative test (log never fires on a legitimate successful-empty response), plus reconciled with fix(review): retry an empty inline files fetch before trusting it #7601's retry-loop tests during rebase.

If any required check was skipped, explain why:

• npm run test:ci (the full aggregate gate) was run locally end-to-end before pushing; see commit history for the two logically-separate changes (observability log, then dependency audit fixes) resolved together after a rebase onto main picked up fix(review): retry an empty inline files fetch before trusting it #7601's just-merged retry logic for the same function.

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. — no API/OpenAPI/MCP surface changed.
• UI changes use live API data or real empty/error/loading states, not production mock/demo fallbacks. — no UI changed.
• 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. — no changelog edit.

UI Evidence

Not applicable — backend/dependency-only change (src/github/backfill.ts, test/unit/backfill-2.test.ts, package.json, package-lock.json), no visible UI/frontend/docs surface.

Notes

• This bundles two otherwise-separable fixes (an observability log-only fix and a dependency-audit
  fix) into one PR at the maintainer's explicit request, to land both together rather than as two
  round-trips.

[superagent-security]

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

[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	loopover-ui	0cfc746	Commit Preview URL Branch Preview URL	Jul 21 2026, 01:11 AM

[codecov]

Bundle Report

Bundle size has no change ✅

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 88.50%. Comparing base (69273b2) to head (0cfc746).
⚠️ Report is 2 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #7608   +/-   ##
=======================================
  Coverage   88.50%   88.50%           
=======================================
  Files         724      724           
  Lines       75959    75961    +2     
  Branches    22609    22610    +1     
=======================================
+ Hits        67230    67232    +2     
  Misses       7681     7681           
  Partials     1048     1048           

Flag	Coverage Δ
shard-1	31.01% <100.00%> (+<0.01%)	⬆️
shard-2	37.93% <100.00%> (+<0.01%)	⬆️
shard-3	39.09% <100.00%> (+0.02%)	⬆️
shard-4	38.85% <100.00%> (+<0.01%)	⬆️
shard-5	32.08% <50.00%> (+<0.01%)	⬆️
shard-6	25.18% <0.00%> (-0.01%)	⬇️

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

Files with missing lines	Coverage Δ
src/github/backfill.ts	95.95% <100.00%> (+<0.01%)	⬆️

[loopover-orb]

Tip

✅ LoopOver review result - approve/merge recommended

_{Review updated: 2026-07-21 01:16:54 UTC}

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

✅ Suggested Action - Approve/Merge

• safe to merge

Review summary
This PR adds a structured console.error warning log when both REST and GraphQL file fetches fail during review file sync, keeping the existing fail-safe empty-array return behavior unchanged, and separately clears two npm audit findings via package.json overrides/updates (adm-zip, body-parser). The logging change is correctly placed after both fetchOnce() attempts and before the files.length===0 early return, so it fires exactly once per call regardless of outcome, matching the stated intent. Tests cover both the double-failure warning path and the no-warning-on-genuine-empty-list path, and the console.error call follows the existing project convention (matches review_files_inline_fetch_failed in processors.ts) rather than being a stray debug leftover.

Nits — 5 non-blocking

• src/github/backfill.ts:2464 — the console.error call sits inside a function documented as fail-safe/best-effort; confirm this doesn't get invoked at high frequency in production in a way that floods logs (e.g. during a sustained GitHub outage), since there's no rate-limiting or sampling.
• package.json's `adm-zip` override to `^0.6.0` bumps the minimum supported Node engine for that transitive dep to >=14 (visible in package-lock.json diff), which is a nit given this repo already requires Node >=22.
• The JSDoc comment referencing 'fix(github): log when both REST and GraphQL file fetches fail during inline PR-review sync #7602' (src/github/backfill.ts:~2446) is fine as an issue-tracking pointer but ties documentation to an external issue number rather than describing behavior standalone — minor style preference only.
• Consider whether the review_files_fetch_failed warning should include a severity/count field if this code path is hit repeatedly for the same PR across retries, to help distinguish transient vs. persistent double failures at the log-consumption layer.
• No migration or schema changes are involved; the dependency bumps are lockfile-only and mechanically consistent with prior PRs (fix(deps): brace-expansion <1.1.16 has a high-severity ReDoS advisory (GHSA-3jxr-9vmj-r5cp) #7568/fix(deps): update brace-expansion to 1.1.16 to clear GHSA-3jxr-9vmj-r5cp #7569), which is good precedent-following.

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	#7602, #7607
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 (2 linked issues).
Validation posture	✅ 25/25	PR body includes validation/test evidence.
Contributor workload	✅ 10/10	Author activity: 23 registered-repo PR(s), 16 merged, 368 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	JSONbored; Gittensor profile; 23 PR(s), 368 issue(s).
Improvement	✅ Minor	risk: clean · value: minor · LLM: moderate

Linked issue satisfaction

Addressed
The diff adds a structured console.error(JSON.stringify({level:"warn", event:"review_files_fetch_failed", ...})) log gated on warnings.length > 0 in fetchAndStorePullRequestFilesForReview, matching the requested convention, without altering the fail-safe return-[] behavior, and includes tests verifying both the logging and non-logging cases.

Review context

• Author: JSONbored
• Role context: owner (maintainer lane)
• Public audience mode: oss maintainer
• Lane context: Repository is configured for direct PR review.
• Public profile languages: Python, TypeScript, Ruby, Go, JavaScript, MDX, Shell, Solidity
• Official Gittensor activity: 23 PR(s), 368 issue(s).
• PR-specific overlap: none found.

Contributor next steps

• Start here: Treat this as maintainer-lane context rather than normal contributor-lane activity.

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.

_{🟩 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.