Add DA_RenderPipelineProfile and Platform Render Profiles documentation

- Introduced DA_RenderPipelineProfile data asset to define rendering pipeline configurations for various platforms and quality tiers.
- Documented enums, structs, variables, and default preset tables for render settings.
- Created a comprehensive developer guide for setting up platform-specific render profiles, including file structure, profile creation, and integration with upscalers.
- Included validation rules, console variable references, and testing matrices for ensuring compliance with platform requirements.

docs/developer/architecture-overview.md

@@ -36,7 +36,10 @@ Direct Reference        │    Interface Calls
 │  LAYER 8: POLISH & META                                         │
 │  Tutorials, Loading, Credits, Analytics, Achievements           │
 ├────────────────────────────────────────────────────────────────┤
-│  LAYER 7.5: HAPTICS                                             │
+│  LAYER 7.5: RENDER PIPELINE                                    │
+│  Quality presets, Lumen/Baked, upscaling, platform profiles     │
+├────────────────────────────────────────────────────────────────┤
+│  LAYER 7: HAPTICS                                              │
 │  Controller vibration, DualSense triggers, heartbeat pulse      │
 ├────────────────────────────────────────────────────────────────┤
 │  LAYER 7: ADAPTIVE                                              │
@@ -92,7 +95,10 @@ All input goes through `SS_EnhancedInputManager`. Context switching uses priorit
 ### 8. GameplayTag-Driven Haptics
 All controller vibration routes through `BPC_HapticsController` on the Player Controller. Gameplay systems trigger haptics by GameplayTag (e.g., `Haptic.Damage.Heavy`) — never calling raw `Play Force Feedback` nodes. The component detects platform (Xbox rumble vs PS5 DualSense adaptive triggers), respects accessibility toggles, and manages effect priority. Heartbeat pulse is driven by `BPC_StateManager.GetCurrentHeartRate()`.
 
-### 9. Force Stack for State Overrides
+### 9. Per-Platform Render Pipeline
+All render quality decisions route through `BPC_RenderPipelineManager`. The system reads `DA_RenderPipelineProfile` Data Assets to determine Lumen vs Baked Lightmass, Virtual Shadow Maps vs Cascaded Shadow Maps, Nanite vs traditional LODs, and the appropriate upscaler (DLSS/FSR/TSR/PSSR) for the detected platform and selected quality preset. Destructive pipeline changes (GI method, shadow method) are queued and applied on level load. The Planar Capture system adjusts its quality budget based on the active pipeline.
+
+### 10. Force Stack for State Overrides
 Death, cutscenes, void space push state onto a stack. `RestorePreviousState()` pops back — the player returns to exactly their previous state after a forced interruption.
 
 ---
@@ -150,13 +156,13 @@ The 16 build phases follow dependency order:
 | `WBP_` Widget Blueprints | 14 | HUDController, InventoryMenu, MainMenu |
 | `DA_` Data Assets | 18 | ItemData, EquipmentConfig, AtmosphereProfile |
 | `SS_` GameInstance Subsystems | 7 | SaveManager, UIManager, AudioManager |
-| `BPC_` Components (haptics) | 1 | HapticsController (PlayerController) |
+| `BPC_` Components (settings) | 2 | HapticsController, RenderPipelineManager |
 | `GI_` Game Instances | 2 | GameFramework, GameTagRegistry |
 | `I_` Interfaces | 3 | InterfaceLibrary, HidingSpot, Persistable |
 | `GM_` GameMode, `GS_` GameState | 2 | CoreGameMode, CoreGameState |
 | `FL_` Function Library | 1 | GameUtilities |
 | `AI_` Controller, `BB_` Blackboard | 2 | BaseAgentController, AgentBoard |
-| **TOTAL** | **141** | |
+| **TOTAL** | **142** | |
 
 ---