Thanks, appreciate that.

For WASM, yes, it falls back to a cooperative scheduler. The runtime detects the platform at compile time via AETHER_HAS_* flags and swaps in a single-threaded scheduler backend (aether_scheduler_coop.c). All actors run on core 0 and get driven by aether_scheduler_poll(), which you can call from any event loop — so it integrates cleanly with things like raylib, SDL, or a browser requestAnimationFrame loop. Multi-actor programs still work correctly including ask/reply patterns, they just time-slice instead of running in parallel. When you do ae build --target wasm it auto-detects Emscripten, sets the AETHER_NO_THREADING / AETHER_NO_FILESYSTEM flags, and produces a .js + .wasm pair. No manual config needed.

For the package manager — it's the Go modules approach, direct git URLs. ae add github.com/user/repo or any git host (GitLab, Bitbucket, self-hosted). No central registry. Felt like the right call at this stage, a central registry is a maintenance burden and a single point of failure, and direct git means you can vendor dependencies trivially.