#219 CLI crashes with exit 134 (Rust panic in tls_wrap.rs) after successful command output

Description

After commands complete successfully and print their full JSON output, swamp crashes with a Rust panic instead of exiting cleanly with code 0.

Steps to Reproduce

swamp extension pull @keeb/ssh
# or
swamp model create @keeb/ssh/host my-host --global-arg host=1.2.3.4 --global-arg user=root

Error Output

thread 'main' (10068854) panicked at ext/node/ops/tls_wrap.rs:2018:31:
called `Option::unwrap()` on a `None` value
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

thread 'main' (10068854) panicked at library/core/src/panicking.rs:230:5:
panic in a function that cannot unwind
stack backtrace:
   0:        0x10189aecc - _uv_mutex_unlock
   1:        0x100b07b5c - <unknown>
   ...
thread caused non-unwinding panic. aborting.

Impact

The JSON output is fully printed before the crash, so the operation itself succeeds. However, the non-zero exit code (134 = SIGABRT) breaks scripting — any --json pipeline that checks the exit code will treat a successful operation as a failure. Also causes confusion since the command visually appears to have worked.

Environment

• swamp version: 20260502.153639.0-sha.907c6883
• OS: macOS Darwin 25.4.0 (arm64)
• Datastore: S3 backend
• Commands affected: swamp extension pull, swamp model create