No output appears
No output is the success path. It can also mean the selected directory is not a Git repository, or no changed files match the supported extensions.
The hook cannot find a build driver
In automatic driver mode, the hook skips repository quality targets and
continues with branch-state gates only when neither Netsukefile nor
Makefile exists. When a supported manifest exists but its matching executable
is unavailable, automatic mode still reports a build-driver error. For explicit
driver selection, ensure the matching manifest and executable both exist.
A target is skipped
Skipped targets are requested by file type but absent from the selected build
driver. Add the target to Netsukefile or Makefile when that gate should run.
Output is missing the middle of a failure
Increase POST_TURN_MAX_OUTPUT_CHARS. The hook truncates long command output
from the middle so the initial context and final error remain visible.