Phase 5 (4/4): replay issues 263 and 273 (hq ADR 0237) #98

2026-10-06T19:18:09Z

mesh-admin commented

2026-10-06 19:18:09 +00:00

hq to-be 45 §9 (M9), ADR 0237 decision 5.

cmd/mesh-controller/replays_test.go: TestReplay263AnIdentityTooLongNeverRefusesItsProvidersMachine and TestReplay273AConsumerBesideItsStoreStaysBoundToIt, written only with what the controller had before each fix so the prover (mesh-lab replays/cmd/prove) lays the file over the older commit.

Proved: 263 fails on 6d620f7^ with the incident's own refusal (mesh_laptop_networkmanager, 26 characters where an S3 access key keeps 20) and passes on 6d620f7; 273 fails on 8bfaf15^ (bound to the store on the other machine) and passes on 8bfaf15.

After merge: mesh-lab's register reads these from feat/replays — flip its HomeRef to main.

hq to-be 45 §9 (M9), ADR 0237 decision 5. `cmd/mesh-controller/replays_test.go`: `TestReplay263AnIdentityTooLongNeverRefusesItsProvidersMachine` and `TestReplay273AConsumerBesideItsStoreStaysBoundToIt`, written only with what the controller had before each fix so the prover (mesh-lab `replays/cmd/prove`) lays the file over the older commit. Proved: 263 fails on 6d620f7^ with the incident's own refusal (`mesh_laptop_networkmanager`, 26 characters where an S3 access key keeps 20) and passes on 6d620f7; 273 fails on 8bfaf15^ (bound to the store on the other machine) and passes on 8bfaf15. After merge: mesh-lab's register reads these from `feat/replays` — flip its `HomeRef` to `main`.

mesh-admin added 1 commit 2026-10-06 19:18:09 +00:00

Replay issues 263 and 273 as tests the commit before each fix fails (hq to-be 45 §9) cbce8f96ef

mesh-admin merged commit b9e0cd34c3 into main

2026-10-06 19:19:49 +00:00

mesh-admin deleted branch feat/replays

2026-10-06 19:19:49 +00:00

mesh-admin commented

2026-10-06 23:10:11 +00:00

Delivery novox/mesh-controller@b9e0cd34c3fb — 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#98 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@b9e0cd34c3fb` — **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#98 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-12 22:54:35 +00:00

A walk's first-machine gate waits for a busy container, and mesh-builder busy drains the agent (issue 594, hq ADR 0335) #283

jschoubben referenced this issue from a commit

2026-10-13 22:07:33 +00:00

Merge origin/main into feat/335, and pin mesh-host at #98's new head

This repo is archived. You cannot comment on pull requests.

1 Participants

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-controller#98