fix: mark muxy transport and binary as unpublishable to crates.io

shellflow-muxy depends on muxy-client/muxy-protocol, git-only beta
crates (pinned by rev) that are absent from crates.io, so it cannot be
published. bin/shellflow's default muxy feature pulls it in, so the
binary is likewise unpublishable. cargo publish --workspace failed on
shellflow-muxy; marking both publish = false lets the four library
crates publish cleanly.

Author: Akagi201

bin/shellflow/Cargo.toml

@@ -9,6 +9,10 @@ authors.workspace = true
 keywords.workspace = true
 categories.workspace = true
 readme.workspace = true
+# Not publishable: its default `muxy` feature pulls in `shellflow-muxy`, which
+# depends on git-only beta crates absent from crates.io. The binary is a
+# build-from-source product; the library crates below are the published artifacts.
+publish = false
 
 [features]
 # Event-driven systemd unit state (D-Bus). Off by default so the standard

crates/shellflow-muxy/Cargo.toml

@@ -9,6 +9,10 @@ authors.workspace = true
 keywords.workspace = true
 categories.workspace = true
 readme.workspace = true
+# Not publishable: it depends on `muxy-client`/`muxy-protocol`, which are
+# git-only beta crates (pinned by rev) and are absent from crates.io. Only the
+# `bin/shellflow` binary consumes it, through the optional `muxy` feature.
+publish = false
 
 [dependencies]
 muxy-client = { workspace = true }