3 Commits

Include renames

Author	SHA1	Message	Date
jochen	daa9f171ae	Issue reports carry only opened: the tracker holds every status, so no copy can drift ... The import of slice 3 (ADR 0275) was checked against every folder: no report changed since the commit it read, and the tracker holds each report's status, owner, fix, design amendment, replay and closing day. The keys are removed from all 361 reports, cycle.py refuses them in any report, and the playbooks, skills and READMEs that still pointed at them name the tracker instead.	2026-10-10 17:44:18 +02:00
jochen	2d18fa3380	Triage issues 228-278: close the fixed, re-check the rest ... Each issue is resolved with its fix and a replay or the reason none exists, or re-checked against main and the live mesh on 2026-10-08.	2026-10-08 01:31:10 +02:00
jochen	0333aac134	Issue 278: a module held by no machine was read as shared code ... The 103-module rebuild ADR 0236 put down to the build agent came from a file of the catalogue's reference module, read as shared because its definition was not in the merge. Records the issue, corrects ADR 0236's open question as a progressive insight (the tiering was right; the build agent never widens a plan) and amends to-be 30's rule for what a merge changed.	2026-10-06 19:57:21 +02:00