Align documentation and user-facing terminology

docs/macos.md

@@ -39,7 +39,7 @@ Every build is signed for distribution outside the App Store: the team's Develop
 
 ## Updates
 
-The app runs Sparkle with its own user driver instead of Sparkle's standard windows, so no update UI offers Skip or turning automatic updates off, which `byre-update` would override. A Mac that runs the server but not the app is updated by `byre-update`, which the server runs daily; it does nothing while the app is running from that bundle, leaving the update to the app's own updater.
+The update UI must not offer Skip or turning automatic updates off: on a Mac running the server, `byre-update` would override either choice while the app isn't running.
 
 ## Persistence
 

docs/operations.md

@@ -126,4 +126,3 @@ byre never signs with a key on the machine it runs on. When a project checkout's
 - Saved commands belong to a user on one server, because what they do is usually tied to that Mac: signing in again to the credential an `apiKeyHelper` uses (AppleConnect's `getToken -n cli` on a work Mac) is the case they were made for. Its terminal stays open after the command, so the result stays readable.
 - It types one byte per write: a program in raw mode that stops reading blocks a PTY write, and the PTY's file doesn't support deadlines, so this keeps the call within its limits while leaving at most one byte to arrive late.
 - zsh gets shell integration through a `.zshenv` in `<data>/zsh` (via `ZDOTDIR`) that reports the prompt (OSC 133) and the line being edited, so byre can wake the agent when a line it left is run. It turns off `PROMPT_SP`, which would print a `%` padded to the width the shell started at, so an agent-opened shell (120 columns) replayed in a narrower tab wraps each one onto an extra line. A user `.zshrc` that sets `zle-line-pre-redraw` with `zle -N` rather than `add-zle-hook-widget` replaces the hook, and byre then sees the line as empty. Other shells get no integration and nothing wakes their agents.
-- The terminal WebSocket checks that `Origin` matches `Host`, so another site can't open one through the user's Tailscale identity.