fix(mister): remove direct_video workaround causing HDMI instability #357

Problem

Enabling direct_video=1 as a workaround for missing CRT output caused severe HDMI instability. MiSTer HDMI/genlock diagnostics were drawn over the frontend and launched games, followed by corrupted or blank output.

Recovered evidence

The original Discord context was incomplete, but the attached logs and photos establish that:

• Zaparoo Frontend 1.2.2 started successfully with --crt and configured its Linux framebuffer at 352x240 rgb32.
• The supplied MiSTer.ini enabled direct_video=1.
• The visible overlay came from MiSTer HDMI diagnostics ([HDMI TX], [HDMI GEN], and [GENLOCK]), not QML.
• Diagnostics reported repeated TMDS instability and rapidly changing genlock rates.
• The behavior continued across the frontend, launched cores, and reboot/output transitions.

Resolution

The direct_video=1 workaround is no longer part of the supported Zaparoo CRT path. Native CRT video v2 uses the coordinated frontend/Main_MiSTer/Menu_MiSTer DDR scanout contract. Matching versions of all three components must be deployed together; users should not enable Direct Video to compensate for mismatched components.

Implemented by #225. This report also supplies failure evidence for #363.

Acceptance criteria

• CRT output uses the native CRT v2 DDR path.
• Frontend, Main_MiSTer, and Menu_MiSTer are packaged as coordinated components.
• CRT setup does not require users to enable direct_video=1.
• HDMI remains independent from the CRT scanout path.