Repository navigation
feat(owner): bind read-only VM inspection to protected registration - #931
Merged
Merged
Conversation
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 installed supervisor previously had no way to compare a VM with a protected registration. It now checks an optional fixed
registered-vm.jsonthrough the exact retained installed owner and caller admission, holds the record, and refuses stale policy/selection tuples, changed records and foreign or replaced native VM identities.The existing
inspect-ownedoperation stays read-only. The native manager remains private; preparation, lifecycle dispatch and agent release remain unavailable. Missing registration preserves process-only inspection with the existing false qualification flags. The current installer does not provision this optional record; its transactional provisioning and real registered-VM qualification are subsequent work.Validation: 75 Windows tests across four suites and five qualification payload builds passed on source
5bb6afff. Subsequent deltas add the two classes to the production compiler list and tighten the native test with a valid ordinary-writable record; all 25 registration tests passed again. All 40 compiled qualification inputs remain unchanged. The actual production build failed before the compiler-list correction and then built all seven helpers. Source review uses two passes by the same reviewer. Five required CI contexts run on final headaa92f033; the fixed Windows11 compatibility lab remains tied to5bb6afff. Synthetic authority/provider tests do not establish positive SCM/Hyper-V registration or E1/E2/E3/A1 acceptance.