hive-c0re: the port range is every agent's, not the sub-agents'

Two more statements of the claim the previous commit removed: the
snapshot field called the clusters "sub-agents", and WEB_PORT_BASE's own
doc called the range sub-agent-only while the function that reads it
says "every agent including the manager" three lines below.

docs/process/gotchas.md already had this right.

hive-c0re/src/dashboard/state_snapshot.rs

@@ -56,9 +56,9 @@ pub(super) struct StateSnapshot {
     /// survive after a destroy-without-purge. The operator can re-spawn
     /// with the same name to resume, or PURG3 to wipe them.
     tombstones: Vec<TombstoneView>,
-    /// Sub-agents whose FNV-1a hashed web UI port collides with at
-    /// least one other agent. Operator resolves by renaming. The
-    /// dashboard renders a banner at the top listing each cluster.
+    /// Agents whose FNV-1a hashed web UI port collides with at least
+    /// one other. Operator resolves by renaming. The dashboard renders
+    /// a banner at the top listing each cluster.
     port_conflicts: Vec<PortConflict>,
     /// Inputs in `meta/flake.lock` the operator can selectively
     /// `nix flake update`. Hyperhive first, then `agent-<n>` rows.

hive-c0re/src/lifecycle/mod.rs

@@ -61,9 +61,9 @@ pub fn container_claude_mount(name: &str) -> String {
 /// willing to lose (other agents may delete them).
 pub const CONTAINER_SHARED_MOUNT: &str = "/shared";
 
-/// Sub-agent web UI port range. Deterministic from the agent's name (FNV-1a
-/// hash mod range size), so the dashboard can compute the same port without
-/// asking hive-c0re.
+/// Web UI port range, shared by every agent including the manager.
+/// Deterministic from the agent's name (FNV-1a hash mod range size), so the
+/// dashboard can compute the same port without asking hive-c0re.
 const WEB_PORT_BASE: u16 = 8100;
 const WEB_PORT_RANGE: u16 = 900;