release: record verified 1.9.0 production migrations - #201
Merged
Merged
Conversation
4 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Record migrations 0011–0015 after the owner applied them to production and an independent read-only transaction verified six tables, backend-only RLS, columns, indexes, constraints and publication backfill. This clears the migration-ledger prerequisite for release #200.
Validation: all 15 SQL files match the ledger; whitespace checks passed. Migration SQL is unchanged. Generation remains paused per the owner; backend/worker deployment before OTA and device acceptance remain pending. The local backup archive is readable; full restore was not tested and cloud restoration was explicitly deferred. No application tests rerun for ledger/documentation changes.