fix: use composerSettings instead of settings in onProviderModelSelect

The model picker displays models based on composerSettings (which
incorporates the active thread's environment server config), but the
onProviderModelSelect handler was resolving model selections against the
primary environment's settings. This mismatch could cause model selections
to silently fail when the active thread's environment has custom models or
instance config that differs from the primary environment.

Use composerSettings consistently so display and selection logic agree.

Author: cursoragent

apps/web/src/components/ChatView.tsx

@@ -4449,7 +4449,7 @@ function ChatViewContent(props: ChatViewProps) {
       }
       const resolvedModel = resolveAppModelSelectionForInstance(
         instanceId,
-        settings,
+        composerSettings,
         providerStatuses,
         model,
       );
@@ -4491,7 +4491,7 @@ function ChatViewContent(props: ChatViewProps) {
       setComposerDraftModelSelection,
       setStickyComposerModelSelection,
       providerStatuses,
-      settings,
+      composerSettings,
     ],
   );
   const onEnvModeChange = useCallback(