Root fix found during T21.4 G10 dogfood: deploy_qualify.py main() required
GITEA_SERVER/GITEA_REPO env vars that only CI exports — the await_operation
first-class tool therefore could never resolve a real verdict (silent
pending). Fallback to gitea_auth canonical defaults when env is absent;
CI behavior unchanged (env always exported).
Root fix found during T21.4 G10 dogfood: deploy_qualify.py main() required
GITEA_SERVER/GITEA_REPO env vars that only CI exports — the await_operation
first-class tool therefore could never resolve a real verdict (silent
pending). Fallback to gitea_auth canonical defaults when env is absent;
CI behavior unchanged (env always exported).
Propagation: deploy qualification authority touched; no umbrella membership changes; dependent umbrellas unaffected (single-script env fallback, verified by test_deploy_qualify.py + test_ci_event_wait.py 31 green).
The await_operation first-class tool (and any local deploy_qualify.py
caller) never exported GITEA_SERVER/GITEA_REPO, so main() printed
'pending' unconditionally — the first-class wait could never resolve
success even against a green, converged deployment. CI behavior is
unchanged (env always exported there); the fallback only fires when
the caller omitted the vars. Root-caused live in T21.4 G10 dogfood.
🤖Headless spec gate (non-blocking, #204 first slice)
Spec-gate agent produced no text output — check runner logs.
Deterministic floors still govern the merge
This comment is advisory. Required checks (lint, tests, canaries, type-check, coverage, dependency lock, impact gate) remain the merge authority per docs/adversarial-review.md proportionality.
🤖 **Headless spec gate (non-blocking, #204 first slice)**
Spec-gate agent produced no text output — check runner logs.
<details><summary>Deterministic floors still govern the merge</summary>
This comment is advisory. Required checks (lint, tests, canaries, type-check, coverage, dependency lock, impact gate) remain the merge authority per docs/adversarial-review.md proportionality.</details>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Root fix found during T21.4 G10 dogfood: deploy_qualify.py main() required
GITEA_SERVER/GITEA_REPO env vars that only CI exports — the await_operation
first-class tool therefore could never resolve a real verdict (silent
pending). Fallback to gitea_auth canonical defaults when env is absent;
CI behavior unchanged (env always exported).
Propagation: deploy qualification authority touched; no umbrella membership changes; dependent umbrellas unaffected (single-script env fallback, verified by test_deploy_qualify.py + test_ci_event_wait.py 31 green).
🤖 Headless spec gate (non-blocking, #204 first slice)
Spec-gate agent produced no text output — check runner logs.
Deterministic floors still govern the merge
This comment is advisory. Required checks (lint, tests, canaries, type-check, coverage, dependency lock, impact gate) remain the merge authority per docs/adversarial-review.md proportionality.