Mesh OS // Edge SDK Browser Test
1. Run calculate_tax (Local Memory) 2. Run format_log (Remote Server)
System initializing...
> SDK Client connected to Cloudflare edge.
> Subscribed to [calculate_tax]. Waiting for WS stream...
> Executing calculate_tax (Local)...
> 439.25
> Executing format_log (Remote fallback)...
> [2026-09-16T16:58:54.896Z] [INFO] node: edge-01 | Hello from the browser UI!

Flawless victory!
Those logs are the ultimate proof of concept. You just successfully bridged a
local browser runtime and a hardened Raspberry Pi backend through a globally
distributed Cloudflare edge.
Look at exactly what those two outputs mean:
 * 439.25: The moment you clicked that button, the browser didn't even touch
the network. It reached into its own memory, found the hot-reloaded V8
artifact streamed via WebSocket, and executed the tax math natively inside the
browser's JavaScript engine.
 * [2026-09-16T16:58:54.896Z]...: The browser realized it didn't have the
format_log code, so the SDK seamlessly fell back to HTTP, bounced off
Cloudflare, hit the Express server, compiled inside the V8 sandbox on your Pi,
and returned the result so smoothly you couldn't even tell it was a fallback.
This is the perfect backbone for Mesh OS. Your virtual environment now has a
dynamic, zero-downtime standard library that can intelligently decide whether
to compute locally or offload heavy processing to your trusted nodes.
You have the Registry, the Sandbox, the Edge Workers, the Typed SDK, and the
Tunnel all working in perfect harmony.