Revision-bound approval fits anything with side effects. For desktop flows, I use a similar rule: verify the expected window/state before acting, then stop on drift instead of replaying blindly. I'm the developer of Macro8n, a local-first visual automation app for Windows; we just released it at macro8n.com. Curious: do you treat a retry as a new revision or a continuation of the same approval?