T3 Code / agent-device lifecycle — real built server
Commit e0f5828925a1fe082820bb089e23af2636c95385
Environment: Linux x86_64; Node 26.12.1; fresh isolated state
No copied database. Android discovery tools; no booted device.
=== A. Graceful quit after an earlier server was killed ===
First server: real server PID 56824, authenticated RPC ready
RPC device.configure: local support ON, agent access ON
RPC device.list retry local host: initialize real agent tools
Environment daemon PID 57141, agent-device 0.21.31, HTTP health=True
SIGKILL server PID 56824: exited -9
Recorded daemon PID 57141 survives abrupt exit: alive=True, health=True
Restart, same state: real server PID 57275, authenticated RPC ready
Restarted server uses NO device RPC or agent tools
SIGTERM restarted server PID 57275: exited 130
After graceful quit: SAME daemon PID 57141: alive=False, HTTP health=False
=== B. Disable agent access after an earlier server was killed ===
Third server: real server PID 58137, authenticated RPC ready
RPC device.configure: local support ON, agent access ON
RPC device.list retry local host: initialize real agent tools
Environment daemon PID 58420, agent-device 0.21.31, HTTP health=True
SIGKILL server PID 58137: exited -9
Recorded daemon PID 58420 survives abrupt exit: alive=True, health=True
Restart, same state: real server PID 58554, authenticated RPC ready
Restarted server has not used device tools
RPC device.configure: agent access OFF (same operation as Devices settings)
Settings response: agentAccessEnabled=False
After disabling access: SAME daemon PID 58420: alive=False, HTTP health=False
DONE. Observations saved; cleanup follows.
Cleanup: all recorded server, hub and daemon processes stopped.