jschoubben 7914fd74c6 The two-node bed joins its second machine through the tunnel ...

A token carries the bus's address, and at genesis that is the anchor's
loopback, which no other machine reaches. The anchor joins locally and
becomes the hub; the laptop makes its tunnel key, is issued a token for
it and joins over the tunnel (novox/hq ADR 0169, issue 146).

2026-10-02 16:41:00 +02:00

..

integration

The two-node bed joins its second machine through the tunnel

2026-10-02 16:41:00 +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

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

catalogue-module.test.ts

The lab stands in for the builder on an upstream artifact too: the reference the manifest pins

2026-09-21 22:33:44 +02:00

connect.test.ts

Reach one scenario from the workstation, by name

2026-09-01 16:42:26 +02:00

diagram.test.ts

The home segment moves off 192.168.1.0/24

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

egress-routes.test.ts

The home segment moves off 192.168.1.0/24

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

enumerate.test.ts

The lab said nothing was running while two machines were

2026-08-29 11:54:33 +02:00

invariants.test.ts

The home segment moves off 192.168.1.0/24

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

lastrun.test.ts

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

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

log.test.ts

Say what the lab is doing, while it is doing it

2026-09-01 10:43:38 +02:00

names.test.ts

Scenario lifecycle: raise, exec, snapshot, restore, destroy

2026-08-24 01:12:49 +02:00

net.test.ts

Scenario lifecycle: raise, exec, snapshot, restore, destroy

2026-08-24 01:12:49 +02:00

pinning.test.ts

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

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

place.test.ts

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

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

rebuild.test.ts

The receipt claims the catalogue the beds read

2026-09-21 14:14:54 +02:00

router.test.ts

The home segment moves off 192.168.1.0/24

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

runtimes.test.ts

The run rebuilds the module runtimes its beds stock

2026-09-21 19:26:59 +02:00

suite.test.ts

A run rebuilds what it tests, and leaves a receipt saying what it covered

2026-08-31 15:02:19 +02:00

supported.test.ts

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

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

validate.test.ts

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

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

warm.test.ts

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

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