jschoubben 9f9ce92d0f lavinmq holds mesh-broker again, now the check reads the store ...

The claim comes back for the third and last time. The store's row says the bus seat
answers for `amqp`, lavinmq provides `amqp`, and with mesh-controller#89 the check
that judges a claim reads that row instead of a copy compiled into the build
machine. So this is accepted for the reason it should have been all along.

Restores the holder the controller composes its own bus address through, which is
what ends tonight's crash loop. nats takes the seat over when the cutover is done
deliberately, not because the seat emptied itself.

2026-09-27 22:23:37 +02:00

..

bootstrap

Add lavinmq amqp provider and amqp-ping consumer

2026-09-06 15:50:19 +02:00

provisioner

Event names are local now, in the manifests and in the code

2026-09-27 14:42:28 +02:00

tools

Add lavinmq amqp provider and amqp-ping consumer

2026-09-06 15:50:19 +02:00

client.ts

Every credential provider says whether it still holds a consumer

2026-09-26 01:09:52 +02:00

Dockerfile

Correct lavinmq Dockerfile's stale MESH_TOOL_MODULES comment (061 review)

2026-09-20 13:32:47 +02:00

index.ts

Event names are local now, in the manifests and in the code

2026-09-27 14:42:28 +02:00

module.json

lavinmq holds mesh-broker again, now the check reads the store

2026-09-27 22:23:37 +02:00

package.json

Every credential provider says whether it still holds a consumer

2026-09-26 01:09:52 +02:00

tsconfig.json

Add lavinmq amqp provider and amqp-ping consumer

2026-09-06 15:50:19 +02:00