chore(publish): enable crates.io publishing for host, shell, and shell-core

These three crates were added after the 0.3.x release cycle with
publish = false while their APIs stabilized. They are now required
transitive dependencies of the published taskers app crate, so they
must be publishable for cargo install to resolve correctly.

Also adds taskers-core, taskers-shell-core, taskers-host, and
taskers-shell to the documented publish order in docs/release.md.

Constraint: crates.io requires all non-optional path deps to be published
Confidence: high
Scope-risk: narrow
Tested: cargo publish --dry-run -p taskers-domain, taskers-paths (leaf crates)
Not-tested: full sequential publish of all 11 crates

Author: OneNoted

crates/taskers-host/Cargo.toml

@@ -7,7 +7,6 @@ license.workspace = true
 readme = "../../README.md"
 repository.workspace = true
 version.workspace = true
-publish = false
 
 [dependencies]
 anyhow.workspace = true

crates/taskers-shell-core/Cargo.toml

@@ -7,7 +7,6 @@ license.workspace = true
 readme = "../../README.md"
 repository.workspace = true
 version.workspace = true
-publish = false
 
 [dependencies]
 parking_lot.workspace = true

crates/taskers-shell/Cargo.toml

@@ -7,7 +7,6 @@ license.workspace = true
 readme = "../../README.md"
 repository.workspace = true
 version.workspace = true
-publish = false
 
 [dependencies]
 dioxus.workspace = true

docs/release.md

@@ -80,7 +80,11 @@ cargo publish -p taskers-paths
 cargo publish -p taskers-control
 cargo publish -p taskers-runtime
 cargo publish -p taskers-ghostty
+cargo publish -p taskers-core
+cargo publish -p taskers-shell-core
 cargo publish -p taskers-cli
+cargo publish -p taskers-host
+cargo publish -p taskers-shell
 cargo publish -p taskers
 ```