tidy-httpbridge: the package's front door describes a retired stance - #253
Merged
Conversation
doc.go's "What it exposes" said GET on the endpoint is answered 405
rather than upgraded to a stream, and that one POST always means one
JSON-RPC answer. Neither holds. GET asking for text/event-stream opens
the ≤ 2025-11-25 notification stream (server.go:262, stream.go), and
subscriptions/listen is a POST whose response IS the stream
(server.go:298).
It cited canonical.md §5b as the authority — and §5b is where the change
is recorded: "Both generations are offered the out-of-band notification
stream on the HTTP face. This RETIRES the stance recorded here that
neither would be." So the package doc was carrying the retired half of
the very section it pointed at, and saying what that section costs: a
face promising `{"tools":{"listChanged":true}}` over a channel it had
decided not to build.
Server's own header has listed the three verbs correctly throughout, so
the disagreement was inside one package — front door against the type
behind it, and the front door is what a reader meets first.
Ruling #29 survives and is now stated as what it is: a rule about the
2024-11-05 two-endpoint transport, not about streamable HTTP's own
server→client channel.
make ci green.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.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
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.
Nightly tidy over the MCP protocol scope (
canonical.md§5b) andinternal/httpbridge.httpbridge/doc.gostill said GET is answered 405 and one POST means one answer — the stance §5b explicitly retiredserver.go's own header has described the three verbs correctly throughout, so the disagreement was inside a single package, between its front door and the type behind it.§5b itself checked out row for row:
SupportedVersionsis[2026-07-28, 2025-11-25, 2025-06-18, 2025-03-26]newest-first;ProtocolVersionstays atVersion2025;carriedNotificationshas exactly the one entry the section claims ("one method today", already machine-guarded byTestCarriedNotificationsMatchTheGateway); the spec-reserved error range is-32020…-32099; and legacy HTTP+SSE remains read-side only.