eric/ConfigKit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Identify conflicting sequence registration positions

Browse Source
This commit is contained in:
Eric Rakestraw
2026-10-24 00:15:23 +00:00
parent 42663cf07c
commit 57edb8ec19
3 changed files with 51 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/roadmap/remediation.md
View File

@@ -319,7 +319,13 @@ Add ordinary/layered parity and warning-plus-later-error regressions.
## 9. Identify Conflicting Application Registrations In Diagnostics — P2
Status: [ ] Open.
Status: [x] Complete.
Completion: definition validation retains original one-based registration
positions and names both positions in each overlap diagnostic. No input path or
new public diagnostic structure is invented. A mixed-selector regression verifies
multiple conflicts even after an earlier invalid registration is skipped.
Verified registration/facade coverage through `./scripts/check.sh`.
Owner: [`compileSequenceIdentityPolicy`](../../internal/engine/sequence_registration.go),
lines 119–128.