5 Commits

Include renames

Author	SHA1	Message	Date
jochen	a5c38892a7	mesh-issues: review — one judgement at a time with new issues first, one verdict applied at a time, a resolved issue left alone on redelivery, the pass's answer a copy (hq ADR 0278) ... An independent review found a pass could starve new issues' checks, two writers could apply one verdict twice, a judged issue resolved by a person could still be linked, and the dry run's answer raced its pass.	2026-10-10 17:20:07 +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	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