docs(M01): mark coordinate fixtures ready

Work-Package: M01-QAR-COORD-FIXTURES-001

Agent: sindo-main-codex

coordination/claims/M01-QAR-COORD-FIXTURES-001.md

@@ -1,6 +1,7 @@
 # M01-QAR-COORD-FIXTURES-001 — Coordinate golden fixtures
 
 <!-- OPENWC_CLAIM:M01-QAR-COORD-FIXTURES-001:sindo-main-codex:2026-07-15 -->
+<!-- OPENWC_HANDOFF:READY:M01-QAR-COORD-FIXTURES-001:ce4f7ec -->
 
 ## Ownership
 
@@ -71,7 +72,38 @@ original-client coordinate observations through coordinate contract version 2.
 
 ## Status
 
-- State: active
-- Done: pinned source and raw-corpus research
-- Next: fixture schema, validator, documentation and gates
+- State: ready-for-review
+- Done: pinned source research, schema 1 fixture, headless validator, module
+  documentation and all package gates
+- Next: integrator review and merge before coordinate consumer migration
 - Blocked by:
+
+## Handoff
+
+- Commit: `ce4f7ec`
+- Branch: `work/sindo-main-codex/m01-coordinate-fixtures`
+- Outcome: one versioned fixture now joins a pinned AzerothCore Human Warrior
+  spawn, private raw MCNK metadata and five original-client build 12340 points
+  through coordinate contract version 2
+- Contract/schema: additive test fixture schema 1; production coordinate API and
+  contract version 2 are unchanged; proprietary bytes remain outside Git
+- Verification: golden fixture PASS (`1` server spawn, `1` raw ADT chunk, `5`
+  original-client points); CoordinateMapper PASS (`5` golden points, `8` tile
+  boundaries, `2` raw MCNK cases, `5` yaw cases); M00 calibration PASS with
+  maximum error `0.000015`; renderer manifest PASS (`7` checkpoints); coordination,
+  documentation, dependency and whitespace checks passed
+- Fidelity: AzerothCore source pinned at revision
+  `68fcf0098b16388093989627f37be530fc91f07d`; private
+  `Azeroth_32_48.adt` SHA-256
+  `D66E27FD82B461AE38B78562952AED428E619777A3F3E35DD8FF97444644770A`;
+  server and raw data independently resolve tile `(32,48)` and chunk `(3,12)`
+- Rebuild: no proprietary input is required to rerun the committed fixture;
+  local ignored renderer resources are still required by the inherited M00
+  manifest probe
+- Remaining risks: TrinityCore equivalence needs a pinned populated TDB snapshot;
+  live server adapter, renderer integration and MDDF/MODF Euler semantics remain
+  subsequent M01 work
+- Recommended merge order: after coordinate contract version 2 (`b55bfca`) and
+  before live coordinate consumer migration
+- Documentation: coordinate-mapping module inputs/outputs, persistence, data-flow
+  diagram, verification, capability matrix, risks and source map updated