Fix: Enable save button for provider dropdown and checkbox changes

[daniel-lxs]

Problem

The save button wasn't enabling when users changed provider settings like dropdowns and checkboxes. This was because setApiConfigurationField was treating all changes from undefined to a defined value as 'initial sync' and not marking the form as dirty.

Solution

Added an optional isUserAction parameter (defaults to true) to setApiConfigurationField to distinguish between:

• User actions (should enable save button) - the default behavior
• Automatic initialization (shouldn't enable save button) - explicitly pass false

Changes Made

• Modified setApiConfigurationField in SettingsView.tsx to accept optional isUserAction parameter
• Updated components that perform automatic initialization to pass isUserAction: false:
  • ModelPicker.tsx - when auto-setting initial model
  • ThinkingBudget.tsx - when auto-adjusting reasoning effort and thinking tokens
  • ApiOptions.tsx - when setting default models during provider switching
  • HuggingFace.tsx - when auto-setting default provider
  • Unbound.tsx - when auto-selecting first available model

What This Fixes

✅ Checkboxes with default values (like openRouterUseMiddleOutTransform ?? true) now enable the save button when clicked
✅ Provider dropdown changes now enable the save button
✅ Any user interaction with settings properly marks the form as dirty
✅ Automatic initialization (like setting default models) won't falsely enable the save button

Testing

• All TypeScript compilation checks pass
• All linting checks pass
• The fix is backward compatible - components that don't need to distinguish between user/auto actions work unchanged

Fixes #[issue-number]

---

Important

Adds isUserAction parameter to setApiConfigurationField to enable save button for user changes in provider settings.

• Behavior:
  • Adds isUserAction parameter to setApiConfigurationField in SettingsView.tsx to differentiate user actions from automatic initializations.
  • User actions enable the save button; automatic initializations do not.
• Components:
  • Updates ModelPicker.tsx, ThinkingBudget.tsx, ApiOptions.tsx, HuggingFace.tsx, and Unbound.tsx to pass isUserAction: false for automatic initializations.
• Fixes:
  • Enables save button for checkbox and dropdown changes in provider settings.
  • Ensures user interactions mark the form as dirty, while automatic initializations do not.
• Testing:
  • All TypeScript compilation and linting checks pass.
  • Backward compatibility maintained for components not distinguishing user/auto actions.

^{This description was created by for 55f7792. You can customize this summary. It will automatically update as commits are pushed.}

[roomote]

Thank you for your contribution! This PR successfully fixes the save button enablement issue for provider settings. The solution is clean, backward-compatible, and well-implemented. I've left some suggestions inline to help improve the implementation.

[roomote]

Consider adding JSDoc documentation for this function to explain the purpose of the isUserAction parameter. This would help future developers understand when to pass false. For example:

Suggested change

	const setApiConfigurationField = useCallback(
	/**
	* Updates a field in the API configuration
	* @param field - The field to update
	* @param value - The new value
	* @param isUserAction - Whether this change is from user interaction (true) or automatic initialization (false).
	* User actions will mark the form as dirty and enable the save button.
	*/
	const setApiConfigurationField = useCallback(
	<K extends keyof ProviderSettings>(field: K, value: ProviderSettings[K], isUserAction: boolean = true) => {

[roomote]

The logic here is correct, but consider adding a comment to explain why we skip change detection for automatic initialization. This would help future maintainers understand the pattern.

[roomote]

Good use of the comment here to clarify that this is automatic initialization! This pattern makes the intent very clear.