stacklok / toolhive / 30272603807
70%

DEFAULT BRANCH: main
Ran
Jobs 1
Files 841
Run time 2min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 69.67% (+0.01%) from 69.66%
30272603807

push

github

web-flow 
Document vMCP backend revision classification (#6016)

The whole dual-revision subsystem was undocumented: zero hits for
server/discover anywhere under docs/, and no Legacy/Modern content in the
vMCP architecture doc, despite CLAUDE.md requiring docs/arch updates for
architectural changes. Both the PR that introduced revision
classification and the go-sdk v1.7 adoption landed without touching it.

Add a "Backend MCP Revision Classification" section covering what a
reader cannot infer from the code without tracing it: that
supportedVersions -- not a clean server/discover response -- is the
authoritative signal, because a v1.7 shim answers discover even while
negotiating down; that the containment check is an exact match and
therefore a tripwire for a future revision; that an inconclusive probe
deliberately does not cache; and that the cache self-heals
asymmetrically, Modern->Legacy via a mismatch but Legacy->Modern in band
off InitializeResult.

Also record two things that read as gaps but are deliberate: the SSE
short-circuit is ToolHive routing rather than a protocol rule, and
elicitation/sampling forwarding is structurally unavailable on Modern
backends because vMCP declares empty clientCapabilities -- a limitation
previously inferable only from three scattered code comments.

Correct one stale reference: 2026-07-28 is no longer "the draft spec".

Refs #6002

80575 of 115653 relevant lines covered (69.67%)

84.82 hits per line

Coverage Regressions

Lines Coverage ∆ File
2
96.05
 0.0% pkg/authserver/storage/memory.go
2
82.06
 -0.21% pkg/vmcp/composer/workflow_engine.go
Jobs
ID Job ID Ran Files Coverage
1 30272603807.1 841
69.67
 GitHub Action Run
Source Files on build 30272603807