jochen aef908b57b Keep an event alive while its bundle handles it, and hold one at a time (hq issue 387) ...

The consumer's ack wait is 30 seconds and the runtime gives a handler two minutes,
so an event handled longer was offered again while it was handled; events waiting
in the client's buffer ran out their ack wait too, so a burst reached max-deliver
with nothing failed. Say in-progress every 10 seconds, as a worker's work does,
and pull one event at a time.

2026-10-10 17:18:35 +02:00

..

alive

Say the node tools are there, every minute (hq to-be 45 Phase 1, S11)

2026-10-06 10:06:29 +02:00

announce

Wait for every runtime discovery hears from, and name the ones it misses

2026-10-05 15:36:10 +02:00

bus

Keep an event alive while its bundle handles it, and hold one at a time (hq issue 387)

2026-10-10 17:18:35 +02:00

console

Rank a search the same whatever order discovery heard things in

2026-10-07 20:27:26 +02:00

launch

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

meshtest

Check the tool runtime's own code before it merges, every test on a bus of its own (hq ADR 0237)

2026-10-06 22:04:46 +02:00

runtime

Fail the contention test when the two writers never collided: it would prove nothing (the review of 2026-10-10)

2026-10-10 12:33:43 +02:00

wire

node-tools in Go: the node's runtime, launch-only, wire-compatible with the TypeScript (hq ADR 0193)

2026-10-03 21:21:52 +02:00