Rollouts — change config safely, a pilot first.

• Use this when a change could break boxes at startup — e.g. swapping a reseller URL or flipping a render flag across a segment.
• 1. Tag a small pilot group on the Devices page (plus the wider target tag).
• 2. Stage a rollout here (helix flags or an m3u source), targeting the segment tag with that pilot tag → Create draft.
• 3. Apply pilot, then watch Metrics: synced = box applied & converged · drifted = polled but not converged (warning) · awaiting = not seen yet.
• 4. Promote to the rest if healthy, or Rollback — every applied device is restored from its pre-change snapshot.
• Auto-failover actions also appear here as auto-failover rollouts (auditable + rollback-able).