The best way to control Claude Code, Codex and more from any computer or phone
| 1 | "@effect/sql/SqlEventLogServer#layerStorage": |
| 2 | include: true |
| 3 | replacement: "effect/eventlog/SqlEventLogServerEncrypted#layerStorage" |
| 4 | note: "Moved to the encrypted server module; remove insertBatchSize. entryTablePrefix and remoteIdTable remain. It requires the `Digest` service from `effect/crypto/Digest` instead of EventLogEncryption, which hashed the table names in v3. Storage uses encrypted batch tables and entry-id lookup tables, not the old per-entry ciphertext schema; existing encrypted tables are not automatically converted." |
| 5 | "@effect/sql/SqlEventLogServer#makeStorage": |
| 6 | include: true |
| 7 | replacement: "effect/eventlog/SqlEventLogServerEncrypted#makeStorage" |
| 8 | note: "Moved to the encrypted server module; remove insertBatchSize. SQL and scope requirements remain; the EventLogEncryption requirement is replaced by the `Digest` service from `effect/crypto/Digest`. Storage uses encrypted batch tables and entry-id lookup tables, not the old per-entry ciphertext schema; existing encrypted tables are not automatically converted." |
| 9 | "@effect/sql/SqlEventLogServer#layerStorageSubtle": |
| 10 | include: true |
| 11 | replacement: "effect/eventlog/SqlEventLogServerEncrypted#layerStorageSubtle" |
| 12 | note: "Moved to the encrypted server module; remove insertBatchSize. The layer supplies the Web Crypto `Digest` layer. Storage now uses encrypted batch tables and entry-id lookup tables; existing per-entry ciphertext tables are not automatically converted." |