hive-c0re: fix stale GetLooseEnds example in dispatch_shared doc comment
The parenthetical claimed the manager can target other agents via GetLooseEnds — true before 65481273, false since. It was the only socket-specific example that comment ever had, so rewrite the sentence to name what dispatch_shared actually defers: ListDescendants and the orchestration verbs, which need per-verb tool-group gating, plus host-admin/unknown requests.
This commit is contained in:
parent
07ec63cc3f
commit
f7843d727d
1 changed files with 4 additions and 3 deletions
|
|
@ -180,9 +180,10 @@ pub(crate) fn recv_timeout(wait_seconds: Option<u64>) -> std::time::Duration {
|
|||
|
||||
/// Handle the subset of `Request` variants that are identical on both
|
||||
/// the agent socket and the manager socket. Returns `Some(response)` for
|
||||
/// every variant it handles; returns `None` for variants with socket-specific
|
||||
/// semantics (e.g. `GetLooseEnds`, where the manager can target other
|
||||
/// agents) or for manager-only variants.
|
||||
/// every variant it handles; returns `None` for the remaining variants —
|
||||
/// `ListDescendants` and the orchestration verbs (schedules / meta-inputs),
|
||||
/// which need per-verb tool-group gating — or for host-admin / unknown
|
||||
/// requests invalid on either socket.
|
||||
///
|
||||
/// The unified `dispatch` calls this first; the remaining arms (which gate
|
||||
/// on topology / capabilities / tool-groups) are handled there.
|
||||
|
|
|
|||
Loading…
Reference in a new issue