Document the handoff to nomologR on the README, and fix the RC-day order - #85
Merged
Merged
Conversation
The maintainer asked that each package's README document the handoff in its own section near the bottom. "The handoff to nomologR", just above References, says what a handoff carries, how to make one (with the README's own fit), the two nomologR calls that read it, how to read its decisions (the reader contract in ?content_handoff), and how schema 1 is versioned. nomologR's README carries the mirror section, "The handoff from contentvalidR", with the same reader-contract wording. ROADMAP.md now gives the release-candidate day in the order agreed with nomologR, so that nomologR's tests pass before either package tags: the 0.99.0 commit and its fixtures first, then nomologR's suite, then both tags, contentvalidR's on exactly the commit the fixtures came from. Opens the 0.10.0.9000 development version. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
JUhalt
added a commit
that referenced
this pull request
Sep 29, 2026
Release contentvalidR 0.10.1 A documentation release. It stamps the version, release notes, citation metadata, README, and roadmap for 0.10.1, which puts the handoff on the front page: - the README section "The handoff to nomologR", mirrored by nomologR's "The handoff from contentvalidR" (#85); - Krippendorff (2011) linked to the Annenberg School copy (#86); - the nomologR reader recorded as tested against 0.6.0 through 0.10.0 (#87). No computed value changes: 25 analyses across every workflow return the same values as v0.10.0, and no function, argument, or handoff field changed. Released on GitHub and R-universe; CRAN keeps 0.4.0 until the joint 1.0. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The maintainer asked that each package's README document the handoff in its own section near the bottom. nomologR is adding the mirror section, "The handoff from contentvalidR", above its "Stability" section. Docs only: no code, no computed value, and no handoff change.
"The handoff to nomologR", just above References
reverse_keyed(orcharacter(0)if checked and none is) andresponse_scale.content_handoff()call on the README's own first analysis. It shows the two carried items.nomo_screen(responses, items = h)andnomo_run(responses, scales = h), shown but not run. Pass the whole handoff, noth$items.?content_handoff(State the handoff reader contract nomologR asked for, and record the joint 1.0 checklist #79).carriedandstatus, never re-derived from a statistic against its criterion or from the producer version.recommendationis prose.keyingofNAmeans unknown.?content_handoff, the handoff vignette, and the joint walkthrough.Also
Verification
"Clear 1" "Clear 2".tools/release-gate.Ron this PR's head (be3097d), run in a detached worktree: build, smoke, and check all pass; R CMD check 0 errors, 0 warnings, 0 notes (the usual CRAN-incoming and V8 notes did not appear in this run). A first run failed only because repository.upenn.edu returned a transient 500 for the Krippendorff (2011) link; it answered 200 minutes later, and the rerun on the same commit passed.🤖 Generated with Claude Code