feat: add Polygon UI-0 run view

README.md

@@ -165,9 +165,29 @@ v1.17.0/Gazebo Harmonic stock Ackermann rover in a fresh loopback-only
 namespace, admitted the run only after world/startup/DDS-writer health markers,
 and stopped both owned PGIDs with zero residue. The persisted run reached
 `completed`, contains eight lifecycle events and zero control commands. This
-opens UI-0 implementation; live pause/resume/step/reset, canonical telemetry,
-PX4 command mapping, watchdog/failsafe evidence and the top-level Polygon
-control surface remain gated.
+run is now visible through UI-0: a direct internal read-only Control Station
+surface backed by the same append-only qualification repository. It exposes
+identity, terminal reason, provider pins, events, command count, artifact
+metadata and the virtual-only authority boundary. Live pause/resume/step/reset,
+canonical telemetry, PX4 command mapping, watchdog/failsafe evidence and the
+top-level Polygon control surface remain gated.
+
+Configure a Mission Core backend that can read the accepted D repository and
+open the direct route:
+
+```bash
+export MISSIONCORE_POLYGON_RUNS_ROOT=/mnt/d/NDC_MISSIONCORE/simulation/artifacts/s1/runs
+uv run uvicorn k1link.web.app:app --host 127.0.0.1 --port 8765
+```
+
+```text
+http://127.0.0.1:8765/?workspace=polygon-run&run=<qualification-run-id>
+```
+
+The API provides `GET /api/v1/polygon/runs` and
+`GET /api/v1/polygon/runs/{run-id}` only. Missing configuration returns `503`;
+invalid/corrupt evidence fails closed. The browser receives no D root, artifact
+bytes, command payloads or PX4/process-lifecycle operation.
 
 See the [Polygon product/SRS](docs/12_SIMULATION_POLYGON_PRODUCT_AND_SRS.md),
 [ADR 0015](docs/adr/0015-simulation-polygon-qualification-boundary.md) and the
@@ -272,9 +292,11 @@ revision or content hash. Publishing/vendoring those packages or enforcing an
 immutable donor revision remains a packaging and CI prerequisite.
 
 Polygon is planned as a seventh section. The read-only direct UI-0 run view is
-now permitted by the accepted S1B backend lifecycle and persisted run history,
-but is not yet present in the current shell. Top-level Polygon navigation and
-control remain gated on accepted clock/frame/command/safety behavior.
+implemented inside the current shell but intentionally omitted from all
+top-level and System navigation. It opens only through
+`?workspace=polygon-run[&run=<id>]` and reads the server-owned qualification
+repository. Top-level Polygon navigation and control remain gated on accepted
+clock/frame/command/safety behavior.
 
 The Observation spatial workspace embeds the open-source Rerun Web Viewer
 inside the Mission Core shell. It can open a compatible RRD over same-origin