feat(miner): enqueue ranked discovery into portfolio queue

[pekar9781]

Summary

• Add enqueueRankedDiscovery to wire ranked fan-out output into the local portfolio queue using each row's rankScore as queue priority.
• Optionally append discovered_issue audit events, completing the feat(miner-foundation): local portfolio/queue store for gittensory-miner #2292 placeholder priority wiring without any GitHub calls.

Scope

• The PR title follows type(scope): short summary Conventional Commit format (feat — new miner capability).
• Focused on portfolio discovery orchestration only — no CLI, network, or unrelated miner changes.

Validation

• npm run test:ci locally — CI will run the full gate on push.
• Unit tests cover enqueue ordering, minRankScore cutoff, malformed row skipping, in_progress preservation, and event-ledger append.

Safety

• No secrets, wallet details, hotkeys, or private scoring output in code or PR text.
• Deterministic, read/write-local only: no network calls.

UI Evidence

Not applicable — miner library only.

Notes

Follow-up to #2292 (portfolio queue foundation) and #2302 (opportunity ranker) — connects rank → queue → ledger locally without GitHub calls.

API edges fail closed: non-array rankedIssues throws invalid_ranked_issues; an explicitly provided but invalid eventLedger throws invalid_event_ledger.

[superagent-security]

Superagent didn't find any vulnerabilities or security issues in this PR.

[loopover-orb]

Warning

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

⏸️ Gittensory review result - manual review recommended

_{Review updated: 2026-07-04 12:25:02 UTC}

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

⏸️ Suggested Action - Manual Review

Review summary
This adds a small local bridge from ranked issue rows into the portfolio queue, and the core path is coherent: invalid rows are skipped, rankScore is passed through as priority, and the existing queue store preserves in-progress rows. I do not see a reachable correctness break in the changed files, and the tests exercise the main queue ordering, cutoff, invalid-row, and ledger append behavior. The main cleanup is tightening the public type contract so it matches the intentionally tolerant runtime API.

Nits — 5 non-blocking

• nit: packages/gittensory-miner/lib/portfolio-discovery.d.ts:23 types `rankedIssues` as `readonly EnqueueRankedDiscoveryInput[]`, but packages/gittensory-miner/lib/portfolio-discovery.js:60 intentionally accepts and counts malformed rows, so consumers cannot call the documented skip-invalid behavior without casts.
• nit: packages/gittensory-miner/lib/portfolio-discovery.js:75 increments `summary.enqueued` for every valid row even when the underlying queue store preserves an existing `in_progress` row and does not actually requeue it, so the metric name is a little stronger than the behavior.
• packages/gittensory-miner/lib/portfolio-discovery.d.ts:23: change the input type to `readonly unknown[]` or add a separate loose input type if malformed-row skipping is part of the public API.
• packages/gittensory-miner/lib/portfolio-discovery.js:75: either rename `enqueued` to `accepted`/`processed` or compare the returned queue entry if you need the summary to mean a row was actually queued or refreshed.
• 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: 956 registered-repo PR(s), 680 merged, 42 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	jony376; Gittensor profile; 956 PR(s), 42 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: 956 PR(s), 42 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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 96.08%. Comparing base (27c2182) to head (69d3f43).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3074   +/-   ##
=======================================
  Coverage   96.08%   96.08%           
=======================================
  Files         265      265           
  Lines       29077    29077           
  Branches    10588    10588           
=======================================
  Hits        27940    27940           
  Misses        493      493           
  Partials      644      644           

🚀 New features to boost your workflow:

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

[loopover-orb]

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