PR: https://git.cafe/pingdotgg/t3code/pulls/35309 Head: 830929b4660d52a23a0c3510d8beb9f45edd53c9 Base verification: github/main d8b80a1097 main: T3CODE_DEV_SEED=0 T3CODE_BACKGROUND_RELAY_URL=http://invalid.example vp run dev [dev-runner] serverPort=16733 webPort=8693 Listening on http://127.0.0.1:16733 GET /.well-known/t3/environment -> HTTP 200, agentActivityPublishing=false Invalid/incomplete override ignored; app starts. connect publish --base-dir /home/user/main/.t3 (production public configuration from .env.example) Publishing agent activity enabled. Run `t3 connect login --base-dir /home/user/main/.t3` first so this environment can be authorized to publish. GET /.well-known/t3/environment -> agentActivityPublishing=false (no relay link) PR exact head, isolated T3 home /home/user/t3code/.t3: T3CODE_BACKGROUND_RELAY_URL=http://invalid.example vp run dev --home-dir /home/user/t3code/.t3 BackgroundRelayConfigInvalid: Configure T3CODE_BACKGROUND_RELAY_URL and T3CODE_BACKGROUND_RELAY_ENVIRONMENT_CREDENTIAL together, using an HTTPS origin and a nonempty credential. The optional T3CODE_BACKGROUND_RELAY_ISSUER must also be an HTTPS origin. Server did not listen. No fallback to primary relay. main neighboring behavior: browser paired, added /home/user/t3code using Add project > Local folder, selected Codex GPT-6.1-Sol, sent real turn. Client rendered RELAY_VERIFY_OK and Done. PR partial override: T3CODE_BACKGROUND_RELAY_URL=https://relay.t3.codes vp run dev --home-dir /home/user/t3code/.t3 BackgroundRelayConfigInvalid (same actionable message). An HTTPS URL without a credential is rejected. No server listener. PR default rollback (all background variables removed): vp run dev --home-dir /home/user/t3code/.t3 [dev-runner] serverPort=13773 webPort=5733 Listening on http://127.0.0.1:13773 GET /.well-known/t3/environment -> HTTP 200, agentActivityPublishing=false connect publish --base-dir /home/user/t3code/.t3 (production public configuration from .env.example) Publishing agent activity enabled. Run `t3 connect login` first so this environment can be authorized to publish. GET /.well-known/t3/environment -> agentActivityPublishing=false (no relay link) connect publish --disable --base-dir /home/user/t3code/.t3 Publishing agent activity disabled. GET /.well-known/t3/environment -> agentActivityPublishing=false Focused existing checks at exact PR head, on Blacksmith: vp test run apps/server/src/relay/BackgroundRelayConfig.test.ts apps/server/src/relay/AgentAwarenessRelay.test.ts apps/server/src/environment/ServerEnvironment.test.ts packages/client-runtime/src/relay/managedRelay.test.ts apps/mobile/src/features/cloud/publicConfig.test.ts apps/mobile/src/features/cloud/managedRelayLayer.test.ts 6 files passed, 68 tests passed. Limit: no provisioned background relay account/credential or APNs/FCM tokens on this VM. No successful authenticated split-relay publish, native registration, push, or Live Activity delivery claimed. No fabricated credentials or mock relay used for runtime verification. PR neighboring provider behavior: Paired dev web client with /pair URL. Add project > Local folder > /home/user/t3code. Selected Codex GPT-6.1-Sol in composer. Sent: Reply with exactly RELAY_VERIFY_OK. Do not use tools or change any files. Real provider response rendered in client: RELAY_VERIFY_OK. Follow-up in same real Codex thread: RELAY_FOLLOWUP_OK rendered; browser reload preserved both responses.