[goastler]

What changed

The Cloudflare Worker setup guide no longer offers an "auto-inject" mode or the SITE_KEY setting. It tells customers to add the Protect script snippet to their own pages, and explains why the Worker doesn't do it for them.

Also fixes a troubleshooting link that pointed at a heading which no longer existed.

Why

The Worker stops editing pages in https://github.com/prosopo/Protect/pull/1345

Tests

Docs only. Checked the headings and links on the two edited pages by hand.

[netlify]

✅ Deploy Preview for peaceful-pothos-9e62ce ready!

Name	Link
🔨 Latest commit	d6af7b5
🔍 Latest deploy log	https://app.netlify.com/projects/peaceful-pothos-9e62ce/deploys/6ad1dbd7ca48c23df55ac4ee
😎 Deploy Preview	https://deploy-preview-115--peaceful-pothos-9e62ce.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[forgetso]

This is superseded by #116 and #118, which are both merged.

#116 removed the auto-inject mode and SITE_KEY from the guide, and #118 did the troubleshooting link fix this PR also carries (the anchor now points at #2a-add-the-snippet). I checked every cloudflare-worker#… anchor used anywhere in the site after that change and they all resolve.

The diff here is against the pre-#116 page, so it would conflict wholesale rather than rebase cleanly.

One thing this PR does better and I'd happily take: the framing. "Why the worker doesn't add the script for you" as a heading, plus the note that Lambda@Edge works the same way, is more useful to a customer than the single sentence that's on main now. Want me to port that bit, or would you rather take it yourself? Either way this branch can close.

[forgetso]

Everything in this PR is now on main, so closing.

• The auto-inject / SITE_KEY removal landed in Cloudflare Worker: drop SITE_KEY injection and ORIGIN_URL from the install guide #116.
• The troubleshooting anchor fix landed in Cloudflare Worker: drop the migration notes, fix the step numbering #118.
• Your framing — "Why the worker doesn't add the script for you" as its own section, plus the note that Lambda@Edge works the same way — and the clearer "Add the Protect script to your pages" heading landed in Cloudflare Worker: explain why you add the script, in its own section #119, credited to you. It was better than what I'd written: I'd left the explanation as a trailing sentence on "What you get", which is not where anyone would look for it.

One thing I deliberately didn't take: this PR describes the install as one <script> tag. There are two — the window.prosopo_config block and the bundle — and the paragraph under the snippet explains why both are needed and what breaks without the first, so main keeps two.

Also worth knowing: the Workers Cache warning in #114 is in too. I rebased it onto main (it conflicted with the step renumbering) and it merged.