feat(scoring): surface the saturated base-score value in the score breakdown

[RenzoMXD]

Summary

Adds a baseScore component to the score breakdown so miners see the saturated base-score value alongside the existing density/contribution multipliers.

What changed:

• baseScoreBreakdown() function — 3 bands: blocked (gate), neutral (sub-cap), full (saturated)
• baseScoreCap field on ScorePreviewResult.scoreEstimate (computed in scoring core)
• BASE_SCORE_SATURATION_RATIO=0.95 for saturation detection (dynamic, per-model cap)
• LeverageScore 75 when gate-blocked (ties with densityBreakdown for tie disclosure)
• 5 test cases: blocked, neutral+bonus, neutral+no-bonus, saturated, + regression with alt constants

Review fixes applied (2 commits):

1. e83f718: Named constant, fixture fix, split tests, bump blocked LS to 75
2. a298b98: baseScoreCap field on ScorePreviewResult — saturation derived from model cap, not hardcoded 29.5

Files changed:

• src/scoring/preview.ts — baseScoreCap typed + computed in scoring core
• src/services/score-breakdown.ts — baseScoreBreakdown + BASE_SCORE_SATURATION_RATIO
• test/unit/score-breakdown.test.ts — 5 new test cases + fixture fix

Validation:

• npx vitest run test/unit/score-breakdown.test.ts → 19/19 pass
• npm run typecheck → clean
• CI: validate OK codecov/patch OK validate-code OK

[gittensory-orb]

Warning

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

⏸️ Gittensory review result - manual review recommended

_{Review updated: 2026-07-01 19:01:55 UTC}

3 files · 1 AI reviewer · no blockers · readiness 48/100 · CI green · clean

⏸️ Suggested Action - Manual Review

• Touches a guarded path — held for manual review

Review summary
The change adds a baseScore breakdown component and carries a model-derived baseScoreCap through the preview result so the UI can distinguish blocked, sub-cap, saturated, and fixed-override cases. The cap calculation is correctly tied to the active scoring model instead of a hardcoded threshold, and the new tests exercise the key visible branches in the breakdown. I do not see a reachable correctness break in the provided diff; the most notable cleanup is test-comment accuracy around the saturation-model case.

Nits — 5 non-blocking

• nit: test/unit/score-breakdown.test.ts:621 has a misleading comment saying a value around 29.2 is below 28.5, while the actual test inputs use sourceTokenScore 100 and totalTokenScore 0 for the sub-cap case; fix the comment so it matches the exercised scenario.
• src/services/score-breakdown.ts:39 consider trimming the long formula comment or moving the derivation detail beside computeScoreCore in src/scoring/preview.ts, since that is now the source of truth for baseScoreCap.
• test/unit/score-breakdown.test.ts:621 update the saturation-model test comment to describe the actual sourceTokenScore 100 / totalTokenScore 0 sub-cap input, then keep the sourceTokenScore 400 full-bonus case as the saturated branch.
• 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	⚠️ Missing	No linked issue or no-issue rationale found.
Related work	⚠️ 3 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:M; 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: 62 registered-repo PR(s), 31 merged, 7 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	RenzoMXD; Gittensor profile; 62 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: TypeScript, Python, Rust, C++, JavaScript, Scala, Clojure, Go
• Official Gittensor activity: 62 PR(s), 7 issue(s).
• Related work: Titles/paths share 8 meaningful terms. (PR #2362)
• Related work: Items reference the same linked issue feat(review): review.suggestions config toggle (default off) gating suggested-change blocks #2142. (issue #2142, PR #2362)
• Related work: Open PR work references issue feat(review): review.suggestions config toggle (default off) gating suggested-change blocks #2142. (issue #2142, PR #2362)
• Additional title-only matches omitted; title-only overlap does not block.

Contributor next steps

• Explain no-issue PR.
• 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.
• Link the issue being solved, or explicitly explain why this is a no-issue PR.
• 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.62%. Comparing base (fa09b39) to head (bb1b63c).
⚠️ Report is 55 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2356   +/-   ##
=======================================
  Coverage   95.61%   95.62%           
=======================================
  Files         218      218           
  Lines       24315    24333   +18     
  Branches     8818     8829   +11     
=======================================
+ Hits        23250    23268   +18     
  Misses        436      436           
  Partials      629      629           

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

🚀 New features to boost your workflow:

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