координаты

RENDER.md

@@ -857,6 +857,22 @@ $exe = Join-Path $env:TEMP 'godot-4.6.1-openwc\Godot_v4.6.1-stable_win64.exe'
 - Coordinate contract version 2, renderer radii, cache formats and visual
   quality profiles are unchanged.
 
+## 2026-07-13 Golden Server Spawn Renderer Evidence
+
+- The pinned AzerothCore Human Warrior start at server position
+  `(-8949.95, -132.493, 83.5312)` maps through `CoordinateMapper` to Godot
+  `(17199.159666667, 83.5312, 26016.616666667)`, ADT `(32,48)` and MCNK `(3,12)`.
+- `server_spawn_render_manifest.json` drives the ordinary Eastern Kingdoms
+  checkpoint capture pipeline at that location; no live database or production
+  spawn entity is introduced.
+- A renderer-native emissive marker starts at the exact mapped origin and keeps
+  depth testing enabled so GUI evidence exposes its relationship to terrain.
+- `verify_server_spawn_renderer.gd` rejects drift between the pinned fixture,
+  manifest target/player coordinates and expected ADT ownership. The unified
+  renderer baseline runs this contract check before capture.
+- This closes a coordinate/renderer integration criterion only. It does not
+  claim TrinityCore row equivalence or visual parity with the original client.
+
 ## Practical Rule For Future Work
 
 If something improves quality but creates visible hitch, it is not done. Move it to bake/cache/background work, split finalization over frames, or prewarm it before the player can see it.