fix(control-station): separate lab contours from recordings

docs/14_LIDAR_DATASET_GATEWAY.md

@@ -61,7 +61,7 @@ Implemented now:
   lower-cell coordinates, signed residual and derived inlier mask are
   content-bound and visible as a read-only 3D overlay;
 - a provider-neutral read-only local-surface laboratory result in
-  **Тестировочный контур → Лабораторные работы**, synchronized to the five existing
+  **Тестировочный контур → Лабораторные контуры → LAB E28**, synchronized to the five existing
   RAVNOVES00 scene selectors and a clickable complete-recording timeline;
 - a complete recorded-host-paced 1× worker replay through authenticated
   ingress, K1 normalization, point/pose binding and a bounded latest-wins
@@ -114,8 +114,13 @@ The gateway and current local-surface work are not live device diagnostics.
   inputs. Opening one dataset exposes its source fragments, sparse annotated
   scans, visual overlays and useful analysis inside the expanded source card.
   Opening another source closes the previous one.
-- **Тестировочный контур → Лабораторные работы** owns immutable experiment
-  configurations, accepted LAB instances and visual conclusions such as E29.
+- **Тестировочный контур → Лабораторные контуры** owns immutable experiment
+  configurations and results. The first selector chooses a configuration
+  profile, the second chooses one LAB work inside it, and the output uses one
+  reusable `task → full visual evidence → structured result` template.
+  LAB E28 owns the L2.6 local-surface viewer and review queue; LAB E29 owns the
+  camera-first semantic/geometry result. Published E19–E26 recordings remain a
+  separate profile and are not duplicated into the saved-session catalog UI.
 - A future **Парк** diagnostics surface must require a connected device and a
   dedicated live diagnostic contract. It cannot reuse an offline replay report.
 - Internal replay-run identity, provenance and immutable artifacts remain a