Separate failed check results from failed worker execution

When a scheduled monitoring worker deliberately returns a nonzero exit after completing checks, the hosting platform's crash label cannot distinguish an observed failure from a failed execution. Read the explicit completion record, selected pass/fail/unknown counts, and the exit contract before diagnosing infrastructure. Keep completed negative observations separate from missing or overrun observations; only the latter establish lost coverage. This distinction does not prove service availability or explain a separate failed image build.

Applies when: A one-shot monitoring job uses its exit code to report check results. Keywords: monitoring cron worker crash exit code completion coverage unknown