knowledge-base.progress: how far a design, milestone, issue or record has come, in one call (issue 1947) #504

Merged

mesh-tools merged 4 commits from feat/1947-progress into main 2026-10-26 16:42:30 +00:00

Conversation 1 Commits 4 Files Changed 23

+3652 -12

4 Commits

Author	SHA1	Message	Date
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
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
jschoubben	5e516317e9	Issue tracker: list rows say when each issue last moved, and list takes linked (issue 1947) ... The knowledge base's progress verb reads a milestone's issues in one call and must say when each last moved, and the issues linked to a record or a design; neither was readable without one get per issue.	2026-10-26 16:29:56 +01:00