Feature summary:

• A JS function, exposed through a global or hook, that pauses the saving of the data by EditRecovery.
  • Alternatively: a mw.config boolean the fieldChangeHandler checks before it executes itself.
• A JS function, exposed through a global or hook, that instructs EditRecovery to reconstruct the originalData the form is compared against when it's modified.

Use case(s):
I have a script that saves the page through the edit API while action=edit is open, so that I can continue editing without navigating back and forth. Since the introduction of EditRecovery, every time I start editing a page last saved with this method, "Changes recovered" pops up, which is completely useless because the "recovered" data has already been saved.

Benefits:
Better access to EditRecovery allows gadget/script developers and users to fine-tune its behavior.