mesh-delivery

Files

T

jschoubben 2469531c2f Subtask A: a record ask is kept while its node waits on it or its yes is unwritten, and an ask written again is asked again under a new id (issue 1966)

The assigner took record.novox.nats away as stale in the same second the operator's yes
was written (the yes counts only while the ask is there), and rewrote it under the id the
router already kept, so the teller never asked it again. The stale test compared a module's
ask with the whole node's composition; it now reads the module's own have, and restore and
record asks are numbered by their writing's time as hold asks are.

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

2026-11-09 22:47:32 +01:00

mesh-delivery-assigner

Subtask A: a record ask is kept while its node waits on it or its yes is unwritten, and an ask written again is asked again under a new id (issue 1966)

2026-11-09 22:47:32 +01:00

mesh-delivery-builder

The builder's build log has a cap that holds its 30 days (issue 1966, recovery)

2026-11-09 09:45:37 +01:00

mesh-delivery-checker

The compose ask carries its request gzip-packed; requests of another version are refused by name (issue 1966)

2026-11-09 16:41:56 +01:00

mesh-delivery-forge-bridge

A lost take-in hold passes the take-in event's check, so it is said (issue 1966)