fix(signals): detect pytest test_*.py prefix as test evidence

[ultrahighsuper]

isTestPath recognized the *_test.py suffix but not pytests default and more common test_*.py**prefix**. A Python PR that adds test files next to source (e.g.mypackage/test_utils.py, src/app/test_auth.py) matched no branch of isTestPathand was scored as shipping **no** test evidence — tripping the missing-test slop finding and undercountingclassifyTestCoverage` / the local scorer.

test_*.py is the default python_files pattern for pytest (and matches unittest discovery), so this is the primary Python test convention, not an edge case. The existing dir-based branch only catches files that live under a test/, tests/, spec/, or __tests__/ directory, which the flat pytest layout does not.

Fix

Add one path-segment-anchored matcher next to the existing suffix rule:

/(^|\/)test_[^/]*\.py$/i.test(file)

The (^|\/) anchor keeps it precise: latest_config.py and testing.py remain non-tests (no test_ at a segment boundary), while the pre-existing *_test.py suffix form is untouched.

Tests

Adds a regression case covering the prefix form, the still-working suffix form, and both non-test negatives. Verified the new case FAILS on current main and PASSES with the fix; the full test-evidence, slop, and path-matchers suites stay green.

No linked issue: issue creation is unavailable for this account.

[loopover-orb]

Warning

🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨

⏸️ Gittensory review result - manual review recommended

_{Review updated: 2026-07-03 02:36:39 UTC}

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

⏸️ Suggested Action - Manual Review

Review summary
The change correctly extends the shared test-path classifier to recognize pytest's default `test_*.py` segment convention while preserving the existing `*_test.py` suffix and avoiding mid-segment false positives like `latest_config.py`. The regression test drives the production helper directly and covers root-level, nested, suffix-preservation, and negative cases, so the visible diff is safe enough to proceed.

Nits — 4 non-blocking

• nit: `src/signals/test-evidence.ts:6` is now a long matcher/comment line; moving the explanation above the regex would keep the matcher list easier to scan.
• nit: `test/unit/local-branch-file-classifiers.test.ts` could add a `test_utils.py` case so the local-branch classifier tests document this convention too, since that path delegates to `isTestPath`.
• In `src/signals/test-evidence.ts:6`, prefer a preceding comment such as `// pytest's default test_*.py prefix convention.` followed by the regex on its own line.
• In `test/unit/local-branch-file-classifiers.test.ts`, add `test_utils.py` or `pkg/test_utils.py` to the `isTestFile` positive cases and, if `isCodeFile` delegates through it, to the code-file exclusion cases.

Signal	Result	Evidence
Code review	✅ No blockers	1 reviewer
Linked issue	✅ No-issue rationale	PR body explains why no issue is linked.
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 (size label size:XS; no linked issue context).
Validation posture	❌ 5/25	Preflight is holding this PR: the review lane is unavailable, so it is not ready for automated review.
Contributor workload	✅ 10/10	Author activity: 41 registered-repo PR(s), 25 merged, 5 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	ultrahighsuper; Gittensor profile; 41 PR(s), 5 issue(s).
Gate result	✅ Passing	No configured blocker found.

Review context

• Author: ultrahighsuper
• Role context: outside_contributor
• Public audience mode: oss maintainer
• Lane context: Repository registration is not available in the local Gittensory cache.
• Public profile languages: not available
• Official Gittensor activity: 41 PR(s), 5 issue(s).
• PR-specific overlap: none found.

Contributor next steps

• Await review-lane availability.
• Refresh registry data or choose a registered active repo.
• Link the issue being solved, or explicitly explain why this is a no-issue PR.

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.

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

• Re-run Gittensory review

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 96.10%. Comparing base (cfbdc9f) to head (999a5db).
⚠️ Report is 25 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2666   +/-   ##
=======================================
  Coverage   96.10%   96.10%           
=======================================
  Files         237      237           
  Lines       26540    26540           
  Branches     9625     9625           
=======================================
  Hits        25507    25507           
  Misses        424      424           
  Partials      609      609           

Files with missing lines	Coverage Δ
src/signals/test-evidence.ts	100.00% <ø> (ø)

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.