feat(lidar): add RAVNOVES field review

docs/10_EXTERNAL_PERCEPTION_WORKER.md

@@ -31,6 +31,17 @@ that evidence in Three.js with unrestricted orbit, pan and zoom plus
 intensity/current/candidate/disagreement color modes. The browser never runs
 Patchwork++, parses private firmware or receives a filesystem path.
 
+`missioncore.lidar-field-review/v1` is the separate operator-readable field
+surface. The read-only `/api/v1/lidar/field-reviews` catalog names the exact
+RAVNOVES00 source, timeline and five central urban windows. The bounded
+`/api/v1/lidar/field-reviews/{review_id}/windows/{window_index}` response
+contains a deterministic accumulated map cloud plus masks that were computed
+per original LiDAR sample before accumulation. Its sibling `/preview` endpoint
+returns the content-bound camera JPEG for that window. No source path,
+Patchwork++ binary, worker control or command authority crosses this boundary.
+The legacy E10 source has no intensity, so the API declares it unavailable
+instead of synthesizing a value.
+
 Static K1 3.0.2 firmware evidence confirms that the appliance internally uses
 a Livox MID-360 point/IMU path with richer timestamp/ring semantics and a
 configured MQTT point-cloud downsample factor of four. This creates a concrete