docs: add current runtime status overlay without altering sealed package - #6
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.
Integrity-preserving follow-up for
blackmore-technology-group/ENTITY#91.The root README and all manifest-bound v3.4.0 package files remain byte-for-byte unchanged. This PR adds only
CURRENT_STATUS.md, outside the sealed repository manifest, to explain current ENTITY v3.4.3 runtime context, BTDU 3.4.2 component status, the sealed v3.4.0 package payload, historical v3.4.1 package requalification context, and the Protocol 1.0 boundary.No package hash, source binding, schema, mapping, authority rule, rights rule, or conformance result is changed.