Should Maka install local validation hooks by default?

[Phoenix500526]

Context

PR #4132 proposes installing Husky hooks during normal root dependency setup. The goal is to run existing repository checks before a branch is pushed, especially when an agent-assisted change violates a repository assumption.

Today those failures often appear only in CI, which adds an avoidable edit, push, and wait cycle.

Proposed behavior

A regular npm install or npm ci would install two hooks:

• pre-commit checks staged changes with Biome, checks ASF headers on new files, runs the Runtime Host protocol epoch guard, and runs git diff --cached --check.
• commit-msg validates Conventional Commit messages with commitlint.

The hooks reuse existing repository checks. CI remains the authority.

Local control and recovery

This changes every local commit, including intermediate commits.

• Skip the hooks for one commit with git commit --no-verify.
• Disable Husky for a command or environment with HUSKY=0.
• npm ci --omit=dev does not install Husky. The prepare script skips hook setup when Husky is absent.
• If hooks already exist but development dependencies are later omitted, the hooks fail clearly instead of running cached or global tools. Run a normal npm install to restore the local tools, or bypass the hooks intentionally.

Questions

1. Should these hooks be installed by default for contributors?
2. Should commit-message validation apply to every local commit, or only to PR titles and merged commits?
3. Would an opt-in setup be better than automatic installation?

Implementation: #4132

[Phoenix500526]

@Astro-Han