meerkat: Skill for Claude Code

Meerkat WASM Embedded Runtime

The meerkat-web-runtime crate compiles the full meerkat agent stack to wasm32-unknown-unknown. It is an embedded deployment target for mobpacks — the JavaScript equivalent of the Rust SDK. Not a protocol server like RPC/REST.

The crate is not published to crates.io (publish = false); browser hosts consume it as the prebuilt WASM inside @rkat/web.

Crate Compatibility Pattern

To make a meerkat crate compile for wasm32, apply this pattern:

Cargo.toml — gate platform-specific deps:

[target.'cfg(not(target_arch = "wasm32"))'.dependencies]
tokio = { workspace = true }
rusqlite = { workspace = true }

[target.'cfg(target_arch = "wasm32")'.dependencies]
tokio_with_wasm = { workspace = true }

lib.rs - tokio alias + module gating:

#[cfg(target_arch = "wasm32")]
pub mod tokio {
    pub use meerkat_core::time_compat::wasm as time;
    pub use meerkat_core::tokio::spawn;
    pub use meerkat_core::tokio::task;
    pub use tokio_with_wasm::alias::*;
}

#[cfg(not(target_arch = "wasm32"))]
mod filesystem_module;

async_trait — dual cfg_attr:

#[cfg_attr(target_arch = "wasm32", async_trait(?Send))]
#[cfg_attr(not(target_arch = "wasm32"), async_trait)]

Time types — use meerkat_core::time_compat::{SystemTime, Instant, Duration}, never std::time::*.

Tokio imports in wasm32-visible code — add #[cfg(target_arch = "wasm32")] use crate::tokio; then existing use tokio::... paths resolve through the alias.

Use the shared core alias for WASM scheduling. Its time adapter owns the exact JavaScript timer handle and cancels it when the Rust future is dropped. Direct tokio_with_wasm::alias::time calls bypass that cleanup. The shared task alias also implements yield_now through the same cancellable timer. Its spawn and task::JoinSet box every future before handing it to tokio_with_wasm, which keeps spawn-wrapper shadow-stack frames small; route spawns through the alias, not tokio_with_wasm::spawn. The SDK's release build fails when a spawn-wrapper frame exceeds 8 KiB (sdks/web/scripts/wasm-frames.mjs). Native code continues to use Tokio. Lifecycle tests must exit naturally after teardown; forcing a successful Node exit hides retained timer resources.