Add toggle_visible to the native omnibar-shown pixel

[YoussefKeyrouz]

Task/Issue URL: https://app.asana.com/1/137249556945/project/72649045549333/task/1217295011063286?focus=true
Tech Design URL (if applicable):
API Proposals URL(s) (if applicable):

Description

Description

Adds a toggle_visible parameter to m_aichat_experimental_omnibar_shown
We fire a pixel whenever the native Input Screen is shown, but can't yet tell what fraction of those
impressions actually offered the Search/Duck.ai toggle. This adds one param:

Pixel	Added
m_aichat_experimental_omnibar_shown / _count	toggle_visible

toggle_visible is a boolean, reusing the same DuckChatInternal.resolvedTogglePosition() != null
check used in other pixels pixel.

Steps to test this PR

Enable the nativeInputField and nativeInputSearchOnly feature flag, attach logcat, filter for Pixel sent:.

toggle_visible on the native Input Screen

• With Search + Duck.ai enabled (toggle offered), open the Input Screen —
  m_aichat_experimental_omnibar_shown_count carries toggle_visible=true
• Turn Search + Duck.ai off so no toggle is offered, open the Input Screen again ->
  toggle_visible=false

UI changes

No UI changes

---

Note

Low Risk
Analytics-only pixel parameter and wiring; no user-facing behavior or security-sensitive paths.

Overview
Adds toggle_visible to the pixel definitions for m_aichat_experimental_omnibar_shown and m_aichat_experimental_omnibar_shown_count, so analytics can split native input impressions by whether the Search/Duck.ai toggle was on screen.

fireOmnibarShown() now passes toggle_visible on both count and daily fires, derived from DuckChatInternal.resolvedTogglePosition() != null. RealDuckChatPixels takes DuckChatInternal as a new constructor dependency.

Tests were updated to supply the mock internal API, and RealDuckChatPixelsTest now asserts toggle_visible=true vs false for the two toggle cases.

^{Reviewed by Cursor Bugbot for commit 4bd21d6. Bugbot is set up for automated code reviews on this repo. Configure here.}

[YoussefKeyrouz]

• Add page_type and source to prompt submission pixels #9568
• Add duck.ai entry point pixel #9550
• Add the wide_return_session wide event for app returns #9516
• Add the m_app_return pixel, fired on every foreground return #9502
• Add toggle_visible to the native omnibar-shown pixel #9479 👈 (View in Graphite)
• Report the toggle's default side on unified input submissions #9467
• Report Duck.ai capability state on the daily feature-state pixel #9465
• develop

This stack of pull requests is managed by Graphite. Learn more about stacking.

[github-actions]

Privacy Review task: https://app.asana.com/0/69071770703008/1217448037272161

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit a9e17c5. Configure here.}