agent-glovebox: Command for GitHub Copilot

You hold no GitHub write credential in this run. git push, gh pr create, gh pr close and gh issue all fail, because the write token lives only in a later job that you never touch.

Commit your work locally as usual — git checkout -b, git add, git commit need no credential — then declare what you want published. Your job uploads your commits and this directory when you finish, and the workflow's publish job performs that list under its own token. It is a fixed list of actions, and the workflow pins each one's target: which base branch a pull request opens against, which tracking issue the issue verb rewrites, which branch you may push, which pull requests you may close, and which issues, if any, you may comment on. .github/scripts/agent_publish.py is the whole list.

Write one JSON object to $RUNNER_TEMP/agent-publish/manifest.json. Create the directory first. Every key is optional; an unknown key fails the publish.

{
  "pull_request": {
    "title": "fix(security): weekly vulnerability remediation",
    "body_file": "pr-body.md",
    "labels": ["security-scan"]
  },
  "close_pull_requests": [412, 413],
  "issue": {
    "title": "the scanner reports a new advisory with no upstream fix",
    "body_file": "issue-body.md",
    "labels": ["security-scan"]
  }
}

Shipping nothing is the whole manifest instead, never a key beside the others:

{ "nothing_to_publish": "every alert was already covered by an open triage PR" }

What each key does:

• pull_request — pushes the branch you are on and opens its pull request. Create a NEW branch first, named with the prefix your task prompt gives: the publish refuses the base branch, a name outside that prefix, and a branch that already exists. The one exception is a branch the workflow pinned for this run: that one is pushed as a fast-forward, and its open pull request gets your title and body. The publish also refuses any commit that changes a file under .github/workflows/ or .github/actions/. Commit everything too — the upload refuses a worktree with uncommitted changes to tracked files, because no pull request would carry them. labels may not include a label that asks for a merge (approved, force-queue, only-queue, red-fix) in any letter case, nor a label holding a comma; the publish refuses either.
• close_pull_requests — closes each number with the comment Superseded by #<your PR>. Needs pull_request in the same manifest. The step refuses a number whose head branch is outside what this job may subsume.
• issue — rewrites this job's own tracking issue, or opens it. The workflow names that issue with a hidden marker, and the step adds the marker itself; you cannot select a different issue. labels apply only when it opens a new one.
• issue_comments — one comment per entry, as [{ "number": 907, "body_file": "comment.md" }]. Use it only when your task prompt says you may comment on issues: the step refuses every number outside the set the workflow staged for this run, and most workflows stage none.
• nothing_to_publish — your reason for shipping nothing. It must be the manifest's only key, and you must have made no commit.

Each body_file holds the finished text, written by you into $RUNNER_TEMP/agent-publish/, and names it relative to that directory: pr-body.md, never an absolute path. Only that directory reaches the publish job, so it refuses an empty file and a path outside it.

Any commit you make must be published by a pull_request in this manifest. A commit with no manifest, a commit beside nothing_to_publish, and a commit whose manifest declares only an issue are all errors — each would drop your work, so the step reds instead.