feat(tui): ctrl+a toggle to hide unconfigured providers in the model picker

[SilentKnight87]

What does this PR do?

Adds a ^a toggle to the TUI model picker's provider stage that hides providers the user hasn't explicitly configured — the same explicit-providers subset the desktop chat picker now defaults to after #60514.

History / scope note: as originally filed (June 19) this PR implemented configured-only filtering across CLI/REST/gateway/desktop/TUI. #60514 (fixing #56974) has since landed the backend params (explicit_only, include_unconfigured) and the desktop-picker defaults, so this PR is rescoped to the surface it left open: the TUI picker deliberately keeps the full provider universe for setup affordances ("paste KEY to activate"), and this change adds user control without touching that default.

Type of Change

• ✨ New feature (non-breaking change that adds functionality)
• ✅ Tests (adding or improving test coverage)

Changes Made

• ui-tui/src/components/modelPicker.tsx
  • ^a in the provider stage toggles between the full universe (include_unconfigured: true — unchanged default) and explicitly configured providers (explicit_only: true, reusing the param introduced by fix: limit desktop model pickers to explicit providers (#56974) #60514).
  • model.options request params extracted into a pure modelOptionsRequestParams helper; refetch effect gains a cancellation guard and loading state on toggle.
  • Footer hint advertises the binding: ^a hide unconfigured ↔ ^a show all.
• ui-tui/src/__tests__/modelPicker.test.ts
  • Param construction for both toggle states, including refresh preservation.

How to Test

1. Open the TUI /model picker — full provider list with setup rows, as today.
2. Press ^a — only explicitly configured providers remain (matches the desktop chat picker subset).
3. Press ^a again — full list returns. Filter and selection state reset cleanly on toggle.

Checklist

• I've read the Contributing Guide
• My commit messages follow Conventional Commits
• I searched for existing PRs to make sure this isn't a duplicate (rescoped to complement fix: limit desktop model pickers to explicit providers (#56974) #60514 rather than duplicate it)
• My PR contains only changes related to this feature (2 files, +91/−16)
• I've added tests for my changes
• I've tested on my platform: macOS
• I've considered cross-platform impact (frontend-only, no platform-specific code)

Screenshots / Logs

• npm exec --workspace ui-tui prettier -- --check — pass
• npm run typecheck --workspace ui-tui — pass
• npm run test --workspace ui-tui -- src/__tests__/modelPicker.test.ts src/__tests__/providers.test.ts — 16 passed

[SilentKnight87]

Updated this branch against current main and resolved the merge conflicts in:

• apps/desktop/src/app/shell/model-menu-panel.tsx
• hermes_cli/inventory.py

Resolution kept the configured-only query key behavior and preserved the newer upstream moa exclusion for unconfigured rows.

Local validation after the merge:

• scripts/run_tests.sh tests/hermes_cli/test_inventory.py tests/test_tui_gateway_server.py -k configured_only — 6 passed
• npm run test:ui --workspace apps/desktop -- src/lib/model-options-query.test.ts — 2 passed

I also ran the broader targeted Python files (tests/hermes_cli/test_inventory.py and tests/test_tui_gateway_server.py): inventory passed 39/39; the TUI gateway file had the existing unrelated test_browser_manage_connect_default_local_reports_launch_hint browser-launch-hint failure that was already documented in the PR body.

GitHub now reports the PR as mergeable; waiting on repository checks/review state.

[SilentKnight87]

Rescoped following #60514. The original version of this PR (June 19) implemented configured-only filtering across the backend, desktop, and TUI; #60514 has since landed the backend params and desktop defaults in response to #56974, so this PR now carries only the remaining surface — a ^a toggle in the TUI picker, reusing the explicit_only param #60514 introduced. The TUI's full-universe default is unchanged. Diff is now 2 files, +91/−16.

[teknium1]

Thanks for narrowing this to the remaining TUI surface. The current picker still unconditionally requests include_unconfigured: true at ui-tui/src/components/modelPicker.tsx:60-69, while the existing RPC already accepts explicit_only at tui_gateway/server.py:12902-12913.

Problems

• The added tests at ui-tui/src/__tests__/modelPicker.test.ts:53-82 validate only modelOptionsRequestParams. They do not cover the new Ctrl+A path in the changed picker: refetching with explicit_only, restoring include_unconfigured, or resetting the filter and selection.

Suggested changes

• Add one interaction-level picker test that sends Ctrl+A and asserts both toggle requests and the visible-state reset.

Automated hermes-sweeper review.