mesh-lab

Files

T

jochen d03f87b00d Register R92 as a bed: genesis on a runtime that trusts no registry (hq issue 92)

The lab's base image trusts the documentation ranges as plain-HTTP registries, so no genesis bed could
see the push to an untrusted registry that issue 92 is about (reviews 73 and 76 on mesh-host #91). The
bed takes that trust off the anchor before the installer runs and asks the runtime it trusts loopback
only, then runs genesis with --registry 192.0.2.10:5000 and holds that the control plane reaches the
registry, trusted by the mesh's name too.

The prover gains a bed kind: it builds the node-engine and its installer at each commit, the carried
builder from the pinned controller, and raises the bed; a bed that never reached the step it replays
skips, and a skip is an error, never the fault reproduced.

Not proved yet: genesis stops at step 6 on both sides, because the temporary controller has no
MESH_BUS_NATS and the bus template is refused by the installer (issue 146).

2026-10-13 02:57:21 +02:00

integration

2026-10-13 02:57:21 +02:00

beds-read-the-catalogue.test.ts

A cache consumer presents the login it was granted, checked over the catalogue; the two-node bed's baserow keeps its own cache and the bed asserts it answers (issue 081)

2026-09-22 12:26:34 +02:00

bus-kept.test.ts

Raise genesis past its broker step and hold that the bus is kept (hq issue 590, ADR 0333 §5)

2026-10-13 02:13:35 +02:00

cache-consumers-present-their-login.test.ts

Review of 081: the bed asserts baserow chose its own cache and it challenges for its password; the check reads only what a module hands its software; stale comments

2026-09-22 12:34:59 +02:00