Future Prevention Rules

  1. Do not accept a D3-TUI build unless Flycast shows the visual D2 target: W/A/R/P tiles from NLOGO.PVM, the 0GDTEX.PVR disc graphic, and the D3-TUI overlay.
  2. Do not restore raw IP.BIN + binary concatenation. Disc packaging is separate future work; Flycast acceptance is the KOS ELF artifact.
  3. Do not run autonomous agent loops that delete builds/ while a canonical build or verification is in progress.
  4. Regenerate asset source with make d2-assets whenever asset-staging/d2/*.PVR or *.PVM changes.
  5. Keep the Pi KOS compatibility stubs with a multi-megabyte _sbrk() heap unless the Pi toolchain is replaced with one that provides the missing newlib hooks.
  6. Keep the final report and manifest with any release candidate so future agents can compare entry point, hash, and screenshot proof.