From 2cf213a77d2a50dcd47c0b0ab07c49f97bdd0534 Mon Sep 17 00:00:00 2001
From: rcourtman <8825017+rcourtman@users.noreply.github.com>
Date: Wed, 7 Oct 2026 16:34:21 +0100
Subject: [PATCH] Describe the Patrol mode selector where it renders today

patrol-intelligence still described the Patrol mode selector as living in
"that header and configuration dialog", with the constrained configuration
dialog using the prominent layout. The configuration dialog was removed in
27ba85ddc6. renderAutonomyPolicyControl has one call site,
PatrolIntelligenceHeader's `Mode and automation` disclosure, which uses the
default segmented variant, and the only remaining Patrol dialog, the
Autopilot acknowledgement, has no mode picker. The clause now says where
the header renders the selector. A surface that hosts it in constrained
space may still use the shared prominent layout.
---
 .../v6/internal/subsystems/patrol-intelligence.md   | 13 +++++++------
 1 file changed, 7 insertions(+), 6 deletions(-)

diff --git a/docs/release-control/v6/internal/subsystems/patrol-intelligence.md b/docs/release-control/v6/internal/subsystems/patrol-intelligence.md
index cd901c6f4e..b96df3b120 100644
--- a/docs/release-control/v6/internal/subsystems/patrol-intelligence.md
+++ b/docs/release-control/v6/internal/subsystems/patrol-intelligence.md
@@ -1624,12 +1624,13 @@ ready raises a fixed warning notification, a failed Patrol mode save raises an e
 notification, and neither offers an Assistant handoff. A provider or model save
 in Settings > Provider & Models reports the readiness summary, provider and
 model in its own save message.
-The Patrol mode selector in that header and configuration dialog must
-compose the shared `frontend-modern/src/components/shared/FilterButtonGroup.tsx`
-instead of rebuilding a local active-button group. The wide default Patrol
-header uses the segmented layout; the constrained configuration dialog may use
-the shared prominent layout so all four mode labels remain readable without
-inventing a Patrol-local selector. Patrol owns the default visible four-level
+The Patrol mode selector in that header must compose the shared
+`frontend-modern/src/components/shared/FilterButtonGroup.tsx` instead of
+rebuilding a local active-button group. When the header shows Patrol mode
+options, it renders the selector in the segmented layout inside its `Mode and
+automation` disclosure; a constrained surface that hosts it may use the shared
+prominent layout so all four mode labels remain readable without inventing a
+Patrol-local selector. Patrol owns the default visible four-level
 policy presentation (`Watch only`, `Ask first`, `Safe auto-fix`,
 `Autopilot`), entitlement locks, and the rule that choosing the highest
 Autopilot level sends `full_mode_unlocked:true` while choosing any lower level clears that