Repository navigation
docs: synchronize the canonical stack overview - #38
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.
Synchronize this README with the canonical stack overview. Add the missing marked overview section while preserving all existing README text.
The copied block has SHA-256
42334a31ca0e6f73815ed0fa3ca57ccaa66aec136b298d9c616de2d18f79e840. Canonical links and wording are copied verbatim, including the redirects for moved repositories. No canonical table, checker, runtime or namespace change is included.Validation: exact marked-block equality and outside-block preservation across all nine scoped README copies; existing stack-checker eight positive/refusal tests pass. The two affected repository-knowledge suites each pass eight tests with their native-schema test explicitly skipped. HOME/resource guard is clean. Public remote audit and the original drift workflow remain pending until the member PRs land.
One independent Codex post-green source review, then normal landing through Tim. Rollback is the inverse of this scoped proposal onto its exact base; it restores the prior README and, where present, prior digest values.