4 Commits

Include renames

Author	SHA1	Message	Date
jochen	3abb07f1e2	State a tool check that waits for the operator as waiting (issue 386, ADR 0283) ... A module whose only fault was a secret the operator had not given yet was stated unhealthy, failed its first-node gate and was put back. The engine now reads the tool's answer through mesh-sdk go/health and states such a resource waiting, with what it waits for, on one look; a malformed wait stays unhealthy.	2026-10-10 21:11:02 +02:00
jochen	5e189c2fca	Say a tool check's errors once and as they stand, and test the link on a real bus ... The evidence read "asking it: asking <subject>": the words are now the link's own. A deadline is said as the time the check gave it. A refusal is said only when the bus refused this question, not an earlier one under a grant since widened. merge-check.sh runs the tests that need a bus against a throwaway nats-server when the toolchain has one, and says so when it does not (hq issue 331).	2026-10-08 17:01:15 +02:00
jochen	bdd44154cc	Judge how a module says it is ready, beside whether it stays up (hq ADR 0240, to-be 48 Phase B) ... Liveness alone could not see a web application whose port was open and whose program ran while every request hung for eleven hours (issue 145). A resource now carries the `health` its module declared: the engine makes http and tcp looks itself from the machine to the endpoint's published port, reads a unit's readiness from the show it already makes, hands an exec command or the image's own check to the runtime as the container's check with the declared timing and reads its state from the inspect it already makes, and asks a module's tool on its own node tools. Starting until the check passed, unhealthy once its looks after the grace fail the declared number of times; never more looks than the measured budget; nothing restarted. The statement says contract 2, which tells the controller this engine may be sent the field.	2026-10-07 14:08:32 +02:00
jochen	1fc1e74cc3	Judge whether what a module runs stays up, and say it (hq ADR 0240, to-be 48 Phase A) ... A container that crash-looped after its compose applied passed every check the gate had: nothing looked at what a module runs. The node-engine now judges every long-running resource on every look — one read of the runtime, one per service manager — keeps the restarts it counts across recreates and its own restarts, and says the state in every report and as an event on change, again every minute while not healthy. It reads only; nothing is restarted for being unhealthy.	2026-10-07 02:28:15 +02:00