Remove broker

docs/gssh-integration.md

@@ -16,14 +16,14 @@ That's the entire job of "let an authorized human run a command on a Charlie hos
 
 A thin Go HTTP+WebSocket client to the existing gssh server, wrapped in a stdio MCP. It:
 
-1. Reads `GSSH_TOKEN` from env at startup (an Authentik JWT minted by the broker, `aud=gssh`).
+1. Reads `GSSH_TOKEN` from env at startup (an Authentik JWT for `aud=gssh`, written into the env by sherlock at agent spawn from the operator's stored TokenSet).
 2. Calls `POST /api/v1/session/initialize` with `Authorization: Bearer <jwt>` to materialise the user's session on the gssh server.
 3. Caches the list of permitted hosts from `GET /api/v1/session/hosts`.
 4. Exposes MCP tools:
    - `ssh.list_hosts()` — returns the cached host list.
    - `ssh.run(host, command, timeout?)` — opens a WebSocket to the session route for `host`, writes `command + "; echo __SHERLOCK_DONE__$?\n"`, reads until it sees the sentinel, returns `{stdout, exit_code}`.
    - `ssh.put_file(host, path, content)` (later) — same shell channel, base64-decode + `tee` on the far side, sentinel as above.
-5. On 401, asks the broker for a refreshed token via the UDS RPC and retries once.
+5. On 401, re-reads the keyring (calling `authn.EnsureFresh`, which `flock`-serialises against concurrent MCP refreshes) and retries once.
 
 No SSH key handling. No cert minting. No `~/Dev/gssh` shell-out.