@ai-ecoverse/wasi-cargo

Cargo 0.99 (Rust 1.98.1) for SLICC's WASI realm. It uses the installed @ai-ecoverse/wasi-rustc driver and targets wasm32-wasip1.

• Registry access. crates.io dependencies come through the realm's HTTP proxy, the one https_proxy names, over the sparse index. The proxy does TLS, so Cargo needs none. Index files and crates are fetched over 6 connections at once (CARGO_HTTP_MAX_CONNECTIONS changes the count). Without a proxy, use --offline with vendored or path dependencies.
• Proc macros. Derives such as serde, clap and thiserror need wasi-rustc 1.98.1-1 or later, which runs proc macros as child processes.
• cargo test builds and runs unit and integration tests with wasi-rustc 1.98.1-5 or later (1.98.1-4's wasm32-wasip1 libc lacked the pthread stubs libtest links, homescoop#1043). Doc tests need rustdoc, which isn't packaged: cargo test skips them with warning: doc tests skipped: rustdoc isn't available in slicc and exits with the status of the tests that ran, and cargo test --doc and cargo doc fail with that reason (since 0.99.0-5, homescoop#1463), as does cargo rustdoc (since 0.99.0-6, homescoop#1540).
• Unsupported on WASI. Git dependencies need a git network transport, and they fail with a message that names the realm.
• Untested. cargo search, publish, login, owner and yank use the same proxy client.

The package sets CARGO_BUILD_JOBS=1 because WASI std cannot query host CPU parallelism. It disables incremental compilation because the realm filesystem does not provide the file locks rustc requires. It also sets CARGO_BUILD_TARGET=wasm32-wasip1.

Cargo runs the installed @ai-ecoverse/wasi-rustc driver found on PATH. It needs wasi-rustc 1.98.1 or later: the 1.83 compiler panicked on rustc -vV, which Cargo runs to probe the compiler.

The package sets CARGO to its installed Bash driver, which Cargo uses for subprocesses. Its WASIX Command bridge sends captured child stdin to /dev/null, so rustc probes do not wait on a live terminal.