This registers R310, the replay of novox/hq issue 310. It is an InRepository replay of TestReplay310 in mesh-controller internal/builder/replay310_test.go, from novox/mesh-controller PR #135.
The test is written with only what the build agent had before the fix. Its case is a pull request with no merge-check.sh into a main that holds one.
Proved locally with go run ./cmd/prove R310:
R310 (issue 310): PROVED — before its fix fails, on its fix passes
On the commit before, the repository layer answered warning ("the repository declares no merge-check.sh").
Before: "1a50d6e" is set because the fix is still on its branch. It is cleared once PR #135 merges.
Merge after novox/mesh-controller PR #135. Until then, Fix names a commit that exists only on that branch.
This registers R310, the replay of novox/hq issue 310. It is an InRepository replay of `TestReplay310` in mesh-controller `internal/builder/replay310_test.go`, from novox/mesh-controller PR #135.
The test is written with only what the build agent had before the fix. Its case is a pull request with no `merge-check.sh` into a main that holds one.
Proved locally with `go run ./cmd/prove R310`:
> R310 (issue 310): PROVED — before its fix fails, on its fix passes
On the commit before, the repository layer answered `warning` ("the repository declares no merge-check.sh").
`Before: "1a50d6e"` is set because the fix is still on its branch. It is cleared once PR #135 merges.
Merge after novox/mesh-controller PR #135. Until then, `Fix` names a commit that exists only on that branch.
Deliverynovox/mesh-lab@157bb18fa8db — delivered since 2026-10-08T09:10:42Z
Delivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
2026-10-08 08:59 (new) → proposed (announced): novox/mesh-lab#65's head announced
2026-10-08 08:59 proposed → checked (checked): the verdict names this commit
2026-10-08 08:59 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-08 09:10 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-08 09:10 published → delivered (done): nothing for a walk to move
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/mesh-lab@157bb18fa8db` — **delivered** since 2026-10-08T09:10:42Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Transitions**
- 2026-10-08 08:59 (new) → proposed (announced): novox/mesh-lab#65's head announced
- 2026-10-08 08:59 proposed → checked (checked): the verdict names this commit
- 2026-10-08 08:59 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-08 09:10 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-08 09:10 published → delivered (done): nothing for a walk to move
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.
This registers R310, the replay of novox/hq issue 310. It is an InRepository replay of
TestReplay310in mesh-controllerinternal/builder/replay310_test.go, from novox/mesh-controller PR #135.The test is written with only what the build agent had before the fix. Its case is a pull request with no
merge-check.shinto a main that holds one.Proved locally with
go run ./cmd/prove R310:On the commit before, the repository layer answered
warning("the repository declares no merge-check.sh").Before: "1a50d6e"is set because the fix is still on its branch. It is cleared once PR #135 merges.Merge after novox/mesh-controller PR #135. Until then,
Fixnames a commit that exists only on that branch.Delivery
novox/mesh-lab@157bb18fa8db— delivered since 2026-10-08T09:10:42ZDelivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.