[jeany55]

Step 6 of the way off eudplib (docs/v4-plan.md: "The game's tables on our own backend"): stats() tables read and written (unit types, weapons, upgrades, techs, players), memory.game / .map / .vision, and the local.* reads.

Every cell is at an address known when built, so this builds on step 5:

• Read: the cell's bits of its dword, moved down. Masked fields get the high-bit skip too, so a word below 256 is read in 8 bits.
• Write: a Set Deaths into the dword, masked for a byte, word or bit, its amount a place of the value (scaled and capped at the field's top).
• Name: its text's string number. Top speed: through the unit type's flingy (speed, acceleration, halt, table control), the writes naming their dwords by a place of the flingy read while the game runs.

Ledger: step 6 0/47 → 50/50. The five local.* rows of step 12 build now and are relabelled step 6. Each prints the same as eudplib's build in the lifted game.

Lifted game, ms (ours / eudplib): start + checks 0.025 / 1.167; 200 word reads 0.092 / 0.140; 200 writes from a value 0.040 / 0.188. Every line of probes/own-memory.ts is ok in both builds; the flingy fields are identical to eudplib's, and the unit name's string reads back "Space Marine".

Suite 1261 pass.

🤖 Generated with Claude Code

https://claude.ai/code/session_01BwPs2Ya2X9rB9TYHijfoom