Clarify Copilot authorization for GitHub publication

[vitek-karas]

Motivation

The existing Agent Merge instructions tell Copilot to "open or update" a Known Build Error issue when a CI failure is unrelated to the PR. The create-kbe skill repeats that instruction without requiring publication approval, while the shared KBE guidance leaves confirmation to the caller.

This guidance was added to make Agent Merge useful by recording legitimate unrelated CI failures instead of repeatedly retriggering CI. Preserve that intentional automation, while making clear that an ordinary coding task does not grant permission to create additional issues or post comments.

Unexpected issue-filing behavior was reported in #134870. Assigning a PR or granting write access alone should not authorize additional publications, and an AI disclosure is not a substitute for authorization.

Changes

Define a consistent publication-authorization rule for repository instructions and the affected skills:

• For incidental issue creation, issue updates, and comments, require explicit user authorization. Without it, prepare a local draft and ask before publishing; if asking is unavailable, leave the draft and report the pending decision.
• Accept advance permission in an interactive prompt. Authorization to compose and publish a specified artifact is sufficient within its scope, without another confirmation or separate approval of generated text.
• Preserve intentional publication by configured agentic workflows through their declared outputs and limits, and by explicitly requested or enabled specialized workflows through their documented publication contracts. Merely loading a skill or reading a workflow does not grant that authority. Draft-only, dry-run, and review-before-publication requests take precedence.
• Define Agent Merge's publication scope in its existing repository-instruction section. Enabling it authorizes review replies on the current PR when review handling is authorized, and creation or updates of eligible Known Build Error issues in dotnet/runtime for unrelated failures on that PR when CI fixing is authorized. These operations do not require another approval prompt; unrelated publication remains unauthorized.

Make publication depend on scoped authorization, with local drafts when authorization is missing. Align the KBE, shared KBE, PR failure-scan, and mobile reporting instructions so they honor the caller's authorized outputs. Keep the Agent Merge no-rerun rule and KBE eligibility requirements intact. Clarify that a user-requested breaking-change documentation task includes its source-PR documentation comment, while creating the docs issue remains a separate publication decision.

These are Markdown guidance changes only. Runtime code, KBE eligibility rules, and configured workflow outputs and limits are unchanged.

Note

This PR and its description were prepared with GitHub Copilot assistance.

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).
15 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

[PureWeen]

Two authorization gaps where the new advance-permission wording removes a pause that previously caught uncertain content. Details are inline.

Note

This review was generated by GitHub Copilot.