A confirmed customization could silently vanish: the modal closed the
moment Confirm was clicked, so a save that failed or hung (dev server
hiccups, transaction timeouts) looked identical to a successful one,
and a thrown preferences write escalated to the app error boundary.
Confirm now spins until the save response and the refreshed side menu
data land, the dialog stays open with an inline error on failure, the
preference routes report failures as responses instead of throwing,
and the preferences transaction retries retriable Prisma errors.
James Ritchie
fd8f3232c8