9 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	f19e3ccffd	knowledge-base: retract an accepted record or its clauses on the operator's Approve ... The operator prefers removing a wrong decision to stacking a correcting record on it, and withdraw took only reserved or proposed records. retract asks the operator through the router like a record that needs the operator, and changes nothing until the Approve; a retracted record or clause no longer holds in ask, holds, get, links and progress, history keeps every version, and the whole-set rules still read a retracted record's links so a retraction alone raises no finding. withdraw with retraction true takes a waiting one back.	2026-10-31 10:07:58 +01:00
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
mesh-tools	3690c149c4	Merge pull request 'Forge rights read as the user sees them; write-only grant for mesh-tools; progress answers in minimal detail (issues 1945, 1947)' (#509) from fix/progress-and-unwritable into main	2026-10-26 20:08:05 +00: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	f0fbe193fa	gitea: mesh-tools administers a user's delivered repository and puts main's rule right, permissions read as the account sees them; knowledge-base.progress: minimal answers leave items to the tree, failed calls warn before parse faults (issues 1945, 1947)	2026-10-26 17:59:34 +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
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