Implement RAII patterns

A game object needs to maintain a texture handle and must free it when the object is destroyed, but game code currently leaks textures when exceptions occur during initialization. Implement an RAII wrapper that acquires the texture in its constructor and releases it in the destructor, and replace existing manual acquire/release calls so texture lifetime is exception-safe. Verify with a fail-in-constructor test.

Before I push the RAII wrapper for texture handles, make review simple: show a minimal example of acquiring a texture with the wrapper and how it behaves when an exception is thrown during object construction, include the destructor’s single responsibility comment, and mark places where manual calls must be removed. Flag any API changes that will require small call-site edits.

A level loader threw halfway through creating actors and several textures leaked. I suspect manual release calls are scattered and not exception-safe. I don’t know which constructors might throw or which call sites depend on the old manual lifetime. Advise whether I should introduce a lightweight RAII handle class and replace all manual calls in one pass, or wrap constructors with try/catch and clean up on error. Which minimizes risk and how to implement the chosen patch safely?

Over multiple modules, resource leaks happen whenever constructors throw because we rely on manual release across many call sites. Where are we losing time and credibility, and what habit should we change? Recommend adopting RAII as a default for all external resources, require constructors to either complete or be noexcept with clear cleanup, and provide a short migration plan and a lint rule to flag manual release patterns.