PR #26455: server.getSettings compatibility verification
Baseline: github/main 32ecd71726 (isolated /home/user/main worktree)
PR head: fd3e0fb566eba3af17d3a8777ee0e19d47170266
Linux Boat VM, real dev server, authenticated JSON WebSocket /ws?orchestrationProtocol=2.
No mocks, database fixtures, or replay provider. UI driven with repo Playwright and /usr/bin/google-chrome.

$ git worktree add ../main github/main && (cd ../main && vp i)
$ setsid nohup vp run dev ...
main: serverPort=16733 webPort=8693
> {"_tag":"Request","id":"1","tag":"server.getSettings","payload":{},"headers":[]}
{
  "_tag": "Exit",
  "requestId": "1",
  "exit": {
    "_tag": "Failure",
    "cause": [
      {
        "_tag": "Die",
        "defect": "Unknown request tag: server.getSettings"
      }
    ]
  }
}
Stopped main process group using captured PID 14494 before starting PR server.
$ git switch -c issue-watch/26446 github/issue-watch/26446 && vp i
$ setsid nohup vp run dev --home-dir /home/user/t3code/.t3 ...
PR: serverPort=13773 webPort=5733, isolated state; automatic live-data seeding disabled.
Created project pointing to /home/user/t3code using Add project > Local folder.
Created and sent a real Codex gpt-6.1-sol turn through the web composer.
Turn ran git rev-parse --show-toplevel and git rev-parse --short HEAD, completed in the UI, replied settings-compat-ok.
In Settings > Providers, favorited GPT-6.1-Sol, hid GPT-5.5, moved GPT-6-Luna above GPT-6-Sol; all survived page reload.
Set a default model and temporary source-control token via server.updateSettings over the real authenticated WebSocket; cleared the temporary token after checking redaction.
PASS settings update -> legacy read preserves default, favorite, hidden model and model ordering
PASS legacy settings deeply equal server.getConfig.settings
PASS source-control token absent from legacy response; {"token":"••••••"}
PASS orchestration:read-only session reads legacy settings and config
PASS settings update rejected: {"_tag":"Failure","cause":[{"_tag":"Fail","error":{"_tag":"EnvironmentAuthorizationError","message":"The authenticated token is missing required scope: settings:write.","requiredScope":"orchestration:operate","requiredPermission":"settings:write"}}]}
{
  "defaultModelSelection": null,
  "favorites": [
    {
      "provider": "codex",
      "model": "gpt-6.1-sol"
    }
  ],
  "providerModelPreferences": {
    "codex": {
      "hiddenModels": [
        "gpt-5.5"
      ],
      "modelOrder": [
        "gpt-6.1-sol",
        "gpt-6-astra",
        "gpt-6-luna",
        "gpt-6-sol",
        "gpt-5.6-sol",
        "gpt-5.6-terra",
        "gpt-5.6-luna",
        "gpt-5.5"
      ]
    }
  },
  "settingsMatch": true
}
$ blacksmith-check run --id <task-owned-worker> "git fetch --depth=3 https://github.com/pingdotgg/t3code.git fd3e0fb566eba3af17d3a8777ee0e19d47170266 && git log -3 --oneline && vp run check:changed 0160c448f61bf24244411781ccc47829a1a51a17"
PASS format, lint, knip (both passes), GraphQL generation check, 32 affected-package typechecks, 29 tests in 3 files.
Initial check setup lacked ancestry; fetched the exact head with depth 3 to restore its two parents, then reran successfully.
No source changes, commits, or pushes.

NOT VERIFIED: installed Swift TestFlight build 68 UI and its actual native decoder, native iOS/Android clients, Electron shell, macOS/Windows hosts, relay/tunnel connections. Linux verification covers the restored wire method and real Codex web-client path, not a claim that TestFlight itself was exercised.