/**
 * Example script demonstrating bidirectional transforms through `definePlugin()`
 * following three common plugin author scenarios
 *
 * Scenarios shown:
 *   1. Custom fields + declarative `mappings`   → definePlugin compiles them
 *   2. Custom fields + hand-written functions    → `ToCommon` / `FromCommon`
 *   3. Transforms with no custom fields          → base CommonGrants schema
 *   X. `mappings` + functions on one entry       → rejected (mappings XOR functions)
 *
 * Run with: `pnpm example:transforms`
 *
 * @remarks
 * The mappings scenario validates `toCommon` output against the extended common
 * schema, so date strings are parsed into `Date` objects on the common side.
 * The round-trip checks below therefore assert on fields that survive verbatim
 * (ids, the three-state `source` null), not on the parsed date fields.
 */
export {};
//# sourceMappingURL=transforms.d.ts.map