---
staging_status: SUCCESS
work_item: ORCH-112
stage: deploy-staging
author_agent: deployer
status: success
created_at: 2026-06-15
model_used: claude-opus-4-8
timestamp: 2026-06-15T12:11:26Z
base_url: http://localhost:8501
---

# Staging Gate Log

Staging test suite completed against the live staging environment (`orchestrator-staging`,
port 8501), executed inside the container via the canonical path
`/repos/orchestrator/scripts/staging_check.py --base-url http://localhost:8501 --mode stub`
(ORCH-048: B6 registry-isolation reads `.env.staging` from the running instance's own process-env).

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

- REAL failed: none
- SANDBOX_INFRA failed (waived, ORCH-061): C9a, C9b

The two failing checks (C9a "Branch appears in orchestrator-sandbox", C9b "Analyst job enqueued in
staging queue") are the known sandbox-infra checks that depend on SANDBOX bot accounts being project
members — not on the pipeline. With every REAL check green, the suite waives them and exits 0.

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

Block A (SMOKE): A1 /health 200, A2 /queue 200, A3 ORCH_STAGING=true — all PASS.
Block B (ACCESS): B4 Plane sandbox, B5 Gitea push, B6 registry isolation — all PASS.
Block C (E2E, stub): C7 create issue PASS, C8 trigger pipeline PASS, C9a/C9b waived sandbox-infra.

Staging gate passed. Task may advance to the `deploy` stage.
