refactor(#2416): remove the non-pr config-change flow (request_apply_commit / applycommit)

docs/setup.md

@@ -65,12 +65,15 @@ the container, via MCP tools):
 request_init_config(name: "iris")
 # → operator approves → config_ready event lands in the inbox
 
-# Step 2: edit /agents/iris/config/agent.nix, commit it, then:
-request_apply_commit(agent: "iris", commit_ref: "<sha>")
-# → operator approves → container built + started
+# Step 2: edit /agents/iris/config/agent.nix and commit it. Then the
+# operator spawns iris (dashboard ◆ R3QU3ST SP4WN / Spawn approval),
+# which builds + starts the container from that config.
+
+# Later config changes: open a PR on agent-configs/iris (hive-forge);
+# the operator reviews + approves it — no MCP tool call.
 ```
 
-See [`approvals.md`](approvals.md) for the full two-step flow.
+See [`approvals.md`](approvals.md) for the full flow.
 
 ### 5 · Useful host commands
 
@@ -97,8 +100,8 @@ See [`tools/hivectl.md`](tools/hivectl.md) for every `hivectl` verb.
 - **No forge admin token is stored in any agent state dir.** Agents
   hold a regular agent token in their `forge-token` file; sensitive
   creds (the core token, the matrix admin token) live on the host.
-- All config changes (`request_apply_commit`) go through operator
-  approval — agents can't unilaterally rebuild containers, by design.
+- All config changes (forge PRs on `agent-configs/<name>`) go through
+  operator approval — agents can't unilaterally rebuild containers, by design.
   See [`boundary.md`](boundary.md) and [`security.md`](security.md).
 
 Once the hive is running, ruth records anything it needs to remember