unbloat-docs workflow: YAML parse error - mapping value not allowed in engine block

[yoursweetginger]

Description

When running gh aw add-wizard githubnext/agentics/unbloat-docs, the workflow fails to stage with a YAML parse error.

Error

✗ .github/workflows/unbloat-docs.md:25:9: error: mapping value is not allowed in this context
  22 | strict: true
  23 | 
  24 | # AI engine configuration
> 25 | engine: copilot
  26 |   id: claude
               ^
  27 |   max-turns: 90
  28 | 
✗ failed to add workflow: failed to add workflows: failed to stage workflow files: failed to stage files: exit status 128

Expected Behavior

The workflow should be added successfully without YAML errors.

Root Cause

In the generated unbloat-docs.md frontmatter, the engine field is set to copilot as a scalar value on line 25, but subsequent lines attempt to add nested keys (id: claude, max-turns: 90) with indentation under it. This is invalid YAML — a scalar value cannot also have child mappings.

The frontmatter likely intends:

engine:
  name: copilot
  id: claude
  max-turns: 90

Environment

• Tool: gh aw add-wizard
• Workflow: githubnext/agentics/unbloat-docs
• OS: Linux
• Engine selected: copilot (with existing COPILOT_GITHUB_TOKEN secret)

[dsyme]

Thanks, this was because the workflow had an engine declaration, and you chose a different engine, and the process of updating the frontmatter during installation caused a bad workflow to be produced

I've removed the unnecessary engine declarations for the workflows in this repository and tracking the GH-AW bug with github/gh-aw#18485