feat(miner): add metadata-only opportunity ranker pipeline

[pekar9781]

Summary

• Add pure engine metadata signal builders (potential, feasibility, batch dup risk) plus freshness/competition parity helpers.
• Wire them into rankMetadataOpportunities so fan-out issue metadata can be sorted with the shared opportunity ranker.
• Add @jsonbored/gittensory-miner rankCandidateIssues / rankCandidateIssuesWithSummary wrappers for the metadata-only discovery → rank path.

Scope

• The PR title follows type(scope): short summary Conventional Commit format.
• This PR is focused on miner discovery ranking and does not mix unrelated UI/deploy changes.
• This follows CONTRIBUTING.md.
• No linked issue — jony376 cannot open issues on this repo; the summary documents the product gap.

Validation

• npm run test:ci locally — Node.js is not installed on the contributor machine; CI will run the full gate on push.
• New behavior has unit tests for positive/negative labels, stale vs fresh issues, dup-risk overlap, goal-spec parsing, contention inputs, malformed-row skipping, and deterministic ordering.

Safety

• No secrets, wallet details, hotkeys, or private scoring output in code or PR text.
• Metadata-only path: no source upload, no GitHub writes, no cloning.

UI Evidence

Not applicable — engine + miner package only.

Notes

• Mirrors the hosted reward-risk freshness/competition curves with injected clocks for deterministic tests.
• Invalid or missing issue timestamps floor freshness instead of ranking malformed metadata first.
• Complements existing fetchCandidateIssues fan-out (feat(miner-discovery): cross-repo GitHub search/listing fan-out (metadata-only) #2307) and rankOpportunities (feat(miner-discovery): pure ranker function — potential x feasibility x laneFit x freshness x (1-dupRisk) #2302) without duplicating source fetch behavior.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 96.19%. Comparing base (f8c4c35) to head (539236b).
⚠️ Report is 10 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2806      +/-   ##
==========================================
+ Coverage   96.16%   96.19%   +0.03%     
==========================================
  Files         248      253       +5     
  Lines       27574    27750     +176     
  Branches    10014    10086      +72     
==========================================
+ Hits        26517    26695     +178     
+ Misses        434      433       -1     
+ Partials      623      622       -1     

Files with missing lines	Coverage Δ
...ges/gittensory-engine/src/opportunity-freshness.ts	100.00% <100.00%> (ø)
...ages/gittensory-engine/src/opportunity-metadata.ts	100.00% <100.00%> (ø)

... and 1 file with indirect coverage changes

🚀 New features to boost your workflow:

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

[loopover-orb]

Warning

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

⏸️ Gittensory review result - manual review recommended

_{Review updated: 2026-07-03 20:24:13 UTC}

12 files · 1 AI reviewer · no blockers · readiness 73/100 · CI green · clean

⏸️ Suggested Action - Manual Review

Review summary
The AI review returned non-blocking notes for this change but did not include a separate narrative summary. Review the nits below before deciding this PR.

Nits — 5 non-blocking

• nit: packages/gittensory-engine/src/opportunity-metadata.ts:76 duplicates timestamp selection and age-decay logic that now also exists in packages/gittensory-engine/src/opportunity-freshness.ts, so future parity changes can drift between feasibility and freshness scoring.
• nit: packages/gittensory-engine/src/opportunity-metadata.ts:162 skips the source peer with a case-sensitive repoFullName comparison while the duplicate scan itself treats repo names case-insensitively; align the self-skip with the normalized repo comparison for consistency.
• packages/gittensory-engine/src/opportunity-metadata.ts:76 should reuse a shared timestamp/age helper or route feasibility through the new freshness helper semantics so metadata age handling cannot diverge silently.
• packages/gittensory-miner/lib/opportunity-ranker.js:91 should build the rank context once in rankCandidateIssuesWithSummary and derive usedDefaultGoalSpec from context.goalSpecsByRepo to avoid double parsing.
• 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 (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: 890 registered-repo PR(s), 639 merged, 28 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	jony376; Gittensor profile; 890 PR(s), 28 issue(s).
Gate result	✅ Passing	No configured blocker found.

Review context

• Author: jony376
• 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: 890 PR(s), 28 issue(s).
• PR-specific overlap: none found.

Contributor next steps

• Explain no-issue PR.
• 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

[loopover-orb]

Gittensory approves — the gate is satisfied and CI is green.