Claude/eloquent davinci s bng g

[killertcell428]

Summary

Closes #

Changes

Type of change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• New detection pattern
• Breaking change (fix or feature that would cause existing behaviour to change)
• Documentation update
• Refactor / performance improvement

Testing

• pytest tests/ -v passes locally
• New tests added for the change
• Existing tests updated if needed (explain why)

For new detection patterns, confirm both:

• Positive test — the pattern correctly detects a malicious input
• Negative test — the pattern does NOT fire on legitimate input

Checklist

• Code follows the style of the project (ruff check passes)
• Type annotations are correct (mypy aigis/ passes)
• Public API changes are reflected in docs/api-reference.md
• CHANGELOG.md updated under [Unreleased]
• I have read CONTRIBUTING.md

Screenshots / output

[killertcell428]

Superseded by #61, which is taking the v1.1.5 release slot.

Why this PR is being closed instead of resolving the conflicts:

• Both this PR and Claude/eloquent davinci o6sfs #61 try to publish v1.1.5. The CHANGELOG / __version__ / INDEX / ROTATION / pyproject.toml conflicts are caused precisely by both PRs writing to the same v1.1.5 sections. Resolving them would still leave one of the two PRs unable to claim v1.1.5.
• Claude/eloquent davinci o6sfs #61 is already in CLEAN / MERGEABLE state (DCO fixed, both commits SSH-verified) and is ready to merge as v1.1.5.
• The DCO failure on this PR has the same root cause as Claude/eloquent davinci o6sfs #61 had: commits authored by aigis auto-improvement <auto-improvement@aigis.local> while the Signed-off-by (if any) is killertcell428 <killertcell428@gmail.com>. DCO requires the two emails to match.

What this PR contained that #61 does not:

• sc_flowise_js_rce — Flowise CVE-2025-59528 (CVSS 10.0), JavaScript Function() constructor RCE in the CustomMCP node. Detects new Function(...) combined with child_process / fs / os / net / process.env references, and the same patterns inside MCP mcpServerConfig / "command": / "args": fields. Also covers the Function.prototype.constructor prototype-chain bypass. Worth re-introducing as v1.1.6 since the CVSS is 10.0 and 12,000+ instances were still exposed when exploitation began.
• A more rigorous CHANGELOG **Tests:** line that names the failing test files (test_spec_lang.py, test_guard.py, test_oss_comparison_bench.py, test_release_preflight.py) and their root causes — closer to what CLAUDE.md asks for than the original draft of Claude/eloquent davinci o6sfs #61. If sc_flowise_js_rce is re-introduced in a follow-up PR, keep this style.

If a follow-up v1.1.6 PR is opened with sc_flowise_js_rce, please ensure (a) the commit is authored with the email that signs off DCO, and (b) signing is enabled (commit.gpgsign=true with the SSH/GPG key registered on the GitHub account), so the same fixup dance is not needed.