Force Duck.ai state in the contextual input widget

The contextual widget shares the per-tab input-state store with the main
omnibar widget. For search-only users the omnibar publishes a
browser/search state that leaked into the contextual sheet, flipping the
tab off "chat" (hiding the tools row) and surfacing the search-only
start-chat shortcut.

applyState now forces DUCK_AI_CONTEXTUAL / DUCK_AI for the contextual
widget so it always renders as a Duck.ai composer, and the StartChat
plugin (a search-only address-bar shortcut that reads the shared state)
is no longer added in the contextual widget.

Also drops the obsolete setModelPickerEnabled assertion from the manager
test, since the picker is now driven through the bound modelPickerEnabled
flow after the develop merge.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: malmstein

duckchat/duckchat-impl/src/main/java/com/duckduckgo/duckchat/impl/ui/nativeinput/views/NativeInputModeWidget.kt

@@ -365,6 +365,10 @@ class NativeInputModeWidget @JvmOverloads constructor(
             launch {
                 viewModel.plugins.collect { plugins ->
                     for (plugin in plugins) {
+                        // The start-chat shortcut is a search-only address-bar affordance; it has no place
+                        // in the contextual sheet's Duck.ai composer (and reads the shared per-tab state,
+                        // which can be search-only), so skip it there.
+                        if (isContextualWidget && plugin.containerId == R.id.startChatContainer) continue
                         val container = findViewById<FrameLayout?>(plugin.containerId) ?: continue
                         val pluginView = plugin.createView(context, this@NativeInputModeWidget)
                         container.removeAllViews()
@@ -690,7 +694,19 @@ class NativeInputModeWidget @JvmOverloads constructor(
         floatingButtons?.setNewLineButtonVisible(visible)
     }
 
-    private fun applyState(state: NativeInputState) {
+    private fun applyState(incomingState: NativeInputState) {
+        // The contextual sheet is always a Duck.ai chat surface, but the shared per-tab state store can
+        // carry a browser/search state written by the main omnibar widget (e.g. for search-only users).
+        // Force the Duck.ai context/toggle here so the contextual widget never renders that search state,
+        // which would otherwise flip the tab off "chat" (hiding the chat-tab controls).
+        val state = if (isContextualWidget) {
+            incomingState.copy(
+                inputContext = NativeInputState.InputContext.DUCK_AI_CONTEXTUAL,
+                toggleSelection = NativeInputState.ToggleSelection.DUCK_AI,
+            )
+        } else {
+            incomingState
+        }
         val previousState = nativeInputState
         val firstStateEmission = previousState == null
         val contextChanged = previousState?.inputContext != state.inputContext

duckchat/duckchat-impl/src/test/kotlin/com/duckduckgo/duckchat/impl/contextual/RealContextualNativeInputManagerTest.kt

@@ -158,7 +158,7 @@ class RealContextualNativeInputManagerTest {
     }
 
     @Test
-    fun `when native chat input enabled and onInputMode then card shown and picker enabled`() {
+    fun `when native chat input enabled and onInputMode then card shown`() {
         val enabled = MutableStateFlow(true)
         whenever(duckChat.observeNativeChatInputEnabled()).thenReturn(enabled)
         val card = mockCard()
@@ -178,8 +178,9 @@ class RealContextualNativeInputManagerTest {
 
         testee.onInputMode()
 
+        // The model picker is re-enabled via the bound modelPickerEnabled flow (covered separately);
+        // here we assert the contextual card itself is shown in INPUT mode.
         verify(card).visibility = View.VISIBLE
-        verify(widget).setModelPickerEnabled(true)
     }
 
     @Test