[Customer account UI extensions 2026-01]: Improved descriptions for "Feedback and status indicators" components

[mcvinci]

This PR:

• Improves JSDoc descriptions for checkout Feedback and Status Indicator components (Announcement, Badge, Banner, Progress, Spinner) to align with admin UI extensions documentation style — clearer opening sentences, bulleted value descriptions for enum props, and inline "Learn more about" links replacing @see tags.
• Adds missing descriptions for ToggleState, ToggleArgumentsEvent, ReducedIconTypes, and the dismiss() method on Announcement, ensuring all public types and methods are documented.
• Updated components-shared.d.ts to keep upstream descriptions consistent with the component-level overrides, removing internal @implementation annotations and vague phrasing like "Adjusts the size" or "Modify the color."
• Relates to https://github.com/shop/world/pull/577654
• Partially closes https://github.com/shop/issues-learn/issues/1494

[github-actions]

🚨🚨🚨 Docs migration in progress 🚨🚨🚨

We are actively migrating UI extension reference docs to MDX in the areas/platforms/shopify-dev zone of the monorepo. This impacts docs for the following surfaces:

• Admin UI extensions
• App Home
• Checkout UI extensions
• Customer account UI extensions
• POS UI extensions

During this migration, please be aware of the following:

.doc.ts files are being deprecated. Changes to .doc.ts files in this repo will not be reflected in the new MDX-based docs. If you need to update docs for a reference that has already been migrated, make your changes directly in the areas/platforms/shopify-dev zone of the monorepo instead.

Doc comments in .ts source files (the comment blocks above types and functions) are also affected. Generating docs from these comments currently requires a newer version of the @shopify/generate-docs library that isn't yet available. Updates to doc comments may not produce the expected output until the migration is complete.

Examples that previously lived in this repo are being moved to the areas/platforms/shopify-dev zone of the monorepo and should be authored there going forward.

What should I do?

• If your PR includes changes to .doc.ts files, doc comments, or examples, please reach out to us in #devtools-proj-templated-refs so we can help ensure your updates are captured correctly.
• If your PR is limited to source code changes (non-docs), you can ignore this notice.

Thanks for your patience while we complete the migration! 🙏

[github-actions]

We detected some changes in packages/*/package.json or packages/*/src, and there are no updates in the .changeset directory. If the changes are user-facing and should cause a version bump, run yarn changeset to track your changes and include them in the next release CHANGELOG. If you are making simple updates to repo configuration, examples, or documentation, you do not need to add a changeset.

[sordaz00]

LGTM! Same comment.