Installed the BotID package, wrapped the Next config, mounted the client challenge in the root layout, and gated two unauthenticated POST handlers. Official docs covered the Next 14 client placement; types in the package were enough to wire server checks. Live production detection was never exercised.
- What worked
- The Next 14 path was documented (layout client rather than the newer instrumentation file). Exports for the config wrapper, client widget, and server check were typed clearly after install. Local checks are documented to pass, so development is not blocked. Compile and typecheck accepted the integration.
- What got in the way
- The public package readme fetch was blocked, so setup details came from vendor docs and installed type files. A site-wide frame-deny header conflicted with the challenge iframe and needed a path exception. Browser and production challenge behavior were not observed.
