P2 — fixed:
- Race condition: stop() called while client.connect() is in-flight could
  fire onconnect after the session was stopped. Guard with `if (this.stopped)`
  immediately after the connect await resolves.
- Missing test: session.subscribe(queue: AMQPQueue) overload was untested;
  add "session.subscribe accepts an AMQPQueue object".
- Flaky test: "session.onconnect fires after successful reconnection" used a
  fixed 500ms setTimeout instead of the onconnect callback as a signal;
  rewrite to use a proper promise/timeout pair like the recovery test.

P3 — fixed:
- JSDoc on session.client warns that overwriting client.ondisconnect breaks
  reconnection.
- JSDoc on subscribe options clarifies that queueArgs is only used when
  queueParams is also provided.

P3 — dismissed:
- Recovery failures keep the dead consumer in the tracking map (will retry
  on next reconnect). Expected behaviour — user can call consumer.cancel()
  to opt out. Not worth adding complexity for V1.

…e API

Introduces AMQPSession as the recommended high-level entry point for
applications that need automatic reconnection and consumer recovery.

New types and classes:
- AMQPSession.connect(url, options?) — picks TCP or WebSocket transport
  from the URL scheme; reconnects with configurable exponential backoff
- AMQPQueue — session-backed handle with publish, subscribe, get, bind,
  unbind, purge, delete; all operations are reconnect-safe
- AMQPExchange — session-backed handle with publish, bind, unbind, delete
- AMQPSubscription / AMQPGeneratorSubscription — stable consumer handles
  that survive reconnection; the generator variant bridges the async
  iterator across reconnects without any caller changes
- QueueSubscribeParams — ConsumeParams & { prefetch? }; prefetch sets
  channel QoS before each consume, including after reconnect
- AMQPSessionOptions — reconnectInterval, maxReconnectInterval,
  backoffMultiplier, maxRetries, tlsOptions, vhost, logger

Breaking changes:
- AMQPChannel.queue() removed; use ch.queueDeclare() + channel methods
  or session.queue() for the high-level API
- AMQPQueue is now session-only (constructor takes session + name);
  no longer returned by channel methods
- AMQPQueue no longer re-exported from AMQPClient / AMQPWebSocketClient
- session.client is private; use session.closed to check state
- Session operation methods (subscribe, publish, publishAndForget, get,
  bind, unbind, purge, deleteQueue, deleteExchange, exchangeBind,
  exchangeUnbind) are @internal and absent from .d.ts declarations;
  use AMQPQueue / AMQPExchange handles instead

Other fixes:
- WebSocket connections now use the vhost option instead of the URL path
- Concurrent getOpsChannel / getConfirmChannel callers no longer open
  duplicate channels

Closes #185