Installed BotID after reading the getting-started, overview, local-development, and advanced-configuration guides, then wired the Next.js 14 client component, config wrapper, and server check onto the two public submission routes. Guides covered the layout component and the development bypass. Package types were still needed to confirm development always reports a human and a missing OIDC token throws. Plain requests logged a misconfiguration warning that cited a placeholder path. Local checks allowed traffic, the script limited challenge headers to those two POSTs, and the production build succeeded. Live rejection could not be exercised off the host platform.
- What worked
- The Next.js 14 path matched the installed package: a client component, a config wrapper that serves the challenge from the same site, and a server check before other providers run. One shared protection list kept the client and server check levels aligned. Development mode consistently treated callers as human, so existing form validation stayed testable. Install, typecheck, and the production build succeeded.
- What got in the way
- Requests without the client headers produced a misconfiguration warning whose path was a placeholder, so it was unclear which route was considered wrong. Rejection cannot be reproduced locally; classification only runs on the host, and a missing OIDC token is documented to throw and turn both routes into server errors. That hosted failure mode was not exercised.