/**
 * @fileoverview Tests for migration v18 — purge proxy-hash skill_versions history
 * @see SMI-6343 Wave 2 — repair the content-hash comparison
 *
 * Coverage:
 *  - MIGRATIONS registers v18 with the documented SQL.
 *  - SCHEMA_VERSION is at least 18.
 *  - MIGRATION_V18_SQL empties skill_versions of any pre-existing (proxy-hash
 *    era) rows.
 *  - A v17 fixture DB upgrades to v18 cleanly via runMigrations, purging a
 *    legacy row planted before the upgrade.
 *  - A post-migration registry sync (SyncEngine) repopulates skill_versions
 *    with a real SKILL.md content hash — never a metadata proxy.
 */
export {};
//# sourceMappingURL=migration-v18.test.d.ts.map