5 Commits

Include renames

Author	SHA1	Message	Date
jochen	ba2806b985	Measure that the postgres module's image initialises where genesis now raises the store (hq issue 609, ADR 0338 §5) ... The genesis bundle raises the store as the postgres module's server: its pgvector image, its data in a directory made before the store starts and owned as the module declares it, its password from a file. The decision names one measurement before it is relied on: that image, on such a directory, empty, initialises a store that answers with that password. The image and the owner are read from the catalogue's manifest, so the measurement moves with the module's pin.	2026-10-13 10:47:34 +02:00
jochen	a1a03f9880	Pull an image named by its digest as the runtime's own client does, and say a pull that failed	2026-10-07 15:52:54 +02:00
jochen	eecbfd6693	Prove every changed health check on a bed before the catalogue merges (hq ADR 0240, to-be 48 Phase D) ... Two of nineteen image checks read unhealthy while working in the mesh's hands; adopted without proof they would have put back two good builds. The replays every catalogue merge check runs now start each long-running container whose declared check or image the change touches, alone, with what its module declares and nothing of the mesh's, and require the check to see the program within its grace: a program that stays up while its check does not see it fails the change; one that does not stay up alone is said and left to the first machine's gate; a check needing a provider must only reach the program. R-studio replays the studio's false unhealthy — a server bound to HOSTNAME's address and an image check asking localhost — failed on the bed, and proved with HOSTNAME=0.0.0.0.	2026-10-07 15:12:26 +02:00
jochen	5e3ae7b835	Replay the crash loop: a container that exits at start fails its gate on the first machine (hq ADR 0240) ... The agent server crash-looped about a hundred times behind every passing check. R-crashloop raises a container whose program exits at start, has the node-engine at its commit judge it through the runtime, and the controller at its commit judge the gate from what the engine said — two repositories, each at its own commit before the fix and on it.	2026-10-07 02:28:50 +02:00
jochen	70f62ee17b	Replay the core incidents, and prove each fails before its fix and passes on it (hq to-be 45 §9) ... Phase 5 is done when the replays of 236, 262, 263 and 266 fail on the commit before their fix and pass after. The register names every replay with its issue and fix; the bus replay (266) runs a consumer filtered like the controller's against a bus of a given release, the resolver replay (262) renders the catalogue's machine list and asks every machine's name by getaddrinfo under musl and glibc, and the prover runs each at both commits: all five (236, 262, 263, 266, 273) proved.	2026-10-06 21:01:39 +02:00