Replace em dashes with hyphens across docs and comments

src/printer/bambu_commands/mod.rs

@@ -1,21 +1,21 @@
-//! Bambu's raw MQTT command/report structs — plain hand-written Rust +
+//! Bambu's raw MQTT command/report structs - plain hand-written Rust +
 //! serde, no protobuf. This data only ever needs to be understood by this
 //! crate (raw vendor wire format, never crosses into TypeScript), and the
-//! actual wire format is JSON over MQTT, not binary protobuf — protobuf's
+//! actual wire format is JSON over MQTT, not binary protobuf - protobuf's
 //! codegen tooling kept fighting us for a payoff (cross-language codegen,
 //! binary wire efficiency) that doesn't apply here at all. Proto stays in
 //! continuum-schemas for continuum.v1, which is a schema we designed
 //! ourselves and that both TS and Rust genuinely need.
 //!
 //! One file per Bambu *category* (`get_version.rs` for "info", `pushall.rs`
-//! + `print.rs` for "pushing"/"print" — see below for why those are two
+//! + `print.rs` for "pushing"/"print" - see below for why those are two
 //! files, not one). Copy `get_version.rs`'s shape for your next command.
 //!
-//! Mirrors continuum-schemas' `schemas/bambulab/` JSON Schemas — same
+//! Mirrors continuum-schemas' `schemas/bambulab/` JSON Schemas - same
 //! category split, same "print vs pushing" correction (see that
 //! directory's README for the full explanation): a `pushall` *request*
 //! goes to the "pushing" key, but the ongoing state-push stream it
-//! triggers arrives under a different key, "print" — so `PushallRequest`
+//! triggers arrives under a different key, "print" - so `PushallRequest`
 //! lives in `pushall.rs` and the thing it triggers, `PrintReport`, gets
 //! its own file, `print.rs`, rather than living together as if one were
 //! simply "the response to" the other.
@@ -29,10 +29,10 @@ pub use print::{AmsState, AmsTray, AmsUnit, EmptyTray, LoadedTray, PrintReport,
 pub use pushall::PushallRequest;
 
 /// Fields every Bambu command/response shares. This is the "inheritance"
-/// replacement for these structs — composition, not extension: every
+/// replacement for these structs - composition, not extension: every
 /// command below *has* one of these, embedded via `#[serde(flatten)]`
 /// (which unwraps it onto the parent object at serialize/deserialize
-/// time, so the JSON stays flat — no extra nesting), rather than
+/// time, so the JSON stays flat - no extra nesting), rather than
 /// *extending* a base class. Exactly the same idea as `BambuGenericPrinter`
 /// in `../bambu.rs`, just expressed with a struct field instead of a
 /// struct-holding-a-struct in `impl` blocks.
@@ -44,9 +44,9 @@ pub struct CommandEnvelope {
 
 /// One request you can send to a Bambu printer, keyed by Bambu's top-level
 /// JSON category ("info", "pushing", ...). NOTE: that top-level key is a
-/// *category*, not the specific command — `CommandEnvelope::command` is
+/// *category*, not the specific command - `CommandEnvelope::command` is
 /// what actually says which one ("get_version", "pushall", ...). A
-/// category can have more than one possible request shape — if that ever
+/// category can have more than one possible request shape - if that ever
 /// happens here, that variant's payload becomes its own small
 /// `#[serde(tag = "command")]` enum instead of a single struct.
 #[derive(serde::Serialize, Debug)]
@@ -56,7 +56,7 @@ pub enum BambuRequest {
     Pushing(PushallRequest),
 }
 
-/// Same idea, the response direction — note "print", not "pushing" (see
+/// Same idea, the response direction - note "print", not "pushing" (see
 /// this module's doc comment).
 #[derive(serde::Deserialize, Debug)]
 #[serde(rename_all = "snake_case")]