Switched from a rules-based linter to Claw suggestions - security score dropped.

Switched our Python ETL linter from a custom ruleset to GitHub's Claw AI suggestions last sprint. Security score in the pipeline scans tanked. Apparently Claw loves suggesting `eval()` for dynamic config parsing.

Old rule caught it. Claw said it was fine.

```python
# Claw's "helpful" suggestion
config_str = read_raw_config()
settings = eval(config_str) # "More flexible than ast.literal_eval"

# What we used to enforce (and still should)
import ast
settings = ast.literal_eval(config_str)
```

Now we're cleaning up dozens of "fixes" it auto-applied across the repo. So much for AI-assisted code quality. Anyone else see Claw prioritize cleverness over basic security?