docs, hive-c0re: retire prose describing the removed get_loose_ends target

Follow-up to 729c5b4f42, which dropped the
`agent` parameter from get_loose_ends and deleted Capability::QueryAgentState
with it. Three prose sites still describe the interface that commit removed:

- socket_server/mod.rs's module doc claimed authority on this socket derives
  from "capabilities for the hive-wide queries and tool-group membership for
  the orchestration verbs". There are no capability-gated queries left —
  `git grep -n has_cap -- hive-c0re/src/socket_server/` returns nothing, and
  require_group("scheduling") is the only gate in dispatch_orchestration.
- agent-hierarchy.md listed loose-ends visibility ("manager sees hive-wide,
  sub-agents only their own") as one of the manager-only overrides that
  "exist across hive-c0re today". It doesn't, and the sentence pointed a
  reader at loose_ends.rs for owner-check logic that is no longer there.
- conventions.md's Loose-ends wire shape still spoke of "the agent-flavour
  and manager-flavour requests" and "the agent-flavour list". There is one
  request shape.

No behaviour change: prose only.

Refs #4480

docs/agent-lifecycle/agent-hierarchy.md

@@ -132,15 +132,17 @@ Manager}` switch picks the MCP tool allow-list claude sees. Both are
   container including the manager, so all token/state paths resolve
   through it the same way everywhere.
 - **Scattered ownership checks** — a handful of independent
-manager-only overrides exist across `hive-c0re` today: loose-ends
-visibility (manager sees hive-wide, sub-agents only their own),
-`destroy` refusing to act on the manager, and crash-watch skipping
+manager-only overrides exist across `hive-c0re` today: `destroy`
+refusing to act on the manager, and crash-watch skipping
 the manager (it autorestarts via systemd instead of going through
 the crash-watch loop). Each is planned to become a capability
 check instead of a manager-name check — see the
-module docs for `loose_ends.rs`, `stores/broker.rs`, `actions.rs`,
+module docs for `stores/broker.rs`, `actions.rs`,
 and `workers/crash_watch.rs` for the current owner-check logic in
-each. (The harness handles reminder cancellation fully in-agent — see
+each. Loose-ends visibility used to be on this list; it isn't a
+manager override any more — `GetLooseEnds` takes no target and every
+agent, `ruth` included, sees only its own rows.
+(The harness handles reminder cancellation fully in-agent — see
 the note on `CancelLooseEndKind::Reminder` in
 `hive-c0re/src/socket_server/mod.rs`.)
 <!-- vale write-good.Passive = YES -->

docs/process/conventions.md

@@ -165,8 +165,8 @@ the dashboard's "mark all read" (unbounded, per-agent).
 
 ### Loose-ends wire shape
 
-`LooseEnd` is the per-row response shape for `GetLooseEnds` (both
-the agent-flavour and manager-flavour requests). Tagged enum so
+`LooseEnd` is the per-row response shape for `GetLooseEnds` — one
+request shape, no per-socket flavours. Tagged enum so
 new thread kinds (forge PRs, long-running approvals from a
 privileged bot, etc.) can land later without breaking existing
 handlers. Each row carries enough context that the caller renders
@@ -194,7 +194,7 @@ Per-variant fields:
 - `PendingMessages { count }` — undelivered inbox messages the
   agent still owes itself a `recv` for. Informational + not
   cancellable (drain with `recv`); only emitted when `count > 0`,
-  and surfaced first in the agent-flavour list as the most
+  and surfaced first in the list as the most
   actionable signal. Counted host-side from the broker
   (`count_pending`), so it reflects what's genuinely still queued —
   the wake-message that drove the current turn is already delivered

hive-c0re/src/socket_server/mod.rs

@@ -4,8 +4,9 @@
 //! you are `foo`; the manager socket simply serves as `ruth`. There is no
 //! privilege flag — both transports run the same [`serve`] / [`dispatch`]
 //! code, and authority derives uniformly from the caller's identity:
-//! capabilities for the hive-wide queries and tool-group membership for the
-//! orchestration verbs. An agent-targeting verb may name any agent, so `ruth`
+//! tool-group membership for the orchestration verbs, and nothing else —
+//! the queries are all self-scoped, so no capability is consulted here at
+//! all. An agent-targeting verb may name any agent, so `ruth`
 //! reaches every agent exactly the way every other agent does, not via any
 //! hardcoded name match.