Scale down smaller diagrams

- sandbox-config: 400px
- session-lifecycle: 500px
- crash-recovery: 500px
- client-interactions: 400px
- events: 400px
- Keeps larger diagrams (architecture, mailbox, automation) at full width

EVENTS.md

@@ -4,7 +4,7 @@ The events system provides a real-time text stream of all AnviLLM activity using
 
 ## Architecture
 
-![Events System](diagrams/events.svg?v=2)
+<img src="diagrams/events.svg?v=2" width="400">
 
 Multiple clients can read from `agent/events` simultaneously, each consuming the same event stream for different purposes: notifications (desktop, SMS, WhatsApp), logging/auditing, custom integrations, etc.
 

README.md

@@ -120,7 +120,7 @@ Templates use `{VARNAME}` syntax. Any environment variable can be referenced.
 
 **Config** (`~/.config/anvillm/`): Layered YAML files, most permissive wins:
 
-![Sandbox Config Layering](docs/diagrams/sandbox-config.svg?v=2)
+<img src="docs/diagrams/sandbox-config.svg?v=2" width="400">
 
 - Default role: `roles/default.yaml`
 
@@ -136,13 +136,13 @@ Set `best_effort: true` for unsandboxed fallback (⚠️ if no Landlock support)
 
 **Session lifecycle:**
 
-![Session Lifecycle](docs/diagrams/session-lifecycle.svg?v=2)
+<img src="docs/diagrams/session-lifecycle.svg?v=2" width="500">
 
 State transitions: `idle` ↔ `running` cycle via CLI hooks (`userPromptSubmit` when user sends prompt, `stop` when agent finishes). Crash → `error` → auto-restart → `starting`. Note: any state can transition to `stopped` or `killed` (not shown); `stopped` can restart → `starting`.
 
 **Self-healing:** Auto-restarts crashes every 5s (preserves context/alias/cwd), skips intentional stops
 
-![Crash Recovery](docs/diagrams/crash-recovery.svg?v=2)
+<img src="docs/diagrams/crash-recovery.svg?v=2" width="500">
 ┌─────────┐  crash   ┌─────────┐  5s wait  ┌─────────┐
 │ running │─────────►│  error  │──────────►│ running │
 └─────────┘          └─────────┘           └─────────┘
@@ -228,7 +228,7 @@ agent/
 
 **Client Interactions:**
 
-![Client Interactions](docs/diagrams/client-interactions.svg?v=2)
+<img src="docs/diagrams/client-interactions.svg?v=2" width="400">
 
 Different clients interact with different parts of the filesystem: frontends read state, control files manage sessions, scripts consume events.