fix(signals): classify MDX source maps as generated

[jimcody1995]

Summary

• Extend isGeneratedFile in path-matchers.ts to treat .mdx.map as generated output, matching the existing .vue.map/.astro.map/.scss.map handling (fix(signals): classify vue/svelte/astro source maps as generated #3357, fix(signals): classify scss and less source maps as generated #3376).
• MDX is a first-class front-end extension in review/visual/paths.ts; bundler source-map siblings were still miscounted as substantive source.

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 test covers dist/page.mdx.map as generated via isGeneratedFile

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 (#3444/#3443 selfhost, #3442 secret-scan, #3441 rees render, #3440 queue, #3439 engine, #3433 integrations, #3431 rees release, #3429 release workflow, #3414 review-evasion, #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 92.99%. Comparing base (e9f6519) to head (ab6248e).
⚠️ Report is 6 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3446   +/-   ##
=======================================
  Coverage   92.99%   92.99%           
=======================================
  Files         294      294           
  Lines       30962    30962           
  Branches    11291    11291           
=======================================
  Hits        28793    28793           
  Misses       1514     1514           
  Partials      655      655           

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 07:28:00 UTC}

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

⏸️ Suggested Action - Manual Review

Review summary
This focused change extends the generated-file source-map matcher to include `.mdx.map`, matching the existing treatment for Vue/Astro/Svelte/style source-map siblings and the visual-path context where MDX is first-class frontend input. The production path is direct: `classifyChangedFile` normalizes once, checks `isGeneratedFileFrom`, and will now classify MDX source maps as `generated`; the unit test exercises the real exported matcher. I do not see a reachable correctness defect in the visible diff.

Nits — 4 non-blocking

• nit: `src/signals/path-matchers.ts:63` still describes the source-map regex as "JS/TS bundle extension" even though the same regex now covers frontend framework/style extensions including MDX; update the comment so the next extension addition does not inherit stale wording.
• `src/signals/path-matchers.ts:63` could say `Source maps for first-class source/bundle extensions` to match the actual regex membership.
• `test/unit/path-matchers.test.ts:38` could add one `classifyChangedFile("dist/page.mdx.map") === "generated"` assertion if you want coverage at the category boundary, though the current `isGeneratedFile` test covers the changed matcher directly.
• 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.