merge-check.sh (TypeScript toolchain): npm ci, typecheck (sources and tests), the unit suite (160 tests). The integration suite and the replays need a lab and the container runtime, which unapproved code is not given: said as not run. Needs git in the TypeScript toolchain (mesh-tools PR) for the last-run test. Tested in the emulated check environment: passes.
`merge-check.sh` (TypeScript toolchain): npm ci, typecheck (sources and tests), the unit suite (160 tests). The integration suite and the replays need a lab and the container runtime, which unapproved code is not given: said as not run. Needs git in the TypeScript toolchain (mesh-tools PR) for the last-run test. Tested in the emulated check environment: passes.
A merge-check.sh, the repository's layer of the mesh's merge check (mesh/repo-check), in
the TypeScript toolchain: install from the lock file, type-check, the unit suite. The
integration suite and the replays need a lab and the container runtime, which unapproved
code is not given: said as not run, never passed silently.
Deliverynovox/mesh-lab@a4f6bb8ce054 — held since 2026-10-06T23:05:27Z
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 nothing: the change touches no module of the mesh's graph
Transitions
2026-10-06 23:05 (new) → proposed (announced): novox/mesh-lab#53 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-lab@a4f6bb8ce054` — **held** since 2026-10-06T23:05:27Z
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 nothing: the change touches no module of the mesh's graph
**Transitions**
- 2026-10-06 23:05 (new) → proposed (announced): novox/mesh-lab#53 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.
merge-check.sh(TypeScript toolchain): npm ci, typecheck (sources and tests), the unit suite (160 tests). The integration suite and the replays need a lab and the container runtime, which unapproved code is not given: said as not run. Needs git in the TypeScript toolchain (mesh-tools PR) for the last-run test. Tested in the emulated check environment: passes.Delivery
novox/mesh-lab@a4f6bb8ce054— held since 2026-10-06T23:05:27ZHeld 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 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.