Function handle_muxspect_conversations 

pub async fn handle_muxspect_conversations(
    __arg0: State<AppState>,
) -> impl IntoResponse

GET /api/v1/muxspect/conversations — a single-call, all-tier glance at every agent’s most recent activity, so an agent (or a human via muxspect conversations) doesn’t have to compose DiscoverAgents + N×GetAgentTranscript calls by hand. See docs/specs/SPEC_MUXSPECT_CROSS_TIER_CONVERSATION_VISIBILITY_2026_08_21.md Phase A.

Host and cross-channel entries carry a last_message_preview (the tail non-blank transcript line) and turn_active, read directly for host (this instance’s own mstore/filestore) and via a single best-effort forwarded HTTP call per channel for cross-channel (same auth/loopback pattern handle_reactive_inject’s Tier 2b and this instance’s own handle_muxspect_verify_sender already use — see those for the security rationale; not repeated here). LAN and WAN entries carry no preview (remote_fetch_required: true) — Phase A deliberately does not invent a remote-read protocol for those tiers; see the spec’s Phase B/C.

Always 200 — an empty agents list is a legitimate result, not an error, matching every other handler in this file.