Removes modules/resolved-split-dns: assigned nowhere, and hq ADR 0196 chose against a systemd-resolved stub on every node. resolv-conf becomes the only claimant of node-resolver-config.
Also corrects resolv-conf's resolver-file comment, which told the reader to assign systemd-resolved or NetworkManager instead; it now says the uplink's holder is required beside it (hq ADR 0117, 0220). Note: this changes the file's content, so /etc/resolv.conf is rewritten once on every node on rollout — same nameserver and options lines, comment only.
Checked: go run ./cmd/mesh-controller module check on resolv-conf passes; the mesh-controller suite passes against this catalogue.
Merge order: after novox/hq ADR 0220 (decision/0220-resolver-config-needs-the-uplink), and before (or in the same window as) novox/mesh-controller feat/resolver-config-needs-the-uplink. Safe alone: the current controller's tests that load this module skip when it is absent.
Removes `modules/resolved-split-dns`: assigned nowhere, and hq ADR 0196 chose against a systemd-resolved stub on every node. `resolv-conf` becomes the only claimant of `node-resolver-config`.
Also corrects `resolv-conf`'s resolver-file comment, which told the reader to assign systemd-resolved or NetworkManager *instead*; it now says the uplink's holder is required beside it (hq ADR 0117, 0220). **Note:** this changes the file's content, so `/etc/resolv.conf` is rewritten once on every node on rollout — same nameserver and options lines, comment only.
Checked: `go run ./cmd/mesh-controller module check` on resolv-conf passes; the mesh-controller suite passes against this catalogue.
**Merge order:** after novox/hq ADR 0220 (`decision/0220-resolver-config-needs-the-uplink`), and **before** (or in the same window as) novox/mesh-controller `feat/resolver-config-needs-the-uplink`. Safe alone: the current controller's tests that load this module skip when it is absent.
The resolv-conf comment pointed operators at it and at NetworkManager as
alternative claimants; it now says the uplink's holder is required beside it
(hq ADR 0220).
Deliverynovox/mesh-catalog@4cac44face33 — 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 new: modules/resolv-conf, modules/resolved-split-dns, sent nowhere; no bus step
Transitions
2026-10-06 23:05 (new) → proposed (announced): novox/mesh-catalog#70 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-delivery:view -->
**Delivery** `novox/mesh-catalog@4cac44face33` — **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 new: modules/resolv-conf, modules/resolved-split-dns, sent nowhere; no bus step
**Transitions**
- 2026-10-06 23:05 (new) → proposed (announced): novox/mesh-catalog#70 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`.
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.
Removes
modules/resolved-split-dns: assigned nowhere, and hq ADR 0196 chose against a systemd-resolved stub on every node.resolv-confbecomes the only claimant ofnode-resolver-config.Also corrects
resolv-conf's resolver-file comment, which told the reader to assign systemd-resolved or NetworkManager instead; it now says the uplink's holder is required beside it (hq ADR 0117, 0220). Note: this changes the file's content, so/etc/resolv.confis rewritten once on every node on rollout — same nameserver and options lines, comment only.Checked:
go run ./cmd/mesh-controller module checkon resolv-conf passes; the mesh-controller suite passes against this catalogue.Merge order: after novox/hq ADR 0220 (
decision/0220-resolver-config-needs-the-uplink), and before (or in the same window as) novox/mesh-controllerfeat/resolver-config-needs-the-uplink. Safe alone: the current controller's tests that load this module skip when it is absent.Delivery
novox/mesh-catalog@4cac44face33— held since 2026-10-06T23:05:28ZHeld for a person: merged without a passing check: only a person decides that it goes on —
mesh-delivery.releasewith why lets it go on.Delivery plan — builds new: modules/resolv-conf, modules/resolved-split-dns, sent nowhere; no bus step
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.