Every form-manager hook in firing order: signature, when it fires, expected return shape, real example. Plus the $local_app_form_array global and the option-key conventions that glue the system together.

The primary notification entry point. Action signature: do_action(‘mam_notification_send_message’, $message). Routed by MAM_Notification_Dispatcher to email/SMS/push channels per the type registry. Frozen contract — legacy filter registration retained per SC #175.

Push-channel hook fired by the dispatcher’s MAM_Pn_Sender. The legacy mam_push_notification_manager bridges to MAM_PushDispatcher. Sibling plugins normally don’t fire this directly — use mam_notification_send_message and let the dispatcher route.

The contract between forms-manager and notifications-manager. Fired after a form submission completes; subscribers fire mam_notification_send_message to dispatch confirmation emails / pushes / SMS. Frozen contract — go through this hook,…

Action fired after a successful app login. Use for analytics, last-seen updates, post-login data warming. Distinct from WP’s wp_login — fires only for app logins through mam_login_manager.