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

# Staging Gate Log

Staging test suite completed against the live staging environment (`orchestrator-staging`,
port 8501, mode=stub). Ran canonically **inside the container** via `docker exec` (ORCH-048)
so the B6 registry-isolation check reads `.env.staging` from the running instance's own
process-env.

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

- REAL failed: none
- All REAL checks (A1–A3 smoke, B4–B6 access incl. registry isolation, C7–C8 E2E
  create-issue / trigger-pipeline) are 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) — C9a/C9b are the two known sandbox-infra checks (depend on SANDBOX
bot accounts being project members, not on the pipeline) and are tolerated under ORCH-061
waiver tolerance (`staging_infra_tolerance_enabled=True`) since every REAL check passed.

ORCH-103 is a docs+tests + new `deploy/bundled/` and `scripts/bootstrap_bundle.py` change;
`src/**`, the root compose, Dockerfile, `STAGE_TRANSITIONS`/`QG_CHECKS`/DB schema are untouched,
so no runtime behaviour regression is expected — consistent with the all-green REAL checks.
