Evaluate and integrate remote's repohealth and JS hooks tooling

[CodeMonkeyCybersecurity]

Context

Merge commit fe4da192 brought in new files from a parallel development stream:

• pkg/repohealth/ownership.go + tests - Repository file ownership auditing
• scripts/install-hooks.js - Node.js-based git hook installer
• scripts/repo-ownership-check.js - Node.js-based repo ownership checker

These exist in the codebase but are not wired into the local CI pipeline or package.json scripts.

Questions to Answer

1. pkg/repohealth/: Does this duplicate existing functionality? Is it worth integrating into eos debug or eos update --fix?
2. scripts/install-hooks.js: Local uses scripts/prompts-submodule.sh install-hook and scripts/install-git-hooks.sh. Should we consolidate or keep JS version?
3. scripts/repo-ownership-check.js: Useful for detecting root-owned files in /opt/eos. Worth adding to npm run ci:preflight?

Proposed Approach

1. Evaluate each for unique value vs existing tooling
2. Either integrate fully or remove to avoid dead code
3. If integrating JS scripts, add to package.json and CI pipeline

Acceptance Criteria

• Each file is either fully integrated or removed
• No dead code from the parallel stream remains
• npm run ci passes