docs: qualify repeated real interactive transitions - #224
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
1 participant
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.
Records the native LTSC qualification of three real logoff/logon cycles, settled-session admission revoke/re-enable, and SCM stop while an enabled interactive notify workload waits for readiness. Four Windows logons, seven workload invocations and 122 ordered ownership snapshots passed; the original guest state was restored.
The immutable runtime source is fdf9d2f, with successful CI 34817416447 and equal-tree merge #222. This documentation change adds no runtime code. Multiple-session/user, native-launch race and remaining profile/security gates stay open.
Validation: independently checked retained artifact hashes, native identities, transitions, stop timing, snapshot counts and restoration evidence; reviewed links, consistency, privacy and whitespace. Three incomplete fixture attempts are retained privately and identified in the ledger.