Catalog option adapters and searchable configuration comboboxes

[quinCode]

Catalog option adapters and searchable configuration comboboxes

Parent

PRD #14: Run workspace usability rewrite

What to build

Replace raw configuration lists with searchable configuration controls. Endpoint, attack, judges, and input should use combobox-style controls backed by a stable OptionViewModel derived from generated API catalog types in one frontend adapter.

The combobox UI should render labels, short descriptions, badges, and search text without directly depending on raw catalog display fields in workspace components.

Acceptance criteria

• A centralized catalog adapter maps generated catalog types to OptionViewModel.
• OptionViewModel includes id, label, optional description, badges, and searchText.
• Endpoint, attack, judges, and input controls use searchable combobox behavior.
• Judges support multi-select behavior.
• Long labels and paths truncate or wrap intentionally and do not overflow adjacent panels.
• Missing optional metadata degrades gracefully without blank or broken options.
• Architecture tests prevent raw catalog display fields such as backend, class names, or file formats from spreading outside the adapter and generated API client.
• Frontend tests cover searching, selecting, multi-select judges, long-label rendering, and option fallback behavior.

Blocked by

• Issue 0013: Design tokens and base layout primitives
• Issue 0015: RunDraft state model with safe persistence

[quinCode]

Dependency note: blocked by #16 and #17.