fix: Use route angle for playlist climb stats

[marcodejongh]

When fetching climbs from a playlist, the stats (difficulty, stars, ascents) were being retrieved for the playlist's stored angle or the climb's original angle. This fix updates the query to use the current route angle instead, ensuring users see the correct metadata for their current board configuration.

Changes:

• Add angle parameter to GetPlaylistClimbsInput GraphQL type
• Update playlistClimbs resolver to use input angle for stats lookup
• Update client to pass the route angle in the query

[vercel]

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

Project	Deployment	Review	Updated (UTC)
boardsesh	Building		Jan 2, 2026 1:15pm

[claude]

Claude Review

✅ Ready to merge - Minor issue noted below, but nothing blocking.

Minor Issues

• Inconsistent angle validation (packages/backend/src/validation/schemas.ts:369): The new angle field uses z.number().int() without min/max bounds, while other angle validations in the same file use .min(0).max(90). Consider adding bounds for consistency: z.number().int().min(0).max(90).