Bug: LLM harness selector is not consistently focusable or clickable

[touch2be]

Problem

The LLM harness selector is not always selected/focused, which prevents users from controlling it via keyboard. In some cases, clicking the selector also does not activate it.

Expected Behavior

The LLM harness selector should reliably receive focus/selection when clicked, so it can be controlled with the keyboard. Clicking it should always activate the selector/open the selection UI.

Current Behavior

Sometimes the selector is not focused or selected. As a result:

• Keyboard control does not work reliably
• Clicking the selector does not always activate it
• The UI can feel unresponsive or inaccessible

Steps to Reproduce

1. Open the screen containing the LLM harness selector.
2. Click the LLM harness selector.
3. Try to control the selection using the keyboard.
4. In some cases, the selector is not focused/selected or does not activate on click.

Impact

This affects keyboard accessibility and makes selecting an LLM harness unreliable.

[akemmanuel]

Root cause

The harness picker is the tab row in ModelSelector (Base UI Tabs).

1. A useEffect always focused the search input on open and on every dialogHarnessId change, so harness tabs never kept focus for keyboard navigation.
2. The trigger used preventDefault() + manual openDialog(), which could fight DialogTrigger and make opens unreliable.

Fix: 275a278 — focus the active harness tab (initialFocus + post-inventory focus), let DialogTrigger handle clicks.

[akemmanuel]

Reopening: reported still not fixed. I’m investigating the actual failing behavior and will follow up with a corrected fix.

[akemmanuel]

Follow-up fix pushed: 6bd39e7.

The first fix addressed dialog/tab focus, but the remaining/root interaction bug was in PromptBox:

• PromptBox had a blanket onClick={() => textarea.focus()} on the whole prompt surface.
• The model / LLM harness selector lives inside that surface.
• A selector click could bubble to PromptBox, which immediately refocused the textarea after the selector tried to activate/focus.
• That made the selector feel intermittently unclickable or unfocusable and broke keyboard control.

The fix now focuses the textarea only for non-interactive prompt-surface clicks, and ignores clicks originating from buttons, inputs, comboboxes, menu items, select triggers, and tabs.

Validation: pnpm vp check passes.