PR #21478 real dev verification, 2026-10-27
main: 570d4b03ee (github/main), /home/user/main
head: 12879b09adf2eba02fe6feab47f422e463d903f6, /home/user/t3code

Setup:
git worktree add ../main github/main
vp i (both checkouts): passed
main: background vp run dev, server 16733, web 8693, isolated .t3
PR: background vp run dev --home-dir /home/user/t3code/.t3,
server 13773, web 5733
Playwright 1.60.0, /usr/bin/google-chrome, real web UI
Projects added through Local folder; real Codex gpt-6.1-sol turns in both apps.

Main reproduction attempt:
Installed JDK 17, Android SDK command-line tools, Emulator 37.2.12,
Android 35 google_apis x86_64 image; created real pr21478 AVD.
emulator -accel-check: KVM (version 12) is installed and usable.
Codex called device_list and device_open via T3 MCP.
device_open: Could not communicate with device support. Try refreshing devices.
Retry after manually restarting real emulator: same failure.
No executable/targetArgs returned. No claim acquired. Original claim leak NOT reproduced.
Two manual emulator starts tried software graphics, no window/audio, 1536/2048 MiB,
2 cores, with final display 480x800 and Vulkan disabled.
ERROR        | detected a hanging thread 'QEMU2 main loop'. No response for 15453 ms
ERROR        | detected a hanging thread 'QEMU2 CPU0 thread'. No response for 17098 ms
ERROR        | detected a hanging thread 'QEMU2 CPU0 thread'. No response for 15435 ms
ERROR        | detected a hanging thread 'QEMU2 CPU1 thread'. No response for 16804 ms
ERROR        | detected a hanging thread 'QEMU2 main loop'. No response for 18106 ms
ERROR        | detected a hanging thread 'QEMU2 main loop'. No response for 15333 ms
The emulator exited without sys.boot_completed=1; adb devices ultimately empty.

PR neighboring behavior via fresh real Codex gpt-6.1-sol thread:
device_list({}): local ready; Android available; pr21478 booted:false; open:[];
hub 0.19.0-canary-20261023-1357114; agent-device 0.21.31.
device_close({shutdown:false}): structuredContent {}, isError:false.
{"name":"DeviceService.close","durationMs":0.2473,"exit":{"_tag":"Success"}}
No device booted or opened in the PR check. This proves empty close only.
A thread created before enabling agent access was denied as expected;
a fresh thread after onboarding had access and successfully called the tools.

Remote checks through blacksmith-check:
vp i && vp test run apps/server/src/device/DeviceMultiHost.test.ts apps/server/src/device/DeviceService.test.ts apps/server/src/device/EasDeviceHost.test.ts apps/server/src/device/LocalDeviceHost.test.ts apps/server/src/device/SshDeviceHost.test.ts apps/server/src/device/sshDeviceScript.test.ts
6 test files passed, 76 tests passed.
PR CI: 27 successful, 0 failing, 0 pending at unchanged head.

UNVERIFIED: claim conflict before close, handoff after close, retained records on
release failure, retry, shutdown with active claims, local hub restart recovery,
SSH reconnect/cleanup, EAS live sessions, native iOS/Android clients and desktop shells.
No source changes, commits, pushes, labels, merge, close, rebase or force-push.