//! Subprocess plugin protocol + host runtime for MLF plugins. //! //! See [`protocol`] for the message shape (line-delimited JSON over //! stdin/stdout). [`host`] spawns a plugin binary and drives it through //! ops, including multi-turn `ask`/`answer` flows. [`ui`] defines the //! handler trait the host uses to service non-terminal `ask` messages //! (terminal prompts, browser-open requests, etc.). [`plugin`] is the //! small helper plugin authors can import to read ops and reply on the //! other side of the pipe. //! //! The protocol is shared across plugin kinds (DNS providers today, //! codegen later); per-kind ops live on top of the generic //! `hello` / `init` / multi-turn RPC envelope. pub mod discovery; pub mod host; pub mod plugin; pub mod protocol; pub mod ui; pub use host::{HostError, PluginHandle}; pub use protocol::{ Ack, Answer, Ask, AskKind, CapabilityMissing, Credentials, Hello, HelloData, OptionField, Request, Response, Terminal, }; pub use ui::{DenyInteractiveUi, TerminalUi, UiHandler, UiMessage};