[deep-report] Add make recompile pre-commit hook to prevent stale lock file CI failures

[github-actions]

Problem Statement

Hippo Memory Insights (2026-05-06, #30572) surfaces the highest-confidence verified memory in the store (score=1.006): stale workflow .lock.yml files cause CI churn because contributors edit markdown workflow source files without running make recompile afterward.

This is a recurring, verified incident with a known fix — but no automation prevents it.

Root Cause

No pre-commit hook or CI preflight check detects dirty (out-of-sync) lock files. Contributors must remember to run make recompile manually after every workflow source edit.

Expected Impact

• Eliminates the rejig docs #1 CI failure class caused by stale lock files
• Reduces CI churn and wasted runner minutes
• Prevents agent-authored PRs from failing CI due to forgotten recompile step

Suggested Fix

1. Add a pre-commit hook (via .git/hooks/pre-commit or husky/lefthook) that runs make recompile and checks for dirty lock files before allowing a commit
2. Alternatively, add a CI preflight step that validates lock files are in sync before running expensive jobs
3. Update CONTRIBUTING.md to make make recompile prominent in the workflow editing checklist

Estimated Effort

Fast (< 1 hour)

Data Source

Hippo Memory Insights — 2026-05-06 (#30572); verified memory mem_4d656997f889

Generated by DeepReport - Intelligence Gathering Agent

Generated by DeepReport - Intelligence Gathering Agent · ● 330.7K · ◷

• expires on May 8, 2026, 3:35 PM UTC