How to diagnose a Harbourmaster review failure

Use this guide when a Harbourmaster job is skipped, fails, or does not post a review.

Confirm the check state

Open the pull request Checks tab. Open Harbourmaster review.

If the job is skipped

Confirm the pull request is not a draft and is not from a fork. The workflow job if condition skips those cases before checkout. GitHub shows a skipped job. The job does not print a skip message.

If the event is labeled and the label is not harbourmaster-review, the job is also skipped.

If the check fails with a re-review warning

If the log contains Human Harbourmaster re-review required, the harbourmaster-review label is already present. A later commit did not start a new review. Remove the label and add it again as a human. Automation must not do this.

If branch protection requires Harbourmaster review, the new head cannot merge until that re-review succeeds.

If the job succeeds but no review appears

Open the job log.

GitHub token unavailable; skipping safely. or GitHub App credentials unavailable; skipping safely. means the action set HARBOURMASTER_SKIP=true and left the job successful.
Draft, fork, head SHA change, or missing write permission cause a policy skip with exit code 0 if the runner starts.
silent and check-only modes do not publish.

If publication fails

Exit code 50 is a github_publish failure. Confirm the token can create pull request reviews. Confirm the checkout HEAD equals head_sha.

If strict runtime fails

The supported workflow sets strict_runtime: "true". A run with no observed model call fails. Open the job log and the OpenCode JSON event artifact.