3 Commits

Include renames

Author	SHA1	Message	Date
jochen	12d4025d30	Say a walk's phases out of order unknown, never a negative time (hq issue 382) ... #206's own walk kept its first send 783 ms before its build, and delivery walks said send-first measured at -783 ms. A moment recorded before the one before it now makes both phases unknown: the earlier one's time joins the unknown time, the later one has none, and the walk goes on from the later moment. Measured phases and unknown time still add up to the total.	2026-10-10 21:15:48 +02:00
jochen	6805e2bcb3	Walk phases: a report past the silent bound never moves a walk's end; keep phases outside the hold on the plans; first-node gate in words (review of #206)	2026-10-10 20:20:07 +02:00
jochen	c640341c50	Keep each walk's phases and say a delivery over its budget (hq ADR 0282 slice 1, issue 382) ... The operator's budget (a leaf module running everywhere within five minutes of its merge, a core module within ten) cannot be held to without knowing where a walk's time goes. A walk now keeps when its batch's window closed, when it was cut and its class (migration 0093), each gate reading, and what each machine of the rest was sent; 'delivery walks' and plan-moved say its phases from the merge to every machine of the rest reporting the build applied, and ended walks keep them as walk-phase durations per class. Probe D16 reads mesh-delivery's 'times' and raises delivery.<class>.over-budget. A phase that cannot be measured is said unknown, never zero. Measurement only: no walk is held, sent or judged differently.	2026-10-10 20:15:01 +02:00