mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-05-21 02:09:57 +00:00
af422ddf2f
Two real UX bugs in the Verify Patrol panel: 1. The button silently tested the previously-saved model instead of the operator's pending dropdown selection. Clicking Verify after changing the model would re-run preflight against the OLD model and the operator would believe the new selection was verified. 2. The result panel rendered the cached green badge even when the form's current selection was a different model from the one in the cache, with no visual cue that the verified result was for something other than what they were looking at. Fixes: - runPatrolToolPreflight now passes form.patrolModel as the model override on the POST. Empty form value falls through to the configured shared default on the backend. - PatrolPreflightControl computes isStaleAgainstFormSelection by comparing the bare model name in form.patrolModel to the cached result.model. When stale, the panel switches to amber tone with a headline that names both models and a detail line prompting the operator to click Verify Patrol. - stripModelProvider helper handles "provider:model" prefix. Architecture guardrail extended with three assertions covering the form-aware verify path and the staleness indicator wiring. frontend-primitives contract updated. Live verified: changing the dropdown from deepseek-v4-flash to deepseek-v4-pro before saving switches the panel from green "Tool calling verified" to amber "Verified result is for deepseek-v4-flash, your current selection is deepseek/deepseek-v4-pro · Click Verify Patrol to test the pending selection." |
||
|---|---|---|
| .. | ||
| internal | ||
| v6 | ||
| control_plane.json | ||
| control_plane.schema.json | ||