docs: describe current behavior and trim implementation history - #318
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.
Summary
Edit the documentation and comments around current behavior rather than implementation history.
No executable code, public types, compiler directives, test names/expectations, generated fixtures, protocol bytes, lockfiles, schema versions, or package versions change. No deleted history is moved into new repository artifacts. Architectural section headings/anchors remain stable.
Verification
just gates < /dev/nullpassed: runtime 827/0/3, seeded scheduling, conformance, packaging/npm, shell/browser realms, OPFS, and TLS/C0 consumer smokes. Formatting and diff checks passed. Existing expected failures/skips unchanged, consumer trees unchanged.145 files edited, approximately 6,000 net lines removed.
Some existing implementation limitations became apparent while checking prose. This PR qualifies claims rather than changing behavior, including directory-cache adapter puts, digest normalization limits, and top-level-only import argument cleanup.