jschoubben bfd70e9e57 The no-fake multi-node bed: two machines, everything built by the mesh itself ...

The scenario names no images and the bed rewrites nothing: the installer raises anchor
(building the control plane), the mesh's own builder builds base, postgres, lavinmq and
the joined node's consumers from the forge and pins every digest itself, the committed
manifests are registered verbatim, and node2 proves both foundation halves cross-node.
Being iterated toward green (run 3 in flight); banked so nothing is lost.

https://claude.ai/code/session_01D6qtiYU3P9jk3pnAXyAFyx

2026-09-17 22:15:34 +02:00

..

adopted-store-cross-node.test.ts

The cross-node bed is green: push the provider node after adding the remote consumer

2026-09-17 01:34:22 +02:00

anthropic-bed.test.ts

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

assigned-audit.test.ts

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

assigned-catalogue-apps.test.ts

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

assigned-catalogue-media.test.ts

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

assigned-catalogue-mqtt.test.ts

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

assigned-catalogue-small.test.ts

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

assigned-grafana.test.ts

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

assigned-model-usage.test.ts

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

assigned-plex.test.ts

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

assigned-redis.test.ts

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

assigned-schedule-tick.test.ts

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

assigned-sonarr.test.ts

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

assigned-tools-confluence.test.ts

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

assigned-tools-gitlab.test.ts

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

assigned-two-node-db.test.ts

two-node-db is GREEN on the one-store model — store cross-node proven end-to-end

2026-09-17 09:53:35 +02:00

builds.test.ts

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

built-store-cross-node.test.ts

The no-fake multi-node bed: two machines, everything built by the mesh itself

2026-09-17 22:15:34 +02:00

canary.test.ts

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

certificates.test.ts

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

events.test.ts

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

fresh-mesh.test.ts

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

genesis-single.test.ts

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

genesis.ts

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

harness.ts

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

lavinmq-bed.test.ts

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

local-model-bed.test.ts

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

mesh-grant-end-to-end.test.ts

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

mesh.test.ts

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

minio-grant-end-to-end.test.ts

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

objectstore.test.ts

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

one-node-mesh.test.ts

Phase 3.3/3.4: prove the store and broker upgrade in place, through the window

2026-09-16 22:55:56 +02:00

openai-bed.test.ts

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

placement.test.ts

Repoint ADR references after HQ consolidated 65 records to 23

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

postgres-grant-end-to-end.test.ts

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

provider-on-backend-network.test.ts

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

provider-uses-mesh-credential.test.ts

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

provisioner.test.ts

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

route-forwarding.test.ts

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

runtime-restart-on-config.test.ts

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +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

The home segment moves off 192.168.1.0/24

2026-09-11 00:00:19 +02:00

whole-mesh-ace.test.ts

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

whole-mesh-full.test.ts

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00

whole-mesh-novox.test.ts

Rename mesh-control -> mesh-controller, substrate -> foundation

2026-09-16 18:40:40 +02:00