Issue 470. Three built binaries were tracked in main at the repository root: mesh-controller (31 MB), postgres-provisioner (15 MB) and redis-provisioner (5 MB), committed by a local build. Nothing builds from them: the Dockerfile builds the controller from source, and ./mesh-controller in module.json is the built bundle's path. They only rode in every clone and every build context. This removes them from the index and ignores them at the root beside /mesh-builder; built artifacts belong in build/. No code changes.
Issue 470. Three built binaries were tracked in main at the repository root: `mesh-controller` (31 MB), `postgres-provisioner` (15 MB) and `redis-provisioner` (5 MB), committed by a local build. Nothing builds from them: the Dockerfile builds the controller from source, and `./mesh-controller` in module.json is the built bundle's path. They only rode in every clone and every build context. This removes them from the index and ignores them at the root beside `/mesh-builder`; built artifacts belong in `build/`. No code changes.
Deliverynovox/mesh-controller@0d4d94ff244c — delivered since 2026-10-11T19:07:41Z
Delivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
2026-10-11 18:53 (new) → proposed (announced): novox/mesh-controller#235's head announced
2026-10-11 18:57 proposed → checked (checked): the verdict names this commit
2026-10-11 18:57 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-11 19:07 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-11 19:07 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-controller@0d4d94ff244c` — **delivered** since 2026-10-11T19:07:41Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Transitions**
- 2026-10-11 18:53 (new) → proposed (announced): novox/mesh-controller#235's head announced
- 2026-10-11 18:57 proposed → checked (checked): the verdict names this commit
- 2026-10-11 18:57 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-11 19:07 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-11 19:07 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.
Issue 470. Three built binaries were tracked in main at the repository root:
mesh-controller(31 MB),postgres-provisioner(15 MB) andredis-provisioner(5 MB), committed by a local build. Nothing builds from them: the Dockerfile builds the controller from source, and./mesh-controllerin module.json is the built bundle's path. They only rode in every clone and every build context. This removes them from the index and ignores them at the root beside/mesh-builder; built artifacts belong inbuild/. No code changes.Delivery
novox/mesh-controller@0d4d94ff244c— delivered since 2026-10-11T19:07:41ZDelivery 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.