feat(design-data): sync components from Spectrum Hub

[GarthDB]

Description

Automated Spectrum Hub → design-data component sync, generated by the Hub Component Sync workflow.

For each Hub slug tracked in component-map.js, this run fetches the RSP and SWC pages (where both exist), merges them per-section with mergeComponentSections() (RSP wins on identical/RSP-only content; genuine divergences and SWC-only sections are flagged below rather than silently resolved), and refreshes the target component's documentBlocks via the existing s2-docs-to-document-blocks transform command. It also updates the embedded component-count guard so the Rust regression test stays aligned with the checked-in JSON set.

Related Issue

spectrum-design-data-085.2.5

Motivation and Context

This replaces a manual fetch + merge + stage + transform pass with a deterministic GitHub Action run, mirroring hub-guideline-sync.yml's already-shipped, live-verified pattern for guideline pages. Component pages need their own workflow (not a hub-guideline-sync.yml extension) because of the RSP+SWC dual fetch, different guard math, and different review cadence — see the bead for the full rationale.

How Has This Been Tested?

This PR was opened with a token that allows .github/workflows/ci.yml (Node and Rust jobs, including moon run sdk:test) to run automatically on the pull_request event. If CI did not start, the repository's GH_TOKEN secret may be unset — re-trigger manually (push a commit, or close/reopen the PR) in that case.

Content flagged for human review

SWC-only sections (4) — not merged in, review whether it belongs

link — "Behaviors"

link — "Single vs. multiple expansion"

By default, only one accordion item may be expanded at a time. However, the component can be configured to allow multiple items to remain open simultaneously.

link — "Title wrapping"

Accordion titles wrap automatically if they exceed the available width.

link — "Optional actions"

An optional action button or switch can be placed on the trailing edge of an accordion item to support contextual interactions.

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• I have signed the Adobe Open Source CLA.
• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[changeset-bot]

🦋 Changeset detected

Latest commit: 02dcbe5

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 10 packages

Name	Type
@adobe/spectrum-design-data	Minor
@adobe/spectrum-component-api-schemas	Patch
@adobe/design-system-registry	Patch
@adobe/design-data-agent-mcp	Patch
@adobe/design-data-mcp	Patch
markdown-generator	Patch
@adobe/token-corpus-migrate	Patch
@adobe/token-naming-audit	Patch
component-options-editor	Patch
@adobe/spectrum-design-data-mcp	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

🧩 Component Schema Changes Report

No component schema changes detected.

This comment was automatically generated by the component schema diff tool. 🤖

[github-actions]

🎨 Token Changes Report

Tokens Changed (0)

Original Branch: beta-hub

---

This comment was automatically generated by the token diff tool. 🤖

[GarthDB]

Superseded by #1524, which includes this public-site sync and promotes Hub guidance directly to main without beta release state.