689 B
689 B
Use durable runs for authoritative schema synchronization
All table, column, relationship, and full-schema synchronizations run as durable background Catalog Sync Runs rather than separate synchronous and asynchronous implementations. Each scope is authoritative within its boundary, while Synchronize All observes one complete schema snapshot; destructive diffs require confirmation and source revalidation before an atomic, fail-closed catalog transaction. A persistent per-database lock, progress events, interruption handling, and binding-version freshness make long operations observable and prevent two processes or stale configuration from producing a partially trusted catalog.