AndreandClaude Opus 5
c0633f11e7
CVE-CHANNEL.md showed the PHP upload-progress rule as its worked example, and that CVE is patched in compiled code. The guard forty lines below the example exists to refuse exactly that — both rules would fire, the scores would add, and one attack would be reported as two. So the example a reader was most likely to copy was the only example that could not be published: published rule CVE-2026-109618-01 patches CVE-2026-109618, which the compiled rule "php_upload_progress" already patches The example is now a CVE that is not patched in code, extracted from this file and run through the engine's own guard to prove it validates. A sentence beside the example says why it is not the PHP one, instead of leaving the reader to find the warning at the bottom after the refusal. cve.json is untouched and its build_datetime is unchanged, so nothing an edge node enforces changes with this commit. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01N5fpE6Gu4W6JoFMXyb7t7r