fix(signals): classify scss and less source maps as generated

[jimcody1995]

Summary

• Extend isGeneratedFile in path-matchers.ts to treat .scss.map and .less.map as generated output, matching the existing .css.map handling (fix(signals): classify vue/svelte/astro source maps as generated #3357).
• Sass/Less bundler source-map siblings were still miscounted as substantive source in classifyChangedFile.

Scope

• Conventional Commit title format.
• Focused — path-matchers + unit tests only.
• Follows CONTRIBUTING.md.
• No linked issue needed.

Validation

• git diff --check
• npm run test:ci on Node 22
• npm audit --audit-level=moderate — 0 vulnerabilities
• Unit tests cover .scss.map and .less.map

Safety

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

UI Evidence

N/A — backend path classifier only.

Notes

Conflict avoidance: Touches only src/signals/path-matchers.ts and test/unit/path-matchers.test.ts. Zero overlap with open PRs (#3373 focus-manifest, #3372/#3304 test-evidence, #3368 engine, #3361 enrichment, #3314 miner, #3305 enrichment-wire, #3304 queue/gate). Merges cleanly after any of those land without rebase.

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.90%. Comparing base (07401e2) to head (157f90c).
⚠️ Report is 5 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3376   +/-   ##
=======================================
  Coverage   93.90%   93.90%           
=======================================
  Files         284      284           
  Lines       30607    30607           
  Branches    11148    11148           
=======================================
  Hits        28743    28743           
  Misses       1208     1208           
  Partials      656      656           

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.

[gittensory-orb]

Warning

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

⏸️ Gittensory review result - manual review recommended

_{Review updated: 2026-07-05 05:42:25 UTC}

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

⏸️ Suggested Action - Manual Review

Review summary
This change correctly extends the generated-file source-map matcher so `.scss.map` and `.less.map` now take the same generated path as existing `.css.map` files, and the direct predicate tests cover both new extensions. The classify path is wired through `isGeneratedFileFrom`, so the production `classifyChangedFile` path will classify these as generated before source/test/doc handling. I do not see a blocking correctness issue in the visible diff.

Nits — 5 non-blocking

• nit: src/signals/path-matchers.ts:65 still omits `.sass.map`, even though the repo's visual-path classifier treats `.sass` as a first-class front-end source extension; either add `sass` here too or leave a reason why indented-syntax Sass maps are intentionally excluded.
• nit: test/unit/path-matchers.test.ts:50 exercises `isGeneratedFile` directly, but the PR describes a `classifyChangedFile` miscount, so add at least one assertion that `classifyChangedFile("dist/styles.scss.map")` and `classifyChangedFile("dist/theme.less.map")` return `"generated"`.
• src/signals/path-matchers.ts:65: consider changing the source-map extension group to include `sass` as well: `...(vue|svelte|astro|scss|sass|less|css)\.map$`.
• test/unit/path-matchers.test.ts:260: extend the representative `classifyChangedFile` cases with `.scss.map` and `.less.map` so the tested behavior matches the bug report's production path.
• Code changes lack test evidence — Add focused regression tests or explain why existing coverage is sufficient.

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 (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: 58 registered-repo PR(s), 31 merged, 0 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	jimcody1995; Gittensor profile; 58 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: not available
• Official Gittensor activity: 58 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.
• 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

[gittensory-orb]

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