Accept alpha.8 isolated execution - #14
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.
What changed
Why
The merged isolated-execution implementation had passed automated coverage but still needed signed physical-device evidence. The owner-device fixture run now proves strict failure containment, child-state isolation, and persistent-shell recovery without reconnecting.
The same run exposed two separate presentation problems. The software keyboard can strand useful transcript content above the viewport, and the saved-history formatter omits the isolated label even though Room retains the mode.
Impact
Alpha.8 becomes the accepted tester build. No application code changes in this PR. The two UX findings remain explicitly deferred with expected behavior recorded for later fixes.
Validation