jochen 0b07e68cb8 Publish the followed events once the controller's consumer exists ...

Made from now since issue 248, the consumer does not replay what was
published before it; the test raced the controller's start and published
first.

2026-10-05 18:04:40 +02:00

..

artifacts

A grant secret belongs to whoever provisions, and the sweep skips what it will not address

2026-10-04 12:21:49 +02:00

broker

Name the issue the event consumer fix answers: 248

2026-10-05 17:15:49 +02:00

builder

A TypeScript bundle installs its module's own packages before it is compiled

2026-10-04 01:17:49 +02:00

catalogue

The node-backup seat: a module contributes its backup, the mesh fills its directories

2026-10-05 11:42:40 +02:00

envfile

An address is read from the node's settings where it is used, never recorded with a port

2026-09-23 23:49:31 +02:00

identity

Adopt the tunnel as a mesh fact, refuse a mismatched takeover, and rekey after enrolment

2026-09-24 00:02:07 +02:00

inventory

Test the bus users as issue 195 made them: an account-reading module is one, another is not

2026-10-05 18:01:28 +02:00

licences

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

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

link

Publish the followed events once the controller's consumer exists

2026-10-05 18:04:40 +02:00

overlay

The roster is the machines: each node's internal domain covers its routes (hq ADR 0191)

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

secrets

A provider with one credential shares it with every consumer, remade for all at once (hq ADR 0158)

2026-10-01 12:26:44 +02:00

store

Run the controller as a Go bundle the host starts as a process (hq issue 213)

2026-10-04 01:45:25 +02:00

token

Record whether a node is adopted and which modules were taken on it (hq ADR 0100)

2026-09-22 17:14:05 +02:00