feat: add agentic cli preferences

[ieow]

Explanation

References

Checklist

• I've updated the test suite for new or updated code as appropriate
• I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
• I've communicated my changes to consumers by updating changelogs for packages I've changed
• I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them

---

Note

Medium Risk
Extending NotificationPreferences with a new required field is a breaking type change for consumers that build or spread preference objects without agenticCli.

Overview
Adds agentic CLI notification settings to authenticated user storage: a new AgenticCliPreference type (in-app and push toggles) and a required agenticCli field on NotificationPreferences.

Test mocks were updated so MOCK_NOTIFICATION_PREFERENCES includes sample agenticCli values.

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

[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 a732e09. Configure here.}

[cursor]

Validation schema missing new agenticCli field

High Severity

The NotificationPreferences type now requires agenticCli, but NotificationPreferencesSchema in validators.ts was not updated to include a corresponding agenticCli field. The assertNotificationPreferences function uses this schema to validate API responses, then asserts the data is NotificationPreferences. This means API data missing agenticCli will pass validation, yet downstream code will trust it's present — causing runtime undefined access errors.

 

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