5 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	98d494619f	mesh-issues: take a delivery's id as mesh-delivery forms it, owner/repo@commit (hq issue 475) ... The delivery link's own pattern refused the slash and the @ every delivery id carries, so no delivery could be linked either. Mirror mesh-delivery's IDOf.	2026-10-11 19:24:23 +02:00
jschoubben	7714f164c3	mesh-issues: take every condition key the controller raises, a delivery's with its slash among them (hq issue 475) ... The tracker's own pattern refused the slash a delivery's id carries, so no issue could track a delivery's condition and the operator's alert kept saying no issue tracks it. Mirror the controller's key rule instead of a pattern of our own; a router test proves a slashed key is matched and named end to end.	2026-10-11 19:22:18 +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
jochen	6f2c76ee71	mesh-issues: an open whose write may have landed never says nothing was opened, and a module must itself be registered ... From the review: a taken key that cannot be read back, or a write never confirmed, now tells the caller to get the number before opening again; an owner entry naming a module is owned only by that module registered; link targets get the secret guard; line separators are refused in one-line fields; the acceptance test now proves the counter's own updates were contended.	2026-10-10 12:56:16 +02:00
jochen	2493e3e048	Add mesh-issues, the issue tracker, so an issue's number comes from one counter no two openers share (hq ADR 0275, to-be 53 slice 1) ... The seat issue-tracker, held once for the mesh: open, get, list, move, note and link. The counter is advanced by the SDK's compare-and-set Increment (go/v0.1.12) and started once at the setting first-number (365, after hq's highest), never below an issue kept. The cycle's issue rules are refused at the write; every change is an event. The runtime does not yet say who called, so every change is recorded as by "unproven" and no argument can name a caller.	2026-10-10 12:51:15 +02:00