storybook-controlled-components

What problem does it solve? Storybook stories for controlled components appear frozen: clicking, typing, selecting, or deleting fires onChange but nothing on screen updates, because the story passes a static value prop and only logs onChange to an action logger. ## Core Features & Use Cases - Stateful CSF3 render pattern: Uses a named render function with React.useState seeded from args so the story owns the selection state while the Controls panel still supplies the initial value. - Control panel hygiene: Disables the panel control for the value prop so it cannot fight local state, while keeping options, label, and other props editable. - Variant reuse: Sibling story variants reuse the first story's render function instead of duplicating the stateful renderer. - Use Case: A multi-select story in a component library is screenshotted by a Playwright visual suite; a frozen story pins an unreachable baseline, so this pattern keeps visual regression baselines honest. ## Quick Start Rewrite the frozen Storybook story for my controlled component so its state lives in a named render function seeded from args.