## Problem When a partial config update is applied via the projection system, nil slice and map fields (not present in the update payload) are written through to YAML, wiping out existing values. For example, `logicalRestore.options.customOptions` gets deleted when an unrelated config field is updated. ## Impact - Admin configuration can be silently corrupted by partial updates - Users lose custom settings (e.g., `customOptions` for logical restore) without any warning - Hard to diagnose — the config looks correct in memory but the persisted YAML is wrong ## Expected Behavior Partial config updates should only modify the fields included in the update payload. Existing slices and maps not present in the update should be preserved. ## Fix MR !1111 fixes the projection Store to skip nil slices and maps during YAML serialization.