mesh-delivery

Files

T

jschoubben 531d05ab4b indexer: hear a group's end, keep merges pending, take in at start (ADR 0633 §2, §4, issue 1585)

The consumer tells a group's end apart by its name before the forge decode,
a merged message goes through the pending state, and the pending revisions
naming this build are taken in before the consumer starts; take-in events go
on the indexer's own stream. Until the pending state is on the bus every
merge is taken in at once, as before.

Claude-Session: https://claude.ai/code/session_01JG73KG7AfSdh6FP8VrBqCn

2026-11-04 23:08:37 +01:00

cmd

indexer: hear a group's end, keep merges pending, take in at start (ADR 0633 §2, §4, issue 1585)

2026-11-04 23:08:37 +01:00

internal

indexer: hear a group's end, keep merges pending, take in at start (ADR 0633 §2, §4, issue 1585)

2026-11-04 23:08:37 +01:00

judge

Words back: the tool runner is what says tool-runner again; sdk/toolrunner goes (issue 774, issue 1585)

2026-11-03 23:09:20 +01:00

testdata/beside

Fall back to a captured copy only for mesh-host, which the checker places beside no mesh-delivery check (issue 1585)