[hippo] Add CI guard for stale workflow lock files after markdown edits

[github-actions]

Summary

A recurring memory and today’s analysis both point to the same preventable failure mode: workflow markdown changes land without regenerated .lock.yml artifacts, causing lock/hash drift and downstream activation failures on main.

Memory: mem_4afaa0965161
Memory: sem_ef67ccfd978b

Rationale

The memory store repeatedly reinforces that make recompile must follow markdown workflow edits, and the open stale-lock issue (#44735) shows this is still escaping into the default branch. A lightweight CI or pre-merge guard would turn a known tribal rule into an enforceable invariant.

Next steps

• Identify the current workflow or check path that validates generated artifacts under .github/workflows/.
• Add a check that detects markdown workflow diffs without corresponding regenerated .lock.yml changes.
• Ensure the failure message tells contributors to run make recompile.
• Validate by editing a sample workflow markdown file and confirming the guard fails before regeneration and passes after regeneration.

Generated by 🦛 Daily Hippo Learn · 12.4 AIC · ⌖ 14 AIC · ⊞ 5.4K · ◷

• expires on Jul 14, 2026, 11:10 PM UTC-08:00

[github-actions]

🍪 Issue Monster selected this for Copilot

I've identified this issue as a good candidate for automated resolution and requested assignment to the Copilot coding agent.

If assignment succeeds, the Copilot coding agent will analyze the issue and create a pull request with the fix.

Om nom nom! 🍪

🍪 Om nom nom by Issue Monster · 1.48 AIC · ⌖ 5.91 AIC · ⊞ 6.2K · ◷