Meta Vens
3fb2613abf
Networking tests: order is data, so pin each change's own publication, not its delivery order ...
The salvaged S1 and in-place re-upsert tests also asserted the delivery order
of the rejected drainer. Under Q-P1 A delivery order across threads and a
nested write's depth-first delivery are not guaranteed; each change is
published once with its own context, and wire peers drop stale changes by
Sequence (Cut 6). Both assertions now say exactly that. The journal tests'
reentrant-write recorder subscribes before the handler that writes.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-09-29 23:52:14 +02:00
Delete the CultCache MessagePack source generator
2026-09-13 23:38:08 +02:00
Delete the CultCache MessagePack source generator
2026-09-13 23:38:08 +02:00
Journal registration counts as disposed only once removal succeeds; a throwing hold body surfaces journal failures
2026-09-29 20:35:50 +02:00
Add canonical System.Text.Json converters for every CultMath value type
2026-09-29 16:57:31 +02:00
Extend the Cut 5 interop lane: a late C# native connector gets the TS retained frame
2026-09-23 18:32:39 +02:00
Fix a flaky disconnect wait in the reliable-ordered retention test
2026-09-23 18:20:36 +02:00
Merge remote-tracking branch 'origin/main' into hands/variants-c1
2026-09-29 06:48:32 +02:00
Wait for a client before quic-realtime-serve broadcasts
2026-09-23 14:38:51 +02:00
Networking tests: order is data, so pin each change's own publication, not its delivery order
2026-09-29 23:52:14 +02:00
Add real browser CultMesh transport proof
2026-08-18 00:05:57 +02:00
Regenerate the C1 variant vector: the variant overrides its indexed code
2026-09-29 06:59:29 +02:00
3fb2613abf