6 Commits

Include renames

Author	SHA1	Message	Date
jochen	1af6efb356	Name the one genesis bundle in every bed and the README (hq issue 146, ADR 0331) ... mesh-host now carries one genesis bundle, foundation-first-node.lock, on the bus the mesh runs on; the NATS one it replaces is deleted. Beds that still named it would point at a file that is gone, and the harness's rewrite for the previous broker's image rewrote nothing.	2026-10-12 22:50:50 +02:00
jschoubben	a734d427c0	A bed says what it actually needs to be pointed at ... The instructions in every bed named the bundle that raises the predecessor's broker, so a first attempt ends in a control plane crash-looping on a missing MESH_BUS_NATS — which reads like a broken lab. They name the bundle that works now, and the README says the host binary needs SYSTEM=arch, because one built without it refuses everything with an empty system name. And the three habits that each cost a run before they were adopted: MESH_LAB_KEEP to leave the machine standing, MESH_LAB_WARM while iterating, and rebuilding all three repositories the bed places rather than the one that changed.	2026-09-29 17:45:09 +02:00
jschoubben	e596758db9	The five beds that read the catalogue read it through the harness ... adopted-store-cross-node, two-node-db and the three whole-mesh beds each carried a private loader; they drifted. The ace loader never resolved a runtime artifact, so a module the mesh builds travelled unresolved; whole-mesh-full still asked for 'registry' and 'firewall', which the catalogue names distribution and nftables, and swallowed the miss as NOT ASSIGNED. One loader now (novox/hq 04-ISSUES/073).	2026-09-21 14:33:02 +02:00
jschoubben	494f73369a	Every test passes the typecheck gate ... tsconfig.test.json existed precisely so a test that does not compile cannot silently be a test that never ran — and four beds did not compile: two returned strings from test bodies, two predate GenesisOptions gaining sdkSource, one passed a nullable host binary. All clean; the gate is now part of launching any bed. https://claude.ai/code/session_01D6qtiYU3P9jk3pnAXyAFyx	2026-09-17 22:53:34 +02:00
jschoubben	b6bf31d4e6	The cross-node bed is green: push the provider node after adding the remote consumer ... A provision secret is minted as a side-effect of composing the CONSUMER's plan, and the provider's grant list is a pure read of secrets already issued from it. So a cross-node consumer's grant exists only after its node is pushed, and the provider's provisioner mints the vhost only when the provider node is composed again. Push anchor once more after node2, and the bed passes: amqp-ping on node2 reaches mesh-broker on anchor over the overlay, its binding names anchor.internal, and its vhost is minted. Proves both halves of issue 055. https://claude.ai/code/session_01D6qtiYU3P9jk3pnAXyAFyx	2026-09-17 01:34:22 +02:00
jschoubben	155800bc9a	A two-node bed: a joined node opening the adopted broker over the overlay (055) ... anchor raises the foundation and adopts lavinmq; node2 joins and runs amqp-ping, which requires amqp and provides nothing. Asserts the grant names anchor.internal, a vhost is minted on the far broker, and the consumer stays up. Currently RED: it caught two real gaps — the broker's amqps port not in the firewall (fixed in mesh-catalog) and the module broker URL using the public address not the overlay (issue 055, needs a controller fix). Goes green when 055 is fixed. https://claude.ai/code/session_01D6qtiYU3P9jk3pnAXyAFyx	2026-09-17 01:01:54 +02:00