11 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	ec93585736	Ask a hold again after a restart, leave a merge ask room, take an answer only for its asking (issue 1906, review) ... A hold written again after a lift and a restart reused its first ask id, which the router drops; the hold's time is now its asking. Seven holds could take the router's three places for the teller and keep a merge Approve from being asked; the teller keeps at most two assigner asks open. A release or keep answered for one hold carried over to a later hold of the same fingerprint; an answer now counts only for the asking its warrant names.	2026-10-25 14:15:44 +01:00
jschoubben	6b63f13da6	Raise the assigner's asks on the operator channel, lift a hold once every node runs it healthy, keep the hold's cause (issue 1906) ... Seven modules stayed held on every machine and the operator was never asked: the teller only filled assigner asks from the view, a single failed check held a fingerprint for good, and the held record kept no cause. The teller now asks every assigner ask as it asks merge asks and writes the phone's answer under the ask's key; the assigner lifts a hold whose fingerprint runs healthy on every node that runs the module, says so once and takes its ask back; the held record names health, phase, when and the node's words.	2026-10-25 14:06:58 +01:00
jschoubben	57258b6fa4	Take the assigner's ask in the SDK's layout and name the asking in the view's answer, so a stale answer never fills a later asking (issue 1297 B9 and B10)	2026-10-23 15:22:32 +02:00
jschoubben	a48279b31a	Fill an assigner ask's answer from the view's answer under its view key, once and never for an ask that needs proof (issue 1297 B10)	2026-10-23 15:19:37 +02:00
jschoubben	037bf1ef36	Ask again at start a merge ask whose refusal the teller did not hear, since the router keeps no record of a refused ask (issue 1610, review round 1)	2026-10-21 16:45:31 +02:00
jschoubben	38116fe00a	Ask again a merge ask the router refused for want of room, once one of the teller's asks ends, so the operator is asked (issue 1610) ... The router holds at most three open asks of one asker and refuses a fourth without keeping it; the teller only logged the refusal, so a merge ask in a burst never reached the operator while the gate read it as asked (issues 1610, 1620). Bounded at six refusals, then said as a condition.	2026-10-21 15:54:08 +02:00
mesh-tools	bf59b5a27b	An answer to an earlier asking no longer blocks the next asking: the teller and the view tell the asking by the answer's warrant id (review round 2, R2-1)	2026-10-20 01:35:26 +00:00
mesh-tools	14e9d56a22	Ask under each asking's own router id, spell the heads in lower case as the gate does, show a removed have plainly; pin mesh-sdk ba684e5 (review round 1: G2, T1, issue 1370)	2026-10-20 01:30:54 +00:00
mesh-tools	5ba1da5b82	Carry the gate's merge asks to the router and write the operator's answer back, a warrant that does not hold said as a condition (issue 1343)	2026-10-20 00:28:36 +00:00
jschoubben	8e6a31bc6a	Fix the teller's integration test taking its result twice: it hung the merge check (issue 1240, review round 1)	2026-10-19 17:39:44 +02:00
jschoubben	a9c3980a2b	Add the teller module that waits for the gate's asks and writes nothing in release 3c (issue 1240)	2026-10-19 15:07:12 +02:00