test(db): cover pruneExpiredRecords' two defensive ?? 0 arms (#8370)

[philluiz2323]

Summary

• pruneExpiredRecords's two defensive ?? 0 fallback arms (src/db/retention.ts:75 dry-run row?.n ?? 0, and :85 delete-loop result.meta?.changes ?? 0) had zero direct test coverage, unlike the identical pattern on this file's sibling function dedupeSignalSnapshots, which already has dedicated tests for both equivalent arms.
• Adds two new tests mirroring dedupeSignalSnapshots's existing tests exactly: mock env.DB.prepare to return a row/meta shape missing the relevant field, and assert the function falls back to 0 rather than throwing or producing NaN.
• Pure test-addition — no production code in src/db/retention.ts was changed, per the issue's explicit scope.

Closes #8370

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:

• This PR only touches test/unit/retention.test.ts (test-only, no src/ production-code change) — no UI/MCP/workers/OpenAPI surface is affected. Verified via npx vitest run test/unit/retention.test.ts: all 21 tests pass, including the 2 new ones. Coverage on the target lines (verified directly against coverage/lcov.info): line 75's branch now shows BRDA:75,10,0,25 / BRDA:75,10,1,1 and line 85's shows BRDA:85,11,0,21 / BRDA:85,11,1,1 — both the truthy and nullish-fallback sides of both ?? 0 arms are hit, closing the previously-uncovered branch the issue identified.

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. (N/A — no auth/session/CORS changes.)
• API/OpenAPI/MCP behavior is updated and tested where needed. (N/A — no API/OpenAPI/MCP surface changed.)
• UI changes use live API data or real empty/error/loading states, not production mock/demo fallbacks. (N/A — no UI changes.)
• Visible UI changes include a UI Evidence section below with JPG/JPEG or PNG screenshots. (N/A — no visible UI changes.)
• Public docs/changelogs are updated where needed; changelogs are only edited for release-prep PRs. (N/A.)

Notes

• Zero production-code risk: src/db/retention.ts itself is unchanged, exactly as the issue scoped it.

[superagent-security]

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

[loopover-orb]

Caution

🛑 LoopOver review result - fixes required

_{Review updated: 2026-07-24 14:43:15 UTC}

1 file · 1 AI reviewer · no blockers · CI failing · blocked

🛑 Suggested Action - Fix Blockers

Review summary
This PR adds two tests for retention.ts's pruneExpiredRecords, exercising the row?.n ?? 0 dry-run fallback and the result.meta?.changes ?? 0 delete-loop fallback by mocking env.DB.prepare to return undefined/empty shapes, mirroring the already-existing pattern used for dedupeSignalSnapshots' equivalent arms lower in the same file. Both mocks are structurally consistent with how the sibling tests mock DB.prepare, and the assertions correctly check deleted: 0 with the cutoff still computed. This is a narrow, well-scoped test-only addition that closes a real coverage gap on branches the production code already contains.

Nits — 3 non-blocking

• The CI failures on validate-merge and validate are undetailed and this branch is 5 commits behind default; likely stale-branch related rather than a defect in this diff — rebase to confirm.
• test/unit/retention.test.ts: the two new mocks don't verify the SQL passed to prepare() the way dedupeSignalSnapshots' tests do (checking sql.includes("SELECT DISTINCT")), so if pruneExpiredRecords ever issues more than one prepare() call per iteration the mock could silently return the wrong shape for the wrong query — worth a comment or assertion confirming call count/order.
• Consider asserting env.DB.prepare call count or captured SQL in the two new tests to guard against future refactors of pruneExpiredRecords that add additional prepare() calls.

CI checks failing

• validate
• validate-tests-merge

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	#8370
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: 1040 registered-repo PR(s), 615 merged, 126 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	philluiz2323; Gittensor profile; 1040 PR(s), 126 issue(s).
Improvement	ℹ️ Insufficient signal	risk: clean · value: insufficient-signal · LLM: minor

Linked issue satisfaction

Addressed
The PR adds two tests mirroring dedupeSignalSnapshots's existing pattern, mocking env.DB to return a missing row/meta shape so pruneExpiredRecords's dry-run row?.n ?? 0 (line 75) and delete-loop result.meta?.changes ?? 0 (line 85) fallbacks are directly exercised and asserted to yield 0. No production code was changed, matching the issue's explicit test-only scope.

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: 1040 PR(s), 126 issue(s).
• PR-specific overlap: none found.

Contributor next steps

• Start here: Triage stale or unlinked PRs.

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 is closing this pull request on the maintainer's behalf (CI is failing (validate, validate-tests-merge)). This is an automated maintenance action — to pursue this change, please open a new pull request with the issues resolved. Closed PRs may be analyzed later to improve review accuracy, but they are not automatically reopened or re-reviewed.