Step Name Alignment Issues
Found in: .github/workflows/shared/mcp-debug.md (compiled into consuming .lock.yml files)
Summary
A single step name uses lowercase server where the project glossary defines MCP Server as a Title Case term. This is the last remaining instance of the casing inconsistency that was previously corrected for the MemPalace and Drain3 MCP Server components.
Issues Identified
1. [Medium Priority] Casing: "Start MCP server" → "Start MCP Server"
Current step name:
.github/workflows/shared/mcp-debug.md:142: Start MCP server
Issue:
The glossary defines MCP Server as a Title Case term. This step starts a genuine MCP Server (it runs ./gh-aw mcp-server --cmd ./gh-aw --port 8765), so the glossary casing rule applies. The lowercase server is inconsistent with sibling components that were already aligned:
Suggested improvement:
Start MCP server → Start MCP Server
Glossary reference: See MCP Server
Precedent: #35396 (MemPalace casing alignment, completed)
Note: prose inside the step's run: script (# Wait a moment for server to start, MCP server failed to start) is body text, not a step name, and is intentionally left out of scope.
Agentic Task Description
- Review the context — confirm line 142 of
shared/mcp-debug.md is the Start MCP server step that launches gh-aw mcp-server.
- Apply the change — update the step name to
Start MCP Server in the source .md file (not the .lock.yml).
- Verify glossary alignment — Title Case
MCP Server per the glossary.
- Recompile — run
gh aw compile so the regenerated .lock.yml files pick up the new step name.
- Test — ensure consuming workflows still function.
Related Files
- Source component:
.github/workflows/shared/mcp-debug.md
- Project glossary:
docs/src/content/docs/reference/glossary.md
Priority
This issue is Medium Priority — a cosmetic but glossary-defined consistency fix that completes the MCP Server casing alignment started in #35396.
AI generated by Step Name Alignment for daily maintenance
Generated by 📋 Step Name Alignment · opus48 804.5K · ◷
Step Name Alignment Issues
Found in:
.github/workflows/shared/mcp-debug.md(compiled into consuming.lock.ymlfiles)Summary
A single step name uses lowercase
serverwhere the project glossary defines MCP Server as a Title Case term. This is the last remaining instance of the casing inconsistency that was previously corrected for the MemPalace and Drain3 MCP Server components.Issues Identified
1. [Medium Priority] Casing: "Start MCP server" → "Start MCP Server"
Current step name:
.github/workflows/shared/mcp-debug.md:142:Start MCP serverIssue:
The glossary defines MCP Server as a Title Case term. This step starts a genuine MCP Server (it runs
./gh-aw mcp-server --cmd ./gh-aw --port 8765), so the glossary casing rule applies. The lowercaseserveris inconsistent with sibling components that were already aligned:shared/mcp/mempalace.md→Start MemPalace MCP Server(fixed in [step-names] Align two source step names: MempPalace MCP Server casing and Cache→Save pattern #35396)shared/mcp/drain3.md:30→Start Drain3 MCP Servershared/mcp/drain3.md:25→Copy Drain3 MCP Server scriptSuggested improvement:
Start MCP server→Start MCP ServerGlossary reference: See MCP Server
Precedent: #35396 (MemPalace casing alignment, completed)
Agentic Task Description
shared/mcp-debug.mdis theStart MCP serverstep that launchesgh-aw mcp-server.Start MCP Serverin the source.mdfile (not the.lock.yml).MCP Serverper the glossary.gh aw compileso the regenerated.lock.ymlfiles pick up the new step name.Related Files
.github/workflows/shared/mcp-debug.mddocs/src/content/docs/reference/glossary.mdPriority
This issue is Medium Priority — a cosmetic but glossary-defined consistency fix that completes the MCP Server casing alignment started in #35396.