The Baileys pairing guard also tests `ws.isOpen`, but the 409 description
still told callers that waiting for `status` to read `qr_ready` was enough.
The status trails the transport: Baileys emits its close only after
`await ws.close()` resolves, so on a silently dropped connection the socket
stops accepting a pairing request while the session still reads `qr_ready`,
for as long as the WebSocket close timeout. A client following the
documented procedure sees a 409 with its precondition already satisfied and
no way to tell that state from the ones the text does describe.
Name the window the way the generic engine-not-ready 409 already names its
own reload window, and mirror it in the API reference and the pairing
example. Contract text only; the guard is unchanged.
Yudhi Armyndharis
9f7b228a88