Skip to content

sync: consume shadcn contract v2.3.0 (record-collection)#23

Merged
ryandmonk merged 1 commit into
mainfrom
sync/shadcn-v2.3.0
Jul 22, 2026
Merged

sync: consume shadcn contract v2.3.0 (record-collection)#23
ryandmonk merged 1 commit into
mainfrom
sync/shadcn-v2.3.0

Conversation

@ryandmonk

Copy link
Copy Markdown
Contributor

Second link of the P1.1 four-repo sequence, per the P0 merge protocol: dspack #23 landed the canonical change; this PR carries the byte-identical consumption (cmp-verified against dspack main).

Governance-only change (no new components): the shadcn catalogs re-emit through the ordinary ajv gates clean; check:sync green; no studio runtime change (generation/linting stays on the astryx catalog, design-swap unchanged).

Downstream still queued: dspack-gen fixture re-sync + goldens + recordings → ds-mcp example re-sync.

🤖 Generated with Claude Code

Byte-copy of dspack #23 per the P0 merge protocol: canonical change
landed upstream first; this PR carries the identical consumption. The
shadcn catalogs re-emit through the ordinary ajv gates unchanged in
shape (no new components — governance only). No runtime change: the
studio still generates and lints under the astryx catalog; the
design-swap still renders the astryx catalog with shadcn visuals.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings July 22, 2026 15:09
@ryandmonk
ryandmonk merged commit cda4f8e into main Jul 22, 2026

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the consumed shadcn/ui dspack contract to v2.3.0, adding the new record-collection intent (plus associated rules and an example surface) to guide/validate semantic data-table usage in the catalog.

Changes:

  • Bump shadcn contract version from 2.2.0 → 2.3.0.
  • Add record-collection intent linked to the existing data-table-with-row-actions pattern.
  • Introduce record-collection rules (requires table, enforces header/body structure and a caption) and add an example surface (ex.support-ticket-queue).

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

"appliesTo": { "intents": ["record-collection"] },
"component": "table",
"requiredSubComponents": [{ "id": "table-caption", "min": 1 }],
"rationale": "The data-table-with-row-actions pattern requires an accessible name via TableCaption or an aria-label. The pattern permits either; the contract can only govern the declarative form, so the caption is the enforceable floor — an aria-label alternative is legitimate but inexpressible in current rule types and remains guidance.",
{ "component": "table-cell", "text": "Cannot export billing statement" },
{
"component": "table-cell",
"children": [{ "component": "badge", "props": { "variant": "destructive" }, "text": "Urgent" }]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants