Redesigning a design component library to match actual usage

Kitchen library was originally built as UMD per-component packages with a CommonJS kitchen-core initially built with UMD per-component packages and CommonJS core.

Bundle inclusion included all Kitchen component code in consumer bundles regardless of usage due to re-export and mixed build formats.

Build references used build-output-based references between components in development components referenced other components by build outputs rather than source paths.

Storybook did not support propTypes automatic inference because components were not directly referenced did not directly reference component source files under the build-output reference scheme.

Design decision switched distribution format to ESM and added explicit exports fields change aimed to let bundlers statically trace imports without extra configuration.