zenkey_fleet/lib.rs
1//! Fleet engine for keyspace-v2 tooling (issue #15).
2//!
3//! The shared core of `zenctl` and `zengui`: everything a bus explorer needs
4//! that is not presentation. The RFC 05 §2.1 fan-in discipline lives in
5//! exactly one place ([`query::fleet_get`], moved verbatim from zenctl —
6//! target `All`, consolidation `None`, attribution by the reply's own key);
7//! the liveliness roster, registry-slice sets, and the schema-aware decode
8//! seam build on it.
9//!
10//! Sessions opened here are deliberately **un-namespaced** (RFC 09 §5): an
11//! explorer sees the wire as it really is, full keys included — that is what
12//! lets it spot a leak. Do not "fix" this by setting a namespace.
13
14pub mod admin;
15pub mod query;
16pub mod registry;
17pub mod roster;
18pub mod session;
19pub mod stats;
20pub mod sub;
21pub mod tree;
22
23#[cfg(feature = "decode")]
24pub mod decode;
25
26pub use admin::{AdminEntry, RouterInfo, admin_get, routers};
27pub use query::{Answer, FleetAnswer, fleet_get, fleet_registry};
28pub use registry::SliceSet;
29pub use roster::roster;
30pub use session::open;
31pub use sub::{EventStream, FleetEvent, Monitor, MonitorCore, MonitorSpec, SampleView, StreamItem};
32pub use tree::KeyTreeSnapshot;