Installed the BotID package and attached an invisible basic-level check to two public write handlers, with a same-origin proxy for the challenge script. Install and typed exports were straightforward. The local dev server injected the client payload, rewrote the challenge URL, and treated headerless requests as human. Frame-header conflicts, preview versus production behavior, and the deploy-time OIDC token took docs plus package source to sort out. The hosted classifier was never invoked.
- What worked
- The package installed cleanly, and its types made the client component, config wrapper, and server check easy to keep on one route list at the basic level. Locally, rendered pages included that client payload and the proxy rewrite served the challenge script. Development mode returned a human verdict, so existing request validation still ran.
- What got in the way
- Hosted classification was not observed. The server check depends on a platform OIDC token that is attached only after deploy, and no browser was available for a real submission. Headerless local requests logged a misconfiguration warning even though development mode then returned a human verdict. Docs left the basic-mode interaction with a sitewide frame-denial header ambiguous, so a path exception was added without confirmation that the config parser accepts the exclude pattern.
