4 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	e2801773c3	Take an ordered engine's report as a send's answer only by its epoch and sequence (novox/hq issue 485) ... A periodic report about an identical earlier send names the same digest and can arrive after a later send the machine never received, so the digest and the time read it as applied. The digest-and-time rule stays for engines that report no order. Tests now hold the digest condition and the sequence one.	2026-10-11 20:44:54 +02:00
jschoubben	fae6bd0a87	Say each machine's last send in status and node show, and as fields in status --json (novox/hq issue 485) ... The send record of issue 234 is now readable only through the controller's verbs (issue 506), and only plan said it. status says per machine when it was last sent a declaration, by whom, from which generation and what it answered; node show says it in full with the refusal's words. A machine's answer is read from its report only when that report is about the send and came after it.	2026-10-11 20:40:48 +02:00
jschoubben	5dd0e3c056	Raise S20 for every generation refusal, ask for a push when the counter was behind, and write a send's generation with its digest (hq issue 234 review) ... A refusal of a send the mesh never recorded went only to stderr; it is now kept with its sender said to be unknown, and raised. A counter behind the machine (a store put back) is raised and the condition names push, since the receive loop must not push. The node's digest and generation are one transaction, and a send record that fails is said loudly without failing the send. The trigger ignores an update that changes nothing, and the put-back mark is dropped: a put-back is composed afresh with the current generation.	2026-10-11 11:55:27 +02:00
jschoubben	313efa826c	Say in every declaration the assignment generation it came from, and record every send (hq issue 234) ... A declaration newer in sequence than every other named four fewer modules than the assignments held, a machine applied it, and nothing the mesh kept said who sent it or from what view. The store now raises an assignment generation in the same transaction as every assignment change (a trigger, so a cascade counts too); a send reads it before composing, carries it to engines that said they read it, marks a gate's put-back, and is recorded with its sequence, sender, generation and modules. The would-send is stamped with what was last sent, so nothing reads behind for it; a refusal is kept on the send it refused and raised as S20 naming the sender; plan says what the machine was last told.	2026-10-11 11:30:16 +02:00