Genesis grants for the gate's event and the bus step's snapshot (hq ADR 0236) #41

Merged
mesh-admin merged 1 commits from feat/core-upgrades-that-roll-back into main 2026-10-06 17:15:07 +00:00
Contributor

The installer's first user list gains the controller's two new grants from hq ADR 0236: publishing mesh.seat.mesh-controller.event.rolled-back (a build put back after its gate failed) and asking mesh.seat.node-backup.tool.now.* (the bus's snapshot before the planned bus step, ADR 0235's dump). Without them a fresh mesh's controller is refused the first time it uses either.

Held by mesh-controller's TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose, which reads this file from the sibling checkout. Independent of the witness (PR #40); merge before or with mesh-controller's PR. go test ./... passes.

The installer's first user list gains the controller's two new grants from hq ADR 0236: publishing `mesh.seat.mesh-controller.event.rolled-back` (a build put back after its gate failed) and asking `mesh.seat.node-backup.tool.now.*` (the bus's snapshot before the planned bus step, ADR 0235's dump). Without them a fresh mesh's controller is refused the first time it uses either. Held by mesh-controller's `TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose`, which reads this file from the sibling checkout. Independent of the witness (PR #40); merge before or with mesh-controller's PR. `go test ./...` passes.
mesh-admin added 1 commit 2026-10-06 16:39:56 +00:00
The controller says a rollback as rolled-back and asks the bus machine's backup holder
for a snapshot before the planned bus step; the installer's first user list must grant
both, or a fresh mesh's controller is refused the first time it uses them.
mesh-admin merged commit ad39988bc6 into main 2026-10-06 17:15:07 +00:00
mesh-admin deleted branch feat/core-upgrades-that-roll-back 2026-10-06 17:15:07 +00:00
Author
Contributor

Delivery novox/mesh-host@ad39988bc65e — delivered since 2026-10-06T23:05:28Z

Transitions

  • 2026-10-06 23:05 (new) → proposed (announced): novox/mesh-host#41 merged; its head was not heard by this owner, so it is made from the forge's word
  • 2026-10-06 23:05 proposed → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on
  • 2026-10-06 23:05 held → delivering (go): its walk started on a word that was not this owner's: the controller's own path, which waits for nobody, or a person's plans go
  • 2026-10-06 23:05 delivering → delivered (done): its walk is done: 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-host@ad39988bc65e` — **delivered** since 2026-10-06T23:05:28Z **Transitions** - 2026-10-06 23:05 (new) → proposed (announced): novox/mesh-host#41 merged; its head was not heard by this owner, so it is made from the forge's word - 2026-10-06 23:05 proposed → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on - 2026-10-06 23:05 held → delivering (go): its walk started on a word that was not this owner's: the controller's own path, which waits for nobody, or a person's `plans go` - 2026-10-06 23:05 delivering → delivered (done): its walk is done: 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`.
Sign in to join this conversation.
No Reviewers
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-host#41