feat(signals): classify Elixir, Swift, and Gradle lockfiles

[kiannidev]

Summary

• Recognize mix.lock, Package.resolved, and gradle.lockfile as dependency lockfiles in slop path matchers

Test plan

• npx vitest run test/unit/path-matchers.test.ts

[gittensory-orb]

Tip

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

✅ Gittensory review result - approve/merge recommended

_{Review updated: 2026-06-30 20:18:44 UTC}

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

✅ Suggested Action - Approve/Merge

• safe to merge

Review summary
This change extends the lockfile basename set with Elixir, SwiftPM, and Gradle lockfiles and adds direct `isLockfile` coverage for each. The implementation is consistent with the existing matcher design because paths are normalized to lowercase before basename lookup, so the `Package.resolved` test is covered by the lowercase set entry. The visible diff is small, coherent, and safe to proceed.

Nits — 2 non-blocking

• Consider adding representative `classifyChangedFile` cases in `test/unit/path-matchers.test.ts` for `mix.lock`, `Package.resolved`, and `gradle.lockfile` so the public classifier path stays explicitly covered, not only the helper matcher.
• Readiness score is below the configured threshold — Use the readiness panel as advisory maintainer context; the score does not block this PR.

Signal	Result	Evidence
Code review	✅ No blockers	1 reviewer
Linked issue	⚠️ Missing	No linked issue or no-issue rationale found.
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; address the blocker before review.
Contributor workload	✅ 10/10	Author activity: 3157 registered-repo PR(s), 1811 merged, 51 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	kiannidev; Gittensor profile; 3157 PR(s), 51 issue(s).
Gate result	✅ Passing	No configured blocker found.

Review context

• Author: kiannidev
• 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: 3157 PR(s), 51 issue(s).
• PR-specific overlap: none found.

Contributor next steps

• Explain no-issue PR.
• Fix the blocker.
• Triage stale or unlinked PRs.
• 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