ruth is created from a ruth archetype that runs sonnet

docs/4-implementation/agent-state/roster.md

@@ -94,7 +94,10 @@ state dirs work as for every other agent.
   key, and nixos-container name are all `ruth` (container `h-ruth`).
   Like every agent it comes from the swarm dashboard or
   `swarmctl agent create`; `hive-c0re` creates nothing at boot.
-  Roster-wise, `ruth` is just another entry.
+  Roster-wise, `ruth` is just another entry. The setup assistant creates
+  her from the [`ruth` archetype](../../2-handbook/swarm/archetypes.md#the-built-in-archetypes):
+  model `sonnet`, plus `manage_root_agent`, `logs` and `metrics` on top of
+  the default permissions.
 - **Wire-protocol** — `hive-core-agent-sock`'s unified `Request` enum
   is the same on both socket flavours. Container lifecycle
   ops (kill/start/restart/rebuild) go through the separate host-admin
@@ -103,8 +106,8 @@ state dirs work as for every other agent.
   both flavours; matrix, bash and forge don't call it — their
   notifications push a todo on the harness's in-agent socket (see
   [`docs/4-implementation/turn-loop/mcp.md`](../turn-loop/mcp.md#waking-the-agent-from-inside-the-container)).
-- **Storage/mounts** — the `manage_root_agent` permission, which the swarm
-  UI's setup assistant creates ruth with, gets a container
+- **Storage/mounts** — the `manage_root_agent` permission, which the
+  [`ruth` archetype](../../2-handbook/swarm/archetypes.md#the-built-in-archetypes) grants, gets a container
   each other agent's `state` dir bind-mounted RW at
   `/agents/<name>/state` (so it can manage any agent's state dir; config
   isn't mounted, since a real config change is a PR from a clone), plus an RO mount for