feat: include relevanceScore in GET /bounties/recommended response

[DrGalio]

Fixes #22

The GET /bounties/recommended endpoint already implements weighted scoring against tech tags and caches results for 15 minutes, but it was stripping the relevanceScore from the response before returning it.

Changes

• Keep relevanceScore in response: Removed the destructuring that stripped it (line 198)
• Include relevanceScore: 0 for the no-tech-stack fallback path
• Updated tests to assert relevanceScore is present in the response

Before

{ "data": [{ "id": "2", "title": "Bounty 2", ... }] }

After

{ "data": [{ "id": "2", "title": "Bounty 2", "relevanceScore": 2, ... }] }

This allows clients to display the relevance score to users and understand why certain bounties were recommended.

@algora-io

[devasign-app]

Merge Score: 95/100

🟢 ███████████████████░ 95%

The PR successfully resolves the issue by retaining the relevanceScore in the /bounties/recommended response and correctly handling the fallback path. The tests have been appropriately updated to assert the presence of the score. The implementation is clean, efficient, and ready to be merged.

Code Suggestions (1)

Low Priority (1)

1. packages/api/src/routes/bounties.ts (Line 169)
   Add a type annotation to the results array for better type safety.

Reasoning: Initializing an empty array with let results = []; implicitly assigns it the type any[] in TypeScript. Adding a specific type annotation improves type safety, enables better IDE autocompletion, and prevents unintended assignments later in the code.

Suggested Code:

let results: Array<typeof openBounties[0] & { relevanceScore: number }> = [];

📊 Review Metadata

• Processing Time: 37s
• Analysis Date: 3/22/2026, 3:52:44 PM

🤖 This review was generated by AI. While we strive for accuracy, please use your judgment when applying suggestions.

💬 Questions about this review? Open an issue or contact support.

[devasign-agent]

Diff correctly exposes relevanceScore in both the scored path and the no-tech-stack fallback (set to 0), removes the destructuring that previously stripped the field, and updates tests to assert its presence. Weighted scoring and caching logic remain intact.

[devasign-agent]

End goal

The GET /bounties/recommended endpoint returns personalized bounty recommendations that include a relevanceScore for each item so clients can display why bounties were recommended.

✅ Acceptance criteria met (all 5 met)

• C1 — The GET /bounties/recommended response includes a relevanceScore field for each bounty in the data array (no longer stripped from the response).
• C2 — The relevanceScore reflects the weighted scoring of the user's tech_stack against the bounty's tech_tags.
• C3 — When the user has no tech stack, the fallback path returns bounties with relevanceScore set to 0.
• C4 — Recommended results continue to be cached for 15 minutes.
• C5 — Tests assert that relevanceScore is present in the recommended response.

---

The diff correctly removes the destructuring that stripped relevanceScore from the scored path (line 198) and adds relevanceScore: 0 to the no-tech-stack fallback. Tests now assert relevanceScore values for both the scored and tie-breaking cases. The weighted scoring logic and 15-minute caching are preserved unchanged. All criteria are met.