claude-bot 28d019a1e2 fix(staging_check): B6 reads registry from running staging instance env ...

B6 false-FAILed because it built the project registry from the
launcher process-env via a host-path hack (sys.path.insert +
importlib.reload), not from the running staging instance. Run from the
host, ORCH_PROJECTS_JSON is unset -> default ET+ORCH registry -> false
FAIL -> spurious deploy-staging -> development rollback.

Variant (v) per ADR-001: remove the host-path hack; canonically run the
suite INSIDE orchestrator-staging via docker exec so src.projects
resolves from /app (PYTHONPATH) with .env.staging. Verdict logic
extracted into pure _evaluate_b6(known) -> (passed, detail) +
_known_project_ids_from_registry() / _run_b6() with deterministic FAIL on
source unavailability. deployer.md and STAGING_CHECK.md updated to the
docker exec command. src/projects.py, .env* and checks A/B4/B5/C
untouched.

Refs: ORCH-048

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

2026-06-06 07:03:31 +00:00

..

orchestrator-deploy-hook.sh

feat(staging): add orchestrator deploy hook with health-check and auto-rollback (ORCH-34)

2026-06-05 09:26:12 +03:00

staging_check.py

fix(staging_check): B6 reads registry from running staging instance env

2026-06-06 07:03:31 +00:00