Lann

I can take a shot at this. Would we expect this specification to be part of this repo?

> Since it's mostly text anyways, perhaps the custom section contents should be human-readable/editable text (unlike, e.g., the name section) so that, e.g., the "exploded" representation of a component has...

> It would be useful to have a well-defined validation predicate that we can regularly check (e.g., on registry publication) to avoid the drift I expect we'd get otherwise. You...

I have some prototype code for this now: https://github.com/bytecodealliance/wasm-tools/pull/1169 The JSON schema ended up being directed a bit by the `wit_parser::Resolve` internals. I think the result of that is that...

> Another question is whether to save markdown or compiled html format. One of the goals of this feature is to be able to transform the binary encoding back into...

I think this may in fact be best served via wasi-observe. Distributed traces are typically keyed off of a trace ID which is either passed in via e.g. [W3C Trace...

I don't think we should do this by default; if an app starts successfully but the port is hosting a different app than expected you could end up with frustration...

> Vite has this feature. I've used Vite and never noticed this! :sweat_smile: As pointed out out-of-band, another option that sort-of works today is `spin up --listen localhost:0`, which picks...

https://github.com/fermyon/spin/issues/2471

I'm somewhat opposed to this behavior being default - `spin up` is used in production in some places (for better or worse...) - but I wouldn't be opposed to an...