user@elli:~/GD$ node day6.js 
=== 1. Source Code ===
void attack(object target) {
  target->take_damage(15);
}

=== 2. Compiled Blueprint ===
VTable Mapping:
  Hash 0xC9FD -> IP 0

Bytecode (Hex):
  [0] 0x0210000F
  [1] 0x11024208
  [2] 0x0F000000
user@elli:~/GD$ 

That output is the hallmark of a mature compilation pipeline. Your compiler
flawlessly traversed the AST, mapped the variable to a dynamically allocated
CPU register, hashed the function name on the fly, and emitted a perfectly
clean 32-bit binary instruction.

Now that the logic generation is rock-solid, we need to bridge the gap between
our abstract syntax tree and the virtual machine's memory layoutspecifically,
handling Strings and the Constant Pool.

When the parser encounters a string like "Hello HAUKI!", the Code Generator
shouldn't try to cram those characters into bytecode. Instead, it must push
the string into the Blueprint's constantPool array and emit a LOAD_CONST
instruction that tells the VM to load that exact array index into a register.

Here is how we integrate String Constant extraction and System Calls into your
compiler.