[aw] Dead-code Removal Rotation produced no safe outputs

[github-actions]

Workflow Failure

Workflow: Dead-code Removal Rotation
Branch: main
Run: https://github.com/elastic/terraform-provider-elasticstack/actions/runs/32804289193

Warning

No Safe Outputs Generated: The agent job succeeded but did not produce any safe outputs.

This typically indicates:

• The safe output server failed to run
• The prompt failed to generate any meaningful result
• The agent should have called noop to explicitly indicate no action was taken

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/elastic/terraform-provider-elasticstack/actions/runs/32804289193

Manually invoke the agent

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

• Start your agent
• Load the agentic-workflows skill from .github/skills/agentic-workflows/SKILL.md or https://github.com/github/gh-aw/blob/main/.github/skills/agentic-workflows/SKILL.md
• Type debug the agentic workflow ci-deadcode-removal-rotation failure in https://github.com/elastic/terraform-provider-elasticstack/actions/runs/32804289193

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 Dead-code Removal Rotation · ◷

[github-actions]

Thanks for filing this! I've added the needs-human label to this issue.

This is an auto-generated report from the ci-deadcode-removal-rotation agentic workflow indicating it ran but didn't produce any safe outputs (e.g. it should have called noop explicitly, or something in the run failed silently). This is an infrastructure/automation issue rather than a Terraform provider feature request or bug, so it doesn't map to the research, reproduction, or spec pipelines — it needs a maintainer to look at the workflow run and debug why no outputs were generated.

A maintainer will review it shortly. If I've misclassified this, please leave a comment and a maintainer can adjust the label manually.