Shadcn Parity

Core Contract

When the user asks for shadcn parity, treat ../shadcn as the source of truth for registry behavior and patterns.

Do not give them "inspired by shadcn". Do not invent a Plate-specific model when upstream shadcn already has one.

The rule is simple:

• upstream schema first
• upstream resolver behavior first
• upstream file/layout patterns first
• upstream namespace semantics first
• Plate divergence only when the repo has a real constraint