---
staging_status: SUCCESS
work_item: ORCH-090
stage: deploy-staging
author_agent: deployer
status: success
created_at: 2026-06-09
model_used: claude-opus-4-8
timestamp: 2026-06-09T18:30:25Z
base_url: http://localhost:8501
---

# Staging Gate Log

Staging test suite completed against the live staging environment
(`orchestrator-staging`, 8501), run canonically inside the container
(ORCH-048, ADR-001):

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

**Verdict: SUCCESS** (exit code 0).

## Results

Result: 8/10 checks PASS. All REAL (pipeline) checks are green:

- **Block A (SMOKE)**: A1 `/health`, A2 `/queue`, A3 `ORCH_STAGING=true` — PASS
- **Block B (ACCESS)**: B4 Plane sandbox, B5 Gitea sandbox (push=true), B6 registry
  isolation (sandbox present, prod ET/ORCH absent) — PASS
- **Block C (E2E, stub)**: C7 create issue in SANDBOX, C8 trigger pipeline via
  `/webhook/plane` — PASS; C9a/C9b — waived sandbox-infra

REAL failed: none.

## Infra waiver (ORCH-061)

The two failed checks are known sandbox-infra checks (C9a branch appears in
`orchestrator-sandbox`, C9b analyst-job enqueued) — they depend on SANDBOX bot
accounts being members of the sandbox Plane project, not on the pipeline. They
were waived per ORCH-061 (`staging_infra_tolerance_enabled=True`); the script
still exited 0 fail-closed because every REAL check is green.

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

Exit code remains the source of truth (fail-closed: any REAL failure still yields
exit 1).
