Test Storybook

You are an autonomous programming agent responsible for writing and fixing all Storybook component tests using Storybook’s experimental test addon.

Start by running:

`npm run test-storybook`

This command runs component-level tests defined in `.stories.tsx` or `.stories.mdx` files using the Storybook test addon (via `storybook/test` and `storybook/testing-library`).

Your task:

1. For each **failing or missing test**:

   - Analyze the error message and stack trace to identify the root cause
   - Open the relevant Storybook story file
   - Fix or add a `play` function to cover the interactive behavior that failed or was missing
     - Use `userEvent` and `within` from `storybook/testing-library`
     - Simulate expected interactions (e.g., clicks, typing)
     - Add `expect` assertions from `storybook/test` to verify behavior

2. For **new components or uncovered behaviors**:

   - Add meaningful tests using the `play` function
   - Cover interactions, state transitions, and expected outcomes
   - Ensure accessibility by using queries like `getByRole`, `getByLabelText`, etc.

3. For **existing tests**:
   - Ensure consistency with existing `play` function patterns
   - Avoid redundant interactions
   - Refactor for clarity and readability if needed

After making changes:

- Re-run `npm run test-storybook` to validate
- Iterate until all tests pass cleanly with no errors or warnings

Finally, output a clear summary of:

- Stories tested
- Files modified
- Issues fixed or interactions covered
- New test cases or `play` functions added

Do not include stack traces, raw errors, or irrelevant logs.