feat(mcp-cli): add gittensory_find_opportunities to the stdio surface

[RenzoMXD]

Summary

Closes #2309.

Reopened from #2681 (closed by the gate after main advanced). Rebased onto latest main; all tests pass.

What changed: Registered \gittensory_find_opportunities\ in \packages/gittensory-mcp/bin/gittensory-mcp.js\ proxying the cross-repo discovery HTTP endpoint via \�piPost, following the exact shape of the neighboring \gittensory_check_before_start\ registration. Added 4 stdio-proxy tests and extended the test fixture server with a /v1/opportunities/find\ endpoint.

Files changed:

• \packages/gittensory-mcp/bin/gittensory-mcp.js\ — added \indOpportunitiesShape\ and
  egisterTool\ call
• \ est/unit/support/mcp-cli-harness.ts\ — added /v1/opportunities/find\ fixture endpoint
• \ est/unit/mcp-cli-find-opportunities.test.ts\ — new test file (4 tests)

Validation:

• 
  px vitest run test/unit/mcp-cli-find-opportunities.test.ts\ — 4/4 pass
• 
  px tsc --noEmit\ — clean
• \git diff --check\ — clean

Linked issue: Closes #2309

Supersedes #2681 (closed by gate after main advanced).

[loopover-orb]

Warning

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

⏸️ Gittensory review result - manual review recommended

_{Review updated: 2026-07-03 06:42:32 UTC}

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

⏸️ Suggested Action - Manual Review

Review summary
The PR adds the stdio MCP registration for `gittensory_find_opportunities`, validates the expected optional arguments, and proxies the request to `/v1/opportunities/find` in the same style as the existing tool registrations. The fixture endpoint and focused stdio tests cover registration, POST routing, response shape, and omission of absent optional fields. I do not see a reachable correctness break in the visible diff.

Nits — 4 non-blocking

• nit: `test/unit/mcp-cli-find-opportunities.test.ts:106` should end with a trailing newline to match normal repository formatting.
• nit: `test/unit/support/mcp-cli-harness.ts:248` defines `targets` and `searchQuery` in the fixture body type but does not exercise them in the response, so the fixture is slightly broader than the behavior it validates.
• `test/unit/mcp-cli-find-opportunities.test.ts:91` could add a case with `targets` and `goalSpec` together so the nested schema and body forwarding path are covered, not just `searchQuery` and `limit`.
• `test/unit/support/mcp-cli-harness.ts:260` could include the received `targets` count or query echo in the fixture response if future tests need to prove those fields reached the endpoint.

Signal	Result	Evidence
Code review	✅ No blockers	1 reviewer
Linked issue	✅ Linked	#2309
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 (draft PR; 1 linked issue).
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: 111 registered-repo PR(s), 61 merged, 7 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	RenzoMXD; Gittensor profile; 111 PR(s), 7 issue(s).
Gate result	✅ Passing	No configured blocker found.

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: not available
• Official Gittensor activity: 111 PR(s), 7 issue(s).
• PR-specific overlap: none found.

Contributor next steps

• Await review-lane availability.
• Mark ready when done.
• Refresh registry data or choose a registered active repo.

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.13%. Comparing base (a2ea220) to head (67219a1).
⚠️ Report is 8 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2694      +/-   ##
==========================================
- Coverage   96.15%   96.13%   -0.02%     
==========================================
  Files         240      240              
  Lines       26867    26976     +109     
  Branches     9751     9790      +39     
==========================================
+ Hits        25833    25934     +101     
- Misses        424      432       +8     
  Partials      610      610              

see 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.