Lann

This is a little tricky to implement as wasmtime doesn't expose the current live instance count and even if it did we would need some signal that the count has...

I'm assuming krew doesn't _automatically_ install plugins and then run them with just a warning? I think that's the main difference here. _Edit: Oh wait we install `cloud` without even...

Oh I guess if you're talking about `--yes` you mean the actual `spin plugins install` command. Yeah I think it would be fine to just display a warning there, or...

Yes and as the harness for the suite of spin env tests.

A smaller change that would still address most of the confusion would be to require explicit imports only where an _exported_ interface depends on that imported interface. Or even incrementaler:...

@ospencer it looks like I could use some of [those pointers](https://github.com/grain-lang/grain/issues/2152#issuecomment-2315689232)... :sweat_smile:

~~Unfortunately due to #2152 I can't run with `--debug`, but manually poking around at the names section it looks like:~~ ``` -> _ZN136_$LT$wasi_snapshot_preview1..bindings..wasi..io..streams..InputStream$u20$as$u20$wasi_snapshot_preview1..bindings.._rt..WasmResource$GT$4drop4drop17h2cb53bfcb8abc006E -> wasi:cli/[email protected]#run ``` (82 and 83 don't...

Ah this is two separate errors smushed together: ``` GrainExceptionError: failed to run main module `hello.component.wasm` ``` `GrainException` (from the Grain runtime) + `Error: failed to run ...` (from Wasmtime)

We should maybe only add it automatically when the known content length is non-zero; there are some cases when servers are supposed to *not* send it (notably 204 No Content).

https://www.rfc-editor.org/rfc/rfc9110#field.content-length > A server MAY send a Content-Length header field in a response to a HEAD request ([Section 9.3.2](https://www.rfc-editor.org/rfc/rfc9110#HEAD)); a server MUST NOT send Content-Length in such a response unless...