say per-agent socket where the manager socket is gone

the manager socket no longer exists; ruth's socket is the per-agent one. Fixes the wire-type crate docs, hive-sh4re manager.rs header and README, and two other mentions.

docs/turn-loop/README.md

@@ -98,7 +98,7 @@ variants regardless of who sends them):
 
 A small `Surface` trait, with one zero-sized impl, factors
 `hive-agent`'s wire types (`hive_core_agent_sock::{Request, Response}` —
-one unified enum shared by the agent and manager sockets) and its turn
+one unified enum shared by every agent socket) and its turn
 loop, so the loop itself has no per-role branches. See
 `hive-agent/src/main.rs`'s module
 doc for the trait shape.

hive-agent/src/web_ui/state.rs

@@ -394,7 +394,7 @@ struct ExtraLink {
 }
 
 /// Best-effort: pull the last 30 messages addressed to us via the
-/// per-agent / manager socket. Empty list on any transport / decode
+/// per-agent socket. Empty list on any transport / decode
 /// failure — the inbox section is decorative, not authoritative.
 async fn recent_inbox(socket: &std::path::Path) -> Vec<hive_sh4re::inbox::InboxRow> {
     const LIMIT: u64 = 30;

hive-core-agent-sock/README.md

@@ -1,8 +1,8 @@
 # hive-core-agent-sock
 
-Wire types for the **per-agent + manager socket** (`/run/hive/mcp.sock`) — the
+Wire types for the **per-agent socket** (`/run/hive/mcp.sock`) — the
 unified `Request` / `Response` protocol spoken between an agent's in-container
-harness (and the manager) and the `hive-c0re` daemon.
+harness and the `hive-c0re` daemon.
 
 ## Why it's its own crate
 

hive-core-agent-sock/src/lib.rs

@@ -1,7 +1,7 @@
-//! Per-agent + manager socket wire types (`/run/hive/mcp.sock`).
+//! Per-agent socket wire types (`/run/hive/mcp.sock`).
 //!
 //! The unified `Request` / `Response` protocol spoken between an agent's
-//! in-container harness (and the manager) and the `hive-c0re` daemon over the
+//! in-container harness and the `hive-c0re` daemon over the
 //! per-agent mcp socket. Re-homed out of `hive-sh4re` so this one socket owns
 //! its own protocol crate, mirroring `hive-host-sock` / `hive-priv-sock`. The
 //! shared payload types it references (`Message`, `LooseEnd`, …)
@@ -17,7 +17,7 @@ fn default_true() -> bool {
     true
 }
 
-/// Unified request enum for both agent and manager sockets. The agent's
+/// Unified request enum for the per-agent socket. The agent's
 /// identity is the socket it arrived on.
 #[derive(Debug, Clone, Serialize, Deserialize)]
 #[serde(tag = "cmd", rename_all = "snake_case")]
@@ -59,9 +59,7 @@ pub enum Request {
     /// Non-mutating — pulls from the broker without delivering. The
     /// per-agent web UI uses this to render its own inbox section.
     Recent { limit: u64 },
-    /// Loose-ends view — always the caller's own. Same shape on the agent
-    /// and manager sockets; the manager (`ruth`) is a normal agent here, it
-    /// just sees its own threads like anyone else. See
+    /// Loose-ends view — always the caller's own. See
     /// `docs/process/conventions.md::Loose-ends wire shape`.
     GetLooseEnds,
     /// Set a free-text status string visible on the dashboard. The harness
@@ -106,7 +104,7 @@ pub enum Request {
     PauseAcknowledged,
 }
 
-/// Unified response enum for both agent and manager sockets.
+/// Unified response enum for the per-agent socket.
 #[derive(Debug, Clone, Serialize, Deserialize)]
 #[serde(tag = "kind", rename_all = "snake_case")]
 pub enum Response {

hive-sh4re/README.md

@@ -13,7 +13,7 @@ split into their own smaller crates so specialised binaries don't have to pull
 in all of `hive-sh4re`:
 
 - `hive-host-sock` — host admin socket (`hivectl` ↔ `hive-c0re`)
-- `hive-core-agent-sock` — per-agent/manager socket (`/run/hive/mcp.sock`)
+- `hive-core-agent-sock` — per-agent socket (`/run/hive/mcp.sock`)
 - `hive-priv-sock` — the privileged-helper socket
 
 Those crates re-export or reference the payload types that still live here

hive-sh4re/src/manager.rs

@@ -1,5 +1,3 @@
-//! Manager socket — `/run/hyperhive/manager/mcp.sock` on the host,
-//! bind-mounted into the manager container at `/run/hive/mcp.sock`.
 //! Reserved recipient names/senders and the out-of-band `HelperEvent`
 //! payload hive-c0re pushes into the manager's inbox.