diff --git a/DESCRIPTION b/DESCRIPTION
index 44bfb72..57e3968 100644
--- a/DESCRIPTION
+++ b/DESCRIPTION
@@ -1,7 +1,7 @@
 Package: contentvalidR
 Type: Package
 Title: Tools for Substantive and Content Validity Pretesting
-Version: 0.10.1
+Version: 0.10.1.9000
 Authors@R: c(
     person(given = "Joshua", family = "Uhalt", email = "Josh.Uhalt@gmail.com",
            role = c("aut", "cre"))
diff --git a/NEWS.md b/NEWS.md
index 09184f5..204cac3 100644
--- a/NEWS.md
+++ b/NEWS.md
@@ -1,3 +1,8 @@
+# contentvalidR 0.10.1.9000 (development version)
+
+* The reader in nomologR is now tested against handoffs from contentvalidR
+  0.6.0 through 0.10.1, and the README says so.
+
 # contentvalidR 0.10.1
 
 A documentation release. The README now documents the handoff to nomologR in
diff --git a/README.Rmd b/README.Rmd
index 162598a..14b9450 100644
--- a/README.Rmd
+++ b/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.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.
+**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.1, 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
 
diff --git a/README.md b/README.md
index be461f1..0749194 100644
--- a/README.md
+++ b/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.10.0, and neither package depends on the
+contentvalidR 0.6.0 through 0.10.1, 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.
diff --git a/ROADMAP.md b/ROADMAP.md
index ab20223..a638221 100644
--- a/ROADMAP.md
+++ b/ROADMAP.md
@@ -864,7 +864,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.10.0.
+        through 0.10.1.
   - [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