Repository navigation
Add admitted component releases and durable Fleet update recovery - #20
Merged
Merged
Conversation
added 2 commits
October 27, 2026 05:08
Preserve both session authorities and pairing-state rollback protection.
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.
Fleet Manager now distinguishes observed, selected and available versions and previews the exact admitted component scope before updating. Stable/dev choices come from real admitted compatible releases. Selected legacy writes fail closed through the owner boundary; authenticated fixed-socket operations retain durable job identity, replay, progress and recovery, including the installed host adoption path for Fleet Manager itself.
Release authority uses fresh administrator checks, purpose-separated CSRF and an actor identity that survives signed-cookie refresh and proxy replacement with the retained secret. Source adoption preserves current auth and configuration, records verified restoration identity, and holds uncertain candidate/recovery phases.
Validation:
build / buildandcpu-build / buildfrom GitHub Actions app 15368; neither is bypassed.Required CI, native Linux/package validation, production admission and owner bootstrap, real self-update, browser/session journeys and final owner acceptance remain held. Production release writes remain disabled until the real integration gates are satisfied. This PR changes no version and does not authorize merge or deployment.