[Docs][Examples][CI] Document and gate the 2026-07-28 lifecycle - #457
Merged
chr-hertel merged 1 commit intoAug 19, 2026
Merged
Conversation
chr-hertel
requested review from
CodeWithKyrian,
Nyholm and
soyuka
as code owners
August 18, 2026 19:10
docs/stateless-lifecycle.md walks the revision end to end - per-request _meta, server/discover, multi round-trip requests, caching and subscriptions - and a runnable example on each side shows what that looks like in code. CI matrixes both conformance roles over both revisions. --spec-version is cumulative across the dated revisions, so 2025-11-25 covers the two before it; 2026-07-28 is not cumulative with them and needs its own run against its own baseline. The runner is pinned so a PR only goes red for reasons in the PR, and conformance-weekly tracks the moving target instead - on both revisions, since the draft scenarios ship only on the alpha dist-tag. The Inspector cannot reach a modern-lifecycle server (it opens with initialize), so the example is covered by integration tests instead: one drives it with hand-built HTTP the way a conforming client would, one drives it with this SDK's client, and one drives the single endpoint from both eras.
chr-hertel
force-pushed
the
pr/2026-docs-examples-ci
branch
from
August 19, 2026 00:54
1448f66 to
23cb079
Compare
This was referenced Aug 19, 2026
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.
Stacked on #456. Tip of the stack.
docs/stateless-lifecycle.mdwalks the revision end to end — per-request_meta,server/discover, multi round-trip requests, caching and subscriptions — and a runnable example on each side shows what that looks like in code.CI matrixes both conformance roles over both revisions.
--spec-versionis cumulative across the dated revisions, so2025-11-25covers the two before it;2026-07-28is not cumulative with them and needs its own run against its own baseline. The runner is pinned to an exact version so a PR only goes red for reasons in the PR, andconformance-weeklytracks the moving target instead — on both revisions, since the draft scenarios ship only on thealphadist-tag.The Inspector cannot reach a modern-lifecycle server (it opens with
initialize), so the example is covered by integration tests instead:StatelessLifecycleTestdrives it with hand-built HTTP the way a conforming client would,StatelessClientTestdrives it with this SDK's client, andDualEraEndpointTestdrives the one endpoint from both eras.At this tip: modern conformance 151/151 · handshake conformance 80/80 · 1502 unit · 64 integration · PHPStan at the pre-existing baseline.
Cross-fork PRs can only target
main, so this diff also carries its ancestors until they merge. Only the last commit(s) belong to this PR — GitHub's "Commits" tab separates them.