fix(enable): explain core.hooksPath when hooks dir is not a directory

[peyton-alt]

https://entire.io/gh/entireio/cli/trails/937

Problem

A user reported entire enable "crashing" with:

failed to install git hooks: failed to create hooks directory: mkdir /dev/null: not a directory

The cause is core.hooksPath = /dev/null in their git config — a common idiom for globally disabling git hooks (e.g. to neuter Husky). GetHooksDir resolves the hooks dir via git rev-parse --git-path hooks, which faithfully returns /dev/null, and os.MkdirAll then fails with a raw OS error. The message says what failed but never mentions core.hooksPath, so users can't connect it to their own config and report it as a bug.

Fix

Before MkdirAll, stat the resolved hooks path; if it exists and is not a directory, fail with guidance:

failed to install git hooks: git resolves the hooks directory to /dev/null, which is not a directory — core.hooksPath is likely set to disable git hooks
Entire requires git hooks to capture sessions. See where it is set with:
  git config --show-origin --get-all core.hooksPath
then unset it (git config --global --unset core.hooksPath) or override for this repo (git config core.hooksPath .git/hooks) and re-run 'entire enable'

Testing

• New TestInstallGitHook_HooksPathNotADirectory (uses /dev/null on Unix, a regular file on Windows); watched it fail on the old behavior first
• mise run fmt, mise run lint, mise run test (8302 tests) all green

🤖 Generated with Claude Code

---

Note

Low Risk
Small, pre-install validation and clearer errors only; no change to successful hook installation paths.

Overview
When entire enable installs git hooks, it now detects a resolved hooks path that exists but is not a directory (e.g. core.hooksPath = /dev/null) before MkdirAll, instead of surfacing a generic mkdir … not a directory error.

Users get an error that names core.hooksPath, shows the resolved path, and suggests git config --show-origin --get-all core.hooksPath plus unset or repo-local override before re-running entire enable.

Coverage is added in TestInstallGitHook_HooksPathNotADirectory (/dev/null on Unix, a file path on Windows).

^{Reviewed by Cursor Bugbot for commit 07ce70c. Configure here.}

[Copilot]

Pull request overview

This PR improves the entire enable hook-install path by detecting when Git resolves the hooks directory to a non-directory (e.g. core.hooksPath=/dev/null) and returning a targeted, actionable error instead of a raw mkdir ... not a directory failure.

Changes:

• Add a pre-MkdirAll os.Stat guard in InstallGitHook to detect a non-directory hooks path and return guidance mentioning core.hooksPath.
• Add a new test covering the “hooks path is not a directory” scenario, including a Windows-specific setup path.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
cmd/entire/cli/strategy/hooks.go	Adds a guard to produce a clearer error when the resolved hooks path exists but is not a directory.
cmd/entire/cli/strategy/hooks_test.go	Adds regression coverage for the non-directory hooks-path case (Unix /dev/null, Windows regular file).