Sam asked to check the Notion Knowledge Base for how the website form was built/configured and to verify whether leads 61-66 were missed. Notion confirmed the intended architecture: Gravity Forms was replaced by the custom WordPress MU plugin sal-custom-contact-intake-v2.php; it should persist locally, create Litify intakes, send Outlook Graph email, and optionally notify Teams.
/?rest_route=/sal/v1/contact-intake, and original recipient expansion./var/www/html/public_html/wp-content/mu-plugins/sal-custom-contact-intake-v2.php, active config /var/www/html/contact-intake-config-v2.php, and legacy_gf payload mode.The reachable Cloudways production app did not have /var/www/html/contact-intake-config-v2.php. Live sal_contact_intake_get_config() returned empty Litify URL, empty sender, and no recipients. The plugin was still looking only at the missing /var/www/html config path.
The stale recipient list also existed in historical WordPress data, including old Gravity Forms metadata and prior wp_sal_contact_attempts payloads. The live emails for leads 61-66 still used that stale list, but the reachable WordPress wp_sal_contact_leads tables stopped before those IDs, so there is likely an alternate or stale relay path still capable of generating the same email format.
/home/master/applications/fctbkwwahp/public_html/wp-content/mu-plugins/sal-private/contact-intake-config-v2.php.sal-custom-contact-intake-v2.php to check the new private config path before the old /var/www/html paths.legacy_gf payload mode and the Litify record base URL.No fake lead was submitted. QA used non-submission checks:
sal_contact_intake_get_config() now returns a populated Litify webhook, Outlook Graph provider, sender sam@kylawoffice.com, and 12 recipients.