Follow-up to #324. When a bridge resumes a stateful HTTP session (skipped handshake), the SDK client has no capabilities or instructions, so after a crash-recovery restart:
mcpc @session shows Capabilities: (none) even though the server session still has its original capabilities,- server instructions are gone from
mcpc @session help / grep,
- the bridge's
resources-subscribe capability pre-check (src/bridge/index.ts, legacy-era branch) reads capabilities.resources.subscribe from the resumed client and would wrongly report "Server does not support resource subscriptions".
#324 restores protocolVersion and serverInfo (both already persisted in sessions.json). Capabilities and instructions are not persisted today; fixing this means persisting them at original connect (instructions can be multi-KB, so maybe capabilities only) and merging them into getServerDetails for resumed connections.
Refs #324
Follow-up to #324. When a bridge resumes a stateful HTTP session (skipped handshake), the SDK client has no
capabilitiesorinstructions, so after a crash-recovery restart:mcpc @sessionshowsCapabilities: (none)even though the server session still has its original capabilities,mcpc @session help/grep,resources-subscribecapability pre-check (src/bridge/index.ts, legacy-era branch) readscapabilities.resources.subscribefrom the resumed client and would wrongly report "Server does not support resource subscriptions".#324 restores
protocolVersionandserverInfo(both already persisted in sessions.json). Capabilities and instructions are not persisted today; fixing this means persisting them at original connect (instructions can be multi-KB, so maybe capabilities only) and merging them intogetServerDetailsfor resumed connections.Refs #324