reproduction: harness-claude-code: readBridgeAsset probes ../bridge/, which never exists in

[ai-sdk-factory]

Bug

harness-claude-code: readBridgeAsset probes ../bridge/, which never exists in a published install, so Turbopack fails the build

Reproduction

• With the reported @ai-sdk/harness-claude-code@1.0.97, Next.js 16.3.3, React 19.2.8, and React DOM 19.2.8, importing createClaudeCode in a server route makes the default Turbopack production build fail with Module not found: Can't resolve '../bridge/' <dynamic>.
• packages/harness-claude-code/src/claude-code-bootstrap.ts probes both ./bridge/${name} and ../bridge/${name}, while the package assembled by packages/harness-claude-code/package.json contains assets under dist/bridge and no root bridge directory.
• The equivalent webpack build succeeds, and the Turbopack build succeeds when @ai-sdk/harness-claude-code is configured in serverExternalPackages, confirming both comparisons reported by the issue.
• Added examples/ai-functions/src/reproduction/issue-19982.ts; it packages the target branch, creates the minimal Next.js server-route application, validates the two successful comparison builds, and fails on the primary default-Turbopack behavior.

Relevant Documentation

• https://nextjs.org/docs/app/api-reference/turbopack
• https://nextjs.org/docs/app/api-reference/config/next-config-js/serverExternalPackages

Related Issues

Reproduces #19982