Installed the BotID package, wrapped the Next config, mounted the client component for two POST routes, and gated those handlers with the server check. Docs and packaged types were enough to wire it, but Next.js 14 versus newer setup paths, client/server import boundaries, and a possible frame-header clash with existing platform headers took extra care. Live bot classification was never exercised.
- What worked
- Package install was straightforward. Client, config wrapper, and server check APIs matched the getting-started guide closely enough to protect only the intended routes without changing shopper-facing forms. Typecheck passed after the wiring.
- What got in the way
- Docs mixed a newer client-instrumentation path with a Next.js 14 layout/head component, so the correct entry point was not obvious. It was unclear whether existing catch-all deny-framing headers would break the challenge path. Local checks are documented to always pass, so production detection was not observed.
