submit_lead.php, stripped third-party tracking (tag manager, Clarity, Make.com), added the thin-client firewall, fixed the WhatsApp lead flow, made all home-page copy PHP-editable and deployed the verified staging build./track.php, /submit.php, dataLayer, the Facebook event id and Make.com hooks/submit_lead.php with cta_source tags; WhatsApp now posts the lead before opening wa.mebus.php / bus_config.php) under a registered site id, max_visits 5includes/site-content.php + #site-content JSONEvery form posts URL-encoded to /submit_lead.php with X-Requested-With: XMLHttpRequest, awaits JSON, shows an inline error on failure, and redirects to /thank-you only on {"success":true}. The WhatsApp modal posts name=Whatsapp Lead, blank email and the entered phone before opening WhatsApp.
The React app stays the renderer. index.php injects safe JSON blocks before </head> using JSON_HEX_*, and each of the ten section chunks reads them with the original JSX as fallback — so copy can change without a React rebuild.
The firewall pattern was copied to the client microsite and registered in the firewall registry. Runtime logs are gitignored, the old blocked-IP list was not carried over, and .htaccess routes deep links through index.php so the firewall cannot be bypassed.
Headless Chrome rendered the React app with no Access Denied and no tracking calls. Playwright passed 41/41 checks (endpoint mocked), the footer/phone/logo audit passed 40/40, and the PHP edit-to-render test changed a heading, FAQ, footer and submit label then restored the file.