4 Commits

Include renames

Author	SHA1	Message	Date
jochen	75213b9091	Say a walk that waits too long, and a delivery's own stalls (hq ADR 0239) ... A walk mesh-delivery never lets go waited for ever with nothing open: S16 says it at 30 minutes, urgent at 4 hours, naming plans go. Phase B: probe D14 reads the delivery owner's stalled and raises delivery.<id>.stalled, and H2 takes the table's transition through its close.	2026-10-07 00:16:32 +02:00
jochen	8ddc019cd2	Grant the self-check its ban-list question, say a refusal at once, judge the engine by its delivered version (hq to-be 45 Phase 1) ... Live on 2026-10-06, two of the first self-check's findings were its own: - D8 asked every machine's node-intrusion-prevention.banned, and the controller's grant did not name the subject: the bus refused it 24 times and D8 timed out after thirty seconds instead of saying so. The verbs the self-check asks are named in broker.VerbsTheSelfCheckAsks and granted (mesh.seat.<seat>.tool.<verb>.*); each probe declares the seat verbs it calls, askSeatTool refuses an undeclared one, and a test over the registry fails a probe whose question the controller is not granted. AskSeatTool now returns a refused publish at once ("the bus refused…") instead of waiting out its timeout; D8 asks the machines in parallel. - D10 read every machine as behind right after a push: a node-engine says its version as the directory it is delivered into, the archive's digest (31045596c83a, catalogue versionOf), and D10 compared that with the build's commit (1545b00a). It now compares with the versions the registered build is delivered as, and a hand-placed engine's commit.	2026-10-06 10:44:38 +02:00
jochen	9873b3bf13	Keep a replay from moving the mesh backwards, and tighten the queue's edges (review of hq ADR 0219) ... A registered replay asked now outranked newer asks of its module, and a plan took any later outcome as its answer. A replay is now refused while the module is asked anywhere, a plan module asked under an id is answered by that id alone, and a rebuild of a commit asks what the module follows. An ask handed back after a restart no longer reads as dead; a cancel that meets a start is withdrawn; pause holds for an ask fetched as it lands; kill removes containers before and after the build ends and says whether its outcome went out; a holder may say only its own machine is paused.	2026-10-05 19:45:45 +02:00
jochen	e610f2d92c	Let a build agent be paused, have a build killed, and end an ask cancelled as it took it (hq ADR 0219) ... A queued ask could only be waited out and a running build only ended by stopping the machine, which redelivered it elsewhere. The holder now serves current, kill, pause and resume on its own machine's subjects; a kill ends the build's process group and labelled containers and settles the ask as failed, killed by hand; pause is kept in the workspace across a restart and said on the bus. The controller writes cancelled ids to a cancelled set the holder reads on taking an ask, closing the race a delete alone leaves.	2026-10-05 19:17:42 +02:00