feat: add Polygon UI-0 run view

docs/01_IMPLEMENTATION_PLAN.md

@@ -24,7 +24,7 @@ Each gate produces evidence and an explicit GO, PAUSE or BLOCKED result.
 | Plugin isolation | GO (laboratory control plane) — vendor backend/frontend and optional scene controls are plugin-owned; manifest/runtime descriptor parity, versioned handshake, lifecycle health and transport correlation fail closed while execution remains in-process |
 | K1 application control | GO (physical staged cycle) — after fixing the PCAP-proven `sint64` time field, one explicit UI launch completed all 14 canonical operations on one control session, reached live `SCANNING + project + init_ready`, displayed real points, then one explicit STOP returned K1 to unbound `READY`. No retry or fallback command was sent. Native-project reuse through LixelGO/USB remains an independent verification |
 | Stage 8 product storage | PAUSE — retention, replication, encryption, capacity monitoring and long-run browser/WASM stress remain deployment gates |
-| Simulation Polygon | SIM S0 GO; S1A complete; S1B real-provider lifecycle PASS — exact commit `6cb1495` passed 25 target tests and one D-only loopback stock-Ackermann run. Mission Core admitted world/startup/DDS health, persisted eight events, sent zero commands and stopped both PGIDs with zero residue. UI-0 implementation is now unblocked. Pause/resume/step/reset, PX4 command delivery, canonical telemetry/frames, watchdog/failsafe, navigation/safety acceptance and real actuator authority remain absent; top-level Polygon remains gated |
+| Simulation Polygon | SIM S0 GO; S1A complete; S1B real-provider lifecycle PASS; UI-0 internal read-only run view PASS — exact commit `6cb1495` passed 25 target tests and one D-only loopback stock-Ackermann run. Mission Core admitted world/startup/DDS health, persisted eight events, sent zero commands and stopped both PGIDs with zero residue. The Control Station now reads that canonical journal through GET-only Polygon API routes and a direct hidden workspace; visual QA opened the real accepted run. Pause/resume/step/reset, PX4 command delivery, canonical telemetry/frames, watchdog/failsafe, navigation/safety acceptance and real actuator authority remain absent; top-level Polygon remains gated |
 
 USB project copying remains optional ground truth rather than a blocker for the
 now-verified network path. Owner-operated LixelGO traffic verifies the MQTT
@@ -162,6 +162,19 @@ groups stopped without residue. Live world control, PX4 command delivery,
 heartbeat/watchdog execution and captured failsafe outcomes remain the next S1
 increments.
 
+UI-0 now consumes the same append-only run repository through
+`GET /api/v1/polygon/runs` and
+`GET /api/v1/polygon/runs/{run-id}`. `QualificationRunStore(read_only=True)`
+does not create, chmod or mutate the configured repository and rejects every
+write transition. The Control Station opens the internal
+`polygon-run-internal` workspace only for the direct
+`?workspace=polygon-run[&run=<id>]` route; it is filtered out of System
+navigation and adds no seventh top-level section. Browser QA loaded the accepted
+real run with eight events, four provider pins, zero commands and the unchanged
+virtual-only authority boundary. A shared operator-facing deployment still
+requires a reviewed read-only D mount/source configuration; UI-0 does not use
+SSH as a product data plane.
+
 ## Stage 0 — repository and host baseline
 
 Deliverables: