T3 terminal close / server shutdown proof AFTER d377cfddda15951c4923292132e79859c2d39551 Linux x86_64 | Node v26.13.1 | real server + native PTY Fresh isolated database | external established TCP socket [0.016s] AFTER | Linux | real T3 server | native node-pty | fresh isolated state [1.812s] Hosting T3 server is listening. No mocks or manager-only harness. [1.916s] terminal.open completed through the real WebSocket RPC. [2.021s] Verified TCP server PID equals the terminal root PID returned by T3. [2.021s] Node TCP server execed as terminal root; external client connected. [2.022s] Established socket: PING -> PONG before close. [2.172s] terminal.close completed; session explicitly removed. [2.172s] Root acknowledged SIGTERM over the existing socket and ignored it. [2.172s] Sent SIGTERM to hosting T3 server 150 ms after terminal.close began (< 1000 ms grace). [5.348s] Hosting T3 server exited gracefully (code=130, signal=null). [6.650s] Original one-second terminal kill grace has elapsed. [6.650s] POST-SHUTDOWN PING -> connection closed: terminal root TERMINATED. [6.650s] Terminal root /proc state: absent. [6.651s] Reproduction complete.