Repository navigation
docs: apply the qualified narrow-page Corpus builder - #70
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.
Thread and Ferry's documentation workflow and local docs scripts explicitly pinned an older Corpus revision. Update all four tool selections to merged Corpus commit b8ecf4cd4c6482bb804cdeea617ebe2d9b78ab05 and explain the narrow-page wrapping in the owning maintenance guide. Package dependencies, runtime source, formats, definitions and release versions are unchanged.
Validation: committed-byte docs freshness and site build passed at the new source head; bundle SHA matches that commit, and emitted CSS is byte-identical to the browser-qualified merged Corpus renderer. The nine-page site keeps eight MCP topics. Normal pre-push gates provide their own source checks; hosted qualification and actual Pages deployment remain separate. No npm publication or live-client activation is performed.