3fc224b584310fa0bea7edaf184090d45e74109e
The Masonry demo on android-view builds, renders through Vulkan, exposes its AccessKit tree to ui-trace, and takes real keystrokes from the phone's own keyboard. What it does not get is autocorrect and suggestions, and the control is what makes that a finding: the same three key taps in the Settings search field on the same device produce Gboard's suggestion strip, and in Masonry's editor they produce nothing. That is the constraint the framework decision turns on, so it is now the first thing I2 has to answer. Also closes the Vulkan line this file had flagged as untested. The missing step was -no-snapshot-load: the guest keeps the old GPU config from its snapshot and reports zero Vulkan devices however the host is set up. And records the watchdog trap that produced one wrong conclusion on the way -- a bounded run's kill timer must be scoped to the pid it guards, or it fires into somebody else's experiment. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Languages
Rust
53%
Kotlin
44.4%
Shell
2.6%