feat: AVE-2026-00082 -- local skill name collision (deterministic router shadowing)- #269 - #281
Merged
Merged
Conversation
…ter shadowing)- #269 Mirrors #269's merge into develop, matching the established pattern (e.g. #270 -> #279 for AVE-2026-00081). Fresh branch off main rather than reusing #280 (develop -> main), whose head/base had diverged enough since #269 merged that a content-only sync commit couldn't resolve GitHub's graph-based mergeability check without either a real merge commit (blocked by this repo's branch-protection rule on develop) or a full rebase of develop (too disruptive to other open work based on it).
5 tasks
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
1 participant
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.
Summary
Mirrors #269's merge into
develop(AVE-2026-00082, local skill name collision / deterministic router shadowing) intomain, matching the established pattern for this repo's dual-branch workflow (e.g. #270 -> #279 for AVE-2026-00081, #266 -> #267 for the framework_sources fix).Supersedes #280. That PR (
develop->main) showed a merge conflict; a content-only sync commit ondevelopsatisfied the record content and this repo's branch-protection rules (no merge commits, signed commits) but couldn't resolve GitHub's graph-based mergeability check for #280 itself, sincedevelopandmainshare a merge-base far enough back that both sides have independently edited the same lines since. Fixing that properly would need either a real merge commit (blocked by branch protection ondevelop) or a full rebase ofdevelopontomain(too disruptive to other open work already based ondevelop, including #277). A fresh branch off currentmaincarrying just this diff -- the same shape as the other already-merged mirror PRs -- avoids both problems.Changes
records/AVE-2026-00082.json+ both conformance fixtures, copied as-published fromdevelop.README.md/CHANGELOG.md: record added to the index, counts updated to the verified total (82 records: 1 CRITICAL / 15 HIGH / 64 MEDIUM / 2 LOW, computed directly from the merged corpus, not carried forward from either branch's own possibly-stale count).dist/ave-records-latest.json+ manifest: regenerated vianode scripts/build-records.jsfrom the full mergedrecords/directory.Test plan
python3 scripts/validate_records.py-- all 82 records validpython3 scripts/check_fixtures.py-- all 82 records have positive/negative fixturespytest tests/ -x -q-- 478 passedmainis exactly the intended 7 files, no unrelated drift