D3-TUI Realignment Brief

Date: 2026-05-10

What went wrong

The previous autonomous work was not anchored to a canonical D3-TUI Forgejo repo. Agents worked in a shared filesystem workspace and drifted into build-image repair loops instead of accumulating traceable repo work.

The visual target also drifted. The repaired Flycast proof used a narrow W/A/R/P subset from NLOGO.PVM plus 0GDTEX.PVR. That proves some D2 texture decoding and KOS/Flycast boot mechanics, but it is not the intended D3-TUI target.

Build-image work also carried contradictory assumptions: CDI, ISO, raw IP.BIN concatenation, MIL-CD exploit booting, and physical hardware packaging were mixed into an emulator validation effort.