fix(spec): complete the @spec anchor truncated mid-slug - #3374
Merged
Conversation
gate-46 (spec-anchor-existence) is failing on development, and this is the one finding. The anchor stops at `...-sequence-with-o`, halfway through `one-position-enabled-at-a-time`, so it resolves to nothing. Worth saying where it came from, because the gate's own message truncates the anchor it reports and reads as though the gate did the truncating: the anchor really is cut short in the source, and it arrived with #3360 earlier today. Verified with the gate's own checker: this file goes from 1 finding to 0, and a full-tree run over every lib/**/*.php reports 0. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Contributor
Quality Report — ConductionNL/openregister @
|
| Check | PHP | Vue | Security | License | Tests |
|---|---|---|---|---|---|
| lint | ✅ | ||||
| phpcs | ✅ | ||||
| phpmd | ✅ | ||||
| psalm | ✅ | ||||
| phpstan | ✅ | ||||
| phpmetrics | ✅ | ||||
| eslint | ✅ | ||||
| stylelint | ✅ | ||||
| build | ✅ | ||||
| check-specs | ✅ | ||||
| test-l10n | ✅ | ||||
| test-l10n-parity | ✅ | ||||
| format | ✅ | ||||
| check-schema-l10n | ✅ | ||||
| check-l10n-js | ✅ | ||||
| composer | ✅ | ✅ 174/174 | |||
| npm | ✅ | ✅ 543/543 | |||
| app:check-code | ⏭️ | ||||
| info.xml | ✅ | ||||
| REUSE | ❌ | ||||
| PHPUnit | ✅ | ||||
| Newman | ✅ | ||||
| Playwright | ⏭️ deferred — runs on the promotion into beta/main, not on a pull request into development | ||||
| Hydra gates | ✅ |
Quality workflow — 2026-09-03 13:25 UTC
Download the full PDF report from the workflow artifacts.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
gate-46(spec-anchor-existence) is red ondevelopment, and this is the single finding.The anchor in
TaskSequenceMapper::findNewestForTemplate()stops at...-sequence-with-o, halfway throughone-position-enabled-at-a-time, so it resolves to nothing. It arrived with #3360 earlier today.Worth calling out because the gate's own message truncates the anchor it reports:
That reads as though the gate did the truncating. It did not — the anchor really is cut short in the source, and the heading it should point at is in the same spec file.
Verification
Run with the gate's own checker (
vendor/conduction/hydra-gates/.../check_spec_anchors.py):lib/Db/TaskSequenceMapper.php: 1 finding → 0lib/**/*.php: 0 findingsChecked first whether the three in-flight spec-anchor branches (
fix/license-triangle-and-spec-anchors,wip/spec-anchor-repair,wip/spec-anchor-repair-round2) already covered this file. None of them touch it.🤖 Generated with Claude Code