4 Commits

Include renames

Author	SHA1	Message	Date
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	87fe2c45cf	Knowledge base: progress counts an issue done only once its fix is delivered, and says every gap (issue 1947, review round 1) ... A resolved issue whose delivery is held or failed is stuck, one merged and not delivered is moving; a row the tracker did not answer, an answer that does not read and linked issues cut by the list's limit are said as warnings instead of passing silently.	2026-10-26 17:02:47 +01:00
jschoubben	5baf8ad1d7	Knowledge base: progress is proven over the bus with the module started whole (issue 1947) ... The verb asks three seats and the records module; only a run over a real bus shows its grants and subjects line up with what the manifest invokes.	2026-10-26 16:39:19 +01:00