feat: add the taskito facade crate

[kartikeya-27]

Claims taskito on crates.io, the one name in the set still unregistered. Rust
was the only SDK without it — pip install taskito, npm i @byteveda/taskito
and org.byteveda:taskito all exist, while a Rust user had to know to reach for
taskito-core. Now cargo add taskito works.

What it is

crates/taskito is a re-export and nothing else:

pub use taskito_core::*;
pub use taskito_core;

taskito::Worker and taskito_core::Worker are the same type, so the two crates
mix freely in one dependency graph and either name compiles. There is one
definition and one set of docs; anything added to the core root appears here with
no edit. The three features forward verbatim, so cargo add taskito --features postgres behaves exactly as the same flag on core.

Renaming taskito-core was the alternative and is no longer available — it is
public at 0.22.0, and taking the name that way would break every existing
dependant. A re-export gets the name without that.

This is deliberately not a placeholder. crates.io's name policy discourages
content-free reservations, and the crate ships a real re-export, a README whose
quick-start is compiled as a doctest, and the same LICENSE as its siblings.

Release wiring

taskito joins the crate set in three places: the publish-crates.yml upload
list, the publish-readiness set in ci-rust.yml, and the binding-free tripwire
that keeps pyo3/napi/jni out of the generic crates. It also gets its own semver
gate, guarded like the others on a crates.io baseline existing.

Before the next release — bootstrap needed

taskito does not exist on crates.io yet, so it has no trusted publisher, and
#630 removed the workflow's token path. A dispatch of Publish to crates.io will
fail until taskito has been published once by hand, and it will fail the whole
run, not just that crate.

Sequence:

1. cargo publish -p taskito locally, with a crates.io token
2. configure the trusted publisher on the new crate — ByteVeda/taskito,
   publish-crates.yml, environment crates.io — to match the other three
3. enable Require trusted publishing for all new versions

After that the workflow owns it like the rest, and re-runs skip it as already
published.

Verification

• cargo test -p taskito --doc — the README quick-start compiles, which is what
  proves the re-export actually carries the names it uses
• cargo package --locked -p taskito -p taskito-core -p taskito-workflows -p taskito-mesh
  — all four package and verify against each other; the taskito tarball carries
  README, LICENSE, src/lib.rs
• cargo check -p taskito --all-features — clean
• cargo clippy --workspace --all-targets --features workflows — zero warnings
• node scripts/version.mjs --check — all manifests agree on 0.22.0; the facade
  inherits version.workspace, so it needs no new mirror
• actionlint — both workflows clean

[coderabbitai]

Warning

Review limit reached

@kartikeya-27, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 47 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: ea1d6ea9-116f-4af9-8bbb-b204e89cdc45

📥 Commits

Reviewing files that changed from the base of the PR and between 3620e83 and 0bd3e1c.

⛔ Files ignored due to path filters (1)

• Cargo.lock is excluded by !**/*.lock

📒 Files selected for processing (7)

• .github/workflows/ci-rust.yml
• .github/workflows/publish-crates.yml
• Cargo.toml
• crates/taskito/Cargo.toml
• crates/taskito/LICENSE
• crates/taskito/README.md
• crates/taskito/src/lib.rs

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}