Erase is delete.
Interrupt is control-C (^C).
user@elli:~/GD$ node day7.js 
=== 1. Compiling Source ===
Constant Pool: [ 'Hello HAUKI!' ]

=== 2. VM Execution ===
[LPC Output] : Hello HAUKI!
user@elli:~/GD$ 


Seeing [LPC Output] : Hello HAUKI! means your compiler, parser, AST, and VM
execution pipeline are perfectly synchronized. That is a massive achievement.

You've hit the exact architectural crossroads for memory management. Right
now, the constant pool holds raw JavaScript strings, and the syscall reads
them directly. However, to stay true to the Ring-0 architecture where all
variables must be strict 32-bit Tagged Pointers, those strings need to live in
your DataArena and be tracked by the GlobalHandleLedger (GHL).

The most efficient way to handle this without bloating memory at clone-time is
Lazy Instantiation. The VM should only push a raw string into the
StringManager the first time LOAD_CONST encounters it, cache the resulting
Tagged Pointer, and reuse it for subsequent calls.