Update Git Operations AI client billing policy

[exzshao]

Description

Adds the client-side follow-up for the Git Operations AI enterprise/tier policy:

• Adds isGitOperationsAiEnabled to the client GraphQL schema and WarpAiPolicy fragments/models.
• Converts the new policy into the app-level workspace billing model.
• Gates Git Operations AI requests and the “Commit & Pull Request Generation” setting on the billing policy instead of the previous hardcoded enterprise client gate.
• Removes the stale TODO that asked for this client-side gate.

This is intended to pair with the server-side schema/policy change in warpdotdev/warp-server#10798. Keeping this PR as draft until the server field is available to clients.

Linked Issue

N/A — client follow-up for the server GraphQL schema/policy PR.

Screenshots / Videos

N/A — this is policy/schema wiring. The existing setting is hidden when the new billing policy disables Git Operations AI.

Testing

• cargo fmt --manifest-path /Users/edward/Repos/edward-update-git-ops-ai-schema/Cargo.toml --all -- --check
• cargo clippy --manifest-path /Users/edward/Repos/edward-update-git-ops-ai-schema/Cargo.toml -p warp_graphql_schema -p warp_graphql -p warp --all-targets --all-features --tests -- -D warnings
• git --no-pager diff --check

No new integration test added; this is a small billing-policy plumbing change that reuses existing settings/request gates.

Agent Mode

• Warp Agent Mode - This PR was created via Warp's AI Agent Mode

Agent conversation: https://staging.warp.dev/conversation/281d784d-6c87-414f-89db-1b29f771f571

Co-Authored-By: Oz oz-agent@warp.dev

[oz-for-oss]

@exzshao

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 wires the new Git Operations AI billing policy through the GraphQL schema/model layer and uses it to gate the Git dialog AI request path plus the corresponding AI settings toggle.

Concerns

• Adding a required serde field to WarpAiPolicy can make existing cached billing_metadata_json rows fail to deserialize, causing the app to drop cached billing metadata until a successful refresh.
• No security-specific findings.

Verdict

Found: 0 critical, 1 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] Existing billing_metadata_json cache rows can contain warp_ai_policy without this new field; without a serde default, deserializing the cached BillingMetadata fails and drops all cached billing policy data until refresh.

Suggested change

	pub is_git_operations_ai_enabled: bool,
	#[serde(default)]
	pub is_git_operations_ai_enabled: bool,