amal66 turns paper-thin safety checks into real gates

This fork replaces reassuring green ticks with checks that actually protect the legal-AI system, and removes the ones that cannot.

amal66 audited the project's automated safeguards and found several were more ceremonial than operational. The proposed changes make the quality story more honest:

Backend test coverage now has an enforced floor, so future losses block affected changes.
Security testing now covers all five key protection components, including safeguards against unsafe outbound requests and unreliable citations.
Targeted pull requests trigger that deeper testing, without adding delay to unrelated work.
Unwired evaluation and load-testing checks are removed; the load-test scenario remains available for local use until a suitable staging environment exists.

The point is not perfection. It is making a pass signal mean something, especially where the product claims citations are verified or blocks risky requests.