feat(engine): add pickTopMetadataOpportunitiesAtOrAboveScore helper

[kiannidev]

Summary

• Add pickTopMetadataOpportunitiesAtOrAboveScore(candidates, context, minScore, limit) to @jsonbored/gittensory-engine: filters via rankMetadataOpportunitiesAtOrAboveScore, then returns the top N survivors.
• Non-finite or zero limits fail closed to an empty list.
• New file metadata-top-min-score.ts composes the merged metadata helpers from feat(engine): add pickTopMetadataOpportunities helper #3331 and feat(engine): add rankMetadataOpportunitiesAtOrAboveScore helper #3336.

Why no linked issue

Completes the metadata discovery ranker toolkit (rank → threshold → top-N) without callers chaining helpers manually.

Conflict avoidance

Touches only packages/gittensory-engine/src/metadata-top-min-score.ts (new), packages/gittensory-engine/src/index.ts (one export line), and test/unit/metadata-top-min-score.test.ts (new). No overlap with open enrichment, miner CLI, queue, signals, or review PRs.

Codecov patch

Local diff-cover reports 100% patch coverage on metadata-top-min-score.ts.

Test plan

• npm run build --workspace @jsonbored/gittensory-engine
• npm run build:miner
• npx vitest run test/unit/metadata-top-min-score.test.ts (6 tests)
• diff-cover coverage/lcov.info --compare-branch=main --fail-under=99 → 100%
• CI validate / validate-code / codecov patch+project / orb review agent

Made with Cursor

[superagent-security]

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.88%. Comparing base (01e96c6) to head (2929932).
⚠️ Report is 4 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3340   +/-   ##
=======================================
  Coverage   93.88%   93.88%           
=======================================
  Files         280      281    +1     
  Lines       30534    30538    +4     
  Branches    11120    11122    +2     
=======================================
+ Hits        28666    28670    +4     
  Misses       1211     1211           
  Partials      657      657           

Files with missing lines	Coverage Δ
...es/gittensory-engine/src/metadata-top-min-score.ts	100.00% <100.00%> (ø)

🚀 New features to boost your workflow:

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

[gittensory-orb]

Warning

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

⏸️ Gittensory review result - manual review recommended

_{Review updated: 2026-07-05 04:49:12 UTC}

3 files · 1 AI reviewer · no blockers · readiness 55/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/metadata-top-min-score.ts:6 documents only non-finite limits, but the implementation also treats negative limits as empty after truncation/clamping, so the comment should state the full limit contract.
• nit: test/unit/metadata-top-min-score.test.ts:42 covers zero, negative, NaN, and Infinity limits but not a positive fractional limit, leaving the intentional `Math.trunc(limit)` behavior undocumented by a test.
• packages/gittensory-engine/src/metadata-top-min-score.ts:6: Update the doc comment to say non-finite, zero, and negative limits return an empty list, and fractional positive limits are truncated.
• test/unit/metadata-top-min-score.test.ts:42: Add one assertion for `limit = 1.9` returning exactly one item so callers can rely on the truncation behavior instead of guessing.
• 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	⚠️ 3 scoped overlaps	Top overlaps are listed below; lower-confidence bulk is hidden.
Change scope	❌ 8/20	High 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: 1334 registered-repo PR(s), 648 merged, 49 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	kiannidev; Gittensor profile; 1334 PR(s), 49 issue(s).
Gate result	✅ Passing	No configured blocker found.

Review context

• Author: kiannidev
• 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: 1334 PR(s), 49 issue(s).
• Related work: Titles/paths share 10 meaningful terms. (issue #2038, issue #2040)
• Related work: Titles/paths share 7 meaningful terms. (issue #2995, issue #2568)
• Related work: Titles/paths share 5 meaningful terms. (issue #1477, issue #1514)
• 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.
• 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

[gittensory-orb]

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