6 Commits

Include renames

Author	SHA1	Message	Date
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
jochen	f58840b8a6	mesh-issues: check every new issue for a duplicate; claude-code: one judgement with no tools (hq ADR 0278) ... The operator asked for duplicate issues to be consolidated as they are opened. The tracker consumes its own opened event and asks the agent on its node, through claude-code's new claude_code_judge, whether an older issue not resolved asks the same question; it closes only the newer issue of a certain duplicate, keeping its report on the older one, and fails loudly when it cannot judge. groom runs the same judgement over the backlog as a dry run, applied on confirm.	2026-10-10 17:11:54 +02:00
jochen	d05308a419	mesh-issues: import hq's issue folders at their own numbers, and an issue with a folder is whole in the tracker (hq ADR 0275, to-be 53 slice 3)	2026-10-10 16:00:19 +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