Skip to content

[aw] Step Name Alignment failed #34371

@github-actions

Description

@github-actions

Workflow Failure

Workflow: Step Name Alignment
Branch: main
Run: https://github.com/github/gh-aw/actions/runs/26352648076

⚠️ Engine Failure: The claude engine terminated unexpectedly.

Last agent output:

2026-05-24T05:16:46.455Z [DEBUG] Spawning shell without login (-l flag skipped)
2026-05-24T05:16:46.780Z [INFO] [Stall] tool_dispatch_end tool=Bash toolUseId=toolu_01S8TUXeNvJPr6dUK5toNN9d outcome=ok durationMs=326
2026-05-24T05:16:46.782Z [DEBUG] LSP Diagnostics: getLSPDiagnosticAttachments called
{"type":"user","message":{"role":"user","content":[{"tool_use_id":"toolu_01S8TUXeNvJPr6dUK5toNN9d","type":"tool_result","content":"{\"body\":\"### Step Name Alignment Issues\\n\\nFound in: multiple `.lock.yml` files\\n\\n### Summary\\n\\nThree step names use an inconsistent style for the `pre-` compound prefix: one uses no hyphen (`Precompute`) while the other two use a hyphen (`Pre-compute`, `Pre-aggregate`). Consistent style improves readability and sets a clear convention for future step names.\\n\\n### Issues Identified\\n\\n#### 1. [High Priority] Inconsistent Hyphenation: `Pre-` Prefix\\n\\n**Current step names:**\\n\\n| Workflow | Line | Name |\\n|---|---|---|\\n| `bot-detection.lock.yml` | 1100 | `Precompute deterministic findings` |\\n| `schema-consistency-checker.lock.yml` | 457 | `Pre-compute schema analysis data` |\\n| `copilot-token-optimizer.lock.yml` | 417 | `Pre-aggregate top workflows by token usage` |\\n\\n**Issue:**\\nAll three step names describe a preparation/pre-processing step, but they use different styles for the `pre-` prefix. Modern English style guides and common technical usage prefer the unhyphenated compound form for standard prefixes like `pre-`.\\n\\n**Suggested improvements:**\\n- `Pre-compute schema analysis data` → `Precompute schema analysis data`\\n- `Pre-aggregate top workflows by token usage` → `Aggregate top workflows by token usage` _(dropping the prefix since \\\"aggregate\\\" already implies a build-up step; alternatively `Preaggregate top workflows by token usage` if the pre-computation framing is important)_\\n\\n**Standard to adopt:** No hyphen after `pre-` (matches `Precompute`, which is already correct).\\n\\n---\\n\\n### Agentic Task Description\\n\\nTo fix these step names:\\n\\n1. **Edit source files** — update step names in `.md` source files (not `.lock.yml` directly):\\n   - `.github/workflows/schema-consistency-checker.md` — change `Pre-compute schema analysis data` to `Precompute schema analysis data`\\n   - `.github/workflows/copilot-token-optimizer.md` — change `Pre-aggregate top workflows by token usage` to `Aggregate top workflows by token usage`\\n2. **Recompile** — run `gh aw compile` on each modified workflow\\n3. **Verify** — confirm changes appear in the regenerated `.lock.yml` files\\n\\n### Related Files\\n\\n- `.github/workflows/bot-detection.md` / `.lock.yml`\\n- `.github/workflows/schema-consistency-checker.md` / `.lock.yml`\\n- `.github/workflows/copilot-token-optimizer.md` / `.lock.yml`\\n\\n### Priority\\n\\nThis issue is **Medium Priority** — naming inconsistency affects readability but not functionality.\\n\\n---\\n\\n> AI generated by [Step Name Alignment](https://github.com/github/gh-aw/actions/workflows/step-name-alignment.lock.yml) for daily maintenance\\n\\n\\n\\n\\n> Generated by [Step Name Alignment](https://github.com/github/gh-aw/actions/runs/25244128618/agentic_workflow) · ● 173.4K · [◷](https://github.com/search?q=repo%3Agithub%2Fgh-aw+is%3Aissue+%22gh-aw-workflow-call-id%3A+github%2Fgh-aw%2Fstep-name-alignment%22&type=issues)\\n> - [x] expires <!-- gh-aw-expires: 2026-05-04T04:57:11.902Z --> on May 4, 2026, 4:57 AM UTC\\n\\n<!-- gh-aw-agentic-workflow: Step Name Alignment, engine: claude, model: auto, id: 25244128618, workflow_id: step-name-alignment, run: https://github.com/github/gh-aw/actions/runs/25244128618 -->\\n\\n<!-- gh-aw-workflow-id: step-name-alignment -->\\n<!-- gh-aw-workflow-call-id: github/gh-aw/step-name-alignment -->\",\"closedAt\":\"2026-05-03T15:40:12Z\",\"state\":\"CLOSED\",\"title\":\"[step-names] Standardize 'pre-' prefix hyphenation across step names\"}","is_error":false}]},"parent_tool_use_id":null,"session_id":"ac3e70e4-3c91-4040-ab97-7d7d91780d38","uuid":"5a1e61b2-ffd9-4c2c-a078-561fb8ea61b7","timestamp":"2026-05-24T05:16:46.780Z","tool_use_result":{"stdout":"{\"body\":\"### Step Name Alignment Issues\\n\\nFound in: multiple `.lock.yml` files\\n\\n### Summary\\n\\nThree step names use an inconsistent style for the `pre-` compound prefix: one uses no hyphen (`Precompute`) while the other two use a hyphen (`Pre-compute`, `Pre-aggregate`). Consistent style improves readability and sets a clear convention for future step names.\\n\\n### Issues Identified\\n\\n#### 1. [High Priority] Inconsistent Hyphenation: `Pre-` Prefix\\n\\n**Current step names:**\\n\\n| Workflow | Line | Name |\\n|---|---|---|\\n| `bot-detection.lock.yml` | 1100 | `Precompute deterministic findings` |\\n| `schema-consistency-checker.lock.yml` | 457 | `Pre-compute schema analysis data` |\\n| `copilot-token-optimizer.lock.yml` | 417 | `Pre-aggregate top workflows by token usage` |\\n\\n**Issue:**\\nAll three step names describe a preparation/pre-processing step, but they use different styles for the `pre-` prefix. Modern English style guides and common technical usage prefer the unhyphenated compound form for standard prefixes like `pre-`.\\n\\n**Suggested improvements:**\\n- `Pre-compute schema analysis data` → `Precompute schema analysis data`\\n- `Pre-aggregate top workflows by token usage` → `Aggregate top workflows by token usage` _(dropping the prefix since \\\"aggregate\\\" already implies a build-up step; alternatively `Preaggregate top workflows by token usage` if the pre-computation framing is important)_\\n\\n**Standard to adopt:** No hyphen after `pre-` (matches `Precompute`, which is already correct).\\n\\n---\\n\\n### Agentic Task Description\\n\\nTo fix these step names:\\n\\n1. **Edit source files** — update step names in `.md` source files (not `.lock.yml` directly):\\n   - `.github/workflows/schema-consistency-checker.md` — change `Pre-compute schema analysis data` to `Precompute schema analysis data`\\n   - `.github/workflows/copilot-token-optimizer.md` — change `Pre-aggregate top workflows by token usage` to `Aggregate top workflows by token usage`\\n2. **Recompile** — run `gh aw compile` on each modified workflow\\n3. **Verify** — confirm changes appear in the regenerated `.lock.yml` files\\n\\n### Related Files\\n\\n- `.github/workflows/bot-detection.md` / `.lock.yml`\\n- `.github/workflows/schema-consistency-checker.md` / `.lock.yml`\\n- `.github/workflows/copilot-token-optimizer.md` / `.lock.yml`\\n\\n### Priority\\n\\nThis issue is **Medium Priority** — naming inconsistency affects readability but not functionality.\\n\\n---\\n\\n> AI generated by [Step Name Alignment](https://github.com/github/gh-aw/actions/workflows/step-name-alignment.lock.yml) for daily maintenance\\n\\n\\n\\n\\n> Generated by [Step Name Alignment](https://github.com/github/gh-aw/actions/runs/25244128618/agentic_workflow) · ● 173.4K · [◷](https://github.com/search?q=repo%3Agithub%2Fgh-aw+is%3Aissue+%22gh-aw-workflow-call-id%3A+github%2Fgh-aw%2Fstep-name-alignment%22&type=issues)\\n> - [x] expires <!-- gh-aw-expires: 2026-05-04T04:57:11.902Z --> on May 4, 2026, 4:57 AM UTC\\n\\n<!-- gh-aw-agentic-workflow: Step Name Alignment, engine: claude, model: auto, id: 25244128618, workflow_id: step-name-alignment, run: https://github.com/github/gh-aw/actions/runs/25244128618 -->\\n\\n<!-- gh-aw-workflow-id: step-name-alignment -->\\n<!-- gh-aw-workflow-call-id: github/gh-aw/step-name-alignment -->\",\"closedAt\":\"2026-05-03T15:40:12Z\",\"state\":\"CLOSED\",\"title\":\"[step-names] Standardize 'pre-' prefix hyphenation across step names\"}","stderr":"","interrupted":false,"isImage":false,"noOutputExpected":false}}
2026-05-24T05:16:46.782Z [DEBUG] LSP Diagnostics: Checking registry - 0 pending
2026-05-24T05:16:46.782Z [DEBUG] Hooks: Found 0 total hooks in registry
2026-05-24T05:16:46.782Z [DEBUG] Hooks: checkForNewResponses returning 0 responses
{"type":"result","subtype":"error_max_turns","duration_ms":175665,"duration_api_ms":171487,"is_error":true,"num_turns":31,"stop_reason":"tool_use","session_id":"ac3e70e4-3c91-4040-ab97-7d7d91780d38","total_cost_usd":1.8761147499999997,"usage":{"input_tokens":34,"cache_creation_input_tokens":72043,"cache_read_input_tokens":2192172,"output_tokens":11180,"server_tool_use":{"web_search_requests":0,"web_fetch_requests":0},"service_tier":"standard","cache_creation":{"ephemeral_1h_input_tokens":0,"ephemeral_5m_input_tokens":72043},"inference_geo":"","iterations":[],"speed":"standard"},"modelUsage":{"claude-opus-4-7[1m]":{"inputTokens":9942,"outputTokens":11202,"cacheReadInputTokens":2192172,"cacheCreationInputTokens":72043,"webSearchRequests":0,"costUSD":1.8761147499999997,"contextWindow":1000000,"maxOutputTokens":64000}},"permission_denials":[{"tool_name":"Bash","tool_use_id":"toolu_019EhJidoX8a6uZBmLqrdx1J","tool_input":{"command":"ls -la /tmp/gh-aw/cache-memory/ 2>/dev/null && ls -la /tmp/gh-aw/agent/ 2>/dev/null","description":"Check cache memory and agent input directories"}},{"tool_name":"Bash","tool_use_id":"toolu_015dXK6Urp7XmSeKCi41kF3J","tool_input":{"command":"ls -la /tmp/gh-aw/cache-memory/ 2>/dev/null || echo \"no cache dir\"","description":"Check cache memory directory"}},{"tool_name":"Bash","tool_use_id":"toolu_013wbpoz8NV3Veo2uaZj9ATq","tool_input":{"command":"ls -la /tmp/gh-aw/agent/ 2>/dev/null || echo \"no agent dir\"","description":"Check agent input directory"}},{"tool_name":"Bash","tool_use_id":"toolu_01HyYk9Uif4pff9JiNfQ2CMK","tool_input":{"command":"wc -l /tmp/gh-aw/agent/step-alignment-input.json && head -c 2000 /tmp/gh-aw/agent/step-alignment-input.json","description":"Check manifest file size and preview"}},{"tool_name":"Bash","tool_use_id":"toolu_01WYQ22cFXE6YJKgjRypnqRx","tool_input":{"command":"wc -l /tmp/gh-aw/agent/step-alignment-input.json","description":"Count lines in manifest"}},{"tool_name":"Bash","tool_use_id":"toolu_01GiAxqYdb3XAAZVPVHeZtyy","tool_input":{"command":"jq -r '.[] | .step_name' /tmp/gh-aw/agent/step-alignment-input.json | sort -u > /tmp/gh-aw/agent/unique-step-names.txt && wc -l /tmp/gh-aw/agent/unique-step-names.txt","description":"Extract unique step names"}},{"tool_name":"Bash","tool_use_id":"toolu_01Kin6ZfTABWwfgGztM5Qxzm","tool_input":{"command":"jq -r '.[] | .step_name' /tmp/gh-aw/agent/step-alignment-input.json | sort -u > /tmp/gh-aw/agent/unique-step-names.txt","description":"Extract unique step names"}},{"tool_name":"Bash","tool_use_id":"toolu_0166qT2C7b7oT9TNKL9tVzsr","tool_input":{"command":"jq -r '[.[].step_name] | unique | .[]' /tmp/gh-aw/agent/step-alignment-input.json > /tmp/gh-aw/agent/unique-step-names.txt","description":"Extract unique step names with jq"}},{"tool_name":"Bash","tool_use_id":"toolu_01UYz27vXkLR9Y66K3QssUpU","tool_input":{"command":"jq -r '[.[].step_name] | unique | .[]' /tmp/gh-aw/agent/step-alignment-input.json > /home/runner/work/gh-aw/gh-aw/.tmp-unique-steps.txt","description":"Extract unique step names to repo dir"}},{"tool_name":"Bash","tool_use_id":"toolu_01CihwHXerggaAAjRp91qfpm","tool_input":{"command":"cp /tmp/gh-aw/agent/step-alignment-input.json /home/runner/work/gh-aw/gh-aw/.tmp-step-input.json","description":"Copy manifest into working dir"}}],"terminal_reason":"max_turns","fast_mode_state":"off","uuid":"30dc727e-91fc-4d56-adaa-10fd13afb5da","errors":["Reached maximum number of turns (30)"]}
2026-05-24T05:16:46.787Z [DEBUG] LSP server manager shut down successfully
2026-05-24T05:16:46.788Z [DEBUG] Cleaned up session snapshot: /home/runner/.claude/shell-snapshots/snapshot-bash-1779599680405-a3p0wr.sh

Action Required

Assign this issue to an agent to debug and fix the issue.

Debug with any coding agent

Use this prompt with any coding agent (GitHub Copilot, Claude, Gemini, etc.):

Debug the agentic workflow failure using https://raw.githubusercontent.com/github/gh-aw/main/debug.md

The failed workflow run is at https://github.com/github/gh-aw/actions/runs/26352648076
Manually invoke the agent

Debug this workflow failure using your favorite Agent CLI and the agentic-workflows prompt.

Tip

Stop reporting this workflow as a failure

To stop a workflow from creating failure issues, set report-failure-as-issue: false in its frontmatter:

safe-outputs:
  report-failure-as-issue: false

Generated from Step Name Alignment · ● opu47 9.1M ·

  • expires on May 24, 2026, 5:17 PM UTC

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions