Repository navigation
Clean up current documentation and preserve historical evidence - #146
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.
Visitors had to read release narratives and completed launch material alongside current guidance. The README is now a short entry point, the owner guide holds detailed usage, and a documentation index maps current guidance, evaluation data, and immutable historical sources.
Current decision premises, receipt requirements, dated claims, confirmed failures, and unverified limits remain inspectable. Contribution policies move to
.github, discovery cases move toevals, and the relocated contribution guide retains its personal-path protection. The installable package changes only its version metadata to 6.3.4.Validation:
scripts/check.pyand stagedgit diff --checkpassed; 222 targeted tests passed during editing.72aef4540d30d3639a2f63af6663971345c6dc5awith their original Git object identities.The first full local attempt inherited a global pytest basetemp setting that conflicted with nested pytest calls. Removing that launch setting resolved the failures without source changes; the final gate uses a task-owned temporary directory.
Release publication and site deployment follow the existing tag workflow after reviewed integration and revision-bound CI.
Independent read-only review approved the candidate with no qualifying material findings. Reviewed staged-diff SHA-256:
77f2d40166cc37d4796a29aafe3e4d9a51f2211c5db1fdfaf6f048a3ee5c12e5; committed tree:6734d7a1a4c608298c1b0af55c2bd81121ad88e4. The reviewer inspected existing evidence and did not repeat verification.