feat(compliance): wire multi-region data residency routing into ingestion pipeline

[DebasmitaBose0]

Closes #366

• Added residency_policy_name / residency_region to TenantConfig
• Wired ResidencyRouter into TenantIngestionPipeline with resolve_tenant_region() and get_region_endpoint()
• Events tagged with residency_region metadata during ingestion
• 7 tests in test_compliance.py
• PR Body:

Summary

Wires multi-region data residency routing into the telemetry ingestion pipeline (#366).

Enterprise telemetry must comply with geographic data residency laws (GDPR, etc.).
This change allows per-tenant configuration of target storage regions and routes
events accordingly.

Key changes

• agentwatch/models/tenant.py — added residency_policy_name and residency_region
  fields to TenantConfig
• agentwatch/telemetry/ingestion.py — TenantIngestionPipeline now:
  • Accepts an optional ResidencyRouter (initialized with default EU/US policies)
  • resolve_tenant_region() selects storage region from tenant config
  • Tags each ingested event with residency_region metadata
  • get_region_endpoint() returns the storage endpoint URL for a tenant
• agentwatch/governance/residency.py — existing module, no changes needed

[vercel]

@DebasmitaBose0 is attempting to deploy a commit to the sreerevanth's projects Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Warning

Review limit reached

@DebasmitaBose0, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 58 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 6a2807f1-960e-4ff4-8d3e-844d6589b5b2

📥 Commits

Reviewing files that changed from the base of the PR and between 2bb8ed2 and 019a29f.

📒 Files selected for processing (3)

• agentwatch/models/tenant.py
• agentwatch/telemetry/ingestion.py
• tests/test_compliance.py

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

🧪 PR Test Results

Check	Result
Tests (pytest tests/)	❌ failure
Lint (ruff check .)	❌ failure
Coverage (agentwatch)	73.62%

_{Python 3.12 · commit 019a29f}

[sreerevanth]

@DebasmitaBose0 can u fix your prs please