docs: update for recent commits (rate limiting, reply threading, screen, auto-reset, two-step spawn, ctx chip)

docs/approvals.md

@@ -47,6 +47,15 @@ step — the operator just sees the name. On approve, hive-c0re
 creates the container in a background task while the dashboard
 shows a spinner.
 
+`InitConfig` approvals are the first step in a two-step spawn
+flow. On approve, hive-c0re seeds the proposed config repo with
+a default `agent.nix` template and sends the manager
+`HelperEvent::ConfigReady { agent }`. The manager then reviews,
+edits, and commits the template before calling `request_spawn`
+to proceed to a Spawn approval. This gives the manager (and
+operator) an explicit review gate on the initial configuration
+before any container is created.
+
 ## Meta flake
 
 The hive-c0re-owned repo at `/var/lib/hyperhive/meta/`
@@ -341,6 +350,10 @@ regular claude turn so the manager can react. Variants
   the operator.
 - `LoggedIn { agent }` — sub-agent just completed login. Manager
   often greets the agent on this event.
+- `ConfigReady { agent }` — a new agent's proposed config repo was
+  just seeded (post-`InitConfig` approval). The manager can now
+  edit `/agents/<agent>/config/agent.nix`, commit the changes,
+  and submit `request_spawn` to create the container.
 - `NeedsUpdate { agent }` — sub-agent's recorded flake rev is
   stale. Manager calls `update(name)` to rebuild — idempotent,
   no approval required.