Feature request: let the GitHub connector manage Actions repository secrets safely

What feature would you like?

Please extend the official Codex GitHub connector so it can safely create and reconcile GitHub Actions repository secrets through the connected GitHub App.

The current connector exposes repository, code, issue, pull-request, workflow, and Actions-run operations, but it does not expose repository-secret operations and the installed GitHub App does not request the repository Secrets permission. Changing Codex's local plugin approval to full access cannot add a permission that the GitHub App itself did not request.

A minimal safe tool surface would be:

1. Retrieve a repository's Actions-secrets public key and key_id.
2. List secret metadata (name and timestamps only).
3. Create or update a secret from a caller-supplied LibSodium sealed-box encrypted_value and key_id.
4. Optionally delete a named secret through an explicitly destructive operation.

The connector should request GitHub App repository permission Secrets: write for write operations. Read/list support can use the corresponding metadata access supported by GitHub.

Why is this needed?

GitHub's REST API already supports GitHub App installation access tokens for repository Actions secrets. Without these connector operations, an agent that otherwise performs a deployment entirely through the GitHub App must fall back to a browser, local gh, or a separately managed token solely to populate project-scoped Actions secrets. That breaks connector-only workflows and encourages unnecessary credential proliferation.

Security requirements

• Never accept or return an unencrypted secret value in connector results.
• Prefer accepting only the LibSodium sealed-box ciphertext produced using the repository public key.
• Never echo request bodies, ciphertext, or credential material into summaries, errors, telemetry, or generated logs.
• Return only status, secret name, and GitHub metadata timestamps.
• Keep secret writes behind an explicit high-risk approval boundary.
• Scope each write to one explicitly named repository and secret.
• Do not silently broaden a selected-repository installation to other repositories.

Observed version

Codex GitHub plugin package: 0.1.8-2841cf9749ae.

I searched open and closed issues for “Actions secrets”, “repository secrets GitHub connector”, and “Secrets: write” before filing and did not find an existing request for this connector capability.