[Bug]: error[E0463]: can't find crate for `core`

(base) ➜ sdfs sdf run
Loading dataflow... - Building package: None
Loading dataflow... / Compiling cfg-if v1.0.0
Compiling zerocopy v0.7.35
Compiling ryu v1.0.20
Compiling once_cell v1.21.1
Compiling itoa v1.0.15
Compiling serde v1.0.219
Compiling memchr v2.7.4
Compiling allocator-api2 v0.2.21
Compiling bitflags v2.9.0
Compiling num-traits v0.2.19
Compiling tinystr v0.7.6
Compiling icu_collections v1.5.0
Compiling wit-bindgen-core v0.39.0
Compiling anyhow v1.0.97
Compiling sdf-parser-core v0.12.0
Compiling wasi v0.11.0+wasi-snapshot-preview1
error[E0463]: can't find crate for `core`
|
= note: the `wasm32-wasip2` target may not be installed
= help: consider downloading the target with `rustup target add wasm32-wasip2`

For more information about this error, try `rustc --explain E0463`.
error: could not compile `cfg-if` (lib) due to 1 previous error
warning: build failed, waiting for other jobs to finish...
error: could not compile `itoa` (lib) due to 1 previous error
error: could not compile `ryu` (lib) due to 1 previous error
error: could not compile `once_cell` (lib) due to 1 previous error
error: could not compile `bitflags` (lib) due to 1 previous error
error: could not compile `allocator-api2` (lib) due to 1 previous error
error: could not compile `num-traits` (lib) due to 1 previous error
error: could not compile `zerocopy` (lib) due to 1 previous error
error: could not compile `memchr` (lib) due to 1 previous error
error: could not compile `anyhow` (lib) due to 1 previous error
error[E0463]: can't find crate for `std`
|
= note: the `wasm32-wasip2` target may not be installed
= help: consider downloading the target with `rustup target add wasm32-wasip2`

error: could not compile `wasi` (lib) due to 1 previous error
error: could not compile `serde` (lib) due to 1 previous error

Build failed: Build failure
Build failed

macos Apple M4 Max

Start by reproducing `sdf run` on the reported macOS Apple M4 Max environment and inspect the build's `wasm32-wasip2` target setup. The error output suggests checking whether that target is available to Rust; done means the example builds without the reported missing `core` and `std` errors.

Written by the indexing model from the issue text.