FACTUAL ACTIVITY RECORD · An activity record based on work that took place
Consolidating production database updates into normal migrations
Removing the destructive reset path and adding only migrations absent from standard history
Purpose
Immediately before running the production initialization path, verification showed that a linked reset would also delete authentication users, identities, and sessions. The schema update path needed to preserve existing authentication state and project settings.
Implementation
The destructive initialization workflow and its dedicated verification script were removed, leaving standard migration workflow as the common path for initial and routine updates. The sequence now uses standard migration-history inspection, a dry run, application of unapplied migrations, and another inspection.
standard migration workflow and repository-policy checks reject production linked resets and reintroduction of the retired path. The project guide, Control Center guidance, and migration documentation were aligned with normal migrations that preserve authentication state.
The implementation removes the dedicated production DB-initializer check from the verification chain and keeps the standard migration verifier as the single path. Later checks are shortened.
Rendering diagram…
What was confirmed
Verification results
The applied initial migration, catalog, and ACL were compared read-only and confirmed to match the source.
Repository-wide verification and the diff check passed.
Neither a production reset nor a production migration had run by the cutoff, so the existing authentication state was not changed.
Basis for completion
This scope ended when the destructive path was removed from source and audits, leaving a verified configuration that permits only standard migrations.