Repository navigation
fix(deployment): bind manifest to repository head - #57
Merged
Merged
Conversation
This was referenced Nov 5, 2026
This branch was previously deployed
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
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.
Outcome\n\n- Bind the production manifest to the migration heads shipped by the current artifact.\n- Retire obsolete extension-cutover lineage from the active deployment guard.\n- Preserve exact application-table and row-count verification while exposing rejected schema details.\n\n## Verification\n\n- pdm run pytest tests/deployment (73 passed)\n- pre-commit on changed files\n- read-only production manifest and no-op transition against the current 22-table schema