Skip to content

chore(ci): block on unresolved @e2e anchors in gate-46 - #3574

Merged
rubenvdlinde merged 2 commits into
developmentfrom
chore/gate-46-block-on-e2e-anchors
Sep 10, 2026
Merged

rubenvdlinde merged 2 commits into
developmentfrom
chore/gate-46-block-on-e2e-anchors

Conversation

@rubenvdlinde

Copy link
Copy Markdown
Contributor

Draft, and blocked on two things. Stacked on #3573 and requires ConductionNL/.github#741. Undraft once both have landed.

What this is

One line: hydra-gates-e2e-anchor-blocking: true.

Gate-46 resolves @spec and @e2e by identical rules but blocks only on @spec. The @e2e half is report-only, and the gate itself invites the opt-in once a repo's count is worked down. This is that opt-in.

The measurement that licenses it

Taken with the gate's own resolver, scripts/lib/check_spec_anchors.py from ConductionNL/.github@main — a fresh clone, not a vendored copy, and not a reimplementation — over gate-46's full file scope, with #3573 applied:

files in scope: 3713
total findings: 0
@spec findings: 0
@e2e  findings: 0

Across 9,948 @spec and 163 @e2e openspec/ tags.

The resolver was mutation-checked before the zero was believed. openspec/specs/totally-imaginary/spec.md#nope reported target file not found and openspec/specs/mdm-frontend/spec.md#REQ-999-invented reported anchor not found. A checker that inspects nothing exits exactly like one that inspects everything and finds it clean.

What will make this fail, and it is meant to

A new test whose @e2e anchor names a spec, requirement or scenario that does not exist. That is the whole point: an anchor that resolves to nothing reads as verified coverage and says nothing.

Three anchors still name the live change mdm-views-route-scoping-e2e (see #3573 for why they were left). They resolve today through gate-46's capability index, which spans a spec's in-flight, archived and canonical homes, and will keep resolving after that change is archived. They do not put this repo at risk under the flag.

Why it is separate from #3573

So it can be reverted on its own. If this ever blocks a PR on inherited debt rather than on that PR's own anchors, reverting one line restores the report-only behaviour without disturbing the repointed anchors.

It also has to be separate: until .github#741 merges, quality.yml@main does not declare this input, and an undeclared input is a workflow error rather than a no-op. This PR's own CI will be red until then, which is expected and is why it is a draft.

🤖 Generated with Claude Code

Conduction Release Bot added 2 commits September 10, 2026 11:49
Twenty-eight `@e2e` anchors in tests/e2e/spec-coverage/ named a change
directory rather than the capability's canonical spec. All three changes
they named — mdm-frontend, mdm-merge-ui, mdm-survivorship-override — were
archived on 2026-07-03, so each path has already moved once.

An anchor belongs at `openspec/specs/<capability>/spec.md#<scenario>`. A
spec path is stable; a change path moves on archive, and that move is what
broke the fifteen anchors repaired earlier today. These twenty-eight still
resolve only because gate-46's capability index spans all three homes of a
spec — in flight, archived, canonical — which rescues the reference without
making it honest about where the requirement lives.

Every anchor keeps its fragment. The prefix is the only thing rewritten, so
each line still names the requirement or scenario the test exists for rather
than pointing at a whole file, which resolves while saying nothing.

Verified with the gate's own resolver, scripts/lib/check_spec_anchors.py at
.github@main, over gate-46's full scope of 3,713 files: 0 unresolved
findings across 9,948 @SPEC and 163 @e2e tags. The resolver was
mutation-checked first — an invented capability and an invented fragment
both reported — so the zero is a measurement, not an empty run.

Three anchors are deliberately left naming a change directory. They point
into `mdm-views-route-scoping-e2e`, which is still live and has no spec at
`openspec/specs/mdm-views-route-scoping/spec.md`. Repointing them there
would still pass the gate, because the capability index would resolve it
back to the live change — an anchor naming a file that does not exist and
reading as though it does. They move when that change is archived and its
spec is promoted.
Gate-46 resolves `@spec` and `@e2e` by identical rules but blocks only on
`@spec`; the `@e2e` half is report-only until a repo opts in. This is that
opt-in, and it is set only because the count reached zero first.

Measured with the gate's own resolver — scripts/lib/check_spec_anchors.py
from ConductionNL/.github@main, not a vendored copy and not a
reimplementation — over gate-46's full scope of 3,713 files, after #3573
repointed the last 28 change-directory anchors:

    total findings: 0
    @SPEC findings: 0
    @e2e  findings: 0

across 9,948 @SPEC and 163 @e2e openspec tags. The resolver was
mutation-checked before the zero was believed: an invented capability and an
invented fragment were both reported.

One line, its own commit, so it can be reverted without touching the
repoints it depends on.

REQUIRES ConductionNL/.github#741, which adds the input. Callers resolve
quality.yml@main and an input main does not declare is a workflow error, so
this cannot merge first.
@rubenvdlinde
rubenvdlinde marked this pull request as ready for review September 10, 2026 10:16
@rubenvdlinde
rubenvdlinde merged commit cc5233e into development Sep 10, 2026
12 checks passed
@rubenvdlinde
rubenvdlinde deleted the chore/gate-46-block-on-e2e-anchors branch September 10, 2026 10:16
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