fix(signals): classify Rust prost/tonic underscore protobuf stubs as generated

[jimcody1995]

Summary

Extend isGeneratedFile to recognize Rust prost/tonic underscore protobuf spellings (*_pb.rs, *_grpc_pb.rs) alongside the existing .pb.rs / .grpc.pb.rs dot-infix matchers. Includes positive/negative isGeneratedFile / classifyChangedFile assertions and representative cases-table entries.

Fixes #3010

Scope

• Conventional Commit title format.
• Focused — path-matchers + unit tests only.
• Follows CONTRIBUTING.md.
• Linked open, unassigned issue (feat(miner): freeze/snapshot mechanism for historical replay targets #3010: miner freeze/snapshot mechanism for historical replay targets).

Validation

• git diff --check
• npx vitest run test/unit/path-matchers.test.ts on Node 22
• npm run typecheck
• npm run test:coverage — 10124 tests pass, 94%+ coverage
• npm audit --audit-level=moderate — 0 vulnerabilities
• Unit tests cover isGeneratedFile, classifyChangedFile, and the representative cases table

If any required check was skipped, explain why:

• None skipped.

Safety

• No secrets, auth, or UI changes.
• N/A for UI Evidence.

UI Evidence

N/A — signals-only change with no visible UI.

Notes

Incremental path-matcher parity for #3010: prost/tonic underscore protobuf outputs now classify as generated via classifyChangedFile, so replay/snapshot diff analysis and slop signals do not treat *_pb.rs / *_grpc_pb.rs stubs as hand-authored source.

Does not deliver the freeze/snapshot mechanism itself — only closes a generated-classification gap in the shared path-matcher module.

Conflict avoidance: Touches only src/signals/path-matchers.ts and test/unit/path-matchers.test.ts. Inserts Rust underscore regexes in the Perl→JS block (lines ~112–114) and tests/table entries in non-overlapping hunks vs open #3763 (Objective-C .pb.objc.* / .pb.m near lines ~93–96). Zero overlap with #3774/#3773 (check-miner-package), #3724 (local-branch Dart scoring), #3771/#3712 (visual shot), #3766 (ops-wire), #3760/#3755/#3721/#3698 (queue processors), or renovate deps PRs.

Made with Cursor

[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 93.29%. Comparing base (ede8961) to head (a10585e).
⚠️ Report is 27 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3782   +/-   ##
=======================================
  Coverage   93.29%   93.29%           
=======================================
  Files         317      317           
  Lines       32368    32368           
  Branches    11872    11872           
=======================================
  Hits        30199    30199           
  Misses       1537     1537           
  Partials      632      632           

Files with missing lines	Coverage Δ
src/signals/path-matchers.ts	89.09% <ø> (ø)

🚀 New features to boost your workflow:

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

[loopover-orb]

Tip

🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩

✅ Gittensory review result - approve/merge recommended

_{Review updated: 2026-07-06 11:31:03 UTC}

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

✅ Suggested Action - Approve/Merge

• safe to merge

Review summary
This is a narrow, well-scoped fix: it adds two regexes (`/_pb\.rs$/`, `/_grpc_pb\.rs$/`) to `isGeneratedFileFrom` in src/signals/path-matchers.ts so prost/tonic's underscore-style Rust protobuf stubs (`*_pb.rs`, `*_grpc_pb.rs`) classify as generated, matching the existing dot-infix `.pb.rs`/`.grpc.pb.rs` handling for other ecosystems. The change is correct and tested with both positive cases (`service_pb.rs`, `service_grpc_pb.rs`) and negative cases (`lib.rs`, `main.rs`) via `isGeneratedFile` and `classifyChangedFile`, and it links to open issue #3010 per the PR description. The one notable detail is that the second regex is redundant: any string ending in `_grpc_pb.rs` already ends in `_pb.rs`, so the first regex alone would match both cases.

Nits — 4 non-blocking

• src/signals/path-matchers.ts: `/_grpc_pb\.rs$/` is redundant since any `*_grpc_pb.rs` path already satisfies `/_pb\.rs$/` immediately above it — harmless but dead pattern; consider dropping it or adding a comment explaining why it's kept for symmetry/readability with the other ecosystems' explicit grpc regex.
• src/signals/path-matchers.ts:82-83: the updated comment now mentions 'the Rust plugin emits `.pb.rs`' twice in the same sentence (once from the original text, once in the new addition) — worth tightening to avoid the duplicate clause.
• Consider consolidating the redundant `_grpc_pb.rs` regex into a single comment noting it's kept only for explicitness/symmetry with the dot-infix Rust entry, so a future reader doesn't wonder if it's load-bearing.
• The test table entries and unit test assertions look sufficient — no further test additions needed for this scope.

Signal	Result	Evidence
Code review	✅ No blockers	1 reviewer
Linked issue	✅ Linked	#3010
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: 132 registered-repo PR(s), 89 merged, 0 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	jimcody1995; Gittensor profile; 132 PR(s), 0 issue(s).
Gate result	✅ Passing	No configured blocker found.

Review context

• Author: jimcody1995
• Role context: outside_contributor
• Public audience mode: oss maintainer
• Lane context: Repository is configured for direct PR review.
• Public profile languages: TypeScript, JavaScript
• Official Gittensor activity: 132 PR(s), 0 issue(s).
• PR-specific overlap: none found.

Contributor next steps

• Keep the PR focused and include validation evidence before maintainer review.

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

[loopover-orb]

Gittensory approves — the gate is satisfied and CI is green.