docs(#1014): update stale root→ruth references in conventions, approvals, agent-hierarchy

docs/approvals.md

@@ -2,7 +2,7 @@
 
 The approval queue is hyperhive's pivot: nothing that changes the
 shape of an agent (its config, whether it exists) happens without an
-operator click. The manager (`root`) is the policy gate in front of
+operator click. The manager (`ruth`) is the policy gate in front of
 that queue; helper events are how it stays informed about what
 happens after a decision lands.
 
@@ -114,7 +114,7 @@ kind-specific payload carrier.
   operator approval. Step 1 of the two-step spawn flow above.
 - `UpdateMetaInputs` — `commit_ref` stores the JSON-encoded inputs
   array (`"[]"` = all inputs, `"[\"nixpkgs\"]"` = just nixpkgs,
-  etc.). `agent` field is set to `root` (the requesting manager).
+  etc.). `agent` field is set to `ruth` (the requesting manager).
   On approve hive-c0re runs `nix flake update [inputs...]` on the
   meta flake and commits the resulting lock changes.
 - `SchedulePrompt` — `commit_ref` stores the JSON-encoded
@@ -438,23 +438,22 @@ notes, the events DB, proposed history, and applied history
 all survive. The manager keeps its session; sub-agents stay
 logged in.
 
-## Manager (`root`) is hive-c0re-managed
+## Manager (`ruth`) is hive-c0re-managed
 
 The manager container runs through the **same lifecycle as
-sub-agents**. On `hive-c0re serve` startup, if `root` is missing,
+sub-agents**. On `hive-c0re serve` startup, if `ruth` is missing,
 hive-c0re creates it. The manager's flake lives at
-`/var/lib/hyperhive/applied/root/`; its proposed config at
-`/var/lib/hyperhive/agents/root/config/`. Manager can edit its own
-`agent.nix` (visible inside the container at `/agents/root/config/`)
-and submit `request_apply_commit("root", <sha>)` for operator
+`/var/lib/hyperhive/applied/ruth/`; its proposed config at
+`/var/lib/hyperhive/agents/ruth/config/`. Manager can edit its own
+`agent.nix` (visible inside the container at `/agents/ruth/config/`)
+and submit `request_apply_commit("ruth", <sha>)` for operator
 approval.
 
 Differences from sub-agents:
 
 - `flake.nix` extends `hyperhive.nixosConfigurations.manager`
   (vs `agent-base`).
-- Container name is `root` (no `h-` prefix).
-- Web UI port via `lifecycle::agent_web_port("root")` — same
+- Web UI port via `lifecycle::agent_web_port("ruth")` — same
   FNV-1a hash as every other agent (8100..8999 range).
 - `set_nspawn_flags` adds two extra binds: `/var/lib/hyperhive/agents`
   → `/agents` (RW) so the manager can edit per-agent proposed repos,