PR 30324 real dev verification
baseline github/main: 7c22e24e3fa1a3bb3a95f27aea000067f198fe7f
PR head: df37fad362909d233e6b4c44991c83d75734df4e
Linux Boat VM; Node 26; Google Chrome via repo Playwright.
Each checkout installed with vp i. One dev server at a time, isolated .t3 homes, no seed data.
Projects added through the web UI pointing at /home/user/t3code (a real git repository).
Real Codex gpt-6.1-sol turns completed through the web composer on both checkouts.
Public Connect configuration: node --env-file=.env.example apps/server/src/bin.ts ...
No Connect account authorization was available; relay revocation is not verified.

MAIN: live server
$ node --env-file=.env.example apps/server/src/bin.ts connect unlink --base-dir .t3
T3 Connect is disabled locally.
The relay-side environment record was not revoked.
Deregister it from the T3 Connect page of your T3 account, or run `t3 connect login` and retry.

MAIN: SIGKILL of captured dev process group 29853 (server PID 30888, port 16733)
The real server left its server-runtime.json behind. No runtime file was fabricated.
$ node --env-file=.env.example apps/server/src/bin.ts connect unlink --base-dir .t3
[transport error: ECONNREFUSED 127.0.0.1:16733]
T3 Connect is disabled, but the running server could not stop its tunnel.
Restart that server to stop the connector.

MAIN: an unrelated HTTP listener takes port 16733; same unlink command
listener recorded: POST /api/connect/unlink; bearer present=true
No bearer values were logged.

PR: live server PID 47143, port 13773
$ node --env-file=.env.example apps/server/src/bin.ts connect unlink --base-dir .t3
T3 Connect is disabled locally.
$ node --env-file=.env.example apps/server/src/bin.ts connect logout --base-dir .t3
T3 Connect is disabled locally.
Signed out of T3 Connect locally.
The background service is managed separately with `t3 service`.
Both commands also warned accurately that the relay-side environment record was not revoked.
Server access log for both commands:
  http.method: POST
  http.url: /api/connect/unlink
  http.status: 200
Real gpt-6.1-sol web turn after these commands: "sol connect verification ready."

PR: SIGKILL of captured dev process group 46401, real runtime record retained
$ node --env-file=.env.example apps/server/src/bin.ts connect unlink --base-dir .t3
T3 Connect is disabled locally.
The server that ran T3 Connect is gone, but its cloudflared process may still be running.
Stop that process if it is.
$ node --env-file=.env.example apps/server/src/bin.ts connect logout --base-dir .t3
T3 Connect is disabled locally.
The server that ran T3 Connect is gone, but its cloudflared process may still be running.
Stop that process if it is.
Signed out of T3 Connect locally.
The background service is managed separately with `t3 service`.
Both commands retained the accurate relay-side-not-revoked warning.

PR: an unrelated HTTP listener takes port 13773
Ran both unlink and logout again: same correct output, zero requests received.
An independent GET /probe returned HTTP 404 and was recorded (bearer present=false), proving the listener was reachable.

PR: restarted same dev server and home
The project, thread, and previous response persisted.
A follow-up web composer gpt-6.1-sol turn completed: "restart preserved this thread."

Blacksmith focused checks:
vp test run apps/server/src/cli/connect.test.ts apps/server/src/cli/up.connect.test.ts apps/server/src/cli/up.test.ts
3 files passed; 29 tests passed.

Not verified: authenticated external relay revocation, a linked cloudflared tunnel/orphan cleanup (client not installed), native mobile/desktop clients, macOS/Windows, and shared-home PID namespaces or PID reuse.
No source changes, commits, or pushes were needed.