Harden peer-review navigation, reader experience, and citation paths - #2
Merged
Merged
Conversation
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.
Purpose
This is a repository-facing sanity pass for peer-review use, first-time readers, and future citation.
Changes
problem_treeexplicitly to the documented maximum-|J| tree (MAXJ);MAXJis not a KL-optimality claim;v1.0.0result from the expanded Version 1.1.0 archive;Scientific scope
No numerical result, frozen source file, primary comparison, effect estimate, or interpretation boundary is changed.
Remaining release action
The repository already has release
v1.0.0for the primary confirmed result. Version 1.1.0 citation guidance now requires either a matching release tag when one is published or the full commit SHA, so citations remain unambiguous in either case.