pacman: the round and the history tools say in plain words what they answer #497

Merged
mesh-tools merged 2 commits from fix/pacman-findable into main 2026-10-26 13:39:17 +00:00
Member

The operator asked "did our weekly system upgrade run on all our nodes?". pacman_round answers that in one call, but its description did not say so in those words, so mesh_search did not find it. This change gives pacman_round and pacman_upgrades a first description line in plain words: whether this week's system upgrade ran on every node and how each ended, and each node's upgrade history and last run; mesh_search shows that line as its answer. Together with mesh-tools' filler-word change (fix/search-ignores-filler), the operator's question ranks pacman_round first. replaces is untouched: it keeps only shell commands (ADR 0245 clause 1). Nothing the tools do changes. Follows the instruction one-question-one-tool.

Tests: pacman's go test and vet pass. Try try-1793020040191405852 passed (unit 2030, integration 2050).

Reviewed-by: review-pacman@shanks at 0300a6fd99

The operator asked "did our weekly system upgrade run on all our nodes?". `pacman_round` answers that in one call, but its description did not say so in those words, so mesh_search did not find it. This change gives `pacman_round` and `pacman_upgrades` a first description line in plain words: whether this week's system upgrade ran on every node and how each ended, and each node's upgrade history and last run; mesh_search shows that line as its answer. Together with mesh-tools' filler-word change (fix/search-ignores-filler), the operator's question ranks `pacman_round` first. `replaces` is untouched: it keeps only shell commands (ADR 0245 clause 1). Nothing the tools do changes. Follows the instruction one-question-one-tool. Tests: pacman's go test and vet pass. Try try-1793020040191405852 passed (unit 2030, integration 2050). Reviewed-by: review-pacman@shanks at 0300a6fd99b5d2963d13a735a4f994a3b1cd8594
mesh-tools added 2 commits 2026-10-26 13:15:37 +00:00
Author
Member

Delivery novox/mesh-catalog@0300a6fd99b5 — merged since 2026-10-26T13:39:17Z

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

Transitions

  • 2026-10-26 13:15 (new) → proposed (announced): novox/mesh-catalog#497's head announced
  • 2026-10-26 13:15 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-26 13:39 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-delivery:view --> **Delivery** `novox/mesh-catalog@0300a6fd99b5` — **merged** since 2026-10-26T13:39:17Z **Source** — source.main moved to novox/mesh-catalog@2da9329df448. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Transitions** - 2026-10-26 13:15 (new) → proposed (announced): novox/mesh-catalog#497's head announced - 2026-10-26 13:15 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-26 13:39 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 2da9329df4 into main 2026-10-26 13:39:17 +00:00
mesh-tools deleted branch fix/pacman-findable 2026-10-26 13:39:17 +00:00
Sign in to join this conversation.
No Reviewers
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-catalog#497