jschoubben 4ee769dda0 Prove a commit reaches a machine already running the old one ...

Commit, build, catalogue, push — and the machine ends up running what the
source says. With the two halves that make the answer trustworthy: it is still
running the old one until it is told, because the mesh changing its mind is not
a machine acting on it; and it stops being reported as behind once it has
caught up, because a status that says "behind" for ever is one nobody reads.

2026-08-31 02:55:10 +02:00

..

builds.test.ts

A machine in the mesh builds a module, and the catalogue records it

2026-08-30 04:06:23 +02:00

harness.ts

Repoint ADR references after HQ consolidated 65 records to 23

2026-08-28 23:33:46 +02:00

mesh.test.ts

Prove a commit reaches a machine already running the old one

2026-08-31 02:55:10 +02:00

placement.test.ts

Repoint ADR references after HQ consolidated 65 records to 23

2026-08-28 23:33:46 +02:00

provisioner.test.ts

Prove a mesh credential becomes a login, against a real database

2026-08-30 01:29:46 +02:00

scenarios.test.ts

Step 2: raise a second scenario, and share the invariants

2026-08-25 00:29:59 +02:00

underlay.test.ts

Repoint ADR references after HQ consolidated 65 records to 23

2026-08-28 23:33:46 +02:00