mermaid_cli/runtime_client/mod.rs
1//! Client side of the daemon protocol.
2//!
3//! `RuntimeClient` talks to a running `mermaidd` over its control socket, and
4//! falls back to opening the SQLite store directly when no daemon is up.
5//! `DaemonRequest` is the typed wire contract both sides share.
6//!
7//! Named `runtime_client`, not `runtime`. The old name collided with the
8//! `mermaid-runtime` crate it sits above, and the module was mostly a
9//! `pub use mermaid_runtime::*` glob — so `crate::runtime::Foo` might be a
10//! local type or a re-exported one, with nothing at the call site to say
11//! which. `src/providers/tool/workspace.rs` had a doc comment saying
12//! `mermaid_runtime::worktree` directly above code saying
13//! `crate::runtime::worktree`, which is what that ambiguity costs. The glob is
14//! gone; everything below the boundary is spelled `mermaid_runtime::`.
15
16pub mod client;
17pub mod protocol;
18
19pub use client::*;
20pub use protocol::DaemonRequest;