fix(shaderdebugger): wire Refresh All to reload tracked shaders

[drsnuggles8]

Summary

• The Shader Debugger panel's "Refresh All" button was a no-op TODO.
• Wires it to ShaderLibrary::ReloadShaders() for both Renderer3D and Renderer2D's shader libraries — the same reload path (Shader::Reload()) used by the filewatch hot-reload, and already exposed via Lua/C# scripting (ShaderLibrary3D_ReloadAll / ShaderLibrary2D_ReloadAll) and the olo_shader_reload MCP tool, so this matches established convention rather than introducing a new one.
• Compile errors surface identically to the automatic hot-reload path, via the existing OnCompilationEnd/OnReloadEnd ShaderDebugger hooks.

Fixes #594

Test plan

• OloEditor Debug build succeeds (proves the code compiles/links correctly)
• OloEngine-Tests Debug build succeeds
• ShaderCompileFailureRecovery.* (the Shader compile/link failure crashes the debug editor (OLO_CORE_VERIFY → DEBUGBREAK) instead of degrading gracefully #568/fix(shader): recover gracefully from GLSL compile/link failures instead of crashing #583 graceful GLSL-failure-recovery contract for this exact reload path) — 3/3 passed
• McpShaderReload.* — 4/4 passed
• Ran the editor and confirmed it launches/renders correctly with no regressions

[coderabbitai]

Warning

Review limit reached

@drsnuggles8, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 59 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Repository UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 93de18ce-6370-4171-bf7e-066f058a2daf

📥 Commits

Reviewing files that changed from the base of the PR and between 5a027f5 and f4db6dc.

📒 Files selected for processing (1)

• OloEngine/src/OloEngine/Renderer/Debug/ShaderDebugger.cpp

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud