---
staging_status: SUCCESS
timestamp: 2026-06-06T08:41:49Z
base_url: http://localhost:8501
---

# Staging Gate Log

Staging test suite completed. All checks passed (10/10).

- Work item: ORCH-044
- Repo: orchestrator (self-hosting → staging gate is real, not a no-op)
- Container: `orchestrator-staging` (port 8501)
- Command (canonical, ran INSIDE the container so B6 reads the instance's own `.env.staging` process-env):
  `python3 /repos/orchestrator/scripts/staging_check.py --base-url http://localhost:8501 --mode stub`
- Exit code: 0

## Results

```
[Block A] SMOKE
  ✓ PASS  A1 GET /health → 200 status=ok
  ✓ PASS  A2 GET /queue → 200 with counts/max_concurrency/resilience
  ✓ PASS  A3 ORCH_STAGING=true (not prod)

[Block B] ACCESS
  ✓ PASS  B4 Plane: sandbox project accessible
  ✓ PASS  B5 Gitea: orchestrator-sandbox accessible, push=true
  ✓ PASS  B6 Registry: sandbox present, prod ET/ORCH absent

[Block C] E2E (mode=stub)
  ✓ PASS  C7 Create issue in Plane SANDBOX
  ✓ PASS  C8 Trigger pipeline via /webhook/plane
  ✓ PASS  C9a Branch appears in orchestrator-sandbox
  ✓ PASS  C9b Analyst job enqueued in staging queue

[CLEANUP]
  ✓ PASS  CLEANUP: deleted branch in orchestrator-sandbox
  ✓ PASS  CLEANUP: deleted Plane issue
  ✓ PASS  CLEANUP DB: deleted job + task rows

RESULT: 10/10 checks PASS
```

> Note: the host in this environment lacks the `docker` CLI, so the canonical
> `docker exec orchestrator-staging ...` was performed via the Docker Engine API
> over `/var/run/docker.sock` (Python stdlib, no host-env leakage). Semantics are
> identical to `docker exec`: the script ran inside `orchestrator-staging` with
> its own `.env.staging` process-env, keeping the B6 registry-isolation check valid.
