Lann

Some options: - Implement our own "argument pre-processor" that takes all args after `up` and extracts all known flags (and their values!) before passing on to the clap subcommand parser....

Agreed that versions make the `use` syntax pretty gnarly. My only concern with quotes is that it sort of suggests that the contents aren't part of the WIT syntax.

> requiring that projection doesn't happen in use statements of interface but only at the top level of files Veering just a bit off-topic, if top-level `use`es brought their symbols...

I'm a little wary of adding a call to `_start` where we haven't done it before. It's _supposed_ to be for WASI command modules, and I don't know how safe...

See wasi-libc's implementation of `_start` calling destructors: https://github.com/WebAssembly/wasi-libc/blob/f2a35a454e8472b63831885daacc7f5fadd46747/libc-bottom-half/crt/crt1-command.c#L45-L46

I've been digging through the tinygo source and these errors still don't make sense to me, but one hack to try might be to call `os.Getenv("ANY_KEY")` and then see if...

I can take a crack at it.

This draft is ready for initial review: https://github.com/WebAssembly/component-model/pull/536 _Moved comment about binary format [to the PR](https://github.com/WebAssembly/component-model/pull/536#issuecomment-3006199206)._

cc @jandubois