---
staging_status: SUCCESS
work_item: ORCH-062
stage: deploy-staging
author_agent: deployer
status: success
created_at: 2026-06-09
model_used: claude-opus-4-8
timestamp: 2026-06-09T16:53:42Z
base_url: http://localhost:8501
---

# Staging Gate Log

Staging test suite completed against the live staging environment (`orchestrator-staging`, port 8501).

- **Mode:** stub
- **Result:** 8/10 checks PASS — **exit code 0**
- **REAL failed:** none
- **Verdict:** SUCCESS (infra-waived)

The canonical invocation was run inside the `orchestrator-staging` container
(`docker exec … python3 /repos/orchestrator/scripts/staging_check.py --base-url http://localhost:8501 --mode stub`),
so B6 registry-isolation read the running instance's own `.env.staging` process-env (sandbox present, prod ET/ORCH absent).

## Block results

- **[A] SMOKE** — A1 `/health` 200, A2 `/queue` 200, A3 `ORCH_STAGING=true` — all PASS.
- **[B] ACCESS** — B4 Plane sandbox (R), B5 Gitea sandbox (R+push=true), B6 registry isolation — all PASS.
- **[C] E2E (stub)** — C7 create issue (PASS), C8 trigger pipeline (PASS), C9a/C9b waived (see below).

## INFRA-WAIVED (ORCH-061, observability)

```
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
```

C9a/C9b are the two sandbox-infra-only checks (sandbox branch / analyst-job) that depend on SANDBOX bot accounts being project members — not on the pipeline. They are tolerated per ORCH-061 because every REAL check is green; the suite still exits 0. Per the verdict contract, the exit-code → `staging_status` mapping is unchanged: exit 0 → SUCCESS.

Advance to `deploy`.
