jochen 1eaa1abbe9 Prove a write by compare-and-set loses no update under contention, on a real bus (hq research 042) ...

The issues module will hand out numbers through mesh/state.create and update. Two writers incrementing one
counter a thousand times each through the module's bus now end at two thousand with every number handed out
once; a stale, zero or future revision is refused with the lost-write code and writes nothing; a deleted key
can be created again; and the lost-write code reaches a bundle wrapped or not, and no other refusal carries it.
Both runtime tests run in the check's bundleless list, so mesh/repo-check runs them.

Part of the issue tracker decision, hq research 042.

2026-10-10 12:31:06 +02:00

..

error_code_test.go

Prove a write by compare-and-set loses no update under contention, on a real bus (hq research 042)

2026-10-10 12:31:06 +02:00

event_answer_test.go

Carry a bundle's seat traffic under its own name and kind, and start a module as its own account (hq ADR 0259)

2026-10-09 10:12:39 +02:00

launch.go

Serve a module from a runtime on its own account instead of switching users, keep bus words from bundles, and never give up a channel's work (hq ADR 0259 revision)

2026-10-09 10:12:39 +02:00

seat_test.go

Carry a bundle's seat traffic under its own name and kind, and start a module as its own account (hq ADR 0259)

2026-10-09 10:12:39 +02:00