Eliminate external subprocess dependencies (curl and wasmtime)

[lambda-alpha-labs]

Description

This feature replaces the current use of external subprocesses for core functionality with native, in-process implementations. Specifically, it involves refactoring the HTTP networking layer to use Zig's native std.http.Client instead of shelling out to the curl binary, and updating the WASM runtime adapter to statically link a lightweight C-based WASM interpreter (such as wasm3 or the wasmtime C-API) rather than invoking the wasmtime CLI via child processes.

Motivation

NullClaw's primary value proposition is being a strictly self-contained, lightweight static binary that requires no external dependencies. Relying on host-installed tools like curl and wasmtime breaks this guarantee of true portability and introduces unnecessary performance bottlenecks due to continuous process-spawning overhead. By bringing these capabilities entirely in-process, we ensure the application remains completely standalone, reduces invocation latency, and fully adheres to its zero-dependency design philosophy while preserving a minimal memory footprint.

[ThinkOffApp]

This matters a lot for embedded targets. We just shipped ClawWatch — NullClaw running natively on a Samsung Galaxy Watch (ARM, 2 GB RAM). On a watch, there is no curl binary, no wasmtime, no standard unix toolchain. The static binary approach works precisely because NullClaw can be self-contained.

Having zero subprocess dependencies means the binary drops into any ARM Linux environment (Android, embedded Linux, Raspberry Pi, smartwatches) and just runs. This is a real blocker for production embedded deployments.

Our build: zig build -Dtarget=arm-linux-musleabihf -Doptimize=ReleaseSmall — produces a 2.8 MB static binary that runs on the watch via ProcessBuilder.

Repo: https://github.com/ThinkOffApp/ClawWatch

[manelsen]

I might have figured it out. Gimme a few days.