From c64676a126488b03d38c951c83a5e78af1c15d9e Mon Sep 17 00:00:00 2001 From: Chris Portscheller Date: Fri, 14 Aug 2026 11:39:25 -0500 Subject: [PATCH] docs(client): point the clearance-fp contract note at cdn/public The app repo's cdn/pro/ directory was removed (its worker was deprecated and deleted); cdn/public/bot-detection-pro.js is the copy that carries computeClearanceFP() now. --- packages/client/src/clearance.ts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/client/src/clearance.ts b/packages/client/src/clearance.ts index c0dfb56..b5b055e 100644 --- a/packages/client/src/clearance.ts +++ b/packages/client/src/clearance.ts @@ -27,7 +27,7 @@ export const CLEARANCE_COOKIE = 'wd_clearance'; * * 1. this function * 2. app repo `edge/clearance-worker/src/device-fp.ts` (the interstitial) - * 3. app repo `cdn/pro/bot-detection-pro.js` computeClearanceFP() + * 3. app repo `cdn/public/bot-detection-pro.js` computeClearanceFP() * * If two of them computed different fps for the same browser, a decoy-triggered * deny would catch one and not the other — the lockout would leak, silently.