The priority argument was passed to Guard::wrap() (which takes a single callable
and silently ignored it) instead of to add_action(), so the add-on registered at
the default priority 10 rather than 5. Move the 5 to add_action's third argument
so registration runs at the same early priority as Gravity Forms' own bundled
add-on bootstraps.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- F-15: uninstall now removes ALL espinstanda_* options and transients (incl. the
encrypted password and its self-provisioned key).
- F-16: register the "Gravity Forms required" admin notice unconditionally so it is
reachable when GF is inactive (gform_loaded never fires then).
- F-22: self-heal the daily retention cron on admin_init (matches the schema self-heal).
- F-19: re-validate the stored payload via Field_Mapper::validate_payload() before a
resubmit (DB-tamper trust boundary).
- F-20: increment the retry count on resubmit and dispatch the previously-dead
espinstanda_resubmit_success notification event.
- F-23: emit the theme's Form-5 date-range JS only on pages that embed a Gravity Form
and disconnect the MutationObserver (was observing the DOM subtree forever).
- F-24: bump plugin to 1.1.0; add readme.txt changelog documenting the audit fixes and
the required ops actions.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
zbatteandClaude Fable 5