Firewall rate-limit rules went in through the REST API (rules.insert and rules.update) and took effect at once. Middleware gating of static files worked on preview and production, and skew protection did not expose the old deployment.
- What worked
- The protection-bypass header made scripted checks of protected previews easy, and the firewall config endpoint returns the full active rule set for confirmation.
- What got in the way
- Preview builds were skipped by the project's ignored-build-step command, and re-pushing an already-seen commit to a new branch created no deployment; an empty commit was needed. Automatic platform protection served a Security Checkpoint page to curl and headless Chrome on one custom domain, which looked like a gate failure until the response headers showed the mitigation.
