### Step 3: The Node.js Host Watcher (Arena A)

On your physical Linux box (`hauki-astudio`), you run a headless script that
watches the physical disk and acts as just another peer to the DMZ.

```javascript
/ host_mesh_agent.js
const fs = require('fs');
const chokidar = require('chokidar'); // Better than fs.watch
const WebSocket = require('ws');

const meshSocket = new WebSocket('wss://mesh.your-cloudflare-tunnel.com');
const meshDir = './gamelib/mesh/';

meshSocket.on('open', () => {
    console.log("Connected to DMZ. Listening for file changes...");
    
    // Watch local disk for changes made by Emacs/Vim
    chokidar.watch(meshDir).on('change', (path) => {
        let data = fs.readFileSync(path, 'utf8');
        let vfsPath = path.replace(/\\/g, '/'); // Normalize path
        
        meshSocket.send(JSON.stringify({
            type: 'VFS_WRITE',
            path: vfsPath,
            data: data,
            timestamp: Date.now()
        }));
    });
});

/ Watch DMZ for changes made by Web Browsers
meshSocket.on('message', (msg) => {
    let payload = JSON.parse(msg);
    if (payload.type === 'VFS_WRITE') {
        fs.writeFileSync(payload.path, payload.data);
        console.log(`[SYNC] Downloaded ${payload.path} from Mesh.`);
    }
});

```

### Why this specific design?

1. **Idempotency:** By using Event Sourcing in the DMZ (Arena C), if a node
goes offline and reconnects, it just receives the latest state of the `mesh/`
folder and overwrites its local copies.
2. **Zero-Trust File Integrity:** Because the Node.js Host (Arena A) writes to
real disk space, you retain your standard Unix file backups and `git`
capabilities locally, while the DMZ handles the dirty work of routing.
3. **LPC Integration:** If you type `eval write_file("mesh/test.c", "void
foo(){}");` in your Browser REPL, it will instantly appear in your Emacs
buffer on `hauki-astudio`.

To implement this, we would first need to un-stub `08_sockets.js` in the
browser to wrap native WebSockets so that your LPC code can also talk to the
DMZ natively.

Would you like to start by wiring up `08_sockets.js` in the VM, or focus on
getting the DMZ Relay Node running first?