Log invalid GraphQL enum values as warnings instead of errors

[alokedesai]

Downgrades all of the Make sure to update client GraphQL types! errors to warnings.

These end up flooding sentry (consuming our quota and/ or causing us to get rate limited). There's no reason they need to hit Sentry because they aren't actually user visible changes.

[oz-for-oss]

@alokedesai

I'm starting a first review of this pull request.

You can view the conversation on Warp.

I completed the review and no human review was requested for this pull request.

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

[oz-for-oss]

Overview

This PR downgrades unknown GraphQL enum fallback reporting from report_error! to log::warn! across AI model, workspace policy, and agent permission conversions.

Concerns

• Policy and permission enum fallbacks now only produce local warnings, so server/client schema skew in admin-controlled settings can silently fall back to user defaults without central reporting.

Security

• Workspace data collection and AI autonomy settings are policy controls; losing centrally reported errors makes it harder to detect new server enum values that old clients treat as RespectUserSetting or no override.

Verdict

Found: 0 critical, 2 important, 0 suggestions

Request changes

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

[oz-for-oss]

⚠️ [IMPORTANT] [SECURITY] This fallback controls workspace data-collection policy; downgrading it to a local warning hides server/client schema skew while falling back to RespectUserSetting, so a new restrictive server value can become user-controlled without central reporting.

[oz-for-oss]

⚠️ [IMPORTANT] [SECURITY] These autonomy settings gate agent actions; if the server adds a new restrictive enum value, old clients now drop the override to None and only log locally, which can silently relax admin permission controls.