Module muxbus_handlers

Expand description

MuxBus cloud connectivity RPC handlers.

Five commands:

muxbus.login — PKCE browser flow (blocks until complete or timeout)
muxbus.login.cancel — abort an in-flight muxbus.login (e.g. user closed the browser)
muxbus.status — current credential status
muxbus.disconnect — clear stored credentials
muxbus.cloudconfig — the cloud settings srv resolved, and where they came from

Structs§

MuxBusCloudConfigReq: Empty request for muxbus.cloudconfig: a struct rather than () so the stub’s {} deserializes, like the request shapes above.
MuxBusCloudConfigResp: Result of muxbus.cloudconfig: the AgentMux Cloud settings srv resolved (SPEC_CLOUD_SETTINGS_DISCOVERY_2026_09_27.md §3.2). A build compiled without a Cognito client id asks this whether sign-in is possible anyway.
MuxBusDisconnectReq
MuxBusDisconnectResp: Result of muxbus.disconnect. Was an inline json!({}); the stub already typed it Record<string, never>, which is exactly what an empty struct generates.
MuxBusLoginCancelReq: Empty request shapes for muxbus.login.cancel, muxbus.status and muxbus.disconnect. The handlers ignore their payload, but these must be structs rather than (): the stub calls all three with {}, and serde deserializes () only from JSON null, so a unit Req would reject every real call at runtime while compiling and passing every CI gate – the bookmarks.list bug.
MuxBusLoginCancelResp
MuxBusLoginReq
MuxBusLoginResp
MuxBusStatusReq
MuxBusStatusResp

clear_wan_peer_cache 🔒: W3-S (SPEC_WAN_JEKT_VERIFICATION_2026_09_24.md §2.3): cached peer records belong to the account they were fetched under. Best-effort — the records are self-certifying, so a stale one can’t verify a forgery; this only keeps one account’s directory from answering for another’s.
cloud_config 🔒: What muxbus.cloudconfig reports for a discovery result.
register_muxbus_handlers