Summary

As discussed with @keithchong, Currently, our sync policy controls (auto-sync, prune, selfHeal) have different UI representations and YAML mapping behaviors. While the current checkbox for auto-sync correctly represents the backend logic, there's room for improvement in making the form-to-YAML relationship more intuitive.

Motivation

When users interact with sync policy controls, the resulting YAML changes aren't always predictable:

• Auto-sync checkbox can produce different YAML (automated: {} or automated: {enabled: true})
• Prune/SelfHeal use buttons with direct YAML mapping
• No visual indication of default vs explicit states

This can be confusing when switching between UI and YAML views or when troubleshooting configurations.

Current Behavior

• Auto-sync: Checkbox with implicit/explicit enabled states
  • automated: {} → checked
  • automated: {enabled: true} → checked
  • automated: {enabled: false} → unchecked
• Prune/SelfHeal: Push buttons with direct YAML mapping

Proposal

1. Create a consistent control pattern:
   • Either unify all as buttons (like prune/selfHeal)
   • Or enhance checkboxes to show default vs explicit states