PR 30777 runtime verification, 2026-11-10 Playwright 1.60.0, /usr/bin/google-chrome, Linux Boat VM Local TLS reverse proxy: https://verify.ts.net:18443, HTTP: http://verify.ts.net:18080 TLS proxy forwards X-Forwarded-Proto=https; HTTP proxy forwards http. Each server used empty isolated state, no mock providers or fixtures. BASELINE github/main 4c924ff4e6 $ git worktree add ../main github/main $ vp i $ vp run dev --no-seed --host 0.0.0.0 [background, captured PID] Actual dev ports: server 16733, web 8693 Browser paired through HTTPS using the startup pairing token. Chrome stored: [{"name":"t3_session_16733_527aeec013da","secure":false,"httpOnly":true,"sameSite":"Lax"}] GET http://verify.ts.net:18080/api/auth/session => 200, authenticated=true BUG REPRODUCED: HTTPS-issued credential was sent over plaintext HTTP. Stopped main by captured PID before starting PR. PR exact head e0c934ab92d21a6ce5737499d4bc3029b019a83d $ git fetch github pull/30777/head $ git checkout -b verify/pr-30777 FETCH_HEAD $ vp i $ vp run dev --no-seed --host 0.0.0.0 --home-dir /home/user/t3code/.t3 [background, captured PID] Actual dev ports: server 13773, web 5733 Browser paired through HTTPS. Chrome stored __Secure-t3_session_13773_5c7566105688; secure=true, httpOnly=true, sameSite=Lax. Before separate HTTP pairing: GET http://verify.ts.net:18080/api/auth/session => 200, authenticated=false. Created cookie-tls-verification as a real local git project through Add project > New project. Selected Codex GPT-6.1-Sol in composer, submitted a real turn through the HTTPS UI. Response: TLS_COOKIE_CODEX_OK NEIGHBORING BEHAVIOR Minted a token through POST /api/auth/pairing-token, entered it in HTTP pairing UI. HTTP session: {"status":200,"authenticated":true} HTTPS after HTTP pairing: {"status":200,"authenticated":true} Chrome stores both schemes independently: [{"name":"__Secure-t3_session_13773_5c7566105688","secure":true,"httpOnly":true,"sameSite":"Lax"},{"name":"t3_session_13773_5c7566105688","secure":false,"httpOnly":true,"sameSite":"Lax"}] Re-paired HTTPS through POST /api/auth/browser-session, carrying both current cookies: HTTP 200. HTTPS after re-pair: {"status":200,"authenticated":true} HTTP after HTTPS re-pair: {"status":200,"authenticated":true} Replaced HTTPS credential alone: HTTP 200, authenticated=false Loaded a fresh Chrome client context with the real stored cookies and re-opened the thread. Submitted a second real GPT-6.1-Sol turn. Response: TLS_RELOAD_CODEX_OK CHECKS $ blacksmith-check run --id 'vp i' Passed. $ blacksmith-check run --id 'vp test run apps/server/src/auth/http.test.ts apps/server/src/auth/EnvironmentAuth.test.ts' 2 files passed, 29 tests passed. GitHub head CI: all reported checks passed or intentionally skipped. NOT VERIFIED Real Tailscale Serve or T3 Connect tunnel; used a local TLS reverse proxy with a test certificate. Native desktop, iOS, Android; other providers; legacy-cookie migration and reusable dev-token browser flows beyond the existing focused tests. No source edits, commits, or pushes.