Add nomadro.live English WordPress stack and audience router

Co-authored-by: Cursor <cursoragent@cursor.com>

deploy/nomadro-live/wordpress/content/posts/04-webhook-automation.html

@@ -0,0 +1,11 @@
+<p>Webhooks turn live events into actions in other systems: a Discord ping, a spreadsheet row, a light on a desk, a CRM note. They are useful when the action is boring and time-sensitive.</p>
+<h2>Start with one rule</h2>
+<p>Pick a single event type—high-value gifts is the usual first choice—and send it to one destination you already check. Ten half-working rules are worse than one reliable rule.</p>
+<h2>Idempotency</h2>
+<p>Live feeds retry. Your receiver must tolerate duplicate event ids. If the upstream has no id, hash timestamp plus sender plus gift name and drop duplicates inside a short window.</p>
+<h2>Secrets and exposure</h2>
+<p>Webhook URLs are credentials. Do not paste them into public docs or client-side code. Rotate them when an operator leaves. Prefer signed payloads if the tool supports them.</p>
+<h2>Backpressure</h2>
+<p>A viral minute can fire hundreds of events. Queue on the receiver. Dropping events silently is better than crashing the live monitor process because a chat app rate-limited you.</p>
+<h2>Test before showtime</h2>
+<p>Send a synthetic event, confirm the destination, then disable the synthetic source. Debugging webhooks during a paid collab is a self-inflicted outage.</p>