Core owns its shared database schema and upgrade path; Pro owns supplemental migrations for its features. Themes do not create or alter booking tables. A code rollback is not a database downgrade or an undo for a provider transaction or privacy erasure.
Identify the current schema source
Current reviewed Core source declares schema 3.12.0. Historical iCal/RC manifests can still describe earlier schema 3.9.0 or 3.8.0 baselines. Preserve those records as history rather than changing current product metadata to satisfy an old test assertion.
Track the actual installed schema/readiness options and owning migration code. Version labels alone do not prove that every supplemental table exists or that a previous upgrade completed. Required schema failures should remain visible and fail closed.
Protect atomic writes
Booking creation rechecks stock and financial quote under the appropriate locks before committing saved history. Its supported submission receipt handles replay identity; it is not universal deduplication across unrelated forms/imports.
External-source reconciliation commits a complete validated snapshot and related health/inventory state consistently. Provider failures, source revisions or inventory conflicts must not leave a partially applied calendar or clear known occupancy.
Never edit lifecycle/payment-status columns to force a business result, delete financial rows to repair a display, or rewrite saved taxes/policies from current settings. Pro and Core ownership checks remain in force when features are unavailable.
Back up and rehearse
Before a migration, capture verified database/files and the exact compatible packages. Test a restore on an isolated copy with outbound integrations disabled. Reconcile later bookings, provider events, queues, external blocks and privacy outcomes before any operational restore.
Privacy redaction can leave retained/linkable financial/audit records deliberately. Installing older code does not reconstruct erased fields or revoke bearer links. Do not restore an old dump indiscriminately to reverse a presentation error.
See backup/incident response, external block contract and known limitations.
