Say the nomologR reader is tested through contentvalidR 0.10.0

NEWS.md

@@ -10,6 +10,8 @@
   answered in 2 to 10 seconds, returned a server error, and timed out. It is
   the same paper, dated 2011.1.25, with its reading list updated in 2013. The
   expert-panel vignette's reference list now gives the link too.
+* The reader in nomologR is now tested against handoffs from contentvalidR
+  0.6.0 through 0.10.0, and the README says so.
 
 # contentvalidR 0.10.0
 

README.Rmd

@@ -168,7 +168,7 @@ nomo_run(responses, scales = h)    # runs the empirical stage on the handoff's s
 
 **Reading a handoff.** Take each item's decision from `carried` and `status`; never re-derive it by comparing a statistic with its criterion, or by branching on the version that produced it. `recommendation` states the same decision in the workflow's own words and, like `rule`, is prose. A `keying` of `NA` means nobody said, never that an item is forward-worded.
 
-**Versions.** The handoff is schema version 1, frozen since 0.7.0: its fields and columns keep their names, positions, and types, and new optional ones may only be added at the end. A change that broke this would be schema version 2, produced beside version 1 for at least a release cycle. The reader in nomologR is tested against handoffs from contentvalidR 0.6.0 through 0.9.0, and neither package depends on the other. See `?content_handoff` for the full contract, `vignette("handoff-to-empirical-validation")` for a guide, and `vignette("one-item-set-both-stages")` for the joint walkthrough.
+**Versions.** The handoff is schema version 1, frozen since 0.7.0: its fields and columns keep their names, positions, and types, and new optional ones may only be added at the end. A change that broke this would be schema version 2, produced beside version 1 for at least a release cycle. The reader in nomologR is tested against handoffs from contentvalidR 0.6.0 through 0.10.0, and neither package depends on the other. See `?content_handoff` for the full contract, `vignette("handoff-to-empirical-validation")` for a guide, and `vignette("one-item-set-both-stages")` for the joint walkthrough.
 
 ## References
 

README.md

@@ -313,7 +313,7 @@ fields and columns keep their names, positions, and types, and new
 optional ones may only be added at the end. A change that broke this
 would be schema version 2, produced beside version 1 for at least a
 release cycle. The reader in nomologR is tested against handoffs from
-contentvalidR 0.6.0 through 0.9.0, and neither package depends on the
+contentvalidR 0.6.0 through 0.10.0, and neither package depends on the
 other. See `?content_handoff` for the full contract,
 `vignette("handoff-to-empirical-validation")` for a guide, and
 `vignette("one-item-set-both-stages")` for the joint walkthrough.

ROADMAP.md

@@ -840,7 +840,7 @@ reads no handoffs and takes no part in the joint 1.0.
         nomologR's reader
         ([nomologR#46](https://github.com/JUhalt/nomologR/issues/46), closed)
         is tested against stored producer output from contentvalidR 0.6.0
-        through 0.9.0.
+        through 0.10.0.
   - [x] schema version 1 is frozen and becomes a compatibility promise (0.7.0).
   - [ ] both packages are on CRAN. contentvalidR 0.4.0 was accepted and
         published on 2026-09-28