fix(#314): enforce maximum difficulty cap in recommendation fallback paths

[Sujini-kudupudi]

Summary

This PR fixes an issue where users could receive issues beyond their allowed difficulty cap (e.g. Level 0 receiving Medium or Hard issues) via fallback paths when the difficulty pool runs dry or when skipping an issue.

Type of Change

• Bug fix
• New feature
• UI / UX improvement
• Refactor
• Documentation
• Other

Related Issue

Closes #314

What was changed?

• Updated filterAndRank in src/lib/pipeline/recommend.ts to strictly cap the fallback difficulty based on the user's level (e.g., Level 0 allows ['E'] only).
• Updated the skipRecommendation action in src/app/actions/recommendations.ts to fetch the user's level from the profiles table.
• Passed level into pickReplacement to calculate allowed difficulties and applied .in('difficulty', allowedDifficulties) during the broad pool fallback query.
• Rewrote the fallback unit test in src/lib/pipeline/recommend.test.ts to correctly assert that the fallback mechanism respects the max difficulty cap.

Screenshots

N/A

Checklist

• My code follows the project structure and conventions
• I tested this locally (npm run dev)
• No hardcoded secrets or credentials
• I have updated documentation if needed

[vercel]

@Sujini-kudupudi is attempting to deploy a commit to the codersogs-3057's projects Team on Vercel.

A member of the Team first needs to authorize it.

[Ayush-Patel-56]

@Sujini-kudupudi can you please fix the failing CI test

[Sujini-kudupudi]

@Ayush-Patel-56 Could you please check it once?

[Ayush-Patel-56]

@Sujini-kudupudi its still failing

[nikhildhamdhere15]

@Sujini-kudupudi It looks like the CI pipeline is still failing on the CI / check step after your last commit. Could you check the build logs or test outputs again?

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
mergeship	Ready	Preview, Comment	Jun 20, 2026 4:40am

[jakharmonika364]

Also this PR has a bunch of unrelated stuff mixed in (resend bump, the issues.ts Octokit rewrite, as any casts in supabase/server.ts) - can we split those out? Makes this harder to review than it needs to be.

The filterAndRank fix itself looks right.

[jakharmonika364]

profiles has no user_id column, it's id (every other lookup in the codebase uses .eq('id', user.id)). This silently fails and userLevel defaults to 0 always - error isn't checked. Should be .eq('id', user.id).