create_issue fields fails on removed IssueField GraphQL fragments

[Knufle]

Summary

The create_issue safe output handler fails when an agent supplies the optional fields array. The issue itself is created, but applying the fields fails during GraphQL issue-field discovery.

Reproduction

Use the create_issue safe output with a field assignment such as:

{
  "type": "create_issue",
  "title": "test",
  "body": "a sufficiently long body",
  "fields": [{"name":"Project","value":"Kanban Board"}]
}

Observed error

No such type IssueField, so it can't be a fragment condition
No such type IssueFieldIteration, so it can't be a fragment condition

The handler creates the issue through REST first and then runs applyIssueFields, so the result is a partial failure: the issue exists but the requested field is not applied.

Context

• Failing runtime: github/gh-aw-actions/setup@v0.87.0
• Failing code path: setup/js/create_issue.cjs -> fetchIssueFields
• The query contains ... on IssueField and ... on IssueFieldIteration, which are not valid types in the current GitHub GraphQL schema.

Expected behavior

The field discovery query should use only valid concrete IssueFields union members, and field application should either complete or fail before creating the issue.

Related

This is related to github/gh-aw#38797, but that closed issue covers set_issue_field; this report covers the separate create_issue.fields path.