The transform sink's write algorithm waited for the backpressure-change
promise in a loop, re-checking the flag after each wake-up. The spec
waits once: a read's pull releases the write, and an enqueue on a stored
controller in that same turn re-asserts backpressure before the write's
reaction runs, yet the write still transforms. Under the loop it parked
again until the next read, so a producer that awaited each write before
reading again deadlocked, and the transformer never saw the chunk. The
C++ implementation waits once.

Both sink writes now wait once and then check the writable for
erroring, as before. The zero-algorithm path's loop could never iterate
twice, since that readable has no controller to enqueue through; it
changes for uniformity.

Pinned in the transform suite's backpressure.js. The release through a
pending read is parity. The release through a dequeue at readable hwm 1
is a divergence (ledger #14): the C++ readable does not pull after a
dequeue that leaves room (readable ledger #5), so its write stays parked
until a read finds the queue empty. An error() in the release's turn is
a divergence too (ledger #15): the woken TypeScript write rejects with
the writable's stored error, the C++ one has already lost its writable
reference and algorithms and rejects with the identity path's enqueue
TypeError.

…-write-stall

Transform a parked TransformStream write after one backpressure wait

…7422)

This applies the same fix as pyodide#6466 but as a JS patch rather than by
changing the C source code. Interestingly, the test case doesn't pass against
0.28.2 either.

Distinguish retry loops that reach the attempt limit from those that run out of retry-start budget. This lets observers identify which constraint ended the loop.

Raise the full-jitter base delay from 50ms to 500ms. The four retry caps now span 500ms through 4s, giving transient failures more time to clear without increasing the attempt limit or retry budget.

* Add Analytics SQL binding types

* Clarify Analytics SQL binding description

* chore: update generated snapshot types

---------

Co-authored-by: Ben Dixon <bdixon@cloudflare.com>

Split actor retry exhaustion outcomes and increase backoff

Document coroutine cleanup patterns

These aren't diagnosed by the compiler since they have a non-trivial destructor.

- Make a few operators const to avoid `ISO C++20 considers use of overloaded
  operator '==' (with operand types <type> and <type>) to be ambiguous despite
  there being a unique best viable function` warnings
- Address `'operator==' is deprecated: Using nullptr as an empty Maybe is
  deprecated and will be removed. Please use kj::none for this purpose instead`
  warnings

This should only be needed for some tests, no need to disable it completely.