Save button allows no‑op updates and shows success toasts

This is a save-without-changes issue: the “Save Changes” button commits the form even when no fields were modified, which can mislead users and add unnecessary writes
Clicking Save with identical values still shows a successful save, implying something changed when it didn’t, and training users to click redundantly