fix(rendering): bound portal resource lifetime

Separate logical ownership, render publication, and GPU retirement across live entities, landblocks, particles, textures, mesh arenas, portal/UI teardown, and per-frame scratch storage. Add bounded DAT/texture caches, upload budgets, three-frame fence retirement, exact-incarnation appearance reconciliation, frame pacing, and extensive lifetime conformance coverage.\n\nThe seven-destination connected route now cuts peak working/private memory roughly in half, returns Caul to 125-153 FPS locally, and produces no WER or AMD reset.\n\nCo-authored-by: OpenAI Codex <codex@openai.com>

docs/architecture/code-structure.md

@@ -4,7 +4,7 @@
 "Code Structure Rules" section in `CLAUDE.md`.
 **Purpose:** Describe the desired structural state of the App layer,
 explain the rules we've adopted, and lay out the safe extraction
-sequence from today's reality (one 10,304-line `GameWindow.cs`) to the
+sequence from today's reality (one 15,288-line `GameWindow.cs`) to the
 target (thin `GameWindow`, small focused collaborators).
 **Companion to:** [`acdream-architecture.md`](acdream-architecture.md)
 (the layered architecture) and
@@ -20,7 +20,7 @@ layer is wire-compatible, the UI has a stable contract, plugins load.
 The structural debt is concentrated in **one file**:
 
 ```
-src/AcDream.App/Rendering/GameWindow.cs   10,304 lines
+src/AcDream.App/Rendering/GameWindow.cs   15,288 lines
 ```
 
 `GameWindow` is the single object that:
@@ -75,28 +75,13 @@ delegate to a collaborator for the substance.
 a GL or windowing namespace, we've lost the ability to test it without
 a graphics context, and the layer split becomes fiction.
 
-**How to apply:** The only currently-allowed seams from Core into the
-WB / GL world are:
-
-- `WorldBuilder.Shared` — stateless helpers (`TerrainUtils`,
-  `TerrainEntry`, `RegionInfo`).
-- `Chorizite.OpenGLSDLBackend.Lib` — stateless helpers
-  (`SceneryHelpers`, `TextureHelpers`).
-
-Both are leaf namespaces with no GL state. If you need a new seam (e.g.
-WB's `ObjectMeshManager` needs to be visible from Core), the change
-**must** come with an inventory-doc update justifying it and ideally a
-slim interface in Core that the App layer implements.
-
-**Current reality:** `src/AcDream.Core/AcDream.Core.csproj` references
-`Chorizite.OpenGLSDLBackend` (not just `OpenGLSDLBackend.Lib`). This is
-historical. Two Core files import from it:
-- `World/SceneryGenerator.cs` — `Chorizite.OpenGLSDLBackend.Lib`
-- `Textures/SurfaceDecoder.cs` — `Chorizite.OpenGLSDLBackend.Lib`
-
-Both use the stateless `Lib` namespace only. The full project reference
-is wider than it needs to be; tightening it to just `WorldBuilder.Shared`
-+ a stateless-helpers shim is a candidate future cut, but not urgent.
+**How to apply:** Phase O removed both external WorldBuilder/backend project
+references. The only currently allowed seams are the GL-free helpers owned in
+our tree under `src/AcDream.Core/Rendering/Wb/`: `TerrainUtils`,
+`TerrainEntry`, `RegionInfo`, `SceneryHelpers`, and `TextureHelpers`.
+`ObjectMeshManager` and every GL resource owner remain in App. If Core needs a
+new capability, define a narrow Core interface and implement it in App; adding
+a new project reference requires an inventory-doc update explaining why.
 
 ### Rule 3: UI panels target `AcDream.UI.Abstractions` only
 
@@ -159,11 +144,12 @@ Today:
 - `tests/AcDream.Core.Tests/` ← `src/AcDream.Core/`
 - `tests/AcDream.Core.Net.Tests/` ← `src/AcDream.Core.Net/`
 - `tests/AcDream.UI.Abstractions.Tests/` ← `src/AcDream.UI.Abstractions/`
+- `tests/AcDream.App.Tests/` ← `src/AcDream.App/`
 
-`AcDream.App` does **not** yet have a test project. The RuntimeOptions
-extraction is the trigger to create `tests/AcDream.App.Tests/`. Future
-App-layer tests (LiveSessionController, SelectionInteractionController,
-etc.) go there.
+`tests/AcDream.App.Tests/` now exists and owns App-layer controller, streaming,
+render-resource lifetime, retained-UI, and `RuntimeOptions` tests. New App tests
+belong there; do not place GL-free Core behavior in that project merely because
+App currently wires it.
 
 ---