Summary
Add a targeted validation that fails clearly when .github/workflows/*.md changes are not accompanied by regenerated .lock.yml files.
Memory: mem_4afaa0965161
Why
Hippo memory repeatedly surfaces stale workflow lock files as a recurring source of churn and CI friction. The memory indicates this is a high-confidence, repeated failure mode rather than a one-off mistake.
Next steps
- Identify the existing validation path in CI or
make agent-report-progress that can enforce workflow source/lock consistency.
- Add or strengthen a check that detects markdown/lock drift after edits under
.github/workflows/.
- Ensure the failure message explicitly tells contributors to run
make recompile.
- Add or update tests/docs covering the new guardrail.
Generated by 🦛 Daily Hippo Learn · 13.7 AIC · ⌖ 24.7 AIC · ⊞ 5.4K · ◷
Summary
Add a targeted validation that fails clearly when
.github/workflows/*.mdchanges are not accompanied by regenerated.lock.ymlfiles.Memory:
mem_4afaa0965161Why
Hippo memory repeatedly surfaces stale workflow lock files as a recurring source of churn and CI friction. The memory indicates this is a high-confidence, repeated failure mode rather than a one-off mistake.
Next steps
make agent-report-progressthat can enforce workflow source/lock consistency..github/workflows/.make recompile.