feat(simulation): establish polygon S0 qualification

docs/01_IMPLEMENTATION_PLAN.md

@@ -24,6 +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 | STARTED, NOT ACCEPTED — product/SRS and ADR 0015 define a separate qualification boundary; SIM S0 has a strict candidate D-only/version/clock/port/process profile and read-only doctor. No target-worker evidence, rover run, navigation/safety acceptance or real actuator authority exists |
 
 USB project copying remains optional ground truth rather than a blocker for the
 now-verified network path. Owner-operated LixelGO traffic verifies the MQTT
@@ -121,6 +122,32 @@ control is plugin-owned. A plugin-commanded acquisition sends one canonical STOP
 and seals locally after protocol-reported standby; an operator-manual acquisition
 still stops and seals only local reception and reports scanner state as unknown.
 
+## Parallel branch — Simulation Polygon
+
+The Polygon branch follows
+[`docs/12_SIMULATION_POLYGON_PRODUCT_AND_SRS.md`](12_SIMULATION_POLYGON_PRODUCT_AND_SRS.md)
+and
+[`ADR 0015`](adr/0015-simulation-polygon-qualification-boundary.md).
+It does not reorder or weaken the K1 physical-evidence gates in this document.
+Its first gate is SIM S0:
+
+- candidate Windows 11/WSL2 Ubuntu 24.04 worker profile;
+- all mutable runtime bytes physically on D;
+- ROS 2 Jazzy, Gazebo Harmonic, PX4 v1.17.0, matching `px4_msgs`,
+  Micro XRCE-DDS and Nav2 compatibility;
+- authoritative Gazebo `/clock`;
+- loopback port and deterministic process ownership;
+- target-worker rover/telemetry/pause/step/stop/resource evidence;
+- explicit `GO`, `INCOMPLETE` or `BLOCKED` result.
+
+The repository doctor is side-effect free:
+
+```text
+uv run missioncore-sim s0 doctor --json
+```
+
+Without admitted target-worker evidence its correct result is `INCOMPLETE`.
+
 ## Stage 0 — repository and host baseline
 
 Deliverables: