Retire node-resolver-config and the seat need only it used (hq ADR 0223 part 2, step 2 of 2) #68

2026-10-05T21:45:08Z

mesh-admin commented

2026-10-05 21:45:08 +00:00

Stacked on resolv-conf-to-uplink; retarget to main once that merges.

node-resolver-config leaves the compiled set (36 seats); migration 0064 deletes its store row and any alias (like 0060). Numbered after 0063 (node-hostname rename, hostname-module), expected to merge first — renumber if the order flips (Pending refuses a lower unapplied number).
Seat.Needs / neededBesideClaims removed: node-resolver-config→node-uplink was its only use.
resolver_needs_uplink_test.go replaced by resolver_file_is_the_uplinks_test.go (seat gone; nothing in the catalogue claims it; every uplink writes the file; nothing else writes the path).

Merge only after resolv-conf is unassigned on every machine and forgotten, with mesh-catalog retire-resolv-conf. go vet, go test ./... green against that sibling.

Stacked on `resolv-conf-to-uplink`; retarget to main once that merges. - `node-resolver-config` leaves the compiled set (36 seats); migration **0064** deletes its store row and any alias (like 0060). Numbered after 0063 (node-hostname rename, `hostname-module`), expected to merge first — renumber if the order flips (`Pending` refuses a lower unapplied number). - `Seat.Needs` / `neededBesideClaims` removed: node-resolver-config→node-uplink was its only use. - `resolver_needs_uplink_test.go` replaced by `resolver_file_is_the_uplinks_test.go` (seat gone; nothing in the catalogue claims it; every uplink writes the file; nothing else writes the path). **Merge only after** resolv-conf is unassigned on every machine and forgotten, with mesh-catalog `retire-resolv-conf`. `go vet`, `go test ./...` green against that sibling.

mesh-admin changed target branch from resolv-conf-to-uplink to main

2026-10-05 22:07:39 +00:00

mesh-admin added 1 commit 2026-10-05 22:07:39 +00:00

Retire node-resolver-config and the seat need it alone used (hq ADR 0223) f68521da28

The uplink's holder writes /etc/resolv.conf, so the seat that wrote it and
ADR 0220's dependency of it on the uplink have nothing left to say. The
migration deletes the store's row; nothing holds it once resolv-conf is
unassigned everywhere.

jschoubben added 1 commit 2026-10-05 22:07:56 +00:00

Number the resolver-config migration 0063: it merges first 09bd0eec4f

mesh-admin merged commit 68a2ebdcc3 into main

2026-10-05 22:08:03 +00:00

mesh-admin deleted branch retire-resolv-conf

2026-10-05 22:08:03 +00:00

mesh-admin commented

2026-10-06 23:09:52 +00:00

Delivery novox/mesh-controller@68a2ebdcc34c — held since 2026-10-06T23:05:28Z

Held for a person: merged without a passing check: only a person decides that it goes on — mesh-delivery.release with why lets it go on.

Delivery plan — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step

tier 0: mesh-controller
tier 1: build-agent
tier 2: route-proxy
ace: receives build-agent, route-proxy
g14: receives build-agent
novox: receives mesh-controller, build-agent, route-proxy
shanks: receives build-agent
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
route-proxy provides route: its consumers are sent again after it
route-proxy keeps data (ADR 0233): what it holds is backed up before it moves

Transitions

2026-10-06 23:05 (new) → proposed (announced): novox/mesh-controller#68 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

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

**Delivery** `novox/mesh-controller@68a2ebdcc34c` — **held** since 2026-10-06T23:05:28Z Held for a person: merged without a passing check: only a person decides that it goes on — `mesh-delivery.release` with why lets it go on. **Delivery plan** — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step - tier 0: mesh-controller - tier 1: build-agent - tier 2: route-proxy - ace: receives build-agent, route-proxy - g14: receives build-agent - novox: receives mesh-controller, build-agent, route-proxy - shanks: receives build-agent - build-agent keeps data (ADR 0233): what it holds is backed up before it moves - route-proxy provides route: its consumers are sent again after it - route-proxy keeps data (ADR 0233): what it holds is backed up before it moves **Transitions** - 2026-10-06 23:05 (new) → proposed (announced): novox/mesh-controller#68 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 The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

mesh-admin referenced this pull request

2026-10-09 11:36:21 +00:00

give: take a module's own secret through a hidden prompt at the operator's desk (hq ADR 0259 §10) #156

mesh-admin referenced this pull request

2026-10-09 13:01:02 +00:00

give: take a module's own secret through a hidden prompt at the operator's desk (hq ADR 0259 §10) #156

jschoubben referenced this issue from a commit

2026-10-09 15:10:19 +00:00

Pin mesh-host at its main (d8ff154), where the installer's first user list carries the controller's ask grants

mesh-tools referenced this pull request

2026-10-22 16:55:26 +00:00

Keep each node's declared packages in a state the pacman module reads (upgrade safety, issue 1840, ADR 0507 §5) #439