[step-names] Standardize "Config" abbreviation in compiler-generated step names

[github-actions]

Step Name Alignment Issues

Found in: compiler-generated steps across .github/workflows/*.lock.yml (189+ workflows)

Summary

Compiler-generated steps inconsistently abbreviate "configuration" — 196 files use Config while the threat-detection step in 189 files uses the full word configuration. A new contributor reading the Actions UI would see both forms side-by-side within the same job and wonder which spelling is authoritative.

Issues Identified

1. [High Priority] Inconsistent abbreviation: "Config" vs "configuration"

Steps using abbreviated form (196 files, 424 occurrences):

• Write Safe Outputs Config
• Generate Safe Outputs MCP Server Config
• Write MCP Scripts Config
• Generate MCP Scripts Server Config
• Write Crush Config
• Write Gemini Config
• Write OpenCode Config

Steps using full word (189+ files):

• Clear MCP configuration for detection
• Compute release configuration (release.lock.yml, daily-choice-test.lock.yml)
• Display test configuration

Issue:
All of these are compiler-generated steps. Within a single workflow run (e.g. daily-fact.lock.yml), the GitHub Actions UI shows both Write Safe Outputs Config and Clear MCP configuration for detection — two forms of the same noun, produced by the same compiler.

Suggested fix:
Standardize on the abbreviated Config form, which is used by ~87% of instances and is more appropriate for short step labels displayed in the UI:

• Clear MCP configuration for detection → Clear MCP Config for detection
• Compute release configuration → Compute release Config (or Compute Release Config)
• Display test configuration → Display test Config

---

2. [Low Priority] Redundant "tool" suffix: "Run stale-repos tool"

File: .github/workflows/stale-repo-identifier.lock.yml

Current: Run stale-repos tool

Issue:
All peer steps in this pattern omit the "tool" suffix: Run skill-optimizer, Run super-linter, Run linter. The word "tool" is redundant — these are all tools by definition.

Suggested fix:

• Run stale-repos tool → Run stale-repos

---

Agentic Task Description

Both issues are in compiler-generated boilerplate, not in user-authored .md workflow files:

1. Locate the step name strings in the compiler source (likely in pkg/ or internal/ Go files that emit the compiled YAML steps)
2. Apply the changes to the compiler templates/constants
3. Recompile all affected workflows: gh aw compile (or the batch compile command)
4. Verify that .lock.yml diffs show only the expected step name changes

Related Files

• Compiler source: search for "Clear MCP configuration" and "stale-repos tool" in Go source files
• Project glossary: docs/src/content/docs/reference/glossary.md
• Example affected workflow: .github/workflows/daily-fact.lock.yml

Priority

High for finding #1 (affects 189+ workflows, visible in every run), Low for finding #2 (single workflow).

---

AI generated by Step Name Alignment for daily maintenance

Generated by Step Name Alignment · ● 411.9K · ◷

• expires on Apr 27, 2026, 7:41 PM UTC

[github-actions]

🍪 *Issue Monster selected this for 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 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! 🍪

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 · ● 28.9K · ◷