[step-names] Align Codex engine step names: "Install Codex CLI" vs "Execute Codex"

[github-actions]

Step Name Alignment Issue

Found in: .github/workflows/smoke-codex.lock.yml and 16 other Codex engine workflows

Summary

Codex engine workflows use inconsistent "CLI" suffix between their install and execute steps. All other engines use the "CLI" suffix in both install and execute step names — Codex installs with "CLI" but executes without it.

Issue Identified

[High Priority] Inconsistent CLI suffix: "Install Codex CLI" vs "Execute Codex"

Current step names (in same workflows):

• name: Install Codex CLI — 17 workflows
• name: Execute Codex — 17 workflows (same files)

Established engine naming pattern:

Engine	Install step	Execute step
GitHub Copilot	Install GitHub Copilot CLI ✅	Execute GitHub Copilot CLI ✅
Claude Code	Install Claude Code CLI ✅	Execute Claude Code CLI ✅
Gemini	Install Gemini CLI ✅	Execute Gemini CLI ✅
Codex	Install Codex CLI ⚠️	Execute Codex ⚠️

Issue:
Install Codex CLI was updated to add the "CLI" suffix (matching the Codex CLI official tool name), but Execute Codex was not updated accordingly, leaving both names in the same workflow files.

Suggested fix:
Update Execute Codex → Execute Codex CLI in all 17 affected Codex workflows to match the install step and align with the engine naming pattern used by all other engines.

Affected workflows (17 total, sample):

• smoke-codex.lock.yml
• ai-moderator.lock.yml
• changeset.lock.yml
• codex-github-remote-mcp-test.lock.yml
• daily-fact.lock.yml
• daily-issues-report.lock.yml
• daily-observability-report.lock.yml
• deep-report.lock.yml
• duplicate-code-detector.lock.yml
• issue-arborist.lock.yml
• schema-feature-coverage.lock.yml
• smoke-agent-all-merged.lock.yml
• smoke-agent-all-none.lock.yml
• smoke-agent-public-approved.lock.yml
• smoke-agent-public-none.lock.yml
• smoke-agent-scoped-approved.lock.yml
• smoke-call-workflow.lock.yml

---

Agentic Task Description

To fix this inconsistency:

1. Identify source files — Find the .md source workflows for each affected .lock.yml
2. Update execute step names — Change Execute Codex → Execute Codex CLI in each source file
3. Recompile — Run gh aw compile (workflow).md to regenerate each .lock.yml
4. Verify — Confirm both Install and Execute steps use Codex CLI suffix in each compiled file

Related Files

• Source workflows: .github/workflows/*.md (Codex engine workflows)
• Compiled workflows: .github/workflows/*.lock.yml (17 affected files)
• Project glossary: docs/src/content/docs/reference/glossary.md

Priority

This issue is High Priority — it affects 17 workflows and breaks the established engine naming pattern.

---

AI generated by Step Name Alignment for daily maintenance

Generated by Step Name Alignment · ◷

• expires on Mar 22, 2026, 12:29 PM UTC

[github-actions]

🍪 Issue Monster has assigned this to Copilot!

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! 🍪

Note

🔒 Integrity filtering filtered 2 items

Integrity filtering activated and filtered the following items during workflow execution.
This happens when a tool call accesses a resource that does not meet the required integrity or secrecy level of the workflow.

• issue:[cli-consistency] CLI Consistency Issues - 2026-03-20 #21967 (issue_read: Resource 'issue:[cli-consistency] CLI Consistency Issues - 2026-03-20 #21967' has lower integrity than agent requires. Agent would need to drop integrity tags [unapproved:all approved:all] to trust this resource.)
• issue:[step-names] Align Codex engine step names: "Install Codex CLI" vs "Execute Codex" #21956 (issue_read: Resource 'issue:[step-names] Align Codex engine step names: "Install Codex CLI" vs "Execute Codex" #21956' has lower integrity than agent requires. Agent would need to drop integrity tags [unapproved:all approved:all] to trust this resource.)

🍪 Om nom nom by Issue Monster · ◷