v0.8.2

A pause in the conversation no longer breaks the next tool call.

Fixes

• An idle HTTP session survives an hour instead of five minutes. rmcp reaps a session after SessionConfig::keep_alive of inactivity, and its default is 300 seconds — a threshold a conversational client crosses constantly. The session worker quit on IdleTimeout, the manager dropped the entry, and the client's next tool call, still carrying the session ID it had been issued, got the spec-mandated 404 Not Found. That 404 is a transport-layer response with no JSON-RPC envelope, so the caller could not attribute it to an expired session: it surfaced as a failed tool and read as a bug in whichever tool happened to be called first after the gap.

Notes

• The timeout remains as the safety net it is meant to be — a session whose HTTP connection dropped silently is still collected, just an hour later.
• Sessions carry no vault state of their own (each is a cheap clone over the shared vault and the one commit lock), so a longer-lived session costs only its worker task.