fix(control-station): align lidar viewer and expose polygon

docs/01_IMPLEMENTATION_PLAN.md

@@ -164,8 +164,8 @@ fresh loopback-only namespace, the run reached `completed`, and both provider
 groups stopped without residue. S1C commit `b7ccca3` adds a persistent
 unprivileged worker agent in the same isolation boundary, a bounded Unix-socket
 gateway, an explicit `internal-virtual-only` backend gate and a browser-native
-live panel. UI-2 commit `60e7916` promotes that panel into a worker-gated
-top-level product root and replaces the diagnostic 2D marker with a
+live panel. UI-2 commit `60e7916` promotes that panel into a top-level product
+root and replaces the diagnostic 2D marker with a
 browser-native Three.js Ackermann Rover scene. The exact D-only generation
 passed 35 target tests and one UI-driven provider run with diagnostic Gazebo
 `VehicleState`, eight persisted lifecycle events, terminal `completed` and zero

docs/12_SIMULATION_POLYGON_PRODUCT_AND_SRS.md

@@ -834,15 +834,16 @@ safety policy.
 
 ## 20. UI gate
 
-Polygon is implemented as a capability-gated seventh top-level bounded context:
+Polygon is implemented as a permanent seventh top-level bounded context:
 
 ```text
-Center | Fleet | Observation | Missions | Data | Polygon* | System
-
-* visible only while Mission Core confirms an admitted available Simulation Worker
+Center | Fleet | Observation | Missions | Data | Polygon | System
 ```
 
-Two UI gates are intentionally distinct.
+The product surface and execution capability are intentionally distinct.
+`Полигон` and its dataset catalog remain visible without a worker. Worker
+capability gates only live lifecycle and command actions, which fail closed and
+show an explicit offline state.
 
 The Polygon navigation is task-oriented:
 
@@ -886,7 +887,7 @@ read-only evidence contract backed by the server-owned run repository and is
 composed into UI-2. A shared review deployment requires a reviewed read-only D
 mount or a co-located backend; SSH is not a product data plane.
 
-### UI-2 — worker-gated top-level Polygon
+### UI-2 — permanent Polygon with worker-gated live actions
 
 The full UI-2 control/scenario gate begins only after:
 
@@ -894,8 +895,10 @@ The full UI-2 control/scenario gate begins only after:
 2. S1 target backend lifecycle and command authority are proven;
 3. run history is persisted independently of a browser session.
 
-Commit `60e7916` accepts the presentation/lifecycle slice before all three
-conditions are complete: conditional header root, direct workspace,
+Commit `60e7916` accepted the presentation/lifecycle slice before all three
+conditions were complete. The root is now permanent so datasets and persisted
+evidence remain reachable while the worker is offline; live start/stop and
+commands remain capability-gated. The slice includes the direct workspace,
 virtual-only start/stop, 3D rover inspection, diagnostic ENU pose and read-only
 history. It does not claim command authority. Scenarios, pause/step/reset,
 canonical rover commands, Compare and Report remain planned. UI-2 cannot own

docs/adr/0015-simulation-polygon-qualification-boundary.md

@@ -55,9 +55,10 @@ reports easy to misuse.
 13. S1 uses exact `px4_msgs` directly. The experimental
     `px4-ros2-interface-lib` is not a mandatory S1 dependency.
 14. The read-only direct UI-0 run view consumes proven target S1B persisted
-    history through GET-only server routes. It is hidden from navigation and
-    cannot mutate a run. Top-level Polygon UI and control remain gated on
-    accepted S1 target command/lifecycle behavior.
+    history through GET-only server routes and cannot mutate a run. The
+    top-level Polygon product surface remains visible so datasets and persisted
+    evidence are reachable offline; live lifecycle and command actions remain
+    gated on admitted worker capability and accepted S1 target behavior.
 15. Real actuator authority requires a new decision and physical safety gate.
 16. S0 processes run inside an ephemeral loopback-only Linux network namespace.
     Micro XRCE-DDS Agent's UDP wildcard bind is acceptable only inside that