feat: lore hooks install/uninstall + CI integration (closes #41)

[Ian-stetsenko]

Summary

Adds commit-msg hook management for automated Lore protocol enforcement — locally via git hooks and in CI via GitHub Actions.

New commands

• lore hooks install — installs a commit-msg hook to .git/hooks/ that runs lore validate --last 1 --strict
• lore hooks install --force — overwrites existing non-Lore hooks (backs up to .bak)
• lore hooks uninstall — removes Lore-managed hooks only (refuses to delete user-managed hooks)

Generated hook script

The hook automatically skips:

• Merge commits (configurable via skip_patterns)
• fixup!/squash! commits (configurable via allow_fixup)
• Commits by specific authors like dependabot[bot] (configurable via skip_authors)
• Falls back from lore to npx lore-protocol when the CLI isn't on PATH

Configuration

New [hooks] section in .lore/config.toml:

[hooks]
enforce = true                   # Use --strict flag (false = soft mode, warnings only)
allow_fixup = true               # Skip fixup!/squash! commits
skip_authors = []                # Authors to skip (e.g., ["dependabot[bot]"])
skip_patterns = ["^Merge "]      # Message patterns to skip

CI Integration

GitHub Actions — .github/workflows/lore-validate.yml:

- run: node ./bin/lore.js validate --since origin/main --strict

pre-commit framework — .pre-commit-hooks.yaml:

repos:
  - repo: https://github.com/Ian-stetsenko/lore-protocol
    rev: v0.5.0
    hooks:
      - id: lore-validate
        stages: [commit-msg]

Husky:

# .husky/commit-msg
npx lore validate --last 1 --strict

Any CI (GitLab, Bitbucket, Jenkins, CircleCI):

npx lore-protocol validate --since origin/main --strict

Files changed (12)

New:

• src/commands/hooks.ts — command registration
• src/interfaces/hook-installer.ts — IHookInstaller interface
• src/services/hook-installer.ts — filesystem operations for hook management
• src/services/hook-script-generator.ts — generates bash hook script from config
• .pre-commit-hooks.yaml — pre-commit framework integration
• .github/workflows/lore-validate.yml — GitHub Actions workflow
• tests/unit/services/hook-installer.test.ts — 9 tests
• tests/unit/services/hook-script-generator.test.ts — 11 tests

Modified:

• src/main.ts — wires HookInstaller + HookScriptGenerator into composition root
• src/types/config.ts — adds hooks section to LoreConfig
• src/services/config-loader.ts — adds hooks to CAMEL_TO_SNAKE mapping
• src/commands/init.ts — adds [hooks] to default config template

Test plan

• 444 tests pass (28 test files)
• Build and typecheck pass
• Manual smoke tests:
  • lore hooks install → creates hook, verified content
  • lore hooks install again → updates existing Lore hook
  • lore hooks uninstall → removes hook
  • lore hooks --help and lore hooks install --help show correct usage
• Generated hook script includes all skip conditions and lore/npx fallback

🤖 Generated with Claude Code

Closes #41

[c-ferrier]

Before looking at this commit, I had missed this that validate takes in --since and turns it into a git range.... whereas --since elsewhere is expected to be a date...

Thoughts

should validate be --sinceRef ? to be clear? or we just know that --since has different meanings in different commands? Or should --since everywhere else be able to take things other than dates? Should validate take in a date? etc. just trying to rationalize expected behavior for --since

[c-ferrier]

Just a follow up on the --since comment, in #55 i made a comment #55 (comment) which describes the changes I made in 43941eb which basically creates a better --since and --until processor that can deal with ISO Dates, references (besides in validate are buggy and return incorrect data) and relative dates (which depend on git, and silently blow up in the JS code but that error is eaten).

Looking forward to hearing your thoughts.