GitHub connector: inconsistent repository parameter name causes misleading schema error

What issue are you seeing?

The GitHub connector exposes inconsistent names for the same repository identifier across sibling tools.

For example, fetch_issue_comments requires repo_full_name, while many other GitHub tools (including create_issue) require repository_full_name. This makes a plausible model-generated call fail before reaching GitHub.

The resulting validation error also includes a workspace-admin message, even though the failure is only an input-field mismatch:

Parameters failed connector schema validation: repo_full_name [required]:
Missing required property (does not match constraints configured by your ChatGPT
workspace admin. If the issue persists, instruct the user to contact their
workspace admin.); repo_full_name [required]: Missing required property

What steps can reproduce the bug?

Call the GitHub connector using the naming convention exposed by many sibling tools:

{
  "repository_full_name": "OWNER/REPO",
  "issue_number": 123
}

Tool:

codex_apps.github.fetch_issue_comments

The call fails schema validation because repo_full_name is required.

Retry with:

{
  "repo_full_name": "OWNER/REPO",
  "issue_number": 123
}

The call succeeds.

What is the expected behavior?

Use one repository-field name consistently across GitHub connector tools, preferably repository_full_name, or accept both forms as compatibility aliases.

For a plain schema mismatch, the error should identify the unexpected/missing field without suggesting workspace-admin intervention.

Additional information

Observed with the OpenAI GitHub plugin version 0.1.8-2841cf9749ae.

This is not an authentication, repository-access, or workspace-policy failure: changing only the parameter name makes the same read-only request succeed.