Readiness checks
How the coordinator waits for containers to answer, and the case where it reports ready without an answer.
Template and resolver checks fail after their last attempt. The processor, plugin and merger check tests i == maxAttempts inside a loop that stops at maxAttempts - 1, so after every attempt fails it still returns success; startMerger logs a failed check and goes on.
Where it lives
sulfone.boron/docker_executor/executor.gosulfone.boron/docker_executor/template_executor.go
Stub: summary only.