9 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	e61141f596	Keep the packages this node's compositions declare in the engine's own key, and answer them on the node seat (ADR 0565 clauses 6 and 15, issue 1953) ... pacman still reads the controller's mirror because no engine wrote its key: the engine now keeps each handed composition's package resources and, after a pass that handed something new, writes mesh-host_packages.<node> only when the value differs, owed after the growing bound when refused. The manifest declares the state so the grants part creates it. The verb packages answers the key beside the mirror's key for the node and their difference, and with write writes the key again from what was composed. H8's integration test proves the write under the grant the grants part composes. Needs mesh-sdk feat/node-packages (0ef7c0c) for DeclaredPackagesOf and the engine's read of the mirror (go.mod pin left for the lead: the SDK commit is not pushed). Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-01 16:09:13 +01:00
jschoubben	9c15610f70	Say when the node composes again after a seat that did not answer, say what a long pass waits on, and serve the verb compose (issue 774) ... On 2026-10-31 ace's route-proxy said only that the vault could not be asked, and ace said nothing for five minutes while a pass waited after the vault restarted; the retry that already existed was invisible. A refusal for a seat or a read that did not answer now says when the node composes again ("the node composes again at HH:MM:SS (try N)"), a retry pass says it starts, a pass that runs on says every minute what it waits on, and the node-engine's verb compose makes a pass now and says how it went, so a person recovers without a restart.	2026-10-31 00:56:47 +01:00
jschoubben	08e9d15817	Serve the node-engine verb composition: a module's composition beside what runs, its judgement and its diff (issue 774) ... Four providers waited for a yes on 2026-10-31 and nobody could read what waited: the have said only "where its data is kept". The read verb composition answers it from the engine: the latest revision of the want's build or the one asked by digest, every revision the bucket keeps, what runs and where that is known from, the want and the have, the move's judgement and whether it waits for a yes, and with diff the resources that differ, a received file naming its consumers. revisionNamed now reads the same revisions.	2026-10-31 00:26:57 +01:00
jschoubben	45d0348044	Revert "Merge pull request 'Revert L3: its node-engine removed every held module on novox, the bus server among them (issue 774)' (#174) from revert/774-l3 into main" ... This reverts commit 1ec73915b8, reversing changes made to 0a4c35f731.	2026-10-29 21:04:13 +01:00
jschoubben	f81e6147ae	Revert L3 (mesh-host, merge 0a4c35f): its node-engine removed every held module on novox, the bus server among them, at 08:54 CET on 2026-10-29 (issue 774) ... L3 lands again with two fixes: a held module is never removed, and the grants cover L3's new subjects.	2026-10-29 09:42:29 +01:00
jschoubben	6cbdb3712e	Judgements and refused setuid searches, which any caller may ask, roll in one bounded key of the node's and add no key to the bucket every node shares; a key per act is kept for hand-overs, access acts and searches started (issue 774, ADR 0563 §2; rev-l3 round 2)	2026-10-28 20:35:33 +01:00
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