docs(M01): claim server spawn renderer evidence #17
@@ -0,0 +1,85 @@
|
|||||||
|
# M01-QAR-SERVER-SPAWN-RENDERER-001 — Golden server spawn renderer evidence
|
||||||
|
|
||||||
|
<!-- OPENWC_CLAIM:M01-QAR-SERVER-SPAWN-RENDERER-001:sindo-main-codex:2026-07-15 -->
|
||||||
|
|
||||||
|
## Ownership
|
||||||
|
|
||||||
|
- Target: M01
|
||||||
|
- Program: QAR/RND
|
||||||
|
- Owner/Agent ID: sindo-main-codex
|
||||||
|
- Branch: `work/sindo-main-codex/m01-server-spawn-renderer`
|
||||||
|
- Lease expires UTC: 2026-07-15
|
||||||
|
- Integrator: M01 milestone integrator
|
||||||
|
|
||||||
|
## Outcome
|
||||||
|
|
||||||
|
Route the pinned AzerothCore Human Warrior spawn fixture through
|
||||||
|
`CoordinateMapper` into the live Eastern Kingdoms renderer and produce
|
||||||
|
repeatable headless contract checks plus GUI screenshot evidence at the mapped
|
||||||
|
ADT tile/chunk.
|
||||||
|
|
||||||
|
## Non-goals
|
||||||
|
|
||||||
|
- Connecting to a live AzerothCore or TrinityCore database.
|
||||||
|
- Claiming TrinityCore spawn equivalence without a pinned populated TDB row.
|
||||||
|
- Changing coordinate formulas, streaming radii, terrain, player movement or
|
||||||
|
production character presentation.
|
||||||
|
- Adding proprietary assets or screenshots to Git.
|
||||||
|
|
||||||
|
## Paths
|
||||||
|
|
||||||
|
- Exclusive: `src/tools/server_spawn_render_manifest.json`,
|
||||||
|
`src/tools/verify_server_spawn_renderer.gd`
|
||||||
|
- Shared/hotspots: `src/tools/capture_render_checkpoints.gd`, renderer runner,
|
||||||
|
coordinate/world-renderer module documentation, `RENDER.md`, this claim
|
||||||
|
- Generated/ignored: Godot UIDs/import metadata and `user://` PNG/JSON evidence
|
||||||
|
|
||||||
|
## Contracts and data
|
||||||
|
|
||||||
|
- Fixture schema and coordinate contract version remain unchanged.
|
||||||
|
- Additive diagnostic checkpoint metadata may request a renderer-native marker;
|
||||||
|
existing M00 checkpoints remain byte-for-byte compatible.
|
||||||
|
- The spawn remains sourced from pinned AzerothCore revision
|
||||||
|
`68fcf0098b16388093989627f37be530fc91f07d`.
|
||||||
|
|
||||||
|
## Dependencies
|
||||||
|
|
||||||
|
- Requires: merged M01 packages through `a07a487`
|
||||||
|
- Blocks: M01 golden server-spawn renderer criterion and milestone closeout
|
||||||
|
- External state: GUI capture requires the existing local extracted/cached
|
||||||
|
renderer corpus; headless contract verification remains non-proprietary
|
||||||
|
|
||||||
|
## Verification
|
||||||
|
|
||||||
|
- Commands: dedicated spawn verifier, coordinate fixture/mapper/boundary gates,
|
||||||
|
renderer baseline dry-run, GUI checkpoint capture and human inspection
|
||||||
|
- Fixture: AzerothCore race `1`, class `1`, map `0`, server position
|
||||||
|
`(-8949.95, -132.493, 83.5312)`
|
||||||
|
- Expected renderer result: Godot position
|
||||||
|
`(17199.159666667, 83.5312, 26016.616666667)`, ADT `(32,48)`, MCNK `(3,12)`
|
||||||
|
- Fidelity classification: server/coordinate integration evidence only; it does
|
||||||
|
not establish full original-client visual parity
|
||||||
|
|
||||||
|
## Documentation deliverables
|
||||||
|
|
||||||
|
- Inline API/tool documentation for new verifier and marker metadata
|
||||||
|
- Coordinate-mapping module capability/evidence update
|
||||||
|
- World-renderer checkpoint input/output/source-map update when marker support is added
|
||||||
|
- Existing synchronous coordinate data-flow diagram updated only if flow changes
|
||||||
|
|
||||||
|
## Simplicity and naming
|
||||||
|
|
||||||
|
- Important names: `server_spawn_render_manifest`,
|
||||||
|
`verify_server_spawn_renderer`, `diagnostic_spawn_marker`
|
||||||
|
- Simplest approach: reuse the existing checkpoint capture pipeline with one
|
||||||
|
dedicated manifest and a renderer-native diagnostic marker
|
||||||
|
- Rejected complexity: live DB adapter, new scene-test framework and production
|
||||||
|
spawn entity implementation before the network/gameplay milestones
|
||||||
|
- Performance: one diagnostic checkpoint outside production runtime
|
||||||
|
|
||||||
|
## Status
|
||||||
|
|
||||||
|
- State: active
|
||||||
|
- Done: merged-package and target evidence audit
|
||||||
|
- Next: implement manifest/verifier/marker, capture GUI evidence and hand off
|
||||||
|
- Blocked by:
|
||||||
Reference in New Issue
Block a user