create-issue-command.md: Undocumented `GH_AW_AGENT_TOKEN` and inconsistent token configuration across safe-outputs

[github-actions]

Summary

The safe-outputs.reply-to-pull-request-review-comment in .github/workflows/create-issue-command.md references secrets.GH_AW_AGENT_TOKEN, but this secret is not mentioned or documented elsewhere in the repository. Additionally, safe-outputs.create-issue does not specify the same matching token, creating an inconsistency that is likely to cause a confusing runtime failure (missing secret and/or insufficient permissions).

File and Location

• File: .github/workflows/create-issue-command.md
• Line: 22

Original Review Comment

safe-outputs.reply-to-pull-request-review-comment references secrets.GH_AW_AGENT_TOKEN, but this secret isn't mentioned elsewhere in the repo docs, and create-issue doesn't specify a matching token. This is likely to cause a confusing runtime failure (missing secret and/or insufficient permissions). Either remove the custom token field and rely on GITHUB_TOKEN with proper permissions, or consistently configure and document the required secret for all write safe-outputs.

View review comment

Recommended Fix

Choose one of the following approaches:

1. Remove the custom token — rely on GITHUB_TOKEN with appropriate permissions (issues: write, pull-requests: write) for all safe-outputs.
2. Consistently use GH_AW_AGENT_TOKEN — apply it to all write safe-outputs (create-issue, reply-to-pull-request-review-comment, etc.) and add documentation in the relevant README/DEVELOPMENT.md explaining what the secret is, what scopes it requires, and how to configure it.

Related PR

Related PR: #51

Generated by PR Review Comment — Create Issue for issue #51