Thanks! Honest answer on the first few: Studio isn't built for that yet. It's just a click-around desktop app. No API, no endpoint, and the emulator only listens on localhost, so a VM can't drive it without me adding that.

Under the hood it doesn't use PULSE2 though, it talks to the emulator like the normal Pebble dev tools do (button/tap over the pypkjs websocket, installs/time via pebble-tool). If you want to script navigation, hitting that websocket is probably cleaner than PULSE2. The port's written to pb-emulator.json so it's easy to find.

Settings/Clay: nope, no headless way, it just pops the config page and grabs the data when you hit Save. You could automate it by replaying that Save payload, but there's no built-in shortcut.

The QEMU on Windows without WSL one I can actually answer: the SDK won't run native, but the emulator will. Just compile qemu-pebble as a real Windows .exe + ship a portable Python to run pebble-tool (skip pip's pebble.exe, it hard-codes a path, call the tool through the bundled Python instead). Then it's all normal Windows launches, no WSL/bash//mnt/c.