`platform-build` has `continue-on-error: true` as a Phase 3 interim
mask while mc#664 handler test failures are in flight. In Gitea,
continue-on-error jobs report result="failure" in the needs context
(unlike GitHub Actions which reports "success"). This caused the
all-required sentinel to hard-fail on every PR.
Add PHASE3_MASKED = {"platform-build"} to the sentinel script so
platform-build failures are treated as Phase 3 suppressed. Remove
this exclusion when mc#664 is resolved and platform-build is healthy.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
The sentinel's Python filter was excluding null (in-flight) and success from
the bad-list, but NOT cancelled. With continue-on-error: true on
platform-build (mc#664 interim mask), failing tests cause the job to
report 'cancelled' (not 'failure'). These cancelled results must not
hard-fail the sentinel while the interim mask is active.
Also adds an INFO line for any cancelled jobs so operators can see the
CoE-masked failures without the sentinel failing.
Bug introduced in 4f7ecc5a.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
The all-required sentinel was reporting no status to the Gitea Actions
API (continue-on-error: true suppresses status entries), so the required
check CI / all-required (pull_request) never appeared in the combined
commit status. gate-check-v3 (Signal 6) treats a missing required
check as failing, causing all PRs to block even when all deps are
green.
Fix: continue-on-error: false on all-required so it always reports.
Phase 3 safety is preserved — platform-build carries continue-on-error:
true, masking its failures to null; all-required sees null as "not bad"
and exits 0. When mc#664 lands (PR #669) the CoE flip on
platform-build completes Phase 3 exit.
Fixes: gate-check-v3 false-positive BLOCKED on all open PRs.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
