fix: Fillout API CI pagination error, flaky phone validation test

[taran-bains]

Fixed Fillout DNS Validator Pagination Logic

File: real_intent/validate/dns.py

Problem: The DNS validator was failing when paginating through large numbers of submissions. The API was returning a 400 error when the offset exceeded the total number of submissions.

Solution: Implemented proper pagination using the totalResponses field from the Fillout API response instead of relying on error handling. The validator now checks if len(submissions) >= total_responses to determine when to stop paginating.

Fixed Flaky Phone Validator Test

File: tests/test_validation.py

Problem: The test was failing because it assumed "fake" phone numbers (properly formatted but non-existent) would be rejected by the Numverify API. However, Numverify's behavior is unpredictable for properly-formatted numbers.

Solution: Removed the unreliable fake_phones list and assertion. The test now only verifies:

• Invalid format phones are rejected (local validation - reliable)
• At least some real phones are validated (API connectivity works)

[augmentcode]

🤖 Augment PR Summary

Summary: Fixes Fillout DNS validator pagination and stabilizes the phone validation integration test.

Changes:

• Update Fillout submissions pagination to stop based on the API-provided totalResponses count.
• Simplify test_phone_validator_with_real_api by removing assertions about “fake but formatted” numbers and focusing on invalid-format rejection + real-number validation.

Technical Notes: Pagination continues in limit=150 increments until collected responses meet/exceed totalResponses.

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. 2 suggestions posted.

Comment augment review to trigger a new review at any time.