Fix upstream sync reliability controls - #229
Merged
Merged
Conversation
Disclosure-Reviewed: reviewed — public-safe only, private facet kept out of this commit
bigboateng
marked this pull request as ready for review
July 28, 2026 09:58
Disclosure-Reviewed: reviewed — public-safe only, private facet kept out of this commit
Disclosure-Reviewed: reviewed — public-safe only, private facet kept out of this commit
Pitot coding-agent E2EIntelligence Flow is the verification source; Pitot's public README carries the latest
Runtime capabilities
Source commit: |
Disclosure-Reviewed: reviewed — public-safe only, private facet kept out of this commit
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.
What changed
interlock upgradesupport using a detached replacement helper, checksum verification, backup/rollback boundary, and completion reportingmainhas required status-check protectionRoot cause
Interlock sync PRs #25–#27 failed because the new upgrade E2E executed an extensionless
interlockpath on Windows while the product explicitly rejected Windows self-upgrade. Separate fleet inspection found Value Map workflow permission drift, Pitot legacy-manifest ownership drift, and no activemainbranch protection in any of the four downstream repositories.Control law
The publisher App proposes and authenticates change; platform E2E tests prove shipped behavior; branch protection decides merge eligibility; ownership migration is automatic only when equivalence is cryptographically proven.
Validation
labs/21-interlock/scripts/validate.shgo test ./...uv run --project labkit --extra dev pytest -q labkit/tests— 77 passedpython -m labkit doctor --repo-root .— all four projections passgit diff --checkRollout prerequisite
The downstream repositories currently have no active required-check protection on
main. The generated sync workflow now fails closed until protections are enabled; after this PR lands, install the generated workflows and configure required checks before re-running fleet syncs.