PR 30480 real Linux CLI verification
main: d51bc58f5e (github/main)
PR: 0f08058918f2ca90ffdbc038e7a54940ee631802

Setup: actual CLI service install, isolated home containing spaces:
  timeout 120 node apps/server/src/bin.ts service install --base-dir '/home/user/pr30480 home'
  Service installed (0.1.6)

Reproduction on main and exact PR head:
  timeout 60 env XDG_RUNTIME_DIR=/tmp/pr30480-no-runtime DBUS_SESSION_BUS_ADDRESS=unix:path=/tmp/pr30480-missing-bus node apps/server/src/bin.ts up --base-dir '/home/user/pr30480 home' --no-lan --yes
The unavailable session bus is a real service-manager failure. No mocks, source edits, or synthetic service records.

MAIN OUTPUT
Updating T3 Code. Running agent turns will stop.
Service setup failed: [user-manager-unavailable] Cannot reach the systemd user manager. Run `systemctl --user status` in a login session for the service user. Install your distribution's systemd user-session support if it is missing; do not run T3 with sudo. Fix that, then run `t3 up` again.

This machine
  Service        installed · t3@0.1.6
  Local network  on · pairing code only

Anyone on your LAN or tailnet can reach the port. A pairing code is the only lock.

Run `t3 pair --base-dir '/home/user/pr30480 home'`. Use the code on your other device.

PR OUTPUT
Updating T3 Code. Running agent turns will stop.
Service setup failed: [user-manager-unavailable] Cannot reach the systemd user manager. Run `systemctl --user status` in a login session for the service user. Install your distribution's systemd user-session support if it is missing; do not run T3 with sudo. Fix that, then run `t3 up --base-dir '/home/user/pr30480 home'` again.

This machine
  Service        installed · t3@0.1.6
  Local network  on · pairing code only

Anyone on your LAN or tailnet can reach the port. A pairing code is the only lock.

Run `t3 pair --base-dir '/home/user/pr30480 home'`. Use the code on your other device.

After each failed update, service.env remained T3CODE_LAN=true (rollback).

RECOVERY WITH THE NORMAL SESSION BUS
  timeout 60 node apps/server/src/bin.ts up --base-dir '/home/user/pr30480 home' --no-lan --yes
Restarting T3 Code. Running agent turns will stop.

This machine
  Service        installed · t3@0.1.6
  Local network  off

Remote access is off. T3 Code still runs here in the background.
After recovery, service.env was T3CODE_LAN=false.
Status command against the same home:
{
  "service": {
    "supported": true,
    "installed": true,
    "installedVersion": "0.1.6"
  },
  "connect": null,
  "lan": {
    "enabled": false,
    "inheritedDefault": false,
    "hostOverride": null
  }
}

REAL CLIENT/PROVIDER
Playwright from repo dependencies; /usr/bin/google-chrome.
PR dev server with explicit isolated --home-dir /home/user/t3code/.t3.
Added /home/user/pr30480-project (real git repo) through Add project > Local folder.
Selected Codex GPT-6.1-Sol in the model picker; submitted an initial turn and a follow-up.
Observed both exact responses and return to an enabled submit button.

CHECKS
Blacksmith: vp test run apps/server/src/cli/up.test.ts: 22 passed.
Blacksmith: vp run check:changed ad4bb6d6fa0af9072fef92b540c12f04997036d5:
format, lint, knip, graphql, typecheck (3 packages), tests (25 across 3 files) passed.
Explicit base supplied because the worker snapshot initially lacked main ancestry; fetched real PR history before rerunning.

NOT VERIFIED
Declined-restart hint: source build has connect:null (T3 Connect unavailable), with no task-owned Connect authorization.
Cannot reach genuine managed-link unlink failure and decline prompt without that external setup.
Windows/PowerShell, macOS/launchd, native iOS/Android, npm-runner/standalone-launcher variants were not exercised.
No code changes were required.