knowledge-base.progress takes since: what changed in the last hour; issue-tracker.changes says each issue's moves from what to what #541

2026-10-28T11:34:14Z

mesh-tools commented

2026-10-28 11:34:14 +00:00

The operator (2026-10-28): "can the progress tool also report the progress made since the last call, or maybe better, the last 60 minutes" - as a parameter.

modules/mesh-knowledge: progress gains since (a window such as 5m or 60m, at most 24 h). The answer lists only what changed under of: milestones moved (from -> to, by, when), issues opened, moved and resolved, pull requests opened, checked, merged, held or closed and on the machines, and what is stuck; headed "N changes in the last M min". Without since nothing changes. It keeps no store of its own.
modules/mesh-issues: a new seat verb issue-tracker.changes {since, number?} reads the tracker's own log changes over a window (binary search on time, replay per issue for from/to, at most 500 changes), so progress says from what state each issue moved; when it fails, progress says the state reached and warns.

Quick vs thorough: thorough (the tracker's history readable by a verb, one-question-one-tool).
Left: mesh-delivery keeps no time for 'reached its machines', so 'on the machines' is as read at call time.
Tests: TestProgressSinceAWindowSaysOnlyWhatChanged and TestChangesSaysEachMoveFromWhatToWhatOverAWindow (each failing first), the bus tests extended; vet, -tags integration and test pass in both modules. mesh-issues 167 and mesh-knowledge 104 Test functions.

Reviewed-by: rev-progress-since@shanks at dfe490d9e2

The operator (2026-10-28): "can the progress tool also report the progress made since the last call, or maybe better, the last 60 minutes" - as a parameter. - modules/mesh-knowledge: progress gains `since` (a window such as 5m or 60m, at most 24 h). The answer lists only what changed under `of`: milestones moved (from -> to, by, when), issues opened, moved and resolved, pull requests opened, checked, merged, held or closed and on the machines, and what is stuck; headed "N changes in the last M min". Without `since` nothing changes. It keeps no store of its own. - modules/mesh-issues: a new seat verb issue-tracker.changes {since, number?} reads the tracker's own log `changes` over a window (binary search on time, replay per issue for from/to, at most 500 changes), so progress says from what state each issue moved; when it fails, progress says the state reached and warns. Quick vs thorough: thorough (the tracker's history readable by a verb, one-question-one-tool). Left: mesh-delivery keeps no time for 'reached its machines', so 'on the machines' is as read at call time. Tests: TestProgressSinceAWindowSaysOnlyWhatChanged and TestChangesSaysEachMoveFromWhatToWhatOverAWindow (each failing first), the bus tests extended; vet, -tags integration and test pass in both modules. mesh-issues 167 and mesh-knowledge 104 Test functions. Reviewed-by: rev-progress-since@shanks at dfe490d9e2453d8a2177200bc02b76dd6c24e78b

mesh-tools added 2 commits 2026-10-28 11:34:14 +00:00

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) 4f317201c9

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

mesh/delivery merged: source.main moved to novox/mesh-catalog@9cdac09ad962

Details

mesh/check being carried to dfe490d9e245 on 9cdac09ad962 | from 25f615456423

dfe490d9e2

mesh-tools commented

2026-10-28 11:34:18 +00:00

Delivery novox/mesh-catalog@dfe490d9e245 — merged since 2026-10-28T11:56:33Z

Source — source.main moved to novox/mesh-catalog@9cdac09ad9. Whether it reached the machines is mesh-delivery-view's, derived from source.main, the wants and the haves.

Transitions

2026-10-28 11:34 (new) → proposed (announced): novox/mesh-catalog#541's head announced
2026-10-28 11:34 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false)
2026-10-28 11:56 ready → merged (merged): on the trunk its modules follow: merged there

The commit's note under refs/notes/mesh-plan keeps every transition of this change up to its merge: git log --notes=mesh-plan.

**Delivery** `novox/mesh-catalog@dfe490d9e245` — **merged** since 2026-10-28T11:56:33Z **Source** — source.main moved to novox/mesh-catalog@9cdac09ad962. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Transitions** - 2026-10-28 11:34 (new) → proposed (announced): novox/mesh-catalog#541's head announced - 2026-10-28 11:34 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false) - 2026-10-28 11:56 ready → merged (merged): on the trunk its modules follow: merged there The commit's note under `refs/notes/mesh-plan` keeps every transition of this change up to its merge: `git log --notes=mesh-plan`.

mesh-tools merged commit 9cdac09ad9 into main

2026-10-28 11:56:32 +00:00

mesh-tools deleted branch feat/progress-since

2026-10-28 11:56:33 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-catalog#541