//! `tauri-plugin-phyto` is split into two feature-gated halves:
//!
//! - **`runtime`** (default) — the actual Tauri plugin: HTTP automation
//! server, IPC commands, [`init`], [`PhytoConfig`], [`PROTOCOL_VERSION`].
//! This is what consumers wire into their Tauri builder.
//! - **`build`** — `std`-only helpers for consumer build scripts. The single
//! entry point [`build::sync_capability`] creates / removes the Phyto
//! capability JSON so `tauri-build` doesn't reject capabilities that
//! reference an unregistered plugin when the `e2e` feature is off. Enable
//! from `[build-dependencies]` with `default-features = false,
//! features = ["build"]` to keep the host compile graph small.
pub use *;