Roll out the approved Lefthook baseline across eligible repositories #8

Outcome

If egohygiene/holon#12 approves Lefthook as the organization Git-hooks standard, use Pace to adopt and reconcile the versioned baseline across eligible repositories without copying divergent hook logic or making local hooks a prerequisite for CI correctness.

This issue is gated on the Holon evaluation/ADR. If Lefthook is rejected, close this issue as not planned with the decision reference.

Scope

• Inventory repositories and existing Git-hook tooling/configuration.
• Classify repositories by ecosystem/profile and hook eligibility.
• Detect conflicting tools such as Husky, pre-commit, custom .git/hooks bootstrap logic, or repository-specific hook managers.
• Consume the approved Holon Lefthook baseline/version rather than creating a second Pace-owned configuration.
• Generate preview migration plans before mutation.
• Preserve repository-specific canonical tasks and compose appropriate overlays.
• Install bootstrap/documentation wiring without requiring hooks for CI execution.
• Verify lefthook validate and representative hook execution after adoption.
• Track baseline version and drift per repository.
• Provide upgrade and removal/reversion behavior.

Migration principles

• Do not replace existing hook tooling blindly; identify behavior that must be preserved or deliberately retired.
• Do not duplicate formatter/linter/test commands into generated hook config when canonical Taskfile/scripts already exist.
• Keep critical validation in Relay/CI.
• Keep developer-local lefthook-local.* files ignored and outside fleet synchronization.
• Do not enable expensive pre-push behavior universally when a repository profile does not need it.
• Preserve repositories where hooks are intentionally not applicable.

Fleet states

Represent at least:

• not evaluated;
• not applicable;
• blocked by conflicting hook system;
• migration planned;
• adopted current version;
• adopted with repository overlay;
• drifted/outdated;
• verification failed.

Acceptance criteria

• Rollout is gated on the Holon Lefthook adoption ADR.
• Existing hook systems are inventoried before changes.
• Pace produces preview plans before replacing/migrating hook configuration.
• Consumer repositories reference/materialize the approved versioned baseline and keep only bounded overlays.
• Critical tasks remain independently runnable without hooks.
• lefthook validate and representative hook behavior are verified after adoption.
• Baseline-version drift is detectable.
• macOS/Linux/devcontainer canaries are included.
• At least JavaScript, Rust, Flutter/Dart, and docs/config repository profiles are proven where eligible.
• Rollback/removal returns repositories to a documented working state.

Dependencies

• Evaluate and add a universal Lefthook local Git-hooks baseline holon#12
• Define a secure reusable workflow catalog and contract relay#1

Related

• Validate architecture and repository structure in CI relay#5
• Define the global Architecture Decision Record standard and inheritance contract hygiene#15