Report Duck.ai capability state on the daily feature-state pixel

[YoussefKeyrouz]

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

Description

Extends m_browser_feature_daily_active_user_d the pixel we already send once a day per active
user with each module's feature state — to include Duck.ai, which contributed nothing to it. Three
new params:

Param	Values	Meaning
duck_ai_input_mode	search_and_duck_ai / search_only	whether the config has the Search/Duck.ai toggle
duck_ai_native_input	1 / 0	the native input field is the active input surface
duck_ai_contextual	1 / 0	contextual mode is enabled

---

Note

Low Risk
Read-only analytics on an existing daily pixel pattern; no auth, payments, or user data handling changes.

Overview
Extends the daily m_browser_feature_daily_active_user_d pixel so Duck.ai contributes three new parameters: duck_ai_input_mode (search_and_duck_ai vs search_only), duck_ai_native_input, and duck_ai_contextual.

A new DuckAiFeatureStateReporterPlugin registers with the existing BrowserFeatureStateReporterPlugin multibinding. Input mode is derived from Duck Chat feature toggles and repository settings; native input and contextual flags come from DuckAiFeatureState. Pixel definitions in browser_feature_state.json5 document the enums, and unit tests cover off/on states and independence of input mode from the native input surface.

^{Reviewed by Cursor Bugbot for commit 344781c. 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
• Report the toggle's default side on unified input submissions #9467
• Report Duck.ai capability state on the daily feature-state pixel #9465 👈 (View in Graphite)
• 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/1217380986937115

[malmstein]

Reviewed statically, telemetry only.

The definition file is the standout: it retro-documents m_browser_feature_daily_active_user_d, which had none. Audited it against every contributor and it is exact, no plugin missing, nothing documented that is not sent, and both enums match the emitted strings (TOP/BOTTOM/SPLIT_TOP from OmnibarType.typeName, new_tab_page/last_opened_tab/specific_page from getDailyPixelValue). The new plugin follows the existing shape and all three params are bounded with no PII.

One question inline on capability read timing, since its default is also a valid value.