v0.2.3

Changed

• The controller assigns @interop/was-client's sync port directly, and
  WireDoc is aliased from the client like the other wire types. The unknown
  cast and the runtime putMeta probe are gone, since @interop/was-client
  0.54.0 types the port as what it implements, so a divergence in any port
  member is now a compile error at the seam rather than an error$ event inside
  a push or pull cycle (WS-10).

Fixed

• A delete with no assumed primary (a row created and deleted locally before the
  replica's first push) is skipped instead of sent as a header-less DELETE.
  Ids are content-addressed, so that unconditional delete tombstoned another
  replica's live copy of the same id. The row is reported accepted with no ack;
  the live copy stays on the server and comes down on its next feed change
  (WS-3).
• The /meta write's delete-race recovery now fires on the default port. A
  metadata-only edit against a resource another replica deleted used to reject
  the batch there (the recovery matched only the mapAuthErrors port's masked
  404), so RxDB retried the same write forever. One classifier now takes the
  default port's not-found signal and the auth port's status: 404 to the same
  corroborating feed re-read, and the row resolves as a tombstone conflict
  entry. Needs @interop/was-client 0.54.0, whose default-port putMeta raises
  the not-found signal (WS-4).