docs(ORCH-058): staging gate re-run — staging_status SUCCESS (10/10 PASS)

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

docs/work-items/ORCH-058/15-staging-log.md

@@ -1,6 +1,6 @@
 ---
 staging_status: SUCCESS
-timestamp: 2026-06-07T09:31:58Z
+timestamp: 2026-06-07T09:50:05Z
 base_url: http://localhost:8501
 ---
 
@@ -13,6 +13,8 @@ Staging test suite completed against the live staging environment. **All checks
   binary is not present in the agent runtime image; the Engine API exec is the exact
   equivalent of `docker exec orchestrator-staging python3 \
   /repos/orchestrator/scripts/staging_check.py --base-url http://localhost:8501 --mode stub`).
+  Running inside the container is required so B6 (registry isolation) reads the staging
+  instance's own process-env (`ORCH_PROJECTS_JSON` = sandbox only).
 - Script: `/repos/orchestrator/scripts/staging_check.py` (bind-mount).
 - Mode: `stub`
 - Exit code: `0`
@@ -25,7 +27,7 @@ Staging test suite completed against the live staging environment. **All checks
   ORCH-33 Staging Check Suite
   base_url : http://localhost:8501
   mode     : stub
-  utc_time : 2026-06-07T09:31:50.514185+00:00
+  utc_time : 2026-06-07T09:50:05.706197+00:00
 ============================================================
 
 [Block A] SMOKE
@@ -57,4 +59,5 @@ Staging test suite completed against the live staging environment. **All checks
 
 Note: B6 registry isolation passed (sandbox present; prod ET/ORCH absent), confirming the
 check ran inside the staging instance's own process-env as required — no false-FAIL/spurious
-rollback risk.
+rollback risk. This is a re-run of the staging gate (prior SUCCESS at 09:31:58Z); verdict
+unchanged: SUCCESS.