From 1998e17c70bd957afa9810936eab4fbb5fdd42dc Mon Sep 17 00:00:00 2001 From: Aditya Pujara <59631311+a0x1ab@users.noreply.github.com> Date: Wed, 23 Sep 2026 14:09:08 +0930 Subject: [PATCH] Revert repository-level X Engineering Agent policy The central service has returned to the Foundry Copilot SDK and Squad architecture, where repository target routing is enforced by the trusted runtime rather than this native-agent policy. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: da851f42-f383-454b-83ea-398b7c4c972a --- .x/fixer.md | 16 ++++------------ 1 file changed, 4 insertions(+), 12 deletions(-) diff --git a/.x/fixer.md b/.x/fixer.md index c02af2b2bfc..819b09e8bd0 100644 --- a/.x/fixer.md +++ b/.x/fixer.md @@ -22,18 +22,10 @@ for a due single follow-up. Stop after either write. For sufficient reports, call the repository-owned `infer_target_for_repo` custom skill with `repo_full_name="Azure/azure-cli"`, the sanitized text, and an empty `pr_files` list. It resolves only against the configured live module -and extension roots, so `unknown` does not by itself reject a repository-level -issue. Verify a resolved target against current repository structure. When no -module or extension is resolved, continue only when the issue identifies -existing handwritten repository-level paths or a subsystem such as packaging, -bootstrap, or shared CLI infrastructure. Verify the exact paths in the current -repository, record them in the analysis, and require a reported reproducing -`az ...` invocation for the title. Otherwise request the missing path or -command evidence and stop. - -- A core module or an unambiguous repository-level target remains in - `Azure/azure-cli`. For repository-level work, use the verified subsystem as - the component and the reported reproducing command. Build the exact +and extension roots. Verify the returned target against current repository +structure. + +- A core module remains in `Azure/azure-cli`. Build the exact `[Component] Fix #N: \`az ...\`: Summary` title with `pr_title_for`, include `pr_format_guidance`, post the evidence-based bug analysis, then start the configured Copilot fork task.