[Bug] Overly aggressive content filtering on git commit messages and SQL queries

**Bug Description**
I've had two commits about git commits during software development flagged with the '[bio]' guard rail. Here is the second one, as a sample:

> The client asked me if I could give them a list of mbox numbers mapped to addresses. The issue may have been that the thing was formatted with box characters and such. I'm not worried about it, just wanted to make sure it didn't confuse you or that my last intended turn (the git commit) wasn't lost.

The other one was either the aforementioned accidental past of about 20 rows of a two-column SQL query, or it was a followup to my telling Claude I had git committed the small source code changes. The software in question is locally-developed tooling to migrate IMAP emails from a very old email system. There's not only nothing about biohazards or bioweapons, but it's not even research of any kind, just one-off IT tooling. For reference, the second occurrence was (REDACTED -- Check feedback for this). These two occurrences are the only time I've ever seen this type of message.

**Environment Info**
- Platform: linux
- Terminal: pycharm
- Version: 2.1.274
- Feedback ID: 29f02fb5-5d54-4398-be68-e651876b5513

**Errors**

Provided to Anthropic upon request.

No source file or test is named. Start by reviewing feedback ID 29f02fb5-5d54-4398-be68-e651876b5513 and the error details available on request, then reproduce filtering with the reported git commit text and SQL query cases. Done means legitimate commit messages and SQL queries no longer trigger the [bio] guard rail.

Written by the indexing model from the issue text.