feat(scoring): surface tied-leverage disclosure in score breakdown

[RenzoMXD]

Summary

Replaces #1982 (cannot reopen after force-push per GitHub policy).

What changed:

• ScoreBreakdownExplanation.highestLeverageLever gains a tiedLeverageComponents: string[] field
• pickHighestLeverage surfaces all components sharing the top leverageScore
• Tests cover no-tie (singleton) and blocked tie paths

Rationale: When two scoring levers tie for highest leverageScore, the breakdown silently showed only one. This disclosure lets contributors see all tied levers so they can prioritize which to fix first.

Files changed:

• src/services/score-breakdown.ts — pickHighestLeverage collects ties; ScoreBreakdownExplanation.highestLeverageLever adds tiedLeverageComponents
• test/unit/score-breakdown.test.ts — 2 new test cases (blocked tie scenario + no-tie scenario)

Validation:

• npx vitest run test/unit/score-breakdown.test.ts — 24/24 pass
• npm run typecheck clean
• git diff --check clean

Linked issue: Closes #2142 (spawned from the tied-leverage gap identified in that issue).

[gittensory-orb]

Warning

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

⏸️ Gittensory review result - manual review recommended

_{Review updated: 2026-07-02 04:19:47 UTC}

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

⏸️ Suggested Action - Manual Review

• Touches a guarded path — held for manual review

Review summary
The change correctly extends the score breakdown response to disclose other components tied at the top leverage score, while preserving the existing deterministic top-component selection. The implementation sorts once, derives ties from the same ranked list, and returns an empty array for the normal no-tie path. The new tests cover the reachable blocked tie path and singleton top path, so the visible diff is safe enough to proceed.

Nits — 6 non-blocking

• nit: src/services/score-breakdown.ts:21 adds a required public field, so confirm any external schema/OpenAPI or extension-facing contract docs are regenerated if this type is serialized outside TypeScript callers.
• nit: src/services/score-breakdown.ts:371 uses exact numeric equality for leverage ties; that is fine for the current integer scores, but would become brittle if future components compute fractional leverage scores.
• src/services/score-breakdown.ts:371 could make the current integer-score assumption explicit by either keeping leverageScore integer-only in the type contract or comparing through a small helper if fractional scores are expected later.
• test/unit/score-breakdown.test.ts:677 should keep one assertion on the serialized output shape so this new public field stays present when highestLeverageLever is consumed as JSON.
• Readiness score is below the configured threshold — Use the readiness panel as advisory maintainer context; the score does not block this PR.
• Touches a guarded path — held for manual review — A maintainer must review and merge this change.

Signal	Result	Evidence
Code review	✅ No blockers	1 reviewer
Linked issue	✅ Linked	#2142
Related work	⚠️ 2 scoped overlaps	Top overlaps are listed below; lower-confidence bulk is hidden.
Change scope	❌ 8/20	High review scope from cached public metadata (size label size:S; 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: 69 registered-repo PR(s), 32 merged, 7 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	RenzoMXD; Gittensor profile; 69 PR(s), 7 issue(s).
Gate result	⚠️ Not blocking	Advisory; not blocking this PR.

Review context

• Author: RenzoMXD
• 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: 69 PR(s), 7 issue(s).
• Related work: Items reference the same linked issue feat(review): review.suggestions config toggle (default off) gating suggested-change blocks #2142. (issue #2142)
• Related work: Open PR work references issue feat(review): review.suggestions config toggle (default off) gating suggested-change blocks #2142. (issue #2142)

Contributor next steps

• Review top overlaps.
• Add a concise scope and risk note.
• Await review-lane availability.
• Triage stale or unlinked PRs.
• Refresh registry data or choose a registered active repo.
• Check active issues and PRs before submitting.

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.83%. Comparing base (9e657e1) to head (b47be58).
⚠️ Report is 41 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2362   +/-   ##
=======================================
  Coverage   95.83%   95.83%           
=======================================
  Files         224      224           
  Lines       24996    24998    +2     
  Branches     9091     9092    +1     
=======================================
+ Hits        23954    23956    +2     
  Misses        428      428           
  Partials      614      614           

Files with missing lines	Coverage Δ
src/services/score-breakdown.ts	99.19% <100.00%> (+0.01%)	⬆️

🚀 New features to boost your workflow:

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