test(signals): rename signals-coverage.test.ts, scope down the signals consolidation

[JSONbored]

Closes #8576.

Summary

Investigated merging signals.test.ts + signals-v2.test.ts + signals-coverage.test.ts per #8576. Found no real duplication to dedupe: across all ~148 top-level test cases in the trio, zero title collisions, and spot-checking similarly-named pairs (e.g. "audits configured labels..." vs "audits label ordering...") confirmed they test different functions entirely (buildConfigQuality vs buildLabelAudit). signals-v2.test.ts genuinely covers newer builders (buildCollisionEdges, buildContributorPatternReport, buildMaintainerPacket, buildRoleContext) absent from signals.test.ts — organic API growth, not lazy duplication.

A forced 6,255-line merge would be pure structural churn with real risk (import/identifier collisions across three large files, same class of risk as #8584 but 3x the size) and zero dedup benefit, so I scoped this down to the action actually warranted: only signals-coverage.test.ts matches the epic's *-coverage.test.ts anti-pattern that #8580's guard will block going forward. Renamed to signals-edge-cases.test.ts, retitled its top-level describe, and updated the three cross-file comments that referenced the old filename. signals.test.ts and signals-v2.test.ts are left untouched — they're legitimately organized.

Test plan

• npx vitest run test/unit/signals-edge-cases.test.ts test/unit/signals.test.ts test/unit/signals-v2.test.ts test/unit/feasibility-gate-branches.test.ts — 185/185 pass
• npm run typecheck — clean
• Pure rename + comment updates, no test-body changes — no coverage impact to verify.

[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	f69592f	Commit Preview URL Branch Preview URL	Jul 24 2026, 10:49 PM

[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 92.54%. Comparing base (b091240) to head (f69592f).
⚠️ Report is 2 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #8586      +/-   ##
==========================================
- Coverage   92.54%   92.54%   -0.01%     
==========================================
  Files         796      796              
  Lines       79850    79850              
  Branches    24135    24135              
==========================================
- Hits        73899    73895       -4     
  Misses       4802     4802              
- Partials     1149     1153       +4     

Flag	Coverage Δ
backend	93.71% <ø> (-0.01%)	⬇️

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

Files with missing lines	Coverage Δ
packages/loopover-engine/src/signals/engine.ts	97.67% <ø> (ø)

... and 1 file with indirect coverage changes

[loopover-orb]

Warning

⏸️ LoopOver review result - manual review recommended

_{Review updated: 2026-07-24 22:47:21 UTC}

4 files · 1 AI reviewer · no blockers · CI green · unstable

⏸️ Suggested Action - Manual Review

Review summary
This is a pure rename/comment-update PR: `signals-coverage.test.ts` → `signals-edge-cases.test.ts`, with three cross-file comment references updated to match, plus a describe-block retitle and an explanatory header comment. The description clearly documents why a full three-file merge was rejected (no title/assertion overlap found across ~148 test cases), which is a well-reasoned, low-risk scope-down. No test bodies changed, so the stated 185/185 pass and clean typecheck are consistent with the diff shown.

Nits — 3 non-blocking

• The new header comment in test/unit/signals-edge-cases.test.ts (lines 59-63) is fairly long for a file-level comment; consider trimming to the load-bearing claim (distinct coverage, verified against Consolidate signals-coverage.test.ts into the signals main suites #8576) rather than restating the PR description inline.
• The Workers Builds: loopover-ui CI failure has no detail provided in this diff's context, and the branch is 2 commits behind default — this is very likely a pre-existing/upstream issue rather than something introduced by this rename-only change, but worth confirming with a rebase.
• Double check no other files in the repo reference the old `signals-coverage.test.ts` filename in comments or docs outside the three already updated (a repo-wide grep for the old name would confirm completeness).

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	#8576
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: 13 registered-repo PR(s), 13 merged, 260 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	JSONbored; Gittensor profile; 13 PR(s), 260 issue(s).
Improvement	✅ Minor	risk: clean · value: minor

Linked issue satisfaction

Partially addressed
The PR performs a rename of signals-coverage.test.ts to signals-edge-cases.test.ts and updates cross-references, but the issue explicitly asked for a duplicate audit followed by merging genuinely unique cases into the main suites and a before/after coverage comparison, none of which appear to have been executed beyond an unverified claim of 'zero title collisions'. The author explicitly declines t

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, MDX, Shell, Solidity, JavaScript
• Official Gittensor activity: 13 PR(s), 260 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