fix(signals): classify grpc-node JS/TS protobuf stubs as generated

[jimcody1995]

Summary

Extend isGeneratedFile to recognize grpc-node message/service stubs (*_pb.js, *_pb.ts, *_grpc_pb.js, *_grpc_pb.ts) and TypeScript declaration stubs (*_pb.d.ts, *_grpc_pb.d.ts), matching the existing .pb.js / .pb.ts dot-form protoc coverage. Includes direct isGeneratedFile / classifyChangedFile assertions and hand-authored negative cases.

Fixes #2279

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:

• None skipped.

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 — signals-only change with no visible UI.

Notes

Incremental maintenance parity for path-matcher slop signals supporting the engine extraction tracked in #2279. Does not complete the full slop-engine deliverable.

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.15%. Comparing base (626b580) to head (f3f08ba).
⚠️ Report is 4 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3581   +/-   ##
=======================================
  Coverage   93.15%   93.15%           
=======================================
  Files         311      311           
  Lines       31702    31702           
  Branches    11579    11579           
=======================================
  Hits        29533    29533           
  Misses       1517     1517           
  Partials      652      652           

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

🚀 New features to boost your workflow:

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

[loopover-orb]

Warning

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

⏸️ Gittensory review result - manual review recommended

_{Review updated: 2026-07-05 17:53:19 UTC}

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

⏸️ Suggested Action - Manual Review

Review summary
This PR extends isGeneratedFile in src/signals/path-matchers.ts to recognize grpc-node JS/TS protobuf stubs (`*_pb.js`, `*_pb.ts`, `*_grpc_pb.js`, `*_grpc_pb.ts`, `*_pb.d.ts`, `*_grpc_pb.d.ts`), mirroring the existing underscore-form patterns already present for Ruby/PHP/Nim/Lua. The two added regexes are correctly ordered and non-overlapping: `/_pb\.(js|ts)$/` matches `_pb.js`/`_pb.ts`/`_grpc_pb.js`/`_grpc_pb.ts` but not `.d.ts` (since `d.ts` is not literally `js` or `ts`), and the second `/_pb\.d\.ts$/` catches the declaration-stub case, so both new tests pass as claimed. Test coverage is direct and thorough, exercising both isGeneratedFile and classifyChangedFile with matching positive cases and hand-authored negative cases (`src/app.js`, `src/app.ts`, `src/types.d.ts`) that verify the pattern doesn't over-match ordinary source.

Nits — 4 non-blocking

• The two new regexes could be combined into a single `/_pb\.(js|ts|d\.ts)$/` for symmetry with how other multi-extension protobuf patterns in this file are expressed as one alternation (src/signals/path-matchers.ts:77-80).
• No test asserts that a `.jsx`/`.tsx` file with a `_pb` suffix is correctly left unmatched, though this is a minor edge case given the issue scope is limited to `.js`/`.ts`/`.d.ts`.
• Consider folding the `d.ts` case into the primary alternation as noted above to keep the generated-file pattern list uniform in style with the rest of the function.
• If grpc-node ever emits `.jsx`/`.tsx` message stubs in some tooling variant, extend the regex accordingly — not needed now.

Signal	Result	Evidence
Code review	✅ No blockers	1 reviewer
Linked issue	✅ Linked	#2279
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	❌ 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: 104 registered-repo PR(s), 72 merged, 0 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	jimcody1995; Gittensor profile; 104 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 registration is not available in the local Gittensory cache.
• Public profile languages: TypeScript, JavaScript
• Official Gittensor activity: 104 PR(s), 0 issue(s).
• PR-specific overlap: none found.

Contributor next steps

• Await review-lane availability.
• Refresh registry data or choose a registered active repo.

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.