Lann

> Prevent myself from having the actual name (magic string) of the key-value store in multiple places You still have a magic string: `"store"`; it is just adding an extra...

I've seen examples of running [wasm3](https://github.com/wasm3/wasm3) on this board, but Spin itself will probably not support very low powered devices like this any time in the foreseeable future.

Perhaps we could have a "contributors" group with triage permissions and add anyone who has made "signficant contributions" to the project? Triage is pretty limited and would only be a...

It appears that you cannot have teams contain members that aren't also org members but we could still maintain a flat list of triagers in the repo.

Somewhere or other I suggested a `spin-up-` prefix for crates that only apply to the `spin up` runtime. I guess that is arguably different than "CLI-specific", but I think it...

`{% raw %}{{ not interpolated }}{% endraw %}` I don't hate it. It's a little odd to introduce "tag" syntax just for `raw` but at least it's familiar.

Sorry, words are hard. This issue is referring just to the runtime config "templating", i.e. what was once called `spin-config`, is now mostly referred to as `spin-variables`, and is implemented...

There is an error in place: https://github.com/fermyon/spin/blob/967fdf368612478cef176bccc491faffad680050/crates/componentize/src/bugs.rs#L46-L48 The current Grain template has been fixed but our language docs need to be updated to reflect changes; really we probably ought to...

Could you try with `WASMTIME_BACKTRACE_DETAILS=1`?

Ah sorry, the env var should actually be in _spin_'s environment, e.g. just `WASMTIME_BACKTRACE_DETAILS=1 spin up`