Repository navigation
Remove obsolete drafting-status sentences throughout repository files - #37
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
1 participant
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.
Remove the remaining obsolete drafting-status sentences from six documentation/work-order files and historical integration-manifest prose, as requested by the owner. Clean up the earlier maintenance description and refresh only the required documentation fingerprints.
The historical manifest's scientific payload and all recorded scientific hashes remain identical. Its prose-only edit is allowed by an exact, pinned before/after full-file hash pair; all other protected-file edits remain rejected. Existing Git history is retained.
Validation: 128 tracked files and 15 ZIP archives (including nested archives) scanned with no remaining matching status wording. Full verify_current.py --all with the pinned release baseline passed: 20 checkers / 60 normal,-O,-OO runs, strict historical byte replay, and separate bounded portability with zero differing float leaves. A negative control confirmed that changing a protected scientific report is rejected even when its current manifest fingerprint is updated. git diff --check passed, and the uploaded tree matches the validated local tree.