GitHub connector lacks delete_issue_comment action

Summary

The curated GitHub connector can create and update issue comments, but it does not expose a way to delete an issue comment.

Current related tools include:

• github_add_comment_to_issue
• github_update_issue_comment
• github_fetch_issue_comments

There is no github_delete_issue_comment action.

Reproduction

1. Create a comment with github_add_comment_to_issue.
2. Later determine that the comment belongs in a standalone issue instead.
3. Create the standalone issue.
4. Attempt to remove the now-superseded comment.

The connector can replace the comment body, but cannot delete the comment. If gh is not installed and no authenticated browser session is available, the user must delete it manually.

This occurred while moving a connector-authored report from a comment on #31114 into standalone issue #37785. The replacement issue succeeded through the connector; the old comment required manual deletion.

Expected behavior

Please expose a narrowly scoped action such as:

github_delete_issue_comment(
  repo_full_name: string,
  comment_id: number
)

It should map to GitHub's issue-comment deletion endpoint and use the same explicit write confirmation model as other destructive connector actions.

Why this matters

Create/update without delete leaves Codex unable to complete ordinary correction, retraction, and report-migration workflows using the connector's existing authentication. Browser or CLI fallbacks require a second authenticated surface and are not always available.

Environment

• GitHub plugin: github@openai-curated
• Installed plugin version: 0.1.8-2841cf9749ae
• Connector ID: connector_76869538009648d5b282a4bb21c3d157
• Observed on Codex Desktop for Windows on 2026-08-09/10.

No credentials, private repository names, account tokens, or private comment contents are included.

Start from the existing github_add_comment_to_issue and github_update_issue_comment actions and trace how their connector entry points handle authentication and explicit write confirmation. Add the narrowly scoped deletion action using GitHub's issue-comment deletion endpoint, then verify that the action accepts repo_full_name and comment_id and follows the existing destructive-action confirmation behavior.