//! The `fdu` command line, and the engine it is built on.
//!
//! The command line lives here and depends on [`fdu_core`] the way any consumer does, so
//! `crate::` does not reach the engine: anything the command line needs is public API, and
//! the compiler decides that on every build rather than a reviewer deciding it in review.
//!
//! The engine is re-exported, so `cargo add fdu` gives a library caller the whole API and
//! there is one name to know for both installing the tool and depending on it.
/// The repository README's Rust examples, compiled and run as doctests so they cannot
/// drift.
///
/// When nothing compiled them, they kept naming an `AnalysisProfile` type for a release
/// after it was gone. The path reaches the workspace copy. A packaged crate carries only
/// its own directory, so the include fails only when doctests run from an extracted
/// package; its crates.io page is `crates/fdu/README.md`.
;
pub use *;
pub use craterun_process;