v0.2.6

Changed

• Update to latest was-client dev dep.

v0.2.5

Fixed

• Fix pnpm workspace, bump latest was-teaching-server devDep.

v0.2.4

Changed

• The undecryptable-side conflict warnings carry a reason (unknown-epoch,
  key-unwrap, or other), classified through @interop/was-client/sync's
  isUnknownEpochError and isKeyUnwrapError, so a spent or unwired descriptor
  refresh is told apart from a key this reader was never given.
• Documented where the unknown-epoch refresh rule sits relative to the driver:
  it runs inside the injected decrypt closure, which on an encrypted
  collection should be @interop/was-client/edv's
  createRefreshingEdvDocCipher. The driver holds no cipher and runs no refresh
  of its own.

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).

v0.2.2

Changed

• Update to latest was-client.

v0.2.1

Fixed

• Fix the was-client dependency from link to npm.

Tests

• The live-server integration suite now covers resurrecting a row that carries
  custom: the content create and the /meta create-if-absent land in one push
  cycle with a single conflict resolution, and a /meta If-Match carrying the
  pre-delete metadata ETag is refused with 412 after the re-create.

v0.2.0

Changed

• Breaking: putContent / deleteContent / putMeta on the sync port now
  resolve a WriteAck ({ version, etag? }) instead of a bare revision number,
  matching was-client's opaque ETag contract. MasterState / WireDoc /
  SyncedDoc gain etag / metaEtag, and a conditional write's ifMatch is
  now the validator echoed back verbatim -- it can no longer be rebuilt from a
  version number. The replica schema's shape changed to carry the new fields, so
  an existing replica is forgotten and re-pulled at the next login (schema
  version stays 0).

Fixed

• Resurrecting a resource another replica deleted converges in one cycle on the
  plain was-client port (WS-2). A 412 whose re-read resolves null now builds
  a tombstone conflict entry with version: 0 and no etag instead of a
  version copied from local state, and an assumed primary that is a tombstone
  routes the next content write to If-None-Match: * (the one precondition a
  server accepts against a tombstone) and a delete to an unconditional DELETE.
  Before the opaque-ETag change the re-push sent If-Match with the fabricated
  version and looped hot; after it, an unconditional PUT that could overwrite
  a concurrent re-create.

v0.1.2

Added

• The driver's swallow points now log: the ack write-back failure at warn, and
  the benign-412 delete re-issue and the conflict hand-back at debug.

Changed

• Breaking: FakeWasServer is removed from @interop/was-sync/testing. The
  integration suite now runs against a live in-process was-teaching-server
  through the real createWasSyncPort from @interop/was-client, so the
  server's conditional-write, tombstone, and changes-feed behavior is
  exercised rather than modeled (WS-11). The stub port and the memory schedule
  and online source remain on the subpath.
• Breaking: SyncLogPort and the per-call log options on
  createSyncController, makeConflictHandler, lwwResolver, and
  makeLwwConflictHandler are removed. The package adopts the ecosystem logging
  library port instead: setLogger and the Logger type on the root entry. An
  app wires one logger once at bootstrap, e.g.
  setLogger(createLogger('sync')); the console fallback (prefixed
  [was-sync]) applies otherwise (WS-12).

Fixed

• A delete's 404 no longer wedges the push batch on the default was-client
  port. The push handler reads the not-found signal from deleteContent (by
  err.name) as the already-gone outcome, matching what a mapAuthErrors: true
  port already resolves itself, so the batch completes and its other rows land
  (WS-1). A spec-conformant server answers 204 for an authorized delete of an
  absent resource; the 404 on that path is a masked authorization refusal,
  which still surfaces on the next feed pull.
• The packaging suite (formerly test:dist) is now test:packaging and lives
  in test/packaging/. The old test/dist/ directory matched the unanchored
  dist line in .gitignore, so the suite was never committed and CI failed
  with "No test files found". The ignore entry is now anchored to /dist.

v0.1.1

Added

• Initial release. The WAS replication driver for RxDB, merged from the two
  copies that had drifted apart in @interop/was-react (src/sync/) and in the
  Freewallet browser wallet (src/lib/sync/). Neither consumer may depend on
  the other, so a shared package is the one home the driver can have. The
  placement, its rejected alternatives, and its revisit criteria are recorded in
  decisions/0001-rxdb-replication-driver-package.md.
• Three entries. @interop/was-sync carries the wire and replica types, the
  synced-document schema, the conflict-handler seam with its last-write-wins
  default, and the writer-id mint; it is free of rxdb in its module graph and
  in its emitted declarations, so an app that never builds a replica resolves it
  with rxdb absent. @interop/was-sync/rxdb carries the pull and push
  handlers, the replicateRxCollection wiring, the feed-backed conflict
  re-read, and the controller core. @interop/was-sync/testing carries the
  fixtures. @interop/was-client and rxdb are peer dependencies; rxdb is
  marked optional.
• The pull side: the changes-feed handler and the wire-to-replica mapping,
  with the empty-page rule keyed on a nullish response checkpoint so the feed
  never restarts from its origin.
• The push side: content-then-metadata write routing (a metadata clear writes
  the cleared state rather than being skipped), the 412 conflict assembler, the
  benign-412 delete retry that keeps a stale revision from leaving a deleted
  resource live on the server, the per-batch primary-read memo, the /meta 404
  corroboration, and the acked-revision write-back.
• The conflict-handler seam. makeConflictHandler takes the decision as an
  injected resolver receiving the whole RxDB conflict input, so a wallet can
  delegate to its own comparator while an app framework uses the packaged
  lwwResolver (which scores an undecryptable side apart from an absent one).
  makeLwwConflictHandler is the two together.
• The controller core: one serialized FIFO lifecycle over a session's
  collections, a terminal stop(), a failed bring-up that unwinds and rethrows
  without latching, the skip-and-flag for a collection no delegated capability
  covers, the auth escalation over RxDB's wrapped error graph, the remote-change
  subscription off the collection stream, and injected timer and reachability
  ports.
• The writer-id mint, over a required key prefix and an injected storage port. A
  storage that cannot answer mints a fresh id per call and remembers nothing.
• An injected { warn, error } log port on the controller core, the
  conflict-handler factory, and the last-write-wins resolver, defaulting to a
  no-op, so diagnostics ride each consumer's own logging seam. The factory logs
  one thing of its own: a resolver that throws, which RxDB treats as a fatal
  replication error, is reported with the row it happened on before it
  propagates. The port's metadata argument is Record<string, unknown>, which a
  namespaced logger satisfies directly.

Changed

• The behavior set is the union of the two source copies, with each side's
  deltas ported into the merge base before the move: the benign-412 delete
  retry, JCS-canonical body equality, the server-managed createdBy carried
  across live documents and tombstones, and err.name classification in place
  of instanceof (@interop/was-client's
  decisions/0001-cross-package-errors-match-by-name.md).
• The synced-document schema is the union of the two copies (createdBy, the
  required list, and the updatedAt index), shipped at version: 0 with no
  migration strategy. RxDB refuses to open a replica whose stored schema hash
  differs at the same version, so every remembered browser in both consuming
  apps needs one forget-and-log-in-again after the upgrade. Transient sessions
  are unaffected.
• The server-side state a 412 re-read resolves is named "primary" throughout
  (PrimaryState, PrimaryReadCache, withFeedPrimaryRead,
  feedPrimaryPort.ts), renamed from the merge base's "master". RxDB's own
  field names on a push row (assumedMasterState, realMasterState) are RxDB's
  API and are unchanged.