fix: Use Aurora user ID for personal climb search filters

[marcodejongh]

The personal progress filters (hideAttempted, hideCompleted, showOnlyAttempted,
showOnlyCompleted) query the Aurora bids/ascents tables which store the Aurora
user ID (integer), not the NextAuth user ID (UUID string).

Previously, the code tried to parse the NextAuth user ID as an integer which
would result in NaN, causing the personal filters to never work.

Now the resolver looks up the Aurora user ID from the aurora_credentials table
based on the authenticated user's NextAuth ID and the board name.

[vercel]

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

Project	Deployment	Review	Updated (UTC)
boardsesh	Building	Preview, Comment	Jan 3, 2026 3:56am

[claude]

Claude Review

✅ Ready to merge - The fix correctly resolves the user ID type mismatch. Minor observations below, but nothing blocking.

Minor observations:

1. packages/backend/src/graphql/resolvers/climbs/queries.ts:76-91: Silent failure when Aurora credentials not found - if a user enables personal filters but hasn't linked their Aurora account, the filters silently do nothing. Consider logging a warning in development or returning an indicator in the response.

2. packages/backend/src/graphql/resolvers/climbs/queries.ts:77: The additional DB query is only executed when personal filters are enabled, which is good optimization. No issues here.

No documentation updates required - this is an internal bug fix that doesn't change the documented architecture.