18 Commits

Include renames

Author	SHA1	Message	Date
mesh-tools	c93954e53c	Pin mesh-sdk to main's merge of #47 (88581d0a), the same tree as ba684e54 the review read	2026-10-20 06:33:01 +00:00
mesh-tools	bf59b5a27b	An answer to an earlier asking no longer blocks the next asking: the teller and the view tell the asking by the answer's warrant id (review round 2, R2-1)	2026-10-20 01:35:26 +00:00
mesh-tools	14e9d56a22	Ask under each asking's own router id, spell the heads in lower case as the gate does, show a removed have plainly; pin mesh-sdk ba684e5 (review round 1: G2, T1, issue 1370)	2026-10-20 01:30:54 +00:00
mesh-tools	34f585106f	Show the open asks in the delivery view: the gate's asks with no answer, in the table, the page and the command's JSON (issue 1345)	2026-10-20 00:34:28 +00:00
mesh-tools	3c655c5ab4	Write a failed build as the controller does, an outcome with failed set (issue 1281)	2026-10-19 22:47:41 +00:00
mesh-tools	8ffcf02a9c	Take the SDK that counts a stateless build record as an outcome; fixtures in the controller's layout (issue 1281)	2026-10-19 22:44:21 +00:00
jschoubben	4b8e71370c	Recognise a trunk build by repository identity and an empty ref in the indexer and the view (issue 1281) ... Build records name their repository by clone URL and a plan-asked build has no ref, so no module fingerprint was ever written or compared; both now use the SDK's tests.	2026-10-19 22:39:51 +02:00
jschoubben	35ff628458	Commit no module's dependencies: fetch them in the check, the pinned SDK from beside it (issue 1235)	2026-10-19 15:27:37 +02:00
jschoubben	9e9c2a7a57	Show the candidate groups and each module's fingerprint against its trunk build's in the delivery view (issue 1241)	2026-10-19 15:10:16 +02:00
jschoubben	d309bb6cef	Put the view's socket in /var/lib/mesh-delivery-view-cli: the node-engine never places a module's directory below /run (issue 1134)	2026-10-19 01:53:11 +02:00
jschoubben	954728b390	Show what the watchman says: offline presence, stuck keys and unreadable values, in the view and its command (issue 1168)	2026-10-19 00:55:19 +02:00
jschoubben	f032b384c9	Pin the SDK at the commit that holds the stuck bucket's types (issue 1168)	2026-10-19 00:54:15 +02:00
jschoubben	8a8cafd3db	Place the view's command as one file in /usr/local/bin, not the directory mesh-cli declares (issue 1134)	2026-10-19 00:09:54 +02:00
jschoubben	67964cae3f	Show a pulled-in module as running with what pulled it in (issue 1134, AC3 revised)	2026-10-18 19:36:03 +02:00
jschoubben	5d48048d41	Make the manifest pass the controller's module check: files archive and moved (issues 1134, 1137)	2026-10-18 19:36:03 +02:00
jschoubben	eb8966c4b7	Add the mesh-delivery-view process, its manifest and the nox-delivery alias (issues 1134, 1137) ... The process watches the three buckets on its own read-only credential; the manifest declares reads only, no state and no emits; the zsh item carries the alias as mesh-cli's does.	2026-10-18 19:31:50 +02:00
jschoubben	1b6763de0d	Serve the rows on a read-only socket and web page, and print them with mesh-delivery-cli (issue 1134) ... The command holds no credential: it asks the local socket, which answers only the rows ask.	2026-10-18 19:31:50 +02:00
jschoubben	0dbe8f9a32	Derive the delivery view's rows from the have, assignments and builds buckets (issue 1134) ... The operator sees per module and node what is assigned, what the node reports and what it waits on; a have with no open assignment is left behind, never running.	2026-10-18 19:31:50 +02:00