Compatibility shim providing otplike.gen-server API backed by loom-otp.

Key differences handled:
- Returns [:ok pid] tuples instead of {:ok pid} maps
- Uses otplike-style process/! for messaging
- Integrates with loom-otp.otplike.process async/await

Compatibility shim for otplike.proc-util.

In otplike, execute-proc creates a process context using go blocks.
In loom-otp, we use virtual threads directly via vfuture.

Compatibility shim providing otplike.process API backed by loom-otp.

Key differences handled:
- `!` function for sending (vs loom-otp's `send`)
- `proc-fn`, `proc-defn` macros (vs loom-otp's plain functions)
- `async`/`await!`/`await!!` implemented via vfuture
- Tuple returns [:ok pid] vs map {:ok pid}
- `receive!!` variant (blocking) is same as receive! in virtual threads

This namespace does NOT modify loom-otp internals.

Compatibility shim providing otplike.supervisor API backed by loom-otp.

This wraps the gen-server-based supervisor implementation to return
[:ok pid] tuples instead of {:ok pid} maps.

Compatibility shim providing otplike.timer API backed by loom-otp.timer.

otplike.timer returns channels as timer references.
This shim wraps loom-otp.timer's Timer records to provide similar semantics.

Compatibility shim providing otplike.trace API backed by loom-otp.