pub enum ClientControlRequest {
ServerDescribe {},
CatalogList {
module_id: Option<String>,
},
RouteOpen {
target: RouteTarget,
identity: BindIdentity,
consumer_identity: Option<ConsumerIdentity>,
consumer_capabilities: Option<Vec<String>>,
admission_facts: Option<Value>,
},
RoutePoll {
route_channel: u16,
route_epoch: u32,
kind: PollKind,
},
SupervisorList {},
SupervisorRestart {
module_id: String,
},
SupervisorReload {
module_id: String,
},
SupervisorRescan {
preview: bool,
},
SupervisorSetEnabled {
module_id: String,
enabled: bool,
},
SupervisorHealthProbe {
module_id: String,
},
SupervisorHealth {},
}Expand description
Client-originated channel-0 control RPC body.
Variants§
ServerDescribe
CatalogList
Fields
RouteOpen
Fields
target: RouteTargetidentity: BindIdentityconsumer_identity: Option<ConsumerIdentity>The consumer’s claim to a supervised launch, which the daemon verifies against its live spawn nonces before stamping a principal.
Absent is a legitimate shape, not an omission: a direct key-holder has
no launch nonce to present, and the daemon stamps Direct. So absence
means NO CLAIM WAS MADE, never that a claim was refused — a refused
claim is an error frame and the route never opens. A provider deciding
what to trust reads the stamped principal on the bind, not this.
consumer_capabilities: Option<Vec<String>>Consumer-declared reverse-request capabilities for the route. This is an unverified declaration, not a privilege grant; if a consumer over-declares, providers may still send reverse requests that later time out or deny. Providers must treat an absent field as no reverse-request capability. The vocabulary is open strings; known MCP method-family values today are “elicitation”, “sampling”, and “roots”.
RoutePoll
SupervisorList
SupervisorRestart
SupervisorReload
SupervisorRescan
Fields
preview: boolCompute the reconciliation and return it WITHOUT applying it.
Rescan retires any supervised module absent from the config, which
stops live processes. Both halves of that decision are inspectable in
advance – the config is a file, the running set is supervisor.list
– but nothing reconstructs the diff for the operator, so it is read
from the result table AFTER the retires have happened.
A preview must be computed daemon-side rather than by a client, because a client would have to locate the daemon’s config itself: two rules selecting one subject, agreeing until someone runs a daemon with a non-default config. A preview that can describe a different file than the operation reads is worse than none, because it is believed.
Defaults to false so an existing client sending {} still executes,
and is OMITTED when false so the bytes an existing client sends are
unchanged. Serialising preview:false would have altered the request’s
wire form for every caller that never asked for a preview – caught by
the golden fixture, which is the whole reason that pin exists.
SupervisorSetEnabled
SupervisorHealthProbe
SupervisorHealth
Trait Implementations§
Source§impl Clone for ClientControlRequest
impl Clone for ClientControlRequest
Source§fn clone(&self) -> ClientControlRequest
fn clone(&self) -> ClientControlRequest
1.0.0 (const: unstable) · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more