Change things freely, you can go back
Every successful change leaves a restore point. Going back costs no credits, and the state you are leaving is saved first.
What it is
The reason people stop editing is fear of breaking something. A reliable way back removes it.
Restore points come in two kinds: source only, and source with data. The list says which one you are looking at.
Restoring saves your current state as a new point first, so an undo can itself be undone.
How to use it
Step 1. Pick a point
Model runs, hand edits, and preview edits all leave points. Bookmark the ones you return to.
Step 2. Your current state is saved
The point you are leaving is written before anything is replaced, so a mis-click has somewhere to land.
Step 3. It restores and rebuilds
Source goes back, data goes back where the point carried it, and the preview is rebuilt.
What we measured
Each point states whether it carried data. When the data dump could not be taken, the point is not labelled as if it had one.
What it does not do
Source-only points leave data alone
Restoring one brings back the code and the preview. Your data stays as it is now, and the list says so before you choose.
A restore runs in stages
Source, schema, data, then build. If a stage fails, the earlier ones are walked back and the screen tells you how far it got.
What already left cannot be recalled
A visitor who already saw the published site, a message already sent, a payment already taken — a restore point does not reach those.