7 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	eb79996336	The tracker derives a fix's delivered from the delivery view's event, not the gate's gone states (issue 1946)	2026-10-24 16:50:50 +02:00
mesh-tools	56ba1c3837	Hear the gate's transition alone: today's module is forgotten (issue 1406)	2026-10-20 13:02:35 +00:00
jochen	983d434623	mesh-issues: keep every issue in the log changes and the bucket as its fold, so the record outlives the bucket's cap and a week of events (hq ADR 0300, issues 501, 502) ... Every write appends one operation at the issue's last sequence before the bucket is written; a refused append writes nothing. The start carries what the bucket holds, refolds what is behind and indexes every issue in memory, so list answers from memory with a ranked search and a before cursor.	2026-10-12 02:41:54 +02:00
jochen	11afde55d6	mesh-issues: an issue says who works on it, and resolves only from fixing (hq issue 399) ... Two agents could start on one issue without seeing each other, and an issue could be resolved without anyone having said they started its fix. A move to diagnosing or fixing now names by, the worker as who@node; get and list show the worker with since and stale; another worker is refused while it is current unless take-over says why (noted); a worker untouched for worker-stale-after (24h) may be taken over from without a reason. Resolved is reached only from fixing. The moved event carries by, since and caller. Fixing counts as not closed for the triage and the duplicate check. hq ADR 0283.	2026-10-10 21:04:32 +02:00
jochen	6bd69ebadc	mesh-issues: a verdict naming issue 0 is none, and the tracker's own module is a registered owner (issue 396) ... The model says 'no issue' as related to 0; the triage took that as an issue not offered and failed the issue instead of triaging it.	2026-10-10 18:27:53 +02:00
jochen	01bde68f96	mesh-issues: an issue knows whether its fix is delivered, says it ready to verify, and a fix stuck after its merge is said (hq ADR 0281) ... The operator approved measuring from the delivery's own events whether each fix an issue names reached the machines; delivered is not resolved, and a merged fix that does not arrive is said on the issue and the operator's channel instead of found.	2026-10-10 18:12:52 +02:00
jochen	9bb8253609	mesh-issues: triage every new issue — severity, needs, suggested owner, dependencies — and say an issue ready when what it depends on is delivered (hq ADR 0279) ... The operator asked for the judgement that already reads the backlog to fill what an issuer cannot know, and for dependencies between issues, an issue being workable only once what it waits for is on the machines. The triage fills only empty values, adds links and removes none; readiness follows mesh-delivery's own events, said once per spell, through a duplicate to its original, and loud when a delivery cannot be asked.	2026-10-10 17:56:08 +02:00