switchroom 0.11.0 → 0.12.0

package/README.md

@@ -22,7 +22,7 @@ Every time an agent starts work, a **progress card** pins into its Telegram topi
 
 No silent gaps. No ghosts. No squinting into a black box.
 
-<p align="center"><img src="docs/diagrams/progress-card-anatomy.jpg" width="700" alt="Annotated progress card: pin badge, user quote, last 5 steps, collapsed older, in-flight pulse, elapsed timer, sub-agent indent"></p>
+<p align="center"><img src="docs/diagrams/progress-card-anatomy.svg" width="700" alt="Annotated progress card: pin badge, user quote, last 5 steps, collapsed older, in-flight pulse, elapsed timer, sub-agent indent"></p>
 
 ```
 ⚙️ Working… · ⏱ 12s
@@ -98,7 +98,7 @@ See [`docs/architecture.md`](docs/architecture.md) for the process model, IPC la
 
 Tools that touch the world — Bash, Edit, Write, anything not on an agent's pre-approved allowlist — pause for explicit approval. Switchroom's **approval kernel** (shipped in v0.5.1) routes every gated tool call through an inline Telegram card with the actual diff or command shown. Tap Allow and the tool resumes. Tap Deny and the agent gets a clean refusal it can recover from.
 
-<p align="center"><img src="docs/diagrams/approval-grant-flow.jpg" width="700" alt="Approval grant flow: agent tool call pauses at the kernel, broker writes pending grant to sqlite, user taps Allow on the Telegram card, broker releases the gate, tool resumes"></p>
+<p align="center"><img src="docs/diagrams/approval-grant-flow.svg" width="700" alt="Approval grant flow: agent tool call pauses at the kernel, broker writes pending grant to sqlite, user taps Allow on the Telegram card, broker releases the gate, tool resumes"></p>
 
 - **Inline cards.** Allow / Deny / Allow once / Allow for 1h. No leaving Telegram.
 - **TTL'd grants.** "Allow Bash for 1h" expires automatically. No silent permanent escalation.
@@ -115,7 +115,7 @@ Switchroom never intercepts auth, never proxies inference, never patches the CLI
 
 Each agent is a long-running service. They survive reboots, network drops, and your laptop closing. But "always on" isn't enough on its own. Things still die. The product has to handle that gracefully or the illusion breaks.
 
-<p align="center"><img src="docs/diagrams/wake-audit-lifecycle.jpg" width="700" alt="Wake-audit lifecycle: kill, crash-pane snapshot, auto-restart, agent boots with SWITCHROOM_PENDING_TURN, acks with three options"></p>
+<p align="center"><img src="docs/diagrams/wake-audit-lifecycle.svg" width="700" alt="Wake-audit lifecycle: kill, crash-pane snapshot, auto-restart, agent boots with SWITCHROOM_PENDING_TURN, acks with three options"></p>
 
 - **Auto-restart.** Agent containers come up with `restart: unless-stopped`, and each service has a healthcheck — a crashed or wedged agent is brought back automatically. No silent dropped work.
 - **Resume protocol.** When an agent reboots mid-turn, `start.sh` exports `SWITCHROOM_PENDING_TURN=true` plus the original chat / message ids. The agent's first action on boot is to acknowledge the gap and ask the user how to proceed (start over, summarise and continue, or drop it).
@@ -157,7 +157,7 @@ Then log out and back in so the docker group takes effect, and:
 
 ```bash
 switchroom setup                       # interactive: Telegram + vault + first agent
-switchroom auth add me --from-oauth    # OAuth into your Claude Pro or Max account (one flow, fleet-wide)
+switchroom auth add me --via-claude    # OAuth into your Claude Pro/Max account, broader scope (first-time setup)
 switchroom apply                       # write ~/.switchroom/compose/docker-compose.yml
 docker compose -p switchroom -f ~/.switchroom/compose/docker-compose.yml up -d
 ```
@@ -329,10 +329,11 @@ Model aliases: the bare names `opus`, `sonnet`, `haiku` are accepted alongside t
 The **Anthropic account is the unit of authentication.** One OAuth flow per account, then every agent in the fleet inherits the fleet-wide active account. The `switchroom-auth-broker` daemon owns the refresh loop and is the sole writer of every `credentials.json`. Per-account quota state fans out across the fleet in seconds. See [`docs/auth.md`](docs/auth.md) for the full operator guide.
 
 ```bash
-switchroom auth add <label> --from-oauth          # New account via OAuth (one flow per Anthropic account)
+switchroom auth add <label> --via-claude          # New account, broader scope — recommended for first-time
+switchroom auth add <label> --from-oauth          # Narrow scope=user:inference (rejected by agents in server: mode)
 switchroom auth add <label> --from-agent <name>   # Seed from an existing agent's creds
 switchroom auth add <label> --from-credentials <path>  # Import a credentials.json
-switchroom auth add <label> --from-oauth --replace     # Re-auth an existing label (drift recovery)
+switchroom auth add <label> --via-claude --replace     # Re-auth an existing label (drift recovery)
 
 switchroom auth list                              # Accounts + health + which one is fleet-active
 switchroom auth show [agent]                      # Full snapshot (fleet + agents + consumers), or one agent