OperationError: The operation failed for an operation-specific reason

## Error

```
The operation failed for an operation-specific reason
```

## Stack trace

```
../app/javascript/components/common/SingleSelect.tsx:5 in SingleSelect
../app/javascript/components/journey/badges-list/OrderSwitcher.tsx:27 in OrderSwitcher
../app/javascript/components/journey/BadgesList.tsx:18 in BadgesList
../app/javascript/components/common/Tab.tsx:54 in TabPanel
../app/javascript/components/journey/JourneyPage.tsx:32 in JourneyPage
../node_modules/@sentry/react/src/errorboundary.tsx:101 in new ErrorBoundary
../node_modules/@tanstack/react-query/src/QueryClientProvider.tsx:29 in QueryClientProvider
```

## Tracking Details
- **Project**: exercism-js
- **Sentry**: [OperationError: The operation failed for an operation-specific reason](https://thalamus-ai.sentry.io/issues/134117897/)
- **Culprit**: id(app/javascript/components/dropdowns/useDropdown)
- **First seen:** Jul 14, 2026

Start with app/javascript/components/common/SingleSelect.tsx and the useDropdown culprit identified by Sentry, then trace the calls through OrderSwitcher.tsx, BadgesList.tsx, and Tab.tsx. Use the linked Sentry event and stack trace to determine the operation-specific failure; done means the error no longer occurs in this path.

Written by the indexing model from the issue text.