7fe88677addocs/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.
17 lines
338 B
Text
17 lines
338 B
Text
.phpunit.cache
|
|
.php-cs-fixer.cache
|
|
composer.lock
|
|
coverage
|
|
vendor
|
|
examples/**/dev.log
|
|
examples/**/cache
|
|
examples/**/sessions
|
|
tests/Conformance/client-conformance.json
|
|
tests/Conformance/server-conformance.json
|
|
tests/Conformance/results*
|
|
tests/Conformance/sessions
|
|
tests/Conformance/logs/*.log
|
|
|
|
# phpDocumentor
|
|
.phpdoc/build/
|
|
.phpdoc/cache/
|