mesofact-dev 0.8.29

Dev-tier affordances for mesofact workloads — a rebuild-on-change watcher, a local S3 surface standing in for R2, and `mesofact_dev::serve_app`, the dev half of a library-tier project's two bin targets. The serving engine lives in the `mesofact` facade; this crate must never be in a prod binary's dependency closure (W225 §2).
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19

//! `mesofact-dev` — the previous name for the `mes` binary, byte-identical in
//! behaviour and kept only so existing callers keep working.
//!
//! It stays because the old name is load-bearing outside this workspace: ~30
//! spawn sites in the parent yah camp (kamaji, desktop, `cli/serve_build.rs`,
//! `xtask/install.rs`, `local.sh`) exec it by name, and `yah-mesofact-store`
//! hardcodes it in both `EXPECTED_BINS` and `SHIM_NAMES` — so dropping it
//! would make every installed version slot report
//! `Incomplete { missing: ["mesofact-dev"] }`.
//!
//! The legacy `mesofact-dev <DIR> --port N …` invocation still parses, as the
//! CLI's bare form (see [`mesofact_dev::cli`], and the
//! `legacy_mesofact_dev_invocation_still_parses` test that holds it). Delete
//! this target once those callers say `mes`.

#[tokio::main]
async fn main() -> std::process::ExitCode {
    mesofact_dev::cli::run().await
}