docs(simulation): record S1 target bootstrap and UI gates

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

@@ -51,8 +51,9 @@ reports easy to misuse.
     backend is C-backed and currently serves unrelated co-tenants.
 13. S1 uses exact `px4_msgs` directly. The experimental
     `px4-ros2-interface-lib` is not a mandatory S1 dependency.
-14. A top-level Polygon UI is gated on accepted contracts and a proven S1
-    backend lifecycle with persisted run history.
+14. A read-only direct UI-0 run view may follow proven target S1B lifecycle and
+    persisted history. Top-level Polygon UI and control remain gated on accepted
+    S1 target command/lifecycle 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
@@ -147,3 +148,9 @@ namespace creation, live readiness probes, restart-safe PID/start-token
 reconciliation and Gazebo world-control/PX4 command adapters remain open. The
 worker port deliberately fixes ownership semantics without prematurely fixing
 the eventual transport.
+
+Commit `630d1ae` subsequently passed a D-only `MissionCore-Sim` bootstrap:
+the exact Git archive SHA was verified, both S1 test modules returned
+`20 passed`, and the test process-residue record was empty. This accepts target
+executability of the foundation only; it does not change the open real-provider
+boundaries above.