runtime: a run subcommand to run a module entrypoint to completion (ADR 0052) #6

2026-09-07T20:58:27Z

jschoubben commented

2026-09-07 20:58:27 +00:00

Reconciles a real gap the whole-mesh dry-run exposed: mesh-tools main lacks the run subcommand, so runtimes for every module with a run-once/scheduled entrypoint (the anthropic adopt/refresh, model-usage migrate, run-once bootstraps) can't build from main. This branch (2 commits: the run subcommand + an ADR-reference resync) has been proven by every model-access bed and the novox whole-server converge. Cleanly ahead of main, no divergence.

Reconciles a real gap the whole-mesh dry-run exposed: mesh-tools `main` lacks the `run` subcommand, so runtimes for every module with a run-once/scheduled entrypoint (the anthropic adopt/refresh, model-usage migrate, run-once bootstraps) can't build from main. This branch (2 commits: the `run` subcommand + an ADR-reference resync) has been proven by every model-access bed and the novox whole-server converge. Cleanly ahead of main, no divergence.

jschoubben added 1 commit 2026-09-13 00:39:12 +00:00

The runtime every module stands on is built from its own repository a174dfd404

It copied in a compiled directory that is not in source control and resolved
the toolkit to a sibling checkout, so only a workstation with two repositories
side by side could produce it — and its fingerprint was then typed into every
module by hand. Nothing could rebuild it, so nothing could check it, and the
rule that catches a base moving had no version on the far end of its edge.

The recipe now also says what the image in service actually is. It claimed
Alpine and has been serving Debian for as long as nobody could rebuild it.

jschoubben added 1 commit 2026-09-13 00:39:55 +00:00

The build stage can fetch a git dependency, and only it can a5d65ada53

jschoubben added 1 commit 2026-09-13 00:44:15 +00:00

Compile the toolkit after installing it, because npm does not 78257cf151

It declares the hook npm is supposed to run after a git install, and this npm
does not run it — so the package arrives as sources with every entry point
pointing at a compiled directory that is not there.

jschoubben added 1 commit 2026-09-13 00:45:18 +00:00

The runtime keeps the compiler, because it is also the build environment 90a15cde20

Every module's recipe starts from this image and invokes the compiler out of
it. Pruning build dependencies made a smaller image that nothing could be
built on.

jschoubben added 1 commit 2026-09-13 00:47:16 +00:00

Move the base, to see whether the mesh notices what it reaches 8318c78125

jschoubben added 1 commit 2026-09-13 00:50:18 +00:00

Change the base for real, so the image moves with the commit 8ad37c33cd

jschoubben added 1 commit 2026-09-13 09:15:42 +00:00

Remove what was only there to move a commit 77493642d8

Two lines added to prove that changing this image makes everything standing on
it go stale. The proof worked and the lines were never meant to stay: nothing
reads MESH_RUNTIME.

jschoubben merged commit 0383c1987a into main

2026-09-13 09:16:12 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-tools#6

runtime: a run subcommand to run a module entrypoint to completion (ADR 0052) #6

runtime: a `run` subcommand to run a module entrypoint to completion (ADR 0052) #6