No browser playground
This site does not compile or run Noble in the browser.
The compiler is the native noble command. A run uses the pinned Node/V8, wasm-tools, and Binaryen paths in the CLI configuration. Component routes also need the host Wasmtime source named in the flake. This repository does not publish a WebAssembly build of that compiler.
Programs compile to WebAssembly. That artifact is the guest, not a compiler a page can load.
A guarded live path exists as a resident Node/V8 process with in-process Wasm emission. It is not a static page, and it does not make unrestricted host effects available here.
Follow-up, recorded as phase 3 of issue #137: a later playground could run bounded Core-Bootstrap examples as Wasm, without implying that the live REPL or unrestricted host effects are available. That needs a separate bounded compiler build. It is not part of this site.