fix: accept non-DNS Common Crawl graph rows

docs/CONSUMERS.md

@@ -34,7 +34,7 @@ source attribution and application-specific malware/content policy.
 
 ## Current contracts
 
-Code version 0.6.0 uses writer schema 5 and `argand.site-rules/v4`.
+Code version 0.6.1 uses writer schema 5 and `argand.site-rules/v4`.
 New compact `COMPLETE.json` files use `argand.site-registry/v3` and bind:
 
 - authenticated `registry.sqlite` bytes;

docs/VALIDATION.md

@@ -2,6 +2,12 @@
 
 # Version 0.6.0 Web Graph and updater validation, 2026-09-22
 
+Patch release 0.6.1 additionally replays the real provider-shaped
+`com.your_domain` case: the row remains in authenticated input/coordinate
+accounting but is not retained as a DNS target. The following valid
+`com.facebook` row is retained at its original `row:2` coordinate. Schema and
+numeric corruption continue to fail closed.
+
 The evaluation contract was written before implementation. The new Common Crawl
 domain-rank integration passed five default integration tests; its sixth test is
 an explicit resource benchmark. The benchmark parsed 100,000 valid provider-shaped