From @t0yv0:

I would like us to pay attention to how failures present themselves to the user. (1) "type" error having either the component's SDK or implementation generate a value that does not match the declared schema; how do we attribute the fault and present this error nicely, or how do we make sure this never happens; (2) general unhandled error inside the implementation; how do we label the error with the component at fault and preserve the original lang stack trace. Just a little bit of attention here would go a long way. In our current code, the default behavior in these cases is not great.