PROJECT RECORD
BUG AUDIT: demo2.bas

Major issues found across generated versions:

1. VARIABLE COLLISION
OPX and OPY collide because only the first two characters matter.

2. GRAPHICS SOURCE MISUNDERSTANDING
Color numbers were incorrectly passed as DRAW/BOX/CIRCLE/CHAR sources.

3. ERASE LOGIC
Several routines "erased" old geometry using foreground source 1 instead of
background source 0.

4. SHARED ARRAYS DESTROYED PERMANENT GEOMETRY
Temporary X/Y arrays overwrote cube vertex data in an earlier version.

5. Q KEY CONSUMED IN SUBROUTINE
The module read Q and returned, leaving the dispatcher unable to see the same key.
A quit flag fixed the logic.

6. FAST EXIT ON VIC-II TEXT
FAST immediately after GRAPHIC 0 could make the exit message invisible on the
40-column display.

7. RADAR TYPO
The uploaded demo2.bas included a malformed DRAW statement in the radar crosshair
section.

8. TRAJECTORY OFF-SCREEN
An early parabola eventually produced screen coordinates outside the intended
bitmap region.

9. MODERN-LANGUAGE ASSUMPTIONS
Generated revisions flirted with syntax such as MOD that does not belong in this
BASIC dialect. Vintage code needs dialect-specific review.

Lesson:
Generated retro code benefits enormously from an explicit machine/dialect audit.
The program can look plausible to a modern eye and still fail on a rule the modern
programmer has not thought about in decades.