Worker lifecycle
Initialize a Rust WASI template, deploy a source folder or compiled WebAssembly file, invoke the worker, list deployed workers, and delete obsolete versions.
Routes and arguments
Each worker has a project-scoped name and route. Invocation arguments follow -- so they are not interpreted as CLI options.
Build requirements
Source deployments require a Rust toolchain capable of producing the configured WASI target. Precompiled .wasm files skip the local build.