Prove every changed health check on a bed before the catalogue merges (hq ADR 0240, to-be 48 Phase D) #56

Merged

mesh-admin merged 2 commits from feat/health-the-bed into main 2026-10-07 16:28:44 +00:00

Conversation 1 Commits 2 Files Changed 3

+624 -4

2 Commits

Author	SHA1	Message	Date
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