Invokes survive reconnects — the claim protocol closes the eternal-spinner root cause

Twice in one evening a crawl finished server-side while the tab spun forever — both times because a workspace-service rebuild severed the socket and the transport threw away its pending invokes. Pending invokes now survive the drop and re-attach by id: the server stashes results whose socket died, and reconnecting clients send claim frames to collect them.