How to persist and restore form validation state in a ClojureScript frontend?

When building a ClojureScript application (e.g., with Reagent, Re-frame, or plain atoms) you often need to keep validation information across page reloads or accidental navigations. The goal is to capture the current validation state, store it durably, and later restore it so the user sees the same error messages and field statuses.

1. Identify the validation data structure: Determine where validation results are kept (e.g., an atom holding a map of field‑to‑error strings or a Re‑frame db slice).
2. Serialize the validation state: Convert the validation map to a JSON‑compatible format (using clj->js or pr-str) and store it in a persistent client‑side store such as localStorage, sessionStorage, or IndexedDB.
3. Trigger persistence on change: Attach a watcher (e.g., add-watch on the atom or a Re‑frame interceptor) that runs the serialization step whenever the validation map updates.
4. Restore on application start: During app initialization, read the stored value, parse it back into ClojureScript data (js->clj or read-string), and reset the validation atom or dispatch an event to update the Re‑frame db.
5. Verification: After a reload, inspect the UI to confirm that previously invalid fields still show their error messages and that valid fields are unchanged.
6. Rollback: If the stored data is corrupted or incompatible, catch the parsing error, clear the storage entry, and re‑initialize validation to a clean state.

Discuss trade‑offs (e.g., storage size limits, security considerations for sensitive validation data, and how to handle schema changes when the validation format evolves).