linux desktop relaunch verification, 2026-11-01

baseline github/main: ce9e01640636
pr head: 12b5da7c81aa33cf2daceecb3938a04a83a439b3
electron: 44.10.0

both checkouts: vp i; vp run dev --no-seed (background, captured PID, then stopped).
real relaunch: blacksmith vp run build:desktop, downloaded assets; Electron main.cjs with isolated T3CODE_HOME, --password-store=basic and debugging port; VITE_DEV_SERVER_URL unset. This runs DesktopLifecycle.relaunch, not the dev wrapper exit(75).

created project /home/user/t3code, thread, and real Codex gpt-6.1-sol turns through app UI.
trigger: settings > sharing & access > network access > restart and enable.
reverse: restart and disable.

baseline terminal transcript:
[verify/linux-relaunch]:~/t3code$ [verify/linux-relaunch]:~/t3code$ printf 'BASELINE BEFORE RELAUNCH\n'; grep NoNewPrivs /proc/self/status; sudo -n id; git status --short
BASELINE BEFORE RELAUNCH
NoNewPrivs:	0
uid=0(root) gid=0(root) groups=0(root)
[verify/linux-relaunch]:~/t3code$ [verify/linux-relaunch]:~/t3code$ [verify/linux-relaunch]:~/t3code$ [verify/linux-relaunch]:~/t3code$ [verify/linux-relaunch]:~/t3code$ printf 'AFTER RELAUNCH\n'; grep NoNewPrivs /proc/self/status; sudo -n id; git status --short
AFTER RELAUNCH
NoNewPrivs:	1
sudo: The "no new privileges" flag is set, which prevents sudo from running as root.
sudo: If sudo is running in a container, you may need to adjust the container configuration to disable the flag.
[verify/linux-relaunch]:~/t3code$ 

pr terminal transcript:
[verify/linux-relaunch]:~/t3code$ 
[verify/linux-relaunch]:~/t3code$ [verify/linux-relaunch]:~/t3code$ [verify/linux-relaunch]:~/t3code$ [verify/linux-relaunch]:~/t3code$ printf 'AFTER RELAUNCH\n'; grep NoNewPrivs /proc/self/status; sudo -n id; git status --short
AFTER RELAUNCH
NoNewPrivs:	0
uid=0(root) gid=0(root) groups=0(root)
[verify/linux-relaunch]:~/t3code$ [verify/linux-relaunch]:~/t3code$ [verify/linux-relaunch]:~/t3code$ printf 'AFTER RELAUNCH\n'; grep NoNewPrivs /proc/self/status; sudo -n id; git status --short
AFTER RELAUNCH
NoNewPrivs:	0
uid=0(root) gid=0(root) groups=0(root)
[verify/linux-relaunch]:~/t3code$ [verify/linux-relaunch]:~/t3code$ [verify/linux-relaunch]:~/t3code$ printf 'AFTER NETWORK ACCESS RELAUNCH\n'; grep NoNewPrivs /proc/self/status; sudo -n id; git status --short
AFTER NETWORK ACCESS RELAUNCH
NoNewPrivs:	0
uid=0(root) gid=0(root) groups=0(root)
[verify/linux-relaunch]:~/t3code$ 

real provider outputs:
main after relaunch: NoNewPrivs: 1; sudo: The "no new privileges" flag is set, which prevents sudo from running as root.
pr after enable, disable, enable again: NoNewPrivs: 0; sudo -n id: uid=0(root) gid=0(root) groups=0(root); git status --short: empty.
web client attached to desktop-owned backend after relaunch: real Codex gpt-6.1-sol turn returned same successful outputs.

blacksmith checks: vp run check:changed 7195b699547b538e49f758e314dde5c8c5d907cf
PASS format, lint, both knip checks, desktop/scripts typechecks, ElectronApp.test.ts 12/12.
blacksmith build: 5/5 tasks passed for each checkout.

limitations: built desktop bundle, not an installed package or actual AppImage; no macOS/Windows or native mobile clients; no Tailscale/relay connection. password-store=basic used to avoid VM keyring setup.