sync: re-sync the astryx contract fixture after dspack #22#44
Merged
Conversation
dspack #22 consumed the studio's example-expansion governance into the canonical contract (3 intents, 3 components, 9 rules, 3 examples, table required flags), so this repo's byte-copy check went correctly red: DRIFT fixtures/astryx.v0_1_2.dspack.json differs from .../dspack/main/examples/astryx.dspack.json Re-synced with check-sync --write. No derived goldens needed regeneration: the context golden is shadcn-only and the violating-astryx expectations hold unchanged (the new content is additive; universal-rule findings are untouched). Full suite green at 108 tests (up from 105 — the worked-examples-as-oracles suite picked up ex.support-ticket-triage, ex.signup-basic, and ex.plan-comparison, and all three validate against their own intents' generation schemas and lint clean: the no-unexpected-semantic-changes confirmation). Test-only fixture; no publish required. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Re-syncs the Astryx contract fixture (astryx.v0_1_2.dspack.json) to match the updated canonical Astryx contract, keeping this repo’s sync/validation pipeline aligned with upstream.
Changes:
- Marked
tablepropsdataandcolumnsas contract-required (so generation schemas can require them). - Added new components (
list,selectable-card,metadata-list) plus supporting intents and lint rules. - Added three new worked examples aligned to the new intents/rules.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| "props": { | ||
| "type": "body" | ||
| }, | ||
| "text": "Name and email is all it takes. You can add the rest later." |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Third and final PR of dspack-studio's P0 (contract synchronization): dspack #22 moved the canonical Astryx contract forward, so this repo's check-sync went correctly red on
fixtures/astryx.v0_1_2.dspack.json. Re-synced with--write.No unexpected semantic changes — the end-to-end confirmation the sync pipeline is clean:
ex.support-ticket-triage,ex.signup-basic,ex.plan-comparison) and all validate against their own intents' generation schemas and lint clean.Test-only fixture; no npm publish required.
🤖 Generated with Claude Code