Fixes novox/hq issue 453: a backup taken by hand (node-backup.now, by a person or by the mesh before a module moves, ADR 0233) was forgotten by the next thinning the same day, because keep-daily keeps only the newest restore point of each day. Seen on ace: plex's 02:35 restore point gone after the 03:01 night.
What changes
now tags each restore point hand beside module=<m>; the night's tags are unchanged, so the nights' groups and thinning stay as they were.
The thinning first lists the restore points, forgets by id each one taken by hand that is older than keep-hand-taken-daysand has a later night of its module, then runs the rotation with --keep-tag hand added. No --keep-within/--keep-last: nothing in the rule keeps every night. A list that does not read thins nothing and is recorded as a failed thinning (the health already raises it).
New preference keep-hand-taken-days, default 7, written into retention.conf as hand=; a count from 1 to 9999 like the others, refused by the night otherwise. The recording of the outcome around forget (#210) is kept; thinned.letGo adds which restore points taken by hand were let go.
backed-up gives each module handTaken: snapshot, at, keptAtLeastUntil, waitsForANight, and a sentence saying until when it is kept. The health line names the hand days and what a thinning let go.
Rollout note: the binary and retention.conf change in the same push. A machine whose retention.conf still lacks hand= is refused by the night (nothing thinned, health says push the machine) until the push writes it.
Tests (written first; all six new ones failed on main's behaviour): fake restic for the tag, the forget arguments, forgetting by id, a list that fails; a table for which restore points are let go; backed-up's answer; and, with restic installed, the issue itself on a temporary repository with full counts: a hand backup then a night the same day keeps both (main: 1 restore point), and eight days on with a later night the hand one is let go. go vet, go test -race -count=1, words check: clean.
Fixes novox/hq issue 453: a backup taken by hand (`node-backup.now`, by a person or by the mesh before a module moves, ADR 0233) was forgotten by the next thinning the same day, because keep-daily keeps only the newest restore point of each day. Seen on ace: plex's 02:35 restore point gone after the 03:01 night.
**What changes**
- `now` tags each restore point `hand` beside `module=<m>`; the night's tags are unchanged, so the nights' groups and thinning stay as they were.
- The thinning first lists the restore points, forgets by id each one taken by hand that is older than `keep-hand-taken-days` **and** has a later night of its module, then runs the rotation with `--keep-tag hand` added. No `--keep-within`/`--keep-last`: nothing in the rule keeps every night. A list that does not read thins nothing and is recorded as a failed thinning (the health already raises it).
- New preference `keep-hand-taken-days`, default 7, written into retention.conf as `hand=`; a count from 1 to 9999 like the others, refused by the night otherwise. The recording of the outcome around `forget` (#210) is kept; `thinned.letGo` adds which restore points taken by hand were let go.
- `backed-up` gives each module `handTaken`: snapshot, at, keptAtLeastUntil, waitsForANight, and a sentence saying until when it is kept. The health line names the hand days and what a thinning let go.
**Rollout note:** the binary and retention.conf change in the same push. A machine whose retention.conf still lacks `hand=` is refused by the night (nothing thinned, health says push the machine) until the push writes it.
**Tests** (written first; all six new ones failed on main's behaviour): fake restic for the tag, the forget arguments, forgetting by id, a list that fails; a table for which restore points are let go; `backed-up`'s answer; and, with restic installed, the issue itself on a temporary repository with full counts: a hand backup then a night the same day keeps both (main: 1 restore point), and eight days on with a later night the hand one is let go. `go vet`, `go test -race -count=1`, words check: clean.
Deliverynovox/mesh-catalog@7211227c7696 — delivered since 2026-10-11T16:20:28Z
Delivery plan — builds restic → ace, g14, novox, shanks; no bus step
tier 0: restic
ace: receives restic
g14: receives restic
novox: receives restic
shanks: receives restic
restic keeps data (ADR 0233): what it holds is backed up before it moves
Machines
restic on ace: passed — healthy 3 times over 3m20s
restic on the rest running it: sent
Transitions
2026-10-11 15:58 (new) → proposed (announced): novox/mesh-catalog#215's head announced
2026-10-11 16:00 proposed → checked (checked): the verdict names this commit
2026-10-11 16:00 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-11 16:15 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-11 16:15 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit
2026-10-11 16:20 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/mesh-catalog@7211227c7696` — **delivered** since 2026-10-11T16:20:28Z
**Delivery plan** — builds restic → ace, g14, novox, shanks; no bus step
- tier 0: restic
- ace: receives restic
- g14: receives restic
- novox: receives restic
- shanks: receives restic
- restic keeps data (ADR 0233): what it holds is backed up before it moves
**Machines**
- restic on ace: passed — healthy 3 times over 3m20s
- restic on the rest running it: sent
**Transitions**
- 2026-10-11 15:58 (new) → proposed (announced): novox/mesh-catalog#215's head announced
- 2026-10-11 16:00 proposed → checked (checked): the verdict names this commit
- 2026-10-11 16:00 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-11 16:15 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-11 16:15 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit
- 2026-10-11 16:20 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says
The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: restic)
mesh/repo-check: PASS — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
Delivery plan — builds restic → ace, g14, novox, shanks; no bus step
tier 0: restic
ace: receives restic
g14: receives restic
novox: receives restic
shanks: receives restic
restic keeps data (ADR 0233): what it holds is backed up before it moves
read by no module's build: modules/restic/cmd/restic-backups/backups_test.go, modules/restic/cmd/restic-backups/hand_test.go, modules/restic/cmd/restic-backups/health_test.go, modules/restic/cmd/restic-backups/retention_test.go
Run by the build seat on novox as build-1791714522601132001 (builds --log build-1791714522601132001).
--- the gate: restic
restic: ok, 3 tool(s), keeps repository (rebuildable), state (cache), ready: night by its tool backup_health every 1m0s; measure by unit every 30s
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 0
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-11T10:25:21Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-11T10:25:21Z
modules the change moves:
- restic (changed)
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 1 module(s) in 1 tier(s): restic
notes:
- modules/restic/cmd/restic-backups/backups_test.go, modules/restic/cmd/restic-backups/hand_test.go, modules/restic/cmd/restic-backups/health_test.go and modules/restic/cmd/restic-backups/retention_test.go read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok git.novox.be/novox/mesh-catalog/checks/words 0.005s
words: 12 retired words and 70 daemons' lines, none in the 41592 strings of 676 files
ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.013s
agent-home: no archive and no file written into under the agent's home
ok git.novox.be/novox/mesh-catalog/checks/paths 0.006s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 69, as kept
testing modules/restic
ok restic/cmd/restic-backups 1.383s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `879bc4bc`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: restic)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
**Delivery plan** — builds restic → ace, g14, novox, shanks; no bus step
- tier 0: restic
- ace: receives restic
- g14: receives restic
- novox: receives restic
- shanks: receives restic
- restic keeps data (ADR 0233): what it holds is backed up before it moves
- read by no module's build: modules/restic/cmd/restic-backups/backups_test.go, modules/restic/cmd/restic-backups/hand_test.go, modules/restic/cmd/restic-backups/health_test.go, modules/restic/cmd/restic-backups/retention_test.go
Run by the build seat on novox as `build-1791714522601132001` (`builds --log build-1791714522601132001`).
```
--- the gate: restic
restic: ok, 3 tool(s), keeps repository (rebuildable), state (cache), ready: night by its tool backup_health every 1m0s; measure by unit every 30s
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 0
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-11T10:25:21Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-11T10:25:21Z
modules the change moves:
- restic (changed)
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 1 module(s) in 1 tier(s): restic
notes:
- modules/restic/cmd/restic-backups/backups_test.go, modules/restic/cmd/restic-backups/hand_test.go, modules/restic/cmd/restic-backups/health_test.go and modules/restic/cmd/restic-backups/retention_test.go read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok git.novox.be/novox/mesh-catalog/checks/words 0.005s
words: 12 retired words and 70 daemons' lines, none in the 41592 strings of 676 files
ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.013s
agent-home: no archive and no file written into under the agent's home
ok git.novox.be/novox/mesh-catalog/checks/paths 0.006s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 69, as kept
testing modules/restic
ok restic/cmd/restic-backups 1.383s
--- its merge-check-typescript.sh (typescript toolchain)
```
mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: restic)
mesh/repo-check: PASS — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
Delivery plan — builds restic → ace, g14, novox, shanks; no bus step
tier 0: restic
ace: receives restic
g14: receives restic
novox: receives restic
shanks: receives restic
restic keeps data (ADR 0233): what it holds is backed up before it moves
read by no module's build: modules/restic/README.md, modules/restic/cmd/restic-backups/backups_test.go, modules/restic/cmd/restic-backups/hand_test.go, modules/restic/cmd/restic-backups/health_test.go, modules/restic/cmd/restic-backups/retention_test.go
Run by the build seat on ace as build-1791734293679606452 (builds --log build-1791734293679606452).
--- the gate: restic
restic: ok, 3 tool(s), keeps repository (rebuildable), state (cache), ready: night by its tool backup_health every 1m0s; measure by unit every 30s
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 0
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-11T11:22:35Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-11T11:22:35Z
modules the change moves:
- restic (changed)
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 1 module(s) in 1 tier(s): restic
notes:
- modules/restic/README.md, modules/restic/cmd/restic-backups/backups_test.go, modules/restic/cmd/restic-backups/hand_test.go, modules/restic/cmd/restic-backups/health_test.go and modules/restic/cmd/restic-backups/retention_test.go read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok git.novox.be/novox/mesh-catalog/checks/words 0.002s
words: 12 retired words and 70 daemons' lines, none in the 41608 strings of 676 files
ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.010s
agent-home: no archive and no file written into under the agent's home
ok git.novox.be/novox/mesh-catalog/checks/paths 0.006s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 69, as kept
testing modules/restic
ok restic/cmd/restic-backups 1.280s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `7211227c`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: restic)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
**Delivery plan** — builds restic → ace, g14, novox, shanks; no bus step
- tier 0: restic
- ace: receives restic
- g14: receives restic
- novox: receives restic
- shanks: receives restic
- restic keeps data (ADR 0233): what it holds is backed up before it moves
- read by no module's build: modules/restic/README.md, modules/restic/cmd/restic-backups/backups_test.go, modules/restic/cmd/restic-backups/hand_test.go, modules/restic/cmd/restic-backups/health_test.go, modules/restic/cmd/restic-backups/retention_test.go
Run by the build seat on ace as `build-1791734293679606452` (`builds --log build-1791734293679606452`).
```
--- the gate: restic
restic: ok, 3 tool(s), keeps repository (rebuildable), state (cache), ready: night by its tool backup_health every 1m0s; measure by unit every 30s
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 0
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-11T11:22:35Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-11T11:22:35Z
modules the change moves:
- restic (changed)
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 1 module(s) in 1 tier(s): restic
notes:
- modules/restic/README.md, modules/restic/cmd/restic-backups/backups_test.go, modules/restic/cmd/restic-backups/hand_test.go, modules/restic/cmd/restic-backups/health_test.go and modules/restic/cmd/restic-backups/retention_test.go read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok git.novox.be/novox/mesh-catalog/checks/words 0.002s
words: 12 retired words and 70 daemons' lines, none in the 41608 strings of 676 files
ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.010s
agent-home: no archive and no file written into under the agent's home
ok git.novox.be/novox/mesh-catalog/checks/paths 0.006s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 69, as kept
testing modules/restic
ok restic/cmd/restic-backups 1.280s
--- its merge-check-typescript.sh (typescript toolchain)
```
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Fixes novox/hq issue 453: a backup taken by hand (
node-backup.now, by a person or by the mesh before a module moves, ADR 0233) was forgotten by the next thinning the same day, because keep-daily keeps only the newest restore point of each day. Seen on ace: plex's 02:35 restore point gone after the 03:01 night.What changes
nowtags each restore pointhandbesidemodule=<m>; the night's tags are unchanged, so the nights' groups and thinning stay as they were.keep-hand-taken-daysand has a later night of its module, then runs the rotation with--keep-tag handadded. No--keep-within/--keep-last: nothing in the rule keeps every night. A list that does not read thins nothing and is recorded as a failed thinning (the health already raises it).keep-hand-taken-days, default 7, written into retention.conf ashand=; a count from 1 to 9999 like the others, refused by the night otherwise. The recording of the outcome aroundforget(#210) is kept;thinned.letGoadds which restore points taken by hand were let go.backed-upgives each modulehandTaken: snapshot, at, keptAtLeastUntil, waitsForANight, and a sentence saying until when it is kept. The health line names the hand days and what a thinning let go.Rollout note: the binary and retention.conf change in the same push. A machine whose retention.conf still lacks
hand=is refused by the night (nothing thinned, health says push the machine) until the push writes it.Tests (written first; all six new ones failed on main's behaviour): fake restic for the tag, the forget arguments, forgetting by id, a list that fails; a table for which restore points are let go;
backed-up's answer; and, with restic installed, the issue itself on a temporary repository with full counts: a hand backup then a night the same day keeps both (main: 1 restore point), and eight days on with a later night the hand one is let go.go vet,go test -race -count=1, words check: clean.Delivery
novox/mesh-catalog@7211227c7696— delivered since 2026-10-11T16:20:28ZDelivery plan — builds restic → ace, g14, novox, shanks; no bus step
Machines
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Merge check at
879bc4bcmesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: restic)mesh/repo-check: PASS — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)Delivery plan — builds restic → ace, g14, novox, shanks; no bus step
Run by the build seat on novox as
build-1791714522601132001(builds --log build-1791714522601132001).Merge check at
7211227cmesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: restic)mesh/repo-check: PASS — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)Delivery plan — builds restic → ace, g14, novox, shanks; no bus step
Run by the build seat on ace as
build-1791734293679606452(builds --log build-1791734293679606452).