[step-names] Align step names: "awf" capitalization and "Safe Outputs" consistency

[github-actions]

Step Name Alignment Issues

Found across: all .github/workflows/*.lock.yml files (compiled output)

Summary

Two systematic step naming inconsistencies were found spanning almost every workflow in the repository. Both originate from shared compilation templates, so a fix at the template level would resolve all instances at once.

Issues Identified

1. [High Priority] Terminology Mismatch: "awf binary" → "AWF binary"

Affected step name (166 files):

• Install awf binary

Issue:
The project glossary defines AWF as an acronym for "Agent Workflow Firewall" and uses all-caps throughout. However, the step name uses lowercase awf, inconsistent with how all other tool names are capitalized in step names across the project:

Current (inconsistent)	Others (consistent)
Install awf binary	Install GitHub Copilot CLI
	Install Codex
	Install Gemini CLI
	Install Claude Code CLI

Suggested improvement:

Install awf binary  →  Install AWF binary
```

**Glossary reference:** [AWF (Agent Workflow Firewall)](docs/src/content/docs/reference/glossary.md#awf-agent-workflow-firewall)

---

#### 2. [High Priority] Capitalization Inconsistency: `"safe output items manifest"`

**Affected step name (157 files):**
- `Upload safe output items manifest`

**Issue:**
This step uses lowercase `safe output`, but every other Safe Outputs-related step in the same workflows consistently capitalizes the term as a product name:

| Current (inconsistent) | Others in same workflow (consistent) |
|---|---|
| `Upload safe output items manifest` | `Upload Safe Outputs` |
| | `Write Safe Outputs Config` |
| | `Generate Safe Outputs MCP Server Config` |
| | `Start Safe Outputs MCP HTTP Server` |
| | `Process Safe Outputs` |

**Suggested improvement:**
```
Upload safe output items manifest  →  Upload Safe Output Items Manifest

---

Agentic Task Description

Since both issues originate from shared compilation templates (not individual workflow source files), the fix should target the template layer:

1. Locate the template — Find where Install awf binary and Upload safe output items manifest step names are generated (likely in the compiler or shared action scripts under .github/actions/ or the gh-aw compiler source)
2. Apply the rename — Update the template strings:
   • Install awf binary → Install AWF binary
   • Upload safe output items manifest → Upload Safe Output Items Manifest
3. Recompile affected workflows — Run gh aw compile on all workflows that use these steps to regenerate the .lock.yml files
4. Verify — Confirm the updated step names appear in the recompiled .lock.yml files

Related Files

• Compiled workflows: .github/workflows/*.lock.yml (all affected)
• Project glossary: docs/src/content/docs/reference/glossary.md

Priority

High Priority — Both issues affect 150+ compiled workflow files and conflict with the project glossary or established internal naming conventions.

---

AI generated by Step Name Alignment for daily maintenance

Generated by Step Name Alignment · ◷

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