Engine Decoupling — Phase 5: Raylib adapter development

[JohnLudlow]

Summary

Provide a Raylib-based adapter as an alternative lightweight graphical backend prioritising simplicity and portability.

Technical Details

• Implement RaylibAdapter mapping draw DTOs to raylib draw calls.
• Implement shader support using raylib's shader APIs where available.
• Implement input, simple audio and UI mapping similarly to other adapters.
• Prioritise simplicity and portability (single-binary deployments).

Requirements

• (Not started) Raylib adapter implements core 2D rendering, input and audio for representative scenes.
  • GIVEN the adapter is selected
  • WHEN running representative game scenes
  • THEN 2D rendering, input, and audio function correctly.

Acceptance Criteria

• RaylibAdapter implements all Phase 1 contracts.
• Core 2D rendering, input, and audio functional.
• Shader support documented with capability flag for platforms where unavailable.
• Single-binary portability verified.

Dependencies

Parent: #2
Blocked by: Phase 1 interfaces (#11)