[step-names] Lock/Unlock steps use "agent workflow" instead of glossary term "agentic workflow"

[github-actions]

Found in: .github/workflows/workflow-generator.lock.yml, .github/workflows/ai-moderator.lock.yml

Summary

Two compiler-generated step names use the phrase "agent workflow" instead of the project-defined term "agentic workflow" from the glossary. While subtle, the distinction matters: the glossary explicitly defines Agentic Workflow as a proper term, and "agent workflow" is not defined.

Issues Identified

[Medium Priority] Terminology Mismatch: "agent workflow" → "agentic workflow"

Current step names (in both affected lock files):

• Lock issue for agent workflow
• Unlock issue after agent workflow

Issue:
The project glossary defines the canonical term as "Agentic Workflow" — an AI-powered workflow that reasons, makes decisions, and takes autonomous actions. Using "agent workflow" (adjective + noun) instead of the established term "agentic workflow" is inconsistent with all other uses across the codebase.

Suggested improvements:

• Lock issue for agent workflow → Lock issue for agentic workflow
• Unlock issue after agent workflow → Unlock issue after agentic workflow

Glossary reference: Agentic Workflow

Root cause:
These steps are compiler-generated when lock-for-agent: true is set in the on: trigger section of a workflow. The fix requires updating the compiler template that generates these step names, not the individual .md source files.

Affected source workflows:

• .github/workflows/workflow-generator.md — uses lock-for-agent: true under on.issues
• .github/workflows/ai-moderator.md — uses lock-for-agent: true under on.issues and on.issue_comment

Affected lock files:

• .github/workflows/workflow-generator.lock.yml
• .github/workflows/ai-moderator.lock.yml

---

Agentic Task Description

To fix these step names:

1. Find the compiler template — Search for the string Lock issue for agent workflow in the compiler source (likely in Go or JS template files)
2. Update the template — Change agent workflow to agentic workflow in both the lock and unlock step name templates
3. Recompile affected workflows — Run gh aw compile .github/workflows/workflow-generator.md and gh aw compile .github/workflows/ai-moderator.md
4. Verify — Confirm the updated .lock.yml files contain the corrected step names

Related Files

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

---

AI generated by Step Name Alignment for daily maintenance

Generated by Step Name Alignment · ● 395.3K · ◷

• expires on May 10, 2026, 4:59 AM UTC

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