Repository files (latest commit first)

Filename	Latest commit message	Latest commit date
Libby 74705c7cd1 Rust RUDP server: answer a superseded sequenced write; order frame and packet by serial arithmetic ... Superseded packet: a reliable-sequenced packet that arrives after a newer one delivers no frame, yet is acknowledged and never resent, so its write went unanswered. The test (red first: only "new" was refused, "old" got nothing) showed the drop happens in the session below frame decoding, but an unfragmented packet carries its whole frame, so the server can read the id from the packet payload. Chosen: refuse it from the packet payload. A superseded fragment of a larger write has no readable id in the packet, so write-receipt.md now says that write may go unanswered and the client's unconfirmed outcome covers it. Ordering: frame.sequence <= packet.sequence is replaced by sequence_at_or_before, serial arithmetic modulo 2^32. Deviation from the brief: cultnet-rs' at_or_before carries a 4096-sequence receive window made for duplicate detection; a frame's first fragment may lie further back than that, so reusing it would leave such a sequenced write unrefused and applied. The new test pins that, and a hand mutant with the window fails it. A wrapped sequence cannot reach this compare through the session today (it is judged a duplicate), so the unit test pins the helper, not an end-to-end wrap. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>		2026-11-08 22:13:24 +00:00
..
cultmesh	content-vectors.ts-written.json regenerated by the script: five-slot chunk references	2026-10-22 22:00:41 +02:00
cultnet	Rust RUDP server: answer a superseded sequenced write; order frame and packet by serial arithmetic	2026-11-08 22:13:24 +00:00