rcourtman 357b1a505e Explain why the Container update risk switch is locked ...

Patrol settings showed the Container update risk switch dimmed on
installs without ai_alerts and gave no reason, so a free install could
not tell a plan limit from a broken setting.

The card now renders the canonical Patrol availability presentation.
patrolAutonomyAvailability.ts keeps one precedence (runtime lock, then
hidden commercial surfaces, then plan lock) and the only action labels,
while Patrol mode and container update risk each supply their lock
state and copy. Links appear only when the session allows upgrade
prompts, and installs that hide commercial surfaces get a neutral line
with no plan or Pro wording. The explanation is tied to the switch with
aria-describedby, because the shared Toggle does not render its
locked/lockedMessage props.

2026-10-05 22:16:21 +01:00

..

internal

Preserve the published 6.4.6 packet's release-line mapping

2026-10-02 21:15:35 +01:00

v6

Explain why the Container update risk switch is locked

2026-10-05 22:16:21 +01:00

control_plane.json

Cut 6.5 and later releases from main

2026-10-04 18:37:43 +01:00

control_plane.schema.json

…