Curtailment: Expose FULL_FLEET mode in manual UI

[rongxin-liu]

Status

Completed by PR #411.

Manual FULL_FLEET / full shutdown support exists in the Energy curtailment UI. Public manual PreviewCurtailmentPlan, StartCurtailment, and StopCurtailment are server-gated with curtailment:manage from #408.

Current Code State

Implemented on main:

• Proto and generated client/server code include CURTAILMENT_MODE_FULL_FLEET.
• Domain models include ModeFullFleet.
• FULL_FLEET selects every eligible candidate in scope.
• Service.Start accepts and persists FULL_FLEET events.
• Non-empty all-skipped FULL_FLEET is treated as insufficient load instead of a successful empty event from Curtailment: distinguish empty scope from all-skipped full fleet #407.
• Manual start UI supports fixed-kW reduction and full shutdown from Curtailment: Expose FULL_FLEET mode in manual UI #411.
• First-class site scope exists from Curtailment: Add first-class site scope #418.
• Backend response profile CRUD exists from Add curtailment response profile CRUD #426.
• Response profile UI and profile-backed manual runs exist from Curtailment: Response profiles and automation rules #435.
• MQTT automation CRUD/executor exists from Curtailment: Add MQTT automation backend #440.
• Settings UI for response profiles and automation rules exists from Curtailment: Response profiles and automation rules #441, with follow-up workflow UX polish from Improve curtailment workflow UX #443.
• Keyed multi-active UI and GetActiveCurtailment removal exists from Curtailment: support multiple active events in the UI #444.

Current Product Boundary

The MQTT source model changed after this issue was written. MQTT source config no longer carries curtail_mode, contracted kW, scope, minimum curtail duration, or direct dispatch state. PR #409 intentionally narrowed sources to connectivity plus signal/runtime state recording.

Source-triggered curtailment now belongs to automation: an enabled MQTT source is bound to a response profile by an automation rule. Users create and enable that automation explicitly.

Remaining Work Tracked Elsewhere

• Enforce MQTT curtailment automation while OFF remains asserted #451: enforce MQTT automation while OFF remains asserted.
• Catalog: distinguish org-scoped vs scoped permissions for UI gates #401: improve frontend scoped-permission gates.
• Add site selection to plan curtailment modal #425: add site selection to the manual plan curtailment modal.