cultmesh-ts tests: drop the bare-id-string snapshot handle assertion

Main's documentFromPeerSnapshot takes a definition only, so the string-handle
read (first record at the key) that C2a held for Eve Electron cannot be
expressed; the assertion and requestCultNetRawSnapshotDocument's
firstRecordAtKey option went with it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Meta Vens 2026-10-14 04:24:12 +02:00
commit a114d6a9db

View file

@ -3293,12 +3293,6 @@ test("CultMesh TS peer snapshots never take another type's record at the key", a
}
// The failed sync of a note at "note:b" left the local record of the other type there untouched.
assert.deepEqual(target.getRequired(incompatibleNoteDocument, "note:b"), { nope: "local b" });
// HELD for the schema-naming fork: a handle named by a bare id string still takes the first record at the key, which
// is how Eve Electron reads the C# daemon's hash-stamped records.
assert.deepEqual(
await CultMesh.documentFromPeerSnapshot(peer, "cultmesh.note.v0", "note:c", { timeoutMs: 1_000 }).latest(),
{ noteId: "note:c", body: "remote c, note-shaped" },
);
// Its own type's record under its own id still syncs.
assert.deepEqual(
await target.syncDocumentFromPeerSnapshot(peer, incompatibleNoteDocument, "note:b", { timeoutMs: 1_000 }),