Skip to content

ci(quality): move hydra-gates-ref v1.0.1 -> v1.3.0 (residual gate-24 is a real gap, documented) - #1153

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

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

Conversation

@rubenvdlinde

Copy link
Copy Markdown
Contributor

One line: hydra-gates-ref: v1.0.1 -> v1.3.0.

This repo's CI is red right now, and it is not this repo's fault

At 2026-08-05T13:52Z, ConductionNL/.github commit f7eaf2a (#164) flipped hydra-gates-require-full-coverage to default true in the shared quality.yml. Every repo references that workflow at @main, so the flip went live everywhere at once. But the flag requires a gate to declare itself not-applicable — and that vocabulary ships in the pinned package:

_skip calls
v1.0.1 (this repo's pin) 0
v1.3.0 36

A pin with no _skip calls cannot say "not applicable". So every gate without subject matter here — 4 (composer-audit, correctly diff-scoped out per ADR-020), 24 (integration-parity), 33 (axe-core, whose producer enable-axe is deliberately off) — became DID NOT RUN and failed the job.

The red is fleet-wide, dated, and caused by a shared-workflow flag meeting a pinned script that predates the vocabulary it needs. It is not a code defect and not anything a PR author did. The control that settles it: decidesk#407 is PHPMD-only with zero npm changes and shows the identical failure, and it passed on pre-13:52Z base runs — the base is a different vintage of the shared workflow, not of the code.

The pin was also four fixes stale

v1.0.1 is f4d9756 (2026-08-03). Every Hydra Gates run this repo has ever made executed a script in which:

PR what it fixed in v1.0.1?
#147 16 gates reported PASS when their helper never ran ❌
#148 gate-33 had no axe report to read, and never said so ❌
#149 gates 6 and 7 reported PASS on an empty scope ❌
#162 gate-5 reported a resolution failure as a security finding ❌

A gate that reports PASS without running emits a tick identical to a real one, which is why nothing in this repo's history shows the difference. Tracked in .github#159.

Measured before opening this PR

Diff-scoped against origin/development, exactly as CI scopes it. Each run in its own mount namespace with a private tmpfs — the runner writes ~50 detail logs to hardcoded /tmp/hydra-gate-<name>.log paths and reads its verdicts back out of them, so two concurrent runs on one host silently corrupt each other's counts (.github#158 item 6). Another agent was running the gates unisolated on the same host during this work, so that is not hypothetical.

v1.0.1   exit 98   FAIL — "GATES THAT DID NOT RUN: 24 33"
v1.3.0   exit 0    PASS — ALL 58 APPLICABLE GATES PASSED, and all 58 ran
                          NOT APPLICABLE: 4 6 7 24 33 — each with a reason

Verified not merely that the job is green but that gates 4, 24 and 33 each name themselves not-applicable and say why. A green that came from somewhere else would not be the fix landing.

Independently confirmed end-to-end by doriath#160, which changed this same single line and nothing else: Hydra Gates went failure -> success.

v1.3.0 is f7eaf2a = .github@main at the time it was cut.

Refs ConductionNL/.github#159


⚠️ This repo does NOT go fully green on this bump, and that is deliberate

Measured on this branch at v1.3.0, diff-scoped:

exit 98 — ALL GATES PASSED — EXCEPT GATES 24, WHICH DID NOT RUN
NOT APPLICABLE: 4 6 7 33

Gate-24 is a genuine structural gap, and the gate says so by name:

[gate-24] integration-parity: SKIPPED (structural) — no scripts/check-integration-parity.sh, but this repo DOES register integration leaves. server↔JS leaf parity (ADR-066 Decisions 4/7) is UNVERIFIED — a leaf whose other half never registered is invisible to this run.

This is not a false positive and it is not something the pin bump caused. Before this change the repo was red on 24 and 33; after it, 33 correctly reports NOT APPLICABLE (its producer enable-axe is deliberately off) and only the real gap remains. The bump strictly improves the signal: it removes the noise and leaves the one finding that is true.

I have deliberately not added hydra-gates-require-full-coverage: false, a continue-on-error, or any waiver to make this green. The fix is to ship scripts/check-integration-parity.sh — a repo that is honestly red is worth more than one that is dishonestly green, which is the entire point of this work.

…failing CI

v1.0.1 is `f4d9756` (2026-08-03) and predates three gate fixes, so every
Hydra Gates run this repo has ever made executed a script in which 16
gates reported PASS when their helper never ran (ConductionNL/.github#147),
gate-33 had no axe report to read and never said so (#148), and gates 6
and 7 reported PASS on an empty scope (#149). The tick was identical
either way, which is why nothing in this repo's history shows it.

That pin is now also RED, and the mechanism is worth writing down.
quality.yml is referenced `@main` while this package is PINNED, so the
two can desync. #164 flipped `hydra-gates-require-full-coverage` to
default true in the shared workflow, and that flag requires a gate to
DECLARE itself not-applicable. v1.0.1 contains ZERO `_skip` calls; v1.3.0
has 36. v1.0.1 has no vocabulary to declare, so every absent prerequisite
became "DID NOT RUN" and failed the job — for gates the repo has no
subject matter for.

Measured on this branch, diff-scoped against origin/development exactly
as CI scopes it, in a private mount namespace with a private tmpfs (the
runner's ~50 /tmp/hydra-gate-*.log paths are shared state and two
concurrent runs corrupt each other's counts, .github#158 item 6):

  v1.0.1  exit 98  FAIL — "GATES THAT DID NOT RUN: 24 33"
  v1.3.0  exit 0   PASS — those gates named NOT APPLICABLE, with reasons

Independently confirmed end-to-end: doriath#160 changed this one line and
nothing else, and its Hydra Gates job went failure -> success.

v1.3.0 is `f7eaf2a` = .github@main at the time it was cut.

Refs ConductionNL/.github#159
@github-actions

github-actions Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Quality Report — ConductionNL/openconnector @ 0231fa1

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

Quality workflow — 2026-08-05 18:20 UTC

Download the full PDF report from the workflow artifacts.

@rubenvdlinde
rubenvdlinde merged commit 3e1d266 into development Aug 5, 2026
34 checks passed
@rubenvdlinde
rubenvdlinde deleted the ci/hydra-gates-v1.3.0 branch August 14, 2026 09:40
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