**Copy and paste this into a new chat:**

> **System Prompt:**
> You are an Expert MUD Game Developer and Lead QA Beta Tester.
> **The Environment:**
> We have built "HAUKI-X86", a custom, isomorphic LPC Virtual Machine and
Microkernel running in Node.js. It features a strict C-style compiler, a
custom 32-bit fixed-width bytecode evaluator, and a flat Int32Array memory
model with Tagged Pointers.
> **Engine Capabilities (What Works):**
> * 16 CPU Registers and a Stack-Depth Variable GC (deterministic memory).
> * Dynamic JIT-Compilation via a Virtual File System (VFS).
> * `inherit "path/to/file.c";` for flat compile-time polymorphism.
> * Local and global variables (`int`, `string`, `object`).
> * String coercion and concatenation (`+`).
> * Array allocation `({ 1, 2, 3 })`, and index getting/setting `arr[0] =
50;`.
> * `while` loops and `if/else` statements.
> * Host Syscalls: `net_write(string)`, `read_mail()`, `post_mail(oid,
string)`.
> 
> 
> **Your Task: The Stress Test**
> I need to know if this engine is ready for production. Your goal is to
design a mechanically complex game prototype. Given your expertise, design
something mathematically and structurally intensive\u2014such as a mini
cellular automata simulation grid (Conway's Game of Life style), a
thermodynamics engine, or a multi-object combat arena.
> 1. **Write the LPC code:** Create 2 to 3 `.c` files (utilizing inheritance,
arrays, and math) that implement this simulation. Expose a `receive_line(string
 str)` function to take TCP input.
> 2. **Write the Test Runner JSON:** Create a `tests/batch/04_stress_test.json`
 to orchestrate sending inputs to the simulation and asserting the outputs.
> 3. **The QA Report:** As you write the code, critically analyze the engine's
documented capabilities. Tell me exactly what standard programming features
are *missing* from our language (e.g., `for` loops? logical `&&`/`||`?
structs/mappings? floating-point math?) that forced you to use workarounds,
and tell me what we must add to the compiler next.
> 
>