crates: the four libraries are not published

hanzo-config, hanzo-kai, hanzo-loop and hanzo-tui keep 0.0.0, and each
says why beside it: upstream crates depend on them, so a version that
moved would recompile everything above them. None is a crate anyone
installs from a registry, so `publish = false`.

crates/hanzo-config/Cargo.toml

@@ -1,6 +1,9 @@
 [package]
 name = "hanzo-config"
+# Never the release's version: upstream crates depend on this one, and a version
+# that moved would recompile everything above them. Not published.
 version = "0.0.0"
+publish = false
 edition = "2021"
 license = "Apache-2.0"
 description = "Hanzo Dev config integration"

crates/hanzo-kai/Cargo.toml

@@ -1,6 +1,9 @@
 [package]
 name = "hanzo-kai"
+# Never the release's version: upstream crates depend on this one, and a version
+# that moved would recompile everything above them. Not published.
 version = "0.0.0"
+publish = false
 edition.workspace = true
 license.workspace = true
 description = "Kai in the Dev loop over the Decisions API: decisions per turn, their trace, and flows."

crates/hanzo-loop/Cargo.toml

@@ -1,6 +1,9 @@
 [package]
 name = "hanzo-loop"
+# Never the release's version: upstream crates depend on this one, and a version
+# that moved would recompile everything above them. Not published.
 version = "0.0.0"
+publish = false
 edition.workspace = true
 license.workspace = true
 description = "What a controller decides inside the agent loop, as data the loop applies."

crates/hanzo-tui/Cargo.toml

@@ -1,6 +1,9 @@
 [package]
 name = "hanzo-tui"
+# Never the release's version: upstream crates depend on this one, and a version
+# that moved would recompile everything above them. Not published.
 version = "0.0.0"
+publish = false
 edition = "2021"
 license = "Apache-2.0"
 description = "Hanzo Dev tui integration"