keyId mismatch

Getting user reports of the keyId mismatch CRDT not ready error:

https://github.com/fireproof-storage/connect/issues/144

Here is the code where the error originates:

https://github.com/fireproof-storage/fireproof/blob/2515cc16b656c670ed424fb01cbef3688d44749e/src/runtime/keyed-crypto.ts#L85

The plan is to lean into named keys which should make this rare.

Start with src/runtime/keyed-crypto.ts around line 85 and compare the reported failure with connect issue 144. Trace when the keyId mismatch and “CRDT not ready” error occurs, then clarify the intended named-key behavior and define completion criteria, since the issue currently provides no specific change or test for done.

Written by the indexing model from the issue text.