I discovered that we do not need to use core::intrinsics::abort, instead we can use core::arch::wasm32::unreachable, which has the same effect, but is stable, as opposed to core::intrinsics::abort which is perma-unstable. I've updated the guides in our documentation, but we should probably update everything else that uses unstable intrinsic (or that we held off on updating due to the instability).

For crates which need to compile for both Wasm and non-Wasm targets, we can use conditional compilation to use the wasm32 intrinsic when appropriate, but I think most everything we have that needs it, is only targeting Wasm anyway.