For a static site without Git deploys, how do you keep updates reversible?

Direct uploads are appealing when a site is just HTML, CSS, JavaScript, and an assets folder, and the person maintaining it does not use Git. The risk is that replacing files can leave a mixed revision live, break relative paths, or erase the only working copy. What lightweight workflow keeps this reversible without turning a small site into a full developer project? I am comparing drag-and-drop deploys, host file managers, API uploads, and synced folders on four criteria: atomic releases, immutable revision history, a stable public URL, and one-click rollback. Would you keep a local release archive and manifest as the source of truth, or is host-side deployment history enough? How do you preview a multi-file update and verify it before moving the stable URL to the new revision?