Repository navigation
Sync setup routing to the published Logfire specialists - #73
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.
Summary
Mirror the four routing files from pydantic/logfire#2574 into plugin and standalone skills. Browser, coding-agent, and Gateway requests route to their specialists before ordinary SDK authentication; server setup remains in the SDK guide.
No independent edits to SDK-owned content. Native MCP query/UI and the CLI-owned procedures are unchanged.
Validation
Seven ownership/sync tests, mirror/reference checks, and diff checks pass. Files match SDK head f2e65bd398e91f9c7586fbb45e75ba14a1443e29.
Merge gate
Merge only after the specialist URLs are published and verified and pydantic/logfire#2574 has merged. Verify the four files against the actual SDK merge before merging this sync. This completes public setup-hub publication; it does not migrate legacy SDK authentication or publish a CLI binary release.