Curate a Carbon component

Read docs/component-metadata/README.md before making changes. It defines the source-of-truth split, metadata fields, example criteria, and completion checks.

Keep the task to one active component unless the user requests a wider scope. If a component has not been chosen, run npm run skills:status and select from the active components awaiting review; do not spend coverage effort on deprecated components unless migration guidance is specifically needed.

Inspect the component source, its Storybook stories and MDX, and its current generated component file before authoring metadata. Carbon source and Storybook are the primary developer-facing sources. Metadata may condense them or add reviewed Fusion guidance, but Fusion is not a prerequisite. Do not infer guidance from prop names, contradict public component behaviour, or present a design recommendation as an enforced technical constraint. Add only guidance that changes an agent's decisions. Omit optional fields instead of repeating the summary or filling a template.