rcourtman d20671a736 Expose Discovery model override in AI settings ...

The backend has had DiscoveryModel + GetDiscoveryModel() with the
shared-default fallback alongside ChatModel and PatrolModel, but the
settings UI only surfaced Assistant and Patrol overrides. Discovery
silently used whatever the shared default was set to, with no way to
dial it independently — yet Discovery is the surface where a cheaper
model (e.g. Haiku) is most often the right tradeoff.

Thread discoveryModel through the form state, load, save payload, and
failure analyzer, and render a third picker in the Model Overrides
section mirroring the Assistant/Patrol pattern. Generalize the section
header and shared-default copy so they no longer enumerate surfaces.

Extend the frontend-primitives contract to recognize Discovery alongside
Assistant and Patrol as a per-surface override, and lock the picker
presence into settingsArchitecture.test.ts.

2026-05-17 20:39:46 +01:00

..

internal

Clear v6 prerelease-to-GA promotion gate

2026-04-20 16:33:03 +01:00

v6

Expose Discovery model override in AI settings

2026-05-17 20:39:46 +01:00

control_plane.json

Capture Pulse Intelligence product direction

2026-05-06 15:56:45 +01:00

control_plane.schema.json

Map legacy stable releases in control plane

2026-04-11 13:23:07 +01:00