Connector action pack: GitHub hardening

[prvnsmpth]

Context

The GitHub connector already exposes GitHub's MCP server as connector actions. That gives Omni broad GitHub tool coverage, but deployed workplace agents need the GitHub action surface to be safe, scoped, well-described, and tested in Omni's connector/action framework.

Goal

Harden the GitHub MCP-backed action pack so agents can reliably and safely work with repositories, issues, pull requests, and discussions.

Scope

• Audit the MCP tools exposed by the GitHub connector and group them into useful Omni-facing capabilities.
• Verify action schemas are model-friendly after MCP-to-Omni conversion.
• Ensure MCP read-only annotations map correctly to mode = read; mutating tools must map to mode = write.
• Confirm OAuth/PAT scopes required for common workflows are documented and enforced.
• Validate source/repository scoping so agents do not operate outside the configured GitHub source where avoidable.
• Add safety affordances for high-risk operations where needed, such as clearer descriptions or hidden/admin-only treatment for unsuitable tools.
• Add or update GitHub-specific skill guidance for common workflows:
  • investigate an issue
  • summarize a PR
  • comment on an issue/PR
  • create/update issues
• Add integration/unit tests around action discovery and representative read/write calls.

Acceptance criteria

• GitHub MCP actions are discoverable through Omni's tool search/load flow.
• Read vs write classification is correct for representative GitHub tools.
• Write actions require chat approval through the existing approval system.
• Credential/scoping behavior is documented and tested.
• At least one read workflow and one write workflow are covered by tests.
• Any MCP tools that are unsafe or not useful in Omni are hidden, constrained, or documented as follow-up work.