docs(bf-5occ): document position format mismatch between simulator and registry

- Registry coordinate system: X=width, Y=height, Z=depth
- Simulator coordinate system: X=width, Y=depth, Z=height
- Y and Z axes are swapped between systems
- registry_bridge.go passes positions without coordinate transformation
- Required fix: swap Y and Z when calling registry methods
- Affects fusion engine, coverage optimization, and position-based tracking

Acceptance criteria:
- Registry's expected position format is documented ✅
- Actual format from simulator is documented ✅
- Format differences are identified ✅
- Required transformations are documented ✅

notes/bf-5occ-findings.md

@@ -1,7 +1,11 @@
-# Position Format Validation: Registry vs Simulator
+# bf-5occ: Position Format Validation - Findings
 
 ## Overview
 
+**Bead ID:** bf-5occ
+**Task:** Validate position formatting for registry - check that positions received by registry_bridge.go are correctly formatted for registry consumption.
+**Status:** ❌ **FORMAT MISMATCH IDENTIFIED**
+
 Analysis of position data flow from simulator → registry_bridge → fleet registry identified a **coordinate system mismatch** between simulator and registry coordinate systems.
 
 ## Registry's Expected Position Format