Fix BYOK status indicator handling of legacy configurations

[Copilot]

Status indicator green dot disappeared for all BYOK models after adding validation state tracking. Legacy configurations with is_valid: undefined/null were incorrectly treated as invalid.

Changes

Updated status indicator condition (sidebar and dropdown):

// Before: required is_valid to be truthy
!!form[idx].provider_id && form[idx].is_valid

// After: only hide when explicitly false
!!form[idx].provider_id && form[idx].is_valid !== false

State tracking in handleVerify():

• Set is_valid: true on successful validation
• Set is_valid: false on validation failure (error response and exception paths)

Behavior

provider_id	is_valid	Green Dot
exists	true	✅ Shows
exists	undefined/null	✅ Shows (legacy)
exists	false	❌ Hidden
missing	any	❌ Hidden

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[Feature Request] BYOK models stays “Active” after re-save fails (invalid key/model name)</issue_title>
<issue_description>### Motivation

If a BYOK config was saved successfully before, but later the API key becomes invalid or the user enters a wrong model name, clicking Save again can fail. The left sidebar status still shows green (Active), but it should switch to Inactive/Error to reflect the invalid configuration.

Solution

No response

Alternatives

No response

Additional context

No response</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes [Feature Request] BYOK models stays “Active” after re-save fails (invalid key/model name) #1180

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[Pakchoioioi]

I just tested this, and the modification is incorrect. The green dot on the left is now missing regardless of whether the configuration succeeded or failed. However, the expected behavior is that the green dot should only be hidden when the configuration is invalid.