Add texas state mapping to config/compliance_rules.yaml

[linus10x]

Context

config/compliance_rules.yaml currently maps patterns to federal regulations (Fair Housing Act, ECOA, FCRA, EU AI Act) and the Colorado AI Act + 10 source-of-income-protection jurisdictions. State-level data-privacy and tenant-screening statutes vary materially — this issue tracks adding a primary-source-cited mapping for texas.

What to do

1. Identify the controlling state statutes for AI-driven tenant-screening AND/OR tenant-data residency in texas
2. Add per-pattern entries under the appropriate pattern keys in config/compliance_rules.yaml (e.g., under fair_housing_preflight_gate.regulations, tenant_pii_data_residency_partitioning.regulations)
3. Every entry MUST cite a primary-source URL (statute text or AG enforcement page) — no secondary law-firm alerts or news summaries
4. Run python scripts/build_compliance_json.py and commit both YAML and JSON
5. Add a test in tests/test_regulation_loader.py asserting the mapping loads
6. Update docs/MAPPING-MATRICES.md if the addition changes a framework mapping

Definition of done

• Both compliance_rules.yaml and compliance_rules.json updated and in sync
• Primary-source URLs verified to resolve (200 OK)
• At least one test passes that loads the new mapping
• Brief paragraph added to README's Real-World Use Cases or Patterns Included if the state mapping unlocks a new scenario
• make verify green

Why this is a good first issue

Bounded scope (one state) · clear acceptance criteria · real regulatory-coverage impact · no architectural changes required · pattern code unchanged.

Per CONTRIBUTING.md, secondary sources (Holland & Knight alerts, Lex Machina summaries, news articles) are NOT acceptable as the sole citation — they may inform but the entry must link to statute text or agency press release.