The distribution gap, and three enforcement layers that close it nuka-ui's main test suite is green. Vitest passes. ESLint passes. TypeScript passes. The Storybook a11y panel shows zero violations on every story. And then someone installs the package in a Next.js App Router project, drops a <Toaster> into a server component, and the build fails with an error that points at React's internals. I have lost more hours to this kind of bug than I want to admit. The shape repeats. The repo is happy. The consumer's project is not. The thing that broke is invisible from inside the repo, because it lives in the part of the codebase that nobody on the project ever runs: the dist directory. What follows is what happened with two of those bugs and what I added to make them stay fixed. A "use client" directive that never made it into dist, and a Tailwind class that the consumer's bundler purged before it ever rendered. All the code referenced below lives in github.com/ku5ic/nuka-ui .…