[step-names] Step name inconsistencies in engine config and cache-memory steps

[github-actions]

Step Name Alignment Issues

Found in: .github/workflows/smoke-crush.lock.yml, .github/workflows/smoke-gemini.lock.yml, .github/workflows/ai-moderator.lock.yml

Summary

Two naming inconsistencies were found across 3 workflow lock files. Both deviate from the established patterns used in the 180+ other workflows in this repository.

---

Issues Identified

1. [Medium Priority] Inconsistent suffix in engine config write steps

Current step names:

• smoke-crush.lock.yml lines 869, 1309: Write Crush configuration
• smoke-gemini.lock.yml lines 918, 1405: Write Gemini Settings

Established pattern (same files, same jobs):

• Write Safe Outputs Config
• Write MCP Scripts Config

Issue:
The "Write" steps for engine-specific config use different suffixes: lowercase configuration (Crush) and Settings (Gemini), while every other "Write" config step in the codebase uses the uppercase suffix Config.

Suggested improvements:

• Write Crush configuration → Write Crush Config
• Write Gemini Settings → Write Gemini Config

---

2. [Low Priority] Inconsistent verb for cache-memory restore step

Current step name:

• ai-moderator.lock.yml line 404: Cache cache-memory file share data

Established pattern (82 other workflows):

• Restore cache-memory file share data

Issue:
ai-moderator.lock.yml uses Cache as the verb for the actions/cache step, causing the word "cache" to appear twice (verb + noun) and deviating from the Restore... pattern used everywhere else for the same step type.

Suggested improvement:

• Cache cache-memory file share data → Restore cache-memory file share data

---

Agentic Task Description

To fix these step names:

1. Review the context — confirm the suggested names are accurate by checking the step implementations
2. Apply changes — update step names in the source workflow .md files (not the .lock.yml directly)
   • .github/workflows/smoke-crush.md — for issue 1
   • .github/workflows/smoke-gemini.md — for issue 2
   • .github/workflows/ai-moderator.md — for issue 3 (may require compiler-level fix since step is compiler-generated)
3. Recompile — run gh aw compile on each changed source file to regenerate the .lock.yml
4. Verify — confirm the compiled output uses the corrected step names

Related Files

• Source workflow: .github/workflows/smoke-crush.md, .github/workflows/smoke-gemini.md, .github/workflows/ai-moderator.md
• Compiled workflow: .github/workflows/smoke-crush.lock.yml, .github/workflows/smoke-gemini.lock.yml, .github/workflows/ai-moderator.lock.yml
• Project glossary: docs/src/content/docs/reference/glossary.md

Priority

This issue is Medium Priority based on cross-workflow consistency impact.

---

AI generated by Step Name Alignment for daily maintenance

Generated by Step Name Alignment · ● 221.4K · ◷

• expires on Apr 19, 2026, 7:45 PM UTC

[github-actions]

🍪 *Issue Monster has assigned this to Copilotecho BEGIN___COMMAND_OUTPUT_MARKER ; PS1= ; PS2= ; unset HISTFILE ; EC=0 ; echo ___BEGIN___COMMAND_DONE_MARKER___0 ; }

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

The Copilot coding agent will analyze the issue and create a pull request with the fix.

Om nom nom! 🍪> [!CAUTION]

Security scanning requires review for Issue Monster

Details

Potential security threats were detected in the agent output. The workflow output should be reviewed before merging.

Review the workflow run logs for details.

🍪 Om nom nom by Issue Monster · ● 516.4K · ◷