refactor(control-station): separate lidar diagnostics from datasets

docs/14_LIDAR_DATASET_GATEWAY.md

@@ -30,7 +30,9 @@ Implemented now:
 - a fail-closed K1 `lio_pcl` boundary;
 - worker storage admission for `D:\NDC_MISSIONCORE\datasets` and
   `/mnt/d/NDC_MISSIONCORE/datasets`;
-- a visible Dataset Gateway panel in **Данные → Качество LiDAR**.
+- a dedicated, honest dataset catalog in **Полигон → Датасеты**;
+- a separate **Парк → Диагностика LiDAR** surface containing only real sensor
+  recordings and their operational evidence.
 
 Not implemented in S0:
 
@@ -40,6 +42,23 @@ Not implemented in S0:
 - no model training or production promotion;
 - no rolling-map implementation yet.
 
+## Product surface boundary
+
+The gateway is not part of device quality diagnostics.
+
+- **Парк → Диагностика LiDAR** answers whether a selected real sensor recording
+  is present, reproducible and operationally usable. It never mixes public
+  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.
+- **Полигон → Прогоны** owns the resulting algorithm comparison, metrics,
+  provenance and decision.
+
+Before real dataset bytes exist, the catalog shows `Не загружен`, explains the
+blocked storage gate and keeps `Открыть` / `Создать прогон` disabled. An
+architecture contract must not look like an executable dataset tool.
+
 ## Why public recordings look different
 
 GOOSE stores one VLS-128 revolution per annotated `.bin` file. A rotating
@@ -130,7 +149,9 @@ time; TTL/dynamic filtering prevents stale ghosts.
 - [x] GOOSE XYZI and labels remain point aligned.
 - [x] Invalid length and non-finite frames fail closed.
 - [x] K1 mapped increments cannot claim raw-scan fields.
-- [x] React exposes the architectural truth before dataset bytes exist.
+- [x] React exposes an honest catalog/empty state before dataset bytes exist.
+- [x] Dataset Gateway is isolated from real-sensor diagnostics and placed under
+  Polygon qualification.
 - [ ] Worker D root configured.
 - [ ] GOOSE validation archive hash recorded.
 - [ ] First real labeled frame visible in React.