Three gaps in the unary/stream runtime:
- A KEYED_COMMAND/NON_REPLAYABLE unary that failed after the transport
was invoked (timeout, throw, UNAVAILABLE, ...) came back retryable
with action "retry", although the server may have applied it. Every
failure of a COMMAND after send now carries effect MAYBE_APPLIED
(retryable false, contact-support). Pre-send rejections and queries
are unchanged.
- A retry did not re-check the scope generation, so after a logout the
previous user's command could be sent again. Each retry now checks
safeIsCurrent first and ends with SCOPE_GENERATION_CHANGED.
- A stream whose consumer aborted but never called return() stayed
suspended at a yield; its finally never ran and the operation stayed
RPC_STREAM_DRAINING for good. The lease is now released (cancel +
positive-close subscription) from the stream's own abort listener;
finally triggers the same path through its abort.
Verified: five new tests failed RED (no effect, second attempt sent,
cancel never called) and pass now; a pin that pre-send command failures
and query failures stay effect-free passes before and after. All lane
gates pass except the known removal-fixture test.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>