4 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	2a0c428ef9	The last setuid search's start and each library's own take ask are keys of their own, which no number of other acts moves (issue 774, ADR 0563 §2, §4; rev-l3 round 1)	2026-10-28 20:35:33 +01:00
jschoubben	81fa009bf4	The node seat's acts and the engine's own asks are the node-engine's declared state acts on the bus: one key each under its own node's keys, written by compare-and-set, one ask open per path made by a create; acts reads one by its id (issue 774, ADR 0563 §2, §3)	2026-10-28 20:35:33 +01:00
jschoubben	aaffc19232	The node seat node-engine served on the engine's link: its verbs with their proven caller, its acts kept in its own state, a hand-over or access act asked of the operator as node-engine-<node> and performed only on the warrant (issue 774, ADR 0563 §1-§3)	2026-10-28 20:35:33 +01:00
jochen	8e79403c21	Show how far the setuid search got, and start a fresh one when the terminal asks (hq issue 361) ... The walk kept its progress every minute and nobody could read it: root-free said only that a search ran. The account verdict now carries the progress (counts, times, mount points; never a path) as fields and in its reason, outside what makes a verdict changed. A signed ask from the controller's terminal throws the last search away and starts a full one, after the operator removed by hand what it found.	2026-10-10 01:55:58 +02:00