1"@effect/experimental/EventLogRemote#Ack":
2 include: true
3 replacement: effect/eventlog/EventLogMessage#WriteAck
4 note: Write RPCs now return arrays of entryId/sequence acknowledgements in request order. WriteSingleRpc returns them directly; WriteChunkedRpc returns them on the completing chunk, with empty arrays for earlier chunks.
5"@effect/experimental/EventLogRemote#Changes":
6 include: true
7 replacement: effect/eventlog/EventLogMessage#ChangesRpc
8 note: ChangesRpc replaces the separate request and response models with one streaming RPC. Encrypted changes carry EncryptedRemoteBatch records. Built-in servers acknowledge writes from this connection instead of echoing them through changes.
9"@effect/experimental/EventLogRemote#decodeRequest":
10 replacement: effect/eventlog/EventLogMessage#EventLogRemoteRpcs
11 note: Generic RPC framing and RpcSerialization.layerSchemaBinary replace the module-specific request decoder.
12"@effect/experimental/EventLogRemote#decodeResponse":
13 replacement: effect/eventlog/EventLogMessage#EventLogRemoteRpcs
14 note: Generic RPC framing and RpcSerialization.layerSchemaBinary replace the module-specific response decoder.
15"@effect/experimental/EventLogRemote#encodeRequest":
16 replacement: effect/eventlog/EventLogMessage#EventLogRemoteRpcs
17 note: Generic RPC framing and RpcSerialization.layerSchemaBinary replace the module-specific request encoder.
18"@effect/experimental/EventLogRemote#encodeResponse":
19 replacement: effect/eventlog/EventLogMessage#EventLogRemoteRpcs
20 note: Generic RPC framing and RpcSerialization.layerSchemaBinary replace the module-specific response encoder.
21"@effect/experimental/EventLogRemote#EventLogRemote":
22 include: true
23 replacement: effect/eventlog/EventLogRemote#EventLogRemote
24 note: Use the v4 Context.Service; methods now take storeId-aware options. write may return entryId/sequence acknowledgement arrays; custom remotes can still return void when confirming uploads through changes instead.
25"@effect/experimental/EventLogRemote#fromSocket":
26 replacement: effect/eventlog/EventLogRemote#makeEncrypted + effect/rpc/RpcClient#makeProtocolSocket
27 note: Construct the encrypted remote separately from its generic RPC socket protocol.
28"@effect/experimental/EventLogRemote#Hello":
29 replacement: effect/eventlog/EventLogMessage#HelloResponse
30 note: HelloResponse replaces Hello and includes the v4 authentication challenge; HelloRpc defines the endpoint.
31"@effect/experimental/EventLogRemote#layerWebSocket":
32 replacement: effect/eventlog/EventLogRemote#layerEncrypted + effect/rpc/RpcClient#layerProtocolSocket
33 note: Compose the encrypted remote with the generic socket protocol, SchemaBinary serialization, and a Socket provider.
34"@effect/experimental/EventLogRemote#layerWebSocketBrowser":
35 replacement: effect/eventlog/EventLogRemote#layerEncrypted + effect/rpc/RpcClient#layerProtocolSocket + @effect/platform-browser/BrowserSocket#layerWebSocket
36 note: Compose the encrypted remote and generic RPC socket protocol with the browser WebSocket layer.
37"@effect/experimental/EventLogRemote#Pong":
38 replacement: none
39 note: The event-log Pong model was removed; heartbeats belong to the generic RPC socket protocol.
40"@effect/experimental/EventLogRemote#ProtocolRequest":
41 replacement: effect/eventlog/EventLogMessage#EventLogRemoteRpcs
42 note: EventLogRemoteRpcs and generic RPC serialization replace the old protocol request union.
43"@effect/experimental/EventLogRemote#ProtocolRequestMsgPack":
44 replacement: effect/rpc/RpcSerialization#layerSchemaBinary
45 note: Use the generic SchemaBinary RPC serialization layer instead of a request-specific schema.
46"@effect/experimental/EventLogRemote#ProtocolResponse":
47 replacement: effect/eventlog/EventLogMessage#EventLogRemoteRpcs
48 note: EventLogRemoteRpcs and generic RPC serialization replace the old protocol response union.
49"@effect/experimental/EventLogRemote#ProtocolResponseMsgPack":
50 replacement: effect/rpc/RpcSerialization#layerSchemaBinary
51 note: Use the generic SchemaBinary RPC serialization layer instead of a response-specific schema.
52"@effect/experimental/EventLogRemote#RemoteAdditions":
53 replacement: none
54 note: This unused protocol model has no v4 counterpart.
55"@effect/experimental/EventLogRemote#RequestChanges":
56 replacement: effect/eventlog/EventLogMessage#ChangesRpc
57 note: ChangesRpc replaces the separate request model with one streaming RPC.
58"@effect/experimental/EventLogRemote#StopChanges":
59 replacement: none
60 note: Interrupt the ChangesRpc stream instead of sending a StopChanges message.
61"@effect/experimental/EventLogRemote#WriteEntries":
62 include: true
63 replacement: effect/eventlog/EventLogMessage#WriteEntries
64 note: Use the storeId-aware write payload with batches of EncryptedBatch instead of iv and encryptedEntries. Each batch contains entryIds, iv, and encryptedBatch; it is not compatible with the old per-entry ciphertext format.