[auto] instructions: (more copilot code review instructions update)

Proposed by the [Update Instructions From PR Reviews](https://github.com/Azure/azure-dev/actions/runs/28546158988) workflow.

**Settings**
- Repo mined: `Azure/azure-dev`
- Range: since `2026-06-29T10:11:17Z` (last run)
- Branch: [`automated/update-instructions-from-pr-reviews` @ `30fa879`](https://github.com/Azure/azure-dev/tree/automated/update-instructions-from-pr-reviews)

**Stats**
- Signal ratio: ~25 genuine reviewer asks kept / ~35 dropped (bots, author acks, LGTM, <30 chars)
- Resolved PRs examined: 27 merged (complete review data for 16; 11 were rate-limited)

**PR comment themes**

- **Test coverage symmetry** — when one prompt path (e.g. subscription) has success/error/cancellation tests, add equivalent tests for the symmetric path (e.g. location); add serialisation round-trip assertions; test compound constraint combinations (step-alignment × max-capacity) — _[#8883](https://github.com/Azure/azure-dev/pull/8883), [#8874](https://github.com/Azure/azure-dev/pull/8874), [#8876](https://github.com/Azure/azure-dev/pull/8876)_

**Themes below promotion threshold (shown for visibility)**

The following themes each appeared in only 1 PR and did not meet the ≥2 PR / ≥2 reviewer or single-reviewer ≥3 threshold:
- `sort.*` → `slices.SortFunc` with `cmp.Compare` — _[#8879](https://github.com/Azure/azure-dev/pull/8879)_ (already in `AGENTS.md`; not promoted)
- `url.PathEscape` for HTTP path parameters — _[#8881](https://github.com/Azure/azure-dev/pull/8881)_
- Use existing helpers over manual flag registration — _[#8881](https://github.com/Azure/azure-dev/pull/8881)_
- Keep PR description in sync when commits change scope — _[#8896](https://github.com/Azure/azure-dev/pull/8896)_

> Generated by [Update Instructions From PR Reviews](https://github.com/Azure/azure-dev/actions/runs/28546158988) · 734.3 AIC · ⌖ 37.8 AIC · ⊞ 36.3K · [◷](https://github.com/search?q=repo%3AAzure%2Fazure-dev+%22gh-aw-workflow-id%3A+update-instructions-from-pr-reviews%22&type=pullrequests)

---

> [!NOTE]
> This was originally intended as a pull request, but GitHub Actions is not permitted to create or approve pull requests in this repository.
> The changes have been pushed to branch `automated/update-instructions-from-pr-reviews`.
>
> **[Click here to create the pull request](https://github.com/Azure/azure-dev/compare/main...automated/update-instructions-from-pr-reviews?expand=1&title=%5Bauto%5D%20instructions%3A%20add%20test%20coverage%20symmetry%20rule%20to%20Go%20review%20guidelines)**

To fix the permissions issue, go to **Settings** → **Actions** → **General** and enable **Allow GitHub Actions to create and approve pull requests**. See also: [gh-aw FAQ](https://github.github.com/gh-aw/reference/faq/#why-is-my-create-pull-request-workflow-failing-with-github-actions-is-not-permitted-to-create-or-approve-pull-requests)

Show patch preview (44 of 44 lines)

```diff
From 30fa879decffb3ba8540e23da9f0dd124e282463 Mon Sep 17 00:00:00 2001
From: "github-actions[bot]"
Date: Wed, 1 Jul 2026 20:49:07 +0000
Subject: [PATCH] instructions: add test coverage symmetry rule to Go review
guidelines
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Adds a new 'Test coverage symmetry' section to go.instructions.md, sourced
from recurring reviewer feedback across three PRs (#8883, #8874, #8876).

Rule covers three patterns flagged by reviewers:
- Symmetric prompt paths (subscription ↔ location: success/error/cancel)
- Serialisation round-trip tests (save + reload, not just write direction)
- Compound constraint interactions (step-alignment × max-capacity)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---
.github/instructions/go.instructions.md | 10 ++++++++++
1 file changed, 10 insertions(+)

diff --git a/.github/instructions/go.instructions.md b/.github/instructions/go.instructions.md
index c39dc04..1ff2589 100644
--- a/.github/instructions/go.instructions.md
+++ b/.github/instructions/go.instructions.md
@@ -31,3 +31,13 @@ all existing imports or declarations.

- When reviewing command input resolution, explicit CLI args and flags should win over defaults. Do not prompt the user toward a different default when they provided a valid new value; reserve prompts for ambiguous choices and preserve deterministic `--no-prompt` behavior for CI/scripts.
- When filtering AI models or quota data by location, keep location-specific usage data associated with only the models available in that location. Empty or unknown usage data from an unrelated location must not make a model eligible elsewhere; add regression coverage for cross-location quota cases.
+
+## Test coverage symmetry
+
+When tests exist for one side of a symmetric code path, flag the missing counterpart:
+
+- **Prompt paths**: If there is a test for subscription prompt (succes
... (truncated)
```