[plan] Adopt shared/cache-deduplication.md in high-impact event-driven workflows #19921

Objective

Identify the most impactful event-driven and scheduled workflows that create issues or discussions on repeated triggers but currently lack cache-memory deduplication, and update them to include shared/cache-deduplication.md.

Context

Discussion #19917 recommends promoting cache-memory deduplication as a standard practice for all workflows that create issues or discussions. Currently 73 workflows use cache-memory, but many still lack formal deduplication checks.

Focus on event-driven workflows (e.g., workflow_run, push, pull_request) and scheduled workflows that can run repeatedly and risk creating duplicate outputs.

Approach

1. Search .github/workflows/*.md for workflows that:
   • Use safe-outputs: create-issue: or safe-outputs: create-discussion: (or post comments)
   • Are triggered by workflow_run, schedule, push, or similar repeated triggers
   • Do NOT already {{#include cache-deduplication.md}}
2. Prioritize the top 5-10 workflows with the highest retry/repeat risk
3. For each selected workflow:
   • Add cache-memory: true to the tools: section if not already present
   • Add {{#include cache-deduplication.md}} in an appropriate section of the prompt body
   • Customize the cache key/path to be unique per workflow (e.g., /tmp/gh-aw/cache-memory/(workflow-name)/last-output.json)
4. Run make recompile to regenerate all affected lock files

Files to Modify

• Up to 10 workflow files in .github/workflows/*.md (the highest-impact ones)

Acceptance Criteria

• At least 5 high-impact workflows updated to use shared/cache-deduplication.md
• Each updated workflow has cache-memory: true in its frontmatter tools
• Each uses a unique cache path to avoid cross-workflow collisions
• make recompile runs without errors

Generated by Plan Command for issue #discussion #19917 · ◷

• expires on Mar 9, 2026, 1:56 AM UTC