Repository navigation
docs: publish source-bound Thread and Ferry documentation - #69
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 lacked a Corpus manifest and docs publication workflow. Add a source-backed documentation site for Thread/Ferry setup, CLI behavior, supported formats and fidelity losses, and schema/identity ownership.
The v2 manifest curates nine pages and eight MCP topics with source-to-document freshness routes. Local scripts and shared docs workflows use Corpus commit
340b66fc8f723c1babe35fce8240c82cd196b0db; PR/merge-group checks gate docs, and main/dispatch publication uses the shared Pages workflow. No production code, package versions, or release behavior changes.Validation:
npm run verifypassed 223 tests plus packed-consumer and tree-shaking checks.npm run docs:check -- --base origin/mainpassed all checks and freshness for 12 changed files.npm run docs:buildverified nine pages and an exact-commit bundle. The documented fixture inspect and Codex → Thread → Anthropic conversion commands also ran successfully.Hosted workflow execution, repository Pages configuration, hub registration, and aggregate MCP discovery require separate delivery verification. No npm publication or live consumer changes are included.