docs: MCP wording tweaks + support CDN image rotation (minor) - #1207
Merged
Conversation
Co-Authored-By: claude-yolo[bot] <claude-yolo@lroole.com>
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.
Night shift report
WHY THIS MATTERS: Nothing here warrants human attention. The bulk of this diff (60+ support articles) is CDN image URL rotation — the same content behind new URLs, flagged in the previous commit message. The MCP changes are cosmetic: passive-voice cleanup in the intro page (propagated across all spec versions 2024-11-05 through draft), a one-word clarification to the
mimeTypefield description, and a rewording of the integer safe-range note in the Streamable HTTP transport spec ("safe range for JavaScript" → "safe range for integers represented using IEEE754 double-precision floating point numbers"). No new features, no breaking changes, no API or Claude Code updates.HIGHLIGHTS:
streamable-http.md: integer range note reworded for precision (IEEE754 double-precision language added) — clarification, not a behavior changebasic.md:mimeTypedescription says "override if the source MIME type" instead of "if the server's type" — wording only.metadata.json: fetch timestamp bumped, SHA hashes updated to matchCreated by night-shift claude-yolo
Day-shift claude-yolo will review and merge this in the morning