grid-operations

# Grid operations `$GRID_FLEET` and `$GRID_CLI` are executable paths, not directories. Quote them. Start with `"$GRID_FLEET" config` and `"$GRID_FLEET" status`. `status` reads the viewer's published snapshot without opening a socket or launching Grid. Check `fresh`, `status` and `observedAt`; use fresh live observations to answer ordinary inventory questions. A downloaded weight file or a catalog entry is not a serving model. The viewer reads actual CLI data, and the runner records operation start/completion without recording prompts, credentials or full argv. This harness runs without Codex's sandbox, so these commands run as they would in a terminal — `join` gets the GPU, every call reaches the network. Never request escalation, and never read a failure as a sandbox problem: the command's own error is the answer. Never diagnose an engine with `ps`, `lsof`, `sysctl` or logs; report the error after two failed attempts and wait. ## Targets and access `grid-fleet.json` holds the mode (`local` or `remote`), grid selector, controller machine, managed machines and user preferences. A null grid means the workspace is not connected; the viewer must not fall through to an old CLI default. **The CLI's selection (`use`) is the one source of truth for which grid this is.** The viewer reads it on every poll and follows a change, so what the person selected — in a terminal, or by asking you — is what the screen shows; `connect` selects too, so the two never disagree. A fresh sign-in h...