nx_tictactoe_render.nx

nx_tictactoe_render.nx -- bits-up HTML rendering + event dispatch for /tictactoe. STATUS 2026-05-20: ARCHITECTURE-COMPLETE BUT BLOCKED ON SUBSTRATE GAPS. This file describes the intended bits-up rendering architecture; it compiles to RISC-V asm (qemu green path) but **does NOT yet compile to WAT** due to two substrate-side gaps: 1. nxc2 --target wat: "unhandled opcode 30 in emit_instr" -- the WAT backend does not yet lower string-literal data into WASM data segments. Same gap blocks nx_html_emit compilation to WAT. Fix: extend nxc2/wasm.c emit_instr switch + add data-segment synthesis from string-literal IR nodes. 2. @ifdef TARGET_X86_64 / @endif blocks in nx_syscalls.nx report "2 unclosed @ifdef/@ifndef block(s)" under --target wat as of 2026-05-20 background changes. Macro expansion regression. Until both close, the /tictactoe page uses minimal bespoke JS for DOM rendering with NishiLang-compiled WASM for game logic + AI. When the gaps close, this file gets compiled into the WASM module and the bespoke JS gets replaced by dist/_nishi/nishi-host.js calling nx_ttt_render + nx_ttt_action via the sentinel-fd-99 convention. Per [[feedback-ui-rendering-bits-up-not-just-game-logic]]: UI emission + click-to-state mapping live in NishiLang. Only the IRREDUCIBLE dist/_nishi/nishi-host.js (~120 LOC: WASM-instantiate + syscall imports + innerHTML setter + addEventListener) is JS. HTML is emitted by writing bytes to fd 99 (sentinel); the JS host captures those bytes into a buffer and sets innerHTML. Same fd-99 convention is reusable across every Nishi game. Exports (called by nishi-host.js): nx_ttt_init() -> *i64 -- allocates + returns initial state nx_ttt_render(s) -> i64 -- emits full HTML to fd 99 nx_ttt_action(s, act, a0, a1, a2, a3) -> i64 -- handles a click/change event; returns 1 if state changed (host re-renders), 0 otherwise.