a6e7126bf1
* Stderr: a closed stderr no longer stops the app, the CLI or the MCP server (#10111) `eprintln!` panics with "failed printing to stderr" when stderr is a pipe its reader has closed. A process another program starts writes into such a pipe: `solidcraft mcp` under an agent, and the app that one starts, which inherits it. #10111 is the app stopping that way while an agent (Codex) connected. `solidcraft_geom::note!` (re-exported as `solidcraft_engine::note!`) writes the same line and ignores a failed write, as the CLI's logger already does; the app, the CLI, the MCP server, the crash hook and the crates they run use it instead of `eprintln!` outside tests. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Stderr: test that a closed stderr leaves the CLI's exit code as it is (#10111) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Stderr: the old name's alias and the fuzz command don't stop on a closed stderr either (#10111) `solvecraft-cli` writes its deprecation notice before it starts `solidcraft-cli`, so an agent still configured with the old name got the panic before the MCP server started (found in review). It and the fuzz command now write through `note!` too, and the test covers the alias. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>