builder: the slow-event and events-behind-bound bounds are settings (F3)

The review found §794's two bounds fixed in code: the builder's 100 ms
for saying a slow event's handling, and builder_health's five minutes
for naming a consumer behind. Both become settings read at run time,
slow-event (100ms) and events-behind-bound (5m), declared in the
manifest's config with those defaults; a value that is no duration
refuses the builder's start, and makes the health say it.

Builds: design 47 H2 §794, H-A-461 (2)
This commit is contained in:
2026-11-22 03:30:26 +01:00
parent eac4dca2a7
commit d68e71700a
7 changed files with 101 additions and 25 deletions
+14
View File
@@ -204,6 +204,20 @@
"default": "30s",
"runtime": true
},
"slow-event": {
"type": "string",
"description": "how long the handling of one heard event may take before the builder says it in its journal, with its duration and the part that took it, a Go duration (design 47 H2 §794; H-A-461 (2)).",
"trusted": false,
"default": "100ms",
"runtime": true
},
"events-behind-bound": {
"type": "string",
"description": "how long a durable consumer's oldest unacknowledged message may wait before builder_health names it, an events backlog or a handler standing still, a Go duration (design 47 H2 §794; H-A-461 (2)).",
"trusted": false,
"default": "5m",
"runtime": true
},
"publish-pause": {
"type": "number",
"description": "seconds before a version's second publish try, doubled per try up to publish-pause-max (design 47 G A-457a).",