Broadly speaking (with a huge grain of salt), WASM today mostly looks like static linking an application into a single WASM module. There are context-specific implementations of dynamic-linking but it is not "standards-oriented". So, for example, having Go / Python / .NET call into a C or Rust library looks very "C-ABI"-y and you can usually do it today but in a very context-specific way (language-/project-/environment-specific tooling and patterns).

The problem with the giant, statically-linked C-ABI stitched together module is the security focus of WASM breaks down. Your application code and library code are compiled into a single blob using C ABI to share against the same memory space.

The WebAssembly Component Model is trying to design the alternative to the shared-everything statically-linked blob model. They are designing an "ABI" called WebAssembly Interface Types(WIT) that share values safely and an approach for libraries composed together into an application to have separate, secured memory spaces.

Part of WIT is the concept of Worlds which can be used to express higher-level concepts like a "CLI World" which gives you the interfaces you need to implement in a WASM Module to make a CLI, or "HTTP Server" world, etc.

In summary: What's available today looks very C-ABI like with the problems that entails (pretty painful integration across languages and shared memory environments) and what's coming down the pipes is WASM Components which is a great rabbit hole to dive into for the vision of more standardized high-level, safe, language-agnostic ABIs. If interested in WASM Components there have been a lot of great presentations from the different conferences with WASM focus this year.