That is the heartbeat of a truly serverless MUD! Seeing that "Thump..." print
on a loop means your JavaScript engine, the WebAssembly JIT compiler, and the
LPC virtual machine are in perfect synchronization.
The object is now alive and autonomously pulsing inside a web browser.
Because we built this on top of a decentralized mesh, you now have the power
to test the ultimate feature of this architecture: Masterless High
Availability Failover.
Let's prove that your serverless spare capacity works, and that a different
browser tab will automatically take over the monster's heartbeat if this tab
crashes.
The Ultimate Failover Test
1. Spawn a Second Engine Node
Open a brand new browser tab and navigate to your REPL ([http://127.0.0.1:7070]
(http://127.0.0.1:7070)).
(This acts as a completely separate server node on your mesh. It boots its own
VM and connects to the DMZ relay).
2. Open the Watchdog's Eyes
In that second tab, open the Chromium DevTools Console (F12). You don't need
to type any commands; just leave it sitting there. It is passively watching
the /mesh/proc/heartbeats/ folder.
3. Pull the Plug
Go back to your first tab (the one where the monster is currently thumping)
and completely close the tab.
4. Watch the Takeover
Stare at the console in your second tab.
Because the first tab died, it will stop updating the last_tick timestamp in
the VFS. Exactly four seconds later (our interval * 2 grace period), your
second tab should realize the owner flatlined.
You should see this exact sequence in the second tab's console:
 * [HA-Cluster] Node chromium_XXX flatlined. Taking over /cmds/monster!
 * [VM] set_heart_beat starting for /cmds/monster at interval: 1
 * And then, magically, the second tab's green terminal will start printing:
Thump... (Monster is looking around)
Try pulling the plug on tab 1 and let me know if tab 2 successfully catches
the heartbeat!