swarm: present tense + no-queue-coordinates wording

The queue's payload ceiling was justified by what the queue was about to
carry; it carries it now, so the comment says so.

The other two sites say "a hive with no queue configured". The swarm has
exactly one queue and a hive cannot lack it — only its coordinates, its
credential, or its ability to reach it. That wording is already used
everywhere else the absence is named; these two predate it.

The docs section on the agents' queue coordinates stopped at delivering
them and never said what the connection is for. It now names the subject
and the degrade rule, which is the part an operator reading an agent's
terminal at the swarm needs.

Refs #3805

hive-c0re/src/swarm_agent_status.rs

@@ -35,7 +35,7 @@ const FAILURES_BEFORE_BANNER: u32 = 3;
 ///
 /// Shares its connect gate with [`crate::swarm_status::spawn`] — both read
 /// `crate::swarm_queue::client()`, which connects once per process — so a
-/// hive with no queue configured pays for this decision once, not twice.
+/// hive with no queue coordinates pays for this decision once, not twice.
 ///
 /// Takes no `Coordinator` handle, unlike its sibling: this task only reads
 /// agent state that already exists on disk / in the container runtime

hive-c0re/src/swarm_notices.rs

@@ -13,8 +13,8 @@
 //! [`swarm_queue_client::notices`] for the stream this publishes into.
 //!
 //! **Best-effort, never fatal to the caller.** A hive with no queue
-//! configured is a silent no-op (the ordinary case). A hive whose queue
-//! is unreachable loses the swarm's visibility of the notice, not the
+//! coordinates is a silent no-op (the ordinary case). A hive that cannot
+//! reach the queue loses the swarm's visibility of the notice, not the
 //! host's — `warn!` fires on every failed attempt regardless, and the
 //! dashboard banners only after [`FAILURES_BEFORE_BANNER`] consecutive
 //! misses, the same debounce shape [`crate::swarm_status`] uses and for