From 758b375e7eb3a4674eb48cb601ff11df9b6466c4 Mon Sep 17 00:00:00 2001 From: sindoring Date: Mon, 13 Jul 2026 14:23:23 +0400 Subject: [PATCH] docs(M01): claim coordinate golden fixtures Work-Package: M01-QAR-COORD-FIXTURES-001 Agent: sindo-main-codex Tests: not applicable (claim only) Fidelity: pinned AzerothCore spawn, raw ADT metadata and build 12340 observations scoped --- .../claims/M01-QAR-COORD-FIXTURES-001.md | 77 +++++++++++++++++++ 1 file changed, 77 insertions(+) create mode 100644 coordination/claims/M01-QAR-COORD-FIXTURES-001.md diff --git a/coordination/claims/M01-QAR-COORD-FIXTURES-001.md b/coordination/claims/M01-QAR-COORD-FIXTURES-001.md new file mode 100644 index 0000000..8ae80c5 --- /dev/null +++ b/coordination/claims/M01-QAR-COORD-FIXTURES-001.md @@ -0,0 +1,77 @@ +# M01-QAR-COORD-FIXTURES-001 — Coordinate golden fixtures + + + +## Ownership + +- Target: M01 +- Program: QAR +- Owner/Agent ID: sindo-main-codex +- Branch: `work/sindo-main-codex/m01-coordinate-fixtures` +- Lease expires UTC: 2026-07-15 +- Integrator: M01 milestone integrator + +## Outcome + +Add a versioned, non-proprietary fixture and headless validator joining one +pinned AzerothCore player spawn, raw ADT/MCNK metadata and the five M00 +original-client coordinate observations through coordinate contract version 2. + +## Non-goals + +- Committing ADT files, SQL dumps or original-client screenshots. +- Claiming TrinityCore spawn equivalence without a pinned populated TDB source. +- Migrating renderer/native consumers or rendering a live server spawn. +- Changing coordinate formulas, IDs or `StreamingFocus`. + +## Paths + +- Exclusive: `src/tests/fixtures/coordinate_golden_points.json`, + `src/tools/verify_coordinate_golden_fixtures.gd` +- Shared/hotspots: `docs/modules/coordinate-mapping.md`, this claim +- Generated/ignored: extracted ADT data, server database downloads and Godot metadata + +## Contracts and data + +- Public API/events: no new production API; fixture schema version 1 +- Coordinate contract: version 2, unchanged +- Migration/compatibility: additive test data; fixture consumers reject unknown schema versions +- Consumers: M01 coordinate mapper, future native/renderer/server adapter migrations + +## Dependencies + +- Requires: merged coordinate contract version 2 at `b55bfca` +- Blocks: coordinate consumer migration and golden server-spawn renderer integration +- External state: source evidence reduced to pinned revision, numeric rows and SHA-256 hashes + +## Verification + +- Commands: fixture validator, coordinate mapper probe, M00 calibration, + manifest, coordination and documentation gates +- Fixtures: AzerothCore Human Warrior start; raw `Azeroth_32_48.adt` MCNK + `(3,12)`; five build 12340 camera points +- Fidelity evidence: exact source provenance and mapper outputs with bounded tolerances +- Performance budget: negligible headless JSON and scalar arithmetic + +## Documentation deliverables + +- Inline public API docs: fixture-validator header and field validation functions +- Module specification: fixture schema, provenance, verification and source map +- Data-flow diagram: server/raw/client fixtures into mapper assertions +- State/sequence/dependency diagrams: unchanged; synchronous stateless validation + +## Simplicity and naming + +- Important names introduced: `coordinate_golden_points`, + `verify_coordinate_golden_fixtures` +- Simplest considered solution: one JSON fixture and one existing-style headless script +- Rejected complexity/abstractions: test framework dependency, SQL parser, ADT bytes in Git +- Unavoidable complexity and justification: three independent source categories need explicit provenance +- Measured optimization evidence: not applicable + +## Status + +- State: active +- Done: pinned source and raw-corpus research +- Next: fixture schema, validator, documentation and gates +- Blocked by: