Skip to content

feat: add AVE-2026-00083, Silent Guardrail Comparison Failure- #277 - #284

Merged
chaksaray merged 1 commit into
mainfrom
feat/AVE-2026-00083-into-main
Sep 22, 2026
Merged

chaksaray merged 1 commit into
mainfrom
feat/AVE-2026-00083-into-main

Conversation

@chaksaray

Copy link
Copy Markdown
Contributor

Summary

Mirrors #277's merge into develop (AVE-2026-00083, silent guardrail comparison failure) into main, matching this repo's established dual-branch mirror pattern (#270 -> #279, #269 -> #281).

Supersedes #283. Same issue as #280/#281: develop and main share a merge-base far enough back (3b9fcc0) that both branches have independently edited the same lines (record counts, index rows) since -- a content-only sync commit on develop can't resolve GitHub's graph-based mergeability check for a develop -> main PR without either a real merge commit (blocked by branch protection on develop) or a full rebase (too disruptive to other work based on develop). A fresh branch off current main carrying just this diff avoids both.

Changes

  • records/AVE-2026-00083.json + both conformance fixtures, copied as-published from develop.
  • README.md / CHANGELOG.md: record added to the index, counts bumped to the verified total (83 records: 1 CRITICAL / 15 HIGH / 65 MEDIUM / 2 LOW, computed directly from the merged corpus).
  • dist/ave-records-latest.json + manifest: regenerated via node scripts/build-records.js.

Test plan

  • python3 scripts/validate_records.py -- all 83 records valid
  • python3 scripts/check_fixtures.py -- all 83 records have positive/negative fixtures
  • pytest tests/ -x -q -- 482 passed
  • Severity breakdown cross-checked against the regenerated dist/ave-records-latest.json, not carried forward from either branch
  • Diff against main is exactly the intended 7 files, matching develop's own diff for this record

Mirrors #277's merge into develop, matching the established pattern
(#270 -> #279, #269 -> #281). Fresh branch off main rather than
reusing #283 (develop -> main): same graph-divergence issue as #280,
where develop and main share a merge-base far enough back that a
content-only sync commit can't resolve GitHub's mergeability check
without a real merge commit (blocked by branch protection on develop)
or a disruptive full rebase.
@chaksaray
chaksaray merged commit 85ccccd into main Sep 22, 2026
8 checks passed
@chaksaray
chaksaray deleted the feat/AVE-2026-00083-into-main branch September 22, 2026 00:14
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