Repository navigation
fix: freeze verified host sources before schema maintenance [skip deploy] - #238
Merged
Merged
Conversation
…sue215-durable-public-activity
lyyzka
marked this pull request as ready for review
October 20, 2026 14:55
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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.
The previous maintenance repeatedly prepared Git after writers stopped; its pinned main checkout also reproducibly conflicted during pull --rebase. This operator-only change requires exact public Compose files to be prepared and verified online using Komodo's native files_on_host mode. The qualified application image remains d1075e3.
Format2 plans bind three raw Compose hashes to the manifest commit. Every one-off, stop, migration and deployment rechecks source/configuration, host identity, errors and actual hashes. Both app nodes' metadata must match before drain and after backup. Existing writer barriers, restored-backup verification, schema boundary and unknown-outcome handling remain mandatory. Cached qualified images are required before stopping services; no explicit preflight PullStack is submitted.
Failure models and failing tests precede implementation.55/55 contracts pass; exact head16313a843aa824050e7cfb88f66db80193a88492 CI39436323154 passed. Independent review reproduced3/3 fresh main rebase conflicts and8/8 clean release-branch repetitions. Actual online staging verified9 terminal operations,15 hashes, unchanged original four containers and48 readiness200 samples. Subsequent target deployment passed18 acceptance checks and independent reconciliation.
Production evidence preserves the earlier failure/recovery, fresh backup, successful migration, one mirror522 recovery and two corrected verifier assumptions. Host-file mode removes Git preparation, but the current Compose pull policy still depends on the approved accelerator. Host cache proof is not atomic filesystem attestation. Empty selected Git/registry accounts are required; no credential/security changes are included.
The legacy ordinary rollout intentionally remains blocked while this source mode is active. A separate strictly same-schema host-release path is being qualified for PR237; blindly restoring the broken checkout is not part of cleanup. Related #216, #219, PR236.