dev-scene-management

Use Addressables.LoadSceneAsync with LoadSceneMode.Additive and await it via UniTask instead of the synchronous SceneManager.LoadScene. Report progress through AsyncOperationHandle.PercentComplete and call SceneManager.SetActiveScene once loading succeeds.

Give each scene a self-contained Bootstrapper MonoBehaviour that creates pure C# systems in Awake and injects them into views via Construct methods. When a scene has more than eight systems or needs child scopes, migrate to a VContainer LifetimeScope.

Use VContainer when a scene has many dependencies, roughly more than eight systems, or requires child scopes and automatic disposal. For simpler scenes, manual constructor injection in a Bootstrapper keeps the dependency tree explicit and lightweight.

Only services that genuinely must persist across all scenes, such as AudioManager, AnalyticsService, and InputSystem. Scene-scoped objects like GameManager, UIManager, PlayerController, and EnemyManager must be re-instantiated per scene by their Bootstrapper.

Memory grows when Addressable handles loaded by the scene are not released or event subscriptions remain active. Release all scene-owned handles, unsubscribe scene-scoped events, then call Resources.UnloadUnusedAssets and GC.Collect after major transitions.