PR 22190 runtime verification, 2026-10-28, Linux Boat VM
main: 40d335a7ba (github/main)
PR: 7dd9e7e617c9c58279ffe5a0030a3bfb734c31a8

Setup
git worktree add ../main github/main
cd ../main && timeout 600 vp i
Started main dev in background; dev-runner: serverPort=16733 webPort=8693.
For desktop verification, stopped main's web/server process group and ran
dev:web plus the actual Electron app with its bundled backend.
Stopped main before starting the PR. Checked out the exact PR head; vp i passed.
Started PR dev in background with explicit isolated --home-dir.
PR dev-runner: serverPort=13773 webPort=5733.
For desktop verification, stopped that server and ran dev:web plus Electron's
bundled backend. Only one task dev backend ran at a time.
Playwright came from the repo; web browser: /usr/bin/google-chrome.
Desktop: real Electron 44.9.3, t3code-dev://app, production public Clerk config
from .env.example. No mocked adapters, seeded databases, or fake tokens.
Used --password-store=basic after the VM requested keyring creation.
No keyring was created or changed.

Before: main, actual Clerk initialization and Settings > Sign in to T3 Connect
Clerk loaded=true, actual anonymous client created; sign-in form rendered.
stat clerk-tokens.json: 666
JSON key: __clerk_client_jwt (value intentionally omitted)
Other-user readability was NOT demonstrated: VM home directory denies traversal.

After: PR, same isolated main state for the actual upgrade
stat clerk/: 700
stat clerk/clerk-tokens.json: 600
legacy clerk-tokens.json removed: true
SHA-256 before/after equal: true (exact persisted bytes preserved)
Actual Clerk sign-in form rendered; close and reopen worked.
After modal reopening: directory=700, file=600.
After renderer reload: Clerk loaded=true, same anonymous client=true.
After full desktop restart: Clerk loaded=true, same anonymous client=true.

Fresh PR state, created by actual app startup in /tmp/pr22190-fresh-home
Clerk loaded=true; actual anonymous client=true; signed-in session=false.
stat userdata/clerk/: 700
stat userdata/clerk/clerk-tokens.json: 600
JSON key: __clerk_client_jwt (value intentionally omitted)
legacy file exists: false

Nearby behavior, actual UI and real Codex gpt-6.1-sol through local proxy
Created local project/repository clerk-permissions-verification through web UI.
Created thread, selected GPT-6.1-Sol, submitted read-only pwd/git status prompt.
Web result: pr22190-codex-ok /home/user/t3code/.t3/projects/clerk-permissions-verification
Added that real repo through desktop UI, created thread, selected GPT-6.1-Sol.
Desktop result: pr22190-desktop-codex-ok /home/user/t3code/.t3/projects/clerk-permissions-verification
Both turns completed and rendered; no repository changes requested or made.

Checks, remote Blacksmith task worker
vp test run apps/desktop/src/app/ClerkTokenStore.test.ts apps/desktop/src/app/DesktopClerk.test.ts
2 files passed, 21 tests passed.
vp run check:changed 87ea18cad91fa246f66e65acd00fe99aa733c14e
4 changed files: format, lint, both knip passes, desktop/scripts typechecks,
and 21 tests passed. Used explicit PR base and fetched 3 history levels because
the worker initially lacked a merge base. Initial worker startup timeout retried.

Limits
No Clerk account credentials: authenticated sign-in, token refresh, and sign-out
were not exercised. Anonymous client persistence is real, but does not prove
those account lifecycle operations. macOS, Windows ACLs, and keyring-backed
encryption were not verified. Relative-path/cross-filesystem/symlink cases are
covered by the existing focused tests, not recreated via UI in this pass.

No source changes, commits, pushes, labels, rebase, force-push, close, or merge.