Skip to content

ci(hydra-gates): move the pin v1.0.1 -> v1.3.0 so gates can declare not-applicable - #160

Merged
rubenvdlinde merged 1 commit into
developmentfrom
ci/hydra-gates-pin-v1.3.0
Aug 5, 2026
Merged

rubenvdlinde merged 1 commit into
developmentfrom
ci/hydra-gates-pin-v1.3.0

Conversation

@rubenvdlinde

@rubenvdlinde rubenvdlinde commented Aug 5, 2026 •

Copy link
Copy Markdown
Contributor

Why the "GATES … DID NOT RUN" failure is not about skipped producers

hydra-gates-require-full-coverage (default ON) fails a run when a gate whose subject matter EXISTS did not report. Its contract, quoting the input's own description:

A gate that emits nothing at all still counts against coverage: not-applicable must be DECLARED.

v1.0.1 contains ZERO _skip calls. It has no na / structural / wiring vocabulary at all, so a gate whose prerequisite is absent emits nothing and is counted as "DID NOT RUN". v1.3.0 contains 36 such declarations.

Measured on this repo

Run 31019022177 on development:

[hydra-gates] COVERAGE: 58 of 61 declared gates reported a result.
[hydra-gates] GATES THAT DID NOT RUN: 4 24 33
RESULT: ALL GATES PASSED — EXCEPT GATES 4 24 33, WHICH DID NOT RUN.

None of those three is starved by a skipped producer job — worth recording, because that is the natural assumption:

gate actual input why it did not report
4 composer-audit composer.json/lock in the diff diff-scoped out under ADR-020
24 integration-parity scripts/check-integration-parity.sh in this repo Newman does not feed it at all
33 axe-core tests/axe/report.json Playwright writes it only when enable-axe: true

In that same run Playwright PASSED and Newman RAN (71 requests / 111 assertions across 2 collections) and gates 24/33 still did not report. That is the direct proof that un-skipping the producers is not the fix for this failure — the pin is.

Under v1.3.0, gate-24 declares itself na for a repo that registers no integration leaves (no new LeafDescriptor( in lib/, no registerIntegration( in src/), and gates listed NOT APPLICABLE are excluded from the verdict rather than failing it.

No gate was weakened, waived or switched off — this lets gates declare what they did not check instead of going silent.

…ot-applicable

hydra-gates-require-full-coverage (default ON) fails the run when a gate
whose subject matter exists did not report, and its contract is that a
legitimately not-applicable gate must DECLARE itself: 'A gate that emits
nothing at all still counts against coverage.'

v1.0.1 contains ZERO _skip calls — it has no na/structural/wiring vocabulary
whatsoever, so any gate whose prerequisite is absent emits nothing and is
counted as DID NOT RUN. v1.3.0 contains 36 such declarations.

Measured here, run 31019022177 on development:
  COVERAGE: 58 of 61 declared gates reported a result.
  GATES THAT DID NOT RUN: 4 24 33

None of the three is starved by a skipped producer job: gate-4 is diff-scoped
out, gate-24's input is scripts/check-integration-parity.sh in this repo, and
gate-33's input needs enable-axe. In that run Playwright PASSED and Newman RAN,
and 24/33 still did not report.
@github-actions

github-actions Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Quality Report — ConductionNL/doriath @ bf155c3

Check PHP Vue Security License Tests
lint ✅
phpcs ✅
phpmd ❌
psalm ✅
phpstan ✅
phpmetrics ✅
eslint ✅
stylelint ✅
build ✅
check-manifest ✅
test-l10n ❌
composer ✅ ✅ 115/115
npm ✅ ✅ 561/561
PHPUnit ✅
Newman ❌
Playwright ✅
Hydra gates ✅

Quality workflow — 2026-08-05 17:31 UTC

Download the full PDF report from the workflow artifacts.

@rubenvdlinde
rubenvdlinde merged commit 170485b into development Aug 5, 2026
31 of 35 checks passed
This was referenced Aug 5, 2026
@rubenvdlinde
rubenvdlinde deleted the ci/hydra-gates-pin-v1.3.0 branch August 14, 2026 09:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant