fix(db): add eight latest-only signal_snapshots types to retention dedupe

[joaovictor91123]

Summary

• Add eight latest-only-consumed signal types to LATEST_ONLY_SIGNAL_SNAPSHOT_TYPES: config-quality, label-audit, maintainer-lane, maintainer-cut-readiness, contributor-intake-health, issue-quality, repo-outcome-patterns, pr-reviewability.
• Extend the dedupeSignalSnapshots harness so each of the eight types collapses N stale rows to 1 per repo (other repos preserved).

Closes #8900

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
• 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:

• Full suite / typecheck / UI / MCP not re-run locally (Node 24 vs engines Node 22). Change is the exported LATEST_ONLY_SIGNAL_SNAPSHOT_TYPES list plus a dedicated dedupeSignalSnapshots unit test covering all 8 types; CI is source of truth.

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

N/A — no visible UI changes.

Notes

• Same retention pattern as the existing repo-* / contributor-intelligence latest-only entries; queue-health remains excluded as a real historical series.

[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 90.58%. Comparing base (10755ed) to head (d2eb740).
⚠️ Report is 5 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #8935      +/-   ##
==========================================
+ Coverage   90.56%   90.58%   +0.02%     
==========================================
  Files          96       97       +1     
  Lines       22490    22547      +57     
  Branches     3884     3904      +20     
==========================================
+ Hits        20367    20424      +57     
  Misses       1945     1945              
  Partials      178      178              

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

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

Files with missing lines	Coverage Δ
src/db/retention.ts	100.00% <ø> (ø)

[loopover-orb]

Tip

✅ LoopOver review result - approve/merge recommended

_{Review updated: 2026-07-26 13:59:16 UTC}

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

✅ Suggested Action - Approve/Merge

• safe to merge

Review summary
This PR appends eight signal-type strings to the exported LATEST_ONLY_SIGNAL_SNAPSHOT_TYPES array in src/db/retention.ts and adds one unit test exercising all eight types through the existing dedupeSignalSnapshots harness (old/mid rows deleted, new kept, other-repo untouched). The change is a pure data-classification addition with no schema or migration impact, and the added test mirrors the existing per-type/per-repo dedupe test pattern already used for the earlier contributor-intelligence and focus-manifest types, so it exercises the real dedupeSignalSnapshots code path rather than a fabricated one.

Nits — 3 non-blocking

• The new test in test/unit/retention.test.ts only seeds a single target_key ("JSONbored/loopover") plus one other-repo key per type; consider also covering a type with multiple distinct target_keys within the same repo (e.g. per-contributor) to match the per-key (not per-repo) grouping the SQL actually performs via GROUP BY target_key.
• Since queue-health is explicitly called out as staying excluded, consider adding a one-line assertion in the new test (or reusing the existing 'preserves bounded history' test) that queue-health snapshots for these same runs are untouched, tightening the regression guard.
• If any of the eight new types can have multiple target_keys per repo (e.g. contributor-scoped variants of maintainer-lane or issue-quality), add a test case with two distinct target_keys under one repo to confirm dedup is per-key and not accidentally collapsing across keys.

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	#8900
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: 162 registered-repo PR(s), 74 merged, 5 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	joaovictor91123; Gittensor profile; 162 PR(s), 5 issue(s).
Improvement	✅ Minor	risk: clean · value: minor · LLM: minor

Linked issue satisfaction

Addressed
The diff adds exactly the eight required signal types to LATEST_ONLY_SIGNAL_SNAPSHOT_TYPES in src/db/retention.ts and includes a new test extending the dedupeSignalSnapshots harness that verifies each of the eight types collapses stale rows to one per repo while leaving other repos untouched.

Review context

• Author: joaovictor91123
• Role context: outside_contributor
• Public audience mode: oss maintainer
• Lane context: Repository is configured for direct PR review.
• Public profile languages: not available
• Official Gittensor activity: 162 PR(s), 5 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 approves — the gate is satisfied and CI is green.