Say how the build agent and the route proxy are ready (novox/hq issue 544)

Neither server declared health, so each walk that moved them waited out the
60 s grace on every machine. The build agent is ready when 'mesh-builder ready'
says it took its build work; the route proxy when its http port accepts.

health-undeclared

@@ -1,4 +1,4 @@
-69
+67
 The long-running resources of this catalogue that do not say how they are ready (`health`, novox/hq ADR 0240
 rule 8), as `module check` counts them. It may only go down: merge-check.sh fails a change that raises it, and
 one that lowers it writes the new number on the first line. From 2026-11-18, or once it is 0, a long-running

modules/build-agent/module.json

@@ -70,7 +70,15 @@
       "restart-on": [
         "agent-env"
       ],
-      "network": "host"
+      "network": "host",
+      "health": {
+        "kind": "exec",
+        "command": "/usr/local/bin/mesh-builder ready",
+        "interval": "10s",
+        "timeout": "5s",
+        "looks": 3,
+        "grace": "60s"
+      }
     }
   ],
   "build": {

modules/route-proxy/module.json

@@ -179,7 +179,15 @@
         "internal-trust",
         "internal-acme-env"
       ],
-      "logging": "journald"
+      "logging": "journald",
+      "health": {
+        "kind": "tcp",
+        "endpoint": "http",
+        "interval": "10s",
+        "timeout": "5s",
+        "looks": 3,
+        "grace": "60s"
+      }
     }
   ],
   "build": {