Engine Decoupling — Phase 4: MonoGame adapter development

[JohnLudlow]

Summary

Implement MonoGame adapters for 2D (and optional 3D) rendering, input, and audio.

Technical Details

• Implement Monogame2DAdapter mapping IRenderContext draw DTOs to sprite-batch calls; manage textures and simple materials.
• Provide shader/material integration where MonoGame supports custom effects; map shader descriptors from DTOs to engine-specific effect parameters.
• Implement audio via MonoGame/NAudio bindings as required by platform.
• Map UI control rendering to sprite/text draw calls with correct layout, theming, and input handling.

Requirements

• (Not started) Monogame2DAdapter implemented with basic UI screens and audio playback.
  • GIVEN the adapter is selected
  • WHEN running a small playtest scenario
  • THEN UI renders correctly and audio plays for sample assets.

Acceptance Criteria

• Monogame2DAdapter implements all Phase 1 contracts.
• Sprite-batch rendering, texture management, and materials working.
• Shader/material descriptor mapping documented.
• Audio playback via MonoGame/NAudio.
• UI screens render correctly in a playtest scenario.

Dependencies

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