Add API for detecting server→client component boundaries in Turbopack
This implements boundary detection for Next.js App Router by leveraging the existing client_references computation. The feature detects server→client component boundaries with zero performance overhead by reusing data already computed for the Client Reference Manifest.
Key changes:
- Add client_references() method to Endpoint trait with default empty implementation
- Implement client_references() on AppEndpoint using ClientReferencesGraphs API
- Add boundary extraction utilities to convert ClientReferenceGraphResult to boundary data
- Expose extractBoundaries() function through NAPI for TypeScript consumption
- Add boundary logging in hot-reloader-turbopack for development mode
This lays the foundation for future security features like detecting sensitive data crossing boundaries and suggesting React's taint API.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>