fix(polygon): unify dataset review workflow

docs/14_LIDAR_DATASET_GATEWAY.md

@@ -65,18 +65,18 @@ The gateway is not part of device quality diagnostics.
   dataset frames into the selected device evidence.
 - **Наблюдение** opens a concrete live or recorded spatial scene.
 - **Данные** owns source-of-record, retention, replay preparation and export.
-- **Полигон → Датасеты** lists admitted evaluation inputs and owns source
-  inspection: source sequences, sparse annotated scans and optional overlays
-  from a selected qualification run.
-- **Полигон → Прогоны** owns the resulting algorithm comparison, metrics,
-  provenance and decision. It does not present the dataset itself as a
-  simulation or continuous vehicle recording.
+- **Полигон → Датасеты** is the single operator surface for admitted evaluation
+  inputs. Opening one dataset exposes its source fragments, sparse annotated
+  scans, visual overlays and useful analysis calculated only for the selected
+  fragment.
+- Internal replay-run identity, provenance and immutable artifacts remain a
+  backend evidence contract. They are not a second operator navigation item
+  and are not presented as vehicle motion.
 
 Before real dataset bytes exist, the catalog explains the blocked storage gate
-and keeps `Открыть` / `Создать прогон` disabled. `Открыть` becomes available
+and keeps `Открыть датасет` disabled. It becomes available
 only after the worker manifest says `frame-ready` and the bounded preview passes
-its own point-alignment and safety checks. `Создать прогон` remains disabled
-until an executable comparison profile exists.
+its own point-alignment and safety checks.
 
 ## Why public recordings look different