---
staging_status: SUCCESS
work_item: ORCH-115
stage: deploy-staging
author_agent: deployer
status: success
created_at: 2026-06-16
model_used: claude-opus-4-8
timestamp: 2026-06-15T23:14:17Z
base_url: http://localhost:8501
---

# Staging Gate Log

Staging test suite completed against the live `orchestrator-staging` container
(8501) via `docker exec` (Docker Engine API over the mounted socket). The suite
ran inside the container so the B6 registry-isolation check reads the registry
from the running instance's own process-env (`.env.staging`).

**Command:**
```
docker exec orchestrator-staging \
  python3 /repos/orchestrator/scripts/staging_check.py \
  --base-url http://localhost:8501 --mode stub
```

**Result: 8/10 checks PASS — exit code 0 → `staging_status: SUCCESS`.**

- REAL failed: none
- All Block A (SMOKE A1–A3), Block B (ACCESS B4–B6), and Block C creation/trigger
  checks (C7, C8) passed.

INFRA-WAIVED: C9a Branch appears in orchestrator-sandbox, C9b Analyst job enqueued in staging queue (known sandbox-infra; real checks green)
VERDICT: SUCCESS (exit 0) — SUCCESS (infra-waived): ['C9a Branch appears in orchestrator-sandbox', 'C9b Analyst job enqueued in staging queue'] are known sandbox-infra checks; all real checks green

Per ORCH-061 waiver tolerance (`staging_infra_tolerance_enabled=True`), the two
infra-only checks C9a/C9b depend on SANDBOX bot accounts being project members —
not on the pipeline — and are tolerated when every REAL check is green. The
script exits 0. Exit-code → verdict mapping is unchanged: trust the exit code.
