Support Cargo scaffolding and human output, and find boolean expressions

2026-11-11 21:57:37 +00:00
parent c7606b8ae9
commit 652ea7960f
7 changed files with 267 additions and 116 deletions
@@ -7,7 +7,11 @@ The response contains newline-delimited JSON events.
 The final `exit` event contains a code and component locations.
 Each location contains an executable path and working directory.

-The CLI forwards the bytes immediately.
+The CLI forwards human output immediately.
+The builder captures compiler JSON for artifact discovery without forwarding it to stdout.
+Compiler diagnostics remain on stderr. `cargo run` reserves stdout for the program.
+`cargo new` and `cargo init` use native Cargo, including `--lib`, `--name`, and `--edition`.
+They need no existing manifest. Subsequent builds use the world's default WASI target.
 For `test` and `run`, it executes the artifacts through the process interface.
 Cargo selects run binaries through a capture runner, so `--bin` and `default-run` retain their normal behavior.
 The test runner uses each package's root directory, even when the caller runs Cargo from a subdirectory.