4 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	dfe490d9e2	issue-tracker.changes reads each issue's moves over a window from the tracker's own log, so progress since says from what each issue moved, not only where it is	2026-10-28 12:33:01 +01:00
jschoubben	4f317201c9	knowledge-base.progress takes since: only what changed in a window, read from the tracker's and mesh-delivery's history, so a five-minute report says what moved (the operator, 2026-10-28)	2026-10-28 12:33:01 +01:00
jschoubben	76e4ec4dc6	mesh-issues and mesh-knowledge: milestones are records of the issue tracker, and progress reads them (ADR 0493 §1 to §4, issue 1781) ... mesh-issues keeps each design's milestone in the state milestones (history 5), says milestone-set and milestone-moved, and serves milestones, milestone-set and milestone-move. An issue's milestone is its own link of kind milestone, so at most one milestone per issue is checked inside the issue's own write; kind commit links a fixing commit. The triage links no milestone, pull request or commit. import with milestones=N seeds a design's table once. mesh-knowledge's progress reads issue-tracker.milestones and its table parse is gone. Squashed from four commits so the branch history does not carry a compiled bundle that was committed by mistake (6 MB); the path is now in .gitignore.	2026-10-26 18:42:51 +01:00
jschoubben	8da33e43d4	Knowledge base: progress says how far a design, milestone, issue or record has come (issue 1947) ... A lead's five-minute report and 'is design 47 nearing its end' were joined by hand from the design file, the tracker and the deliveries. One verb now works the state out (ADR 0424 §1), minimal for every five minutes, detailed for the report's tree. Milestones are read from the design's table until the tracker's milestone records (issue 1781) are delivered.	2026-10-26 16:37:54 +01:00