No ads.txt in the cache for this site
The local cache has no ads.txt for site.domain, so the first payment hop cannot be checked against the publisher's authorization file.
What it means
Opt-in --resolve looked up ads/<site.domain>/ads.txt (and ads/<domain>/ads.txt with a leading www. stripped) and found no file.
Why it matters
ads.txt is how a publisher authorises who may sell its inventory. Without the file, the first SupplyChain hop cannot be matched to a DIRECT or RESELLER line.
How to fix it
Fetch https://<site.domain>/ads.txt into the cache as ads/<site.domain>/ads.txt, then re-run with --resolve --cache.
Example that trips it
rtblint validate --resolve --cache ./supply-cache request.json
Fires when site.domain is set, a payment hop exists, and the cache has no ads.txt for that domain.
Check your payload
Paste a bid request or response into the tester to see whether this code fires against it, or gate on the id in CI with the CLI: the id is stable, wording is not.
Back to the full diagnostic code reference.