Cover computer_use in the autonomy drift guard

The lowered check ignores three fields, not two. computer_use is the likeliest
of them to drift: the lowering carries it into AiAutonomySettings, so it reads
as an omission from the check rather than a field the check has no view of.
Adding it to autonomy_allowed_by_policy previously left every test passing.

Also drops caller descriptions from the two new doc comments, per AGENTS.md.

Author: warp-agent-staging[bot]

app/src/workspaces/user_workspaces.rs

@@ -1065,8 +1065,9 @@ impl UserWorkspaces {
     /// The tier policy is billing entitlement, which belongs to the paying workspace rather
     /// than to any team, so it is read from the workspace either way.
     ///
-    /// Callers are on render and per-action paths, so this asks each team's settings the
-    /// question directly rather than lowering them into [`AiAutonomySettings`] first.
+    /// Asks each team's settings the question directly rather than lowering them into
+    /// [`AiAutonomySettings`] first, which would compile every list entry into a regex to
+    /// answer something that needs none.
     pub fn all_teams_allow_ai_autonomy(&self) -> bool {
         let tier_allows_autonomy = self.current_workspace().is_none_or(|workspace| {
             workspace

app/src/workspaces/user_workspaces_tests.rs

@@ -48,7 +48,9 @@ use warpui::{AddSingletonModel, App, Element, TypedActionView, View, ViewHandle,
 use warpui_extras::user_preferences;
 
 use super::*;
-use crate::ai::execution_profiles::{ActionPermission, WriteToPtyPermission};
+use crate::ai::execution_profiles::{
+    ActionPermission, ComputerUsePermission, WriteToPtyPermission,
+};
 use crate::ai::llms::LLMModelHost;
 use crate::auth::AuthManager;
 use crate::cloud_object::model::persistence::CloudModel;
@@ -1556,8 +1558,10 @@ fn test_team_autonomy_configuration_agrees_with_the_lowered_policy() {
                 ..Default::default()
             },
         ),
-        // Neither of the next two counts as evidence of autonomy in the lowered check, so
-        // both implementations must ignore them.
+        // None of the next three counts as evidence of autonomy in the lowered check, so
+        // both implementations must ignore them. `write_to_pty` and `computer_use` are the
+        // likeliest to drift: the lowering does carry them into `AiAutonomySettings`, so
+        // they read as omissions from the check rather than as fields it has no view of.
         (
             "write_to_pty only",
             TeamAiAutonomySettings {
@@ -1568,6 +1572,16 @@ fn test_team_autonomy_configuration_agrees_with_the_lowered_policy() {
                 ..Default::default()
             },
         ),
+        (
+            "computer_use only",
+            TeamAiAutonomySettings {
+                computer_use: EnforceableSetting {
+                    value: Some(ComputerUsePermission::AlwaysAsk),
+                    is_enforced_by_workspace: false,
+                },
+                ..Default::default()
+            },
+        ),
         (
             "create_plans only",
             TeamAiAutonomySettings {

app/src/workspaces/workspace.rs

@@ -1122,9 +1122,8 @@ impl TeamAiAutonomySettings {
     /// Whether an admin configured any of the policies that count as evidence autonomy is
     /// in use — the same fields the lowered [`AiAutonomySettings`] is inspected for.
     ///
-    /// Answers without lowering on purpose. Lowering compiles every allow- and denylist
-    /// entry into a regex, and the callers asking this question are on render and
-    /// per-action paths that would pay for that on every frame and then discard it.
+    /// Answers without lowering on purpose: lowering compiles every allow- and denylist
+    /// entry into a regex, and this question does not need one.
     pub fn configures_any_policy(&self) -> bool {
         self.apply_code_diffs.value.is_some()
             || self.read_files.value.is_some()