/**
 * Legacy-JSON → composition-prop remapping.
 *
 * The composition layer was refactored to use shadcn-style normalised
 * prop names, but plenty of JSON in the wild still uses the old v2
 * names (`triggerButtonLabel` instead of `triggerLabel`, GxP variant
 * aliases like `"primary"` instead of `"default"`, etc).
 *
 * This module is consulted by `ElementRenderer` after stripping
 * schema-only keys and before spreading the result onto the resolved
 * composition. It's a thin compatibility layer — every entry here is
 * a known legacy form. Renderers themselves stay schema-agnostic.
 *
 * Adding a new alias:
 *   - For a prop-name rename, add to `PROP_RENAMES[<category>]`.
 *   - For a value-only alias (e.g. variant strings), add to
 *     `VALUE_ALIASES[<category>].<prop>`.
 */
/**
 * Per-category prop-name renames. The string on the left is the legacy
 * JSON key; the string on the right is the new composition prop name.
 *
 * Matched against the element's category prefix (`element.type` split
 * at the dot). `*` is a wildcard that applies to every element.
 */
export declare const PROP_RENAMES: Record<string, Record<string, string>>;
/**
 * Per-(category, prop) value aliases. Used when a prop's accepted value
 * union changed and we want legacy JSON to still resolve. Lookups are
 * case-sensitive; unknown values pass through untouched.
 */
export declare const VALUE_ALIASES: Record<string, Record<string, Record<string, string>>>;
/**
 * Apply prop renames + value aliases for an element. Returns a NEW
 * object — never mutates input. Pass the result through `v-bind`.
 */
export declare function applyLegacyRemaps(type: string, props: Record<string, unknown>): Record<string, unknown>;
export declare const __testing: {
    PROP_RENAMES: Record<string, Record<string, string>>;
    VALUE_ALIASES: Record<string, Record<string, Record<string, string>>>;
};
//# sourceMappingURL=legacyPropRemap.d.ts.map