feat(scoring): explain issue-discovery validity floor in score breakdown

[bohdansolovie]

Summary

Adds an issueDiscoveryHistoryMultiplier component to explainScoreBreakdown, matching the merged-PR history breakdown pattern.

The breakdown now mirrors the same upstream invariants as preview.ts:

• Inactive linked-issue mode (linkedIssueMode: none) — floor not enforced; neutral breakdown even when history fields are supplied.
• Partial history — only validSolvedIssues or only issueCredibility observed; neutral until both are present.
• Full history + active linked-issue — full/blocked bands when floors are met or missed.

Why

buildScorePreview already applies the issue-discovery validity multiplier and emits issue_discovery_validity_floor blockers, but the score breakdown never explained that gate. Review on #1979 asked for explicit handling of partial history and inactive linked-issue inputs rather than relying on implicit upstream behavior.

Test plan

• npx vitest run test/unit/score-breakdown.test.ts
• Neutral when linked-issue mode is inactive (history supplied)
• Neutral when only valid-solved or only issue-credibility is observed
• Neutral when both history fields are unobserved
• Full when both fields meet upstream floors
• Blocked with actionable lever when below floors

[gittensory-orb]

Warning

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

⏸️ Gittensory review result - manual review recommended

_{Review updated: 2026-07-01 06:42:15 UTC}

2 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 dedicated issue-discovery validity-floor component to the breakdown and wires it into the returned component list. The implementation follows the stated invariant: inactive linked-issue mode and partial/unobserved history stay neutral, while fully observed history produces a full or blocked band based on the same floor inputs. The tests cover the important visible branches and also verify public text sanitization through the existing output path.

Nits — 6 non-blocking

• nit: src/services/score-breakdown.ts:149 duplicates the same neutral object shape across three early returns; extracting a small neutral helper would make future wording-only changes less error-prone.
• nit: test/unit/score-breakdown.test.ts:126 recreates the same issueDiscoveryRepo and baseInput in several tests; a local helper would reduce fixture drift as this breakdown grows.
• src/services/score-breakdown.ts:149: consider a small helper such as `neutralIssueDiscoveryHistory(summary, lever)` so all neutral branches keep the same component, band, and leverageScore contract.
• test/unit/score-breakdown.test.ts:126: factor the repeated repo/base input setup into a helper scoped to this describe block to keep the new branch tests focused on only the changed inputs.
• 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	⚠️ 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:M; no linked issue context).
Validation posture	❌ 5/25	Preflight is holding this PR; address the blocker before review.
Contributor workload	✅ 10/10	Author activity: 141 registered-repo PR(s), 75 merged, 23 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	bohdansolovie; Gittensor profile; 141 PR(s), 23 issue(s).
Gate result	⚠️ Not blocking	Advisory; not blocking this PR.

Review context

• Author: bohdansolovie
• Role context: outside_contributor
• Public audience mode: oss maintainer
• Lane context: Repository registration is not available in the local Gittensory cache.
• Public profile languages: Python, C++, JavaScript
• Official Gittensor activity: 141 PR(s), 23 issue(s).
• Related work: Titles/paths share 6 meaningful terms. (PR #1935)
• Related work: Titles/paths share 7 meaningful terms. (PR #1978)

Contributor next steps

• Explain no-issue PR.
• Review top overlaps.
• Add a concise scope and risk note.
• 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.
• 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

[JSONbored]

Merge conflicts:

This branch has conflicts that must be resolved
Use the [web editor](https://github.com/JSONbored/gittensory/pull/1984/conflicts) or the command line to resolve conflicts before continuing.

test/unit/score-breakdown.test.ts

Closing.