1"@effect/experimental/EventJournal#EntryIdTypeId":
2 replacement: effect/eventlog/EventJournal#EntryIdTypeId
3 note: Import EntryIdTypeId from the v4 EventJournal module; it is now a string brand.
4"@effect/experimental/EventJournal#ErrorTypeId":
5 replacement: none
6 note: The v4 error marker is private; narrow with EventJournalError instead.
7"@effect/experimental/EventJournal#makeEntryId":
8 include: true
9 replacement: effect/eventlog/EventJournal#makeEntryIdUnsafe
10 note: The unchecked EntryId constructor was renamed to makeEntryIdUnsafe. Without explicit msecs, ids advance monotonically within the process using a logical millisecond and counter, so their timestamp can exceed wall-clock time when the clock stalls or moves backwards. Explicit msecs bypasses this sequence.
11"@effect/experimental/EventJournal#makeRemoteId":
12 replacement: effect/eventlog/EventJournal#makeRemoteIdUnsafe
13 note: The unchecked RemoteId constructor was renamed to makeRemoteIdUnsafe.
14"@effect/experimental/EventJournal#RemoteIdTypeId":
15 replacement: effect/eventlog/EventJournal#RemoteIdTypeId
16 note: Import RemoteIdTypeId from the v4 EventJournal module; it is now a string brand.
17"@effect/experimental/EventJournal#makeMemory":
18 replacement: effect/eventlog/EventJournal#makeMemory
19 note: The in-memory constructor moved into core Effect and now returns the Context.Service implementation through its Service projection.
20"@effect/experimental/EventJournal#EventJournal":
21 include: true
22 replacement: effect/eventlog/EventJournal#EventJournal
23 note: Custom journal services must implement entriesById, writeMany, and writeRemoteAcks. writeFromRemote.effect now receives one array of entry/conflicts pairs per batch, not one pair per callback. Read conflicts before invoking it and commit the batch only after it succeeds. Replay entries in entry-id order; conflicts are stored entries with strictly greater ids, also in id order. Compaction replacements use the source entry as their ordering and conflict anchor.