[Follow-up to #49368] Recover incoming pyamqp windows and resolve changelogs

.chronus/changes/agentserver-conversation-engine-20261015.md

@@ -0,0 +1,7 @@
+---
+changeKind: feature
+packages:
+  - azure-ai-agentserver-invocations
+---
+
+Added a standalone `/voice_conversation_engine` WebSocket route to `VoiceAgentServerHost`, reusing the typed Bridge event relay alongside its unchanged `/invocations_ws` route without new constructor options. Generic `InvocationAgentServerHost` raw WebSocket handlers are unchanged.

.chronus/changes/agentserver-steering-current-input.md

@@ -0,0 +1,7 @@
+---
+changeKind: fix
+packages:
+  - sdk/agentserver/azure-ai-agentserver-core
+---
+
+Fixed queued steering turns being skipped by Responses ownership checks by atomically persisting the promoted turn as the current task input before execution. Attachment-backed inputs retain the existing input offload behavior.

.chronus/changes/agentserver-user-barge-in-20261019.md

@@ -0,0 +1,7 @@
+---
+changeKind: feature
+packages:
+  - azure-ai-agentserver-invocations
+---
+
+Aligned the experimental Voice caller-interruption contract with `user.barge_in`, `UserBargeIn`, `UserBargeInCallback`, and `VoiceAgentServerHost.on_user_barge_in`. Playback snapshots and application-owned cancellation/history are preserved. Voice Live senders must use the same event contract. Generic raw WebSocket handlers are unchanged.

.chronus/changes/azure-ai-projects-zero-temperature-tracing-2026-10-27.md

@@ -0,0 +1,7 @@
+---
+changeKind: fix
+packages:
+  - sdk/ai/azure-ai-projects
+---
+
+Fixed agent creation tracing to record the `gen_ai.request.temperature` and `gen_ai.request.top_p` span attributes when their value is `0`.

.chronus/changes/azure-identity-1-27-stable.md

@@ -0,0 +1,7 @@
+---
+changeKind: internal
+packages:
+  - sdk/identity/azure-identity
+---
+
+Prepare the 1.27.0 stable release metadata and document AKS identity binding configuration. The existing release entries remain in CHANGELOG.md.

.chronus/changes/pyamqp-incoming-window-recovery.md

@@ -0,0 +1,8 @@
+---
+changeKind: fix
+packages:
+  - sdk/servicebus/azure-servicebus
+  - sdk/eventhub/azure-eventhub
+---
+
+Fixed pyAMQP receive-window recovery after a link handler raises or is cancelled. Replenishment happens after delivery and only while the session is mapped, so closing sessions do not advertise new receive capacity.

.github/CODEOWNERS

@@ -301,10 +301,10 @@
 /sdk/loadtesting/azure-developer-loadtesting/    @mitsha-microsoft @ninallam @prativen
 
 # PRLabel: %Machine Learning
-/sdk/ml/    @achauhan-scc @jayesh-tanna @kingernupur
+/sdk/ml/    @achauhan-scc @jayesh-tanna @kingernupur @novaturient95 @viragjain611
 
 # PRLabel: %Machine Learning
-/sdk/ml/azure-ai-ml/    @achauhan-scc @arunsu @jayesh-tanna @jialiu103 @JustinFirsching @kingernupur @nick863 @NonStatic2014 @novaturient95 @PhaniShekhar @raduk @rtanase @sharma-riti @vivram @yuanzhuangyuanzhuang
+/sdk/ml/azure-ai-ml/    @achauhan-scc @arunsu @jayesh-tanna @jialiu103 @JustinFirsching @kingernupur @nick863 @NonStatic2014 @novaturient95 @PhaniShekhar @raduk @rtanase @sharma-riti @viragjain611 @vivram @yuanzhuangyuanzhuang
 
 # ServiceLabel: %Machine Learning
 # ServiceOwners: @Azure/azure-ml-sdk @azureml-github
@@ -752,10 +752,10 @@
 # ServiceOwners: @antcp @AzureAppServiceCLI
 
 # PRLabel: %Service Bus
-/sdk/servicebus/    @EldertGrootenboer @skarri-microsoft @j7nw4r @meetamitbhatia
+/sdk/servicebus/    @EldertGrootenboer @skarri-microsoft @j7nw4r @meetamitbhatia @pranz1996
 
 # ServiceLabel: %Service Bus
-# ServiceOwners: @EldertGrootenboer @skarri-microsoft @j7nw4r @meetamitbhatia
+# ServiceOwners: @EldertGrootenboer @skarri-microsoft @j7nw4r @meetamitbhatia @pranz1996
 
 # PRLabel: %Service Fabric
 /sdk/servicefabric/    @QingChenmsft @samedder
@@ -798,7 +798,7 @@
 # Management Libraries
 ####################
 
-/**/*mgmt*/                                                          @ChenxiJiang333 @msyyc
+/**/*mgmt*/                                                          @ChenxiJiang333 @msyyc @Azure/azure-arm-sdk-reviewers
 
 # ServiceLabel: %ARM %Service Attention
 # ServiceOwners:          @armleads-azure
@@ -859,10 +859,10 @@
 /eng/tools/emitter/                                                  @tadelesh @msyyc @iscai-msft @xirzec @lirenhe @ChenxiJiang333
 
 /pylintrc                                                            @JennyPng @l0lawrence @danieljurek @laiapat
-/sdk/**/ci.yml                                                       @JennyPng @l0lawrence @msyyc @xirzec @danieljurek
+/sdk/**/ci.yml                                                       @JennyPng @l0lawrence @msyyc @xirzec @danieljurek @Azure/azure-arm-sdk-reviewers
 
 # Add Johnathan Walker as code owner for Event Hubs SDK
 /sdk/eventhub/azure-eventhub/* @j7nw4r @meetamitbhatia @SwayGom @sagar0207
 
-# Add Johnathan Walker as code owner for Service Bus SDK
-/sdk/servicebus/azure-servicebus/* @j7nw4r @meetamitbhatia @SwayGom @sagar0207
+# Service Bus SDK team code owners
+/sdk/servicebus/azure-servicebus/* @j7nw4r @meetamitbhatia @SwayGom @sagar0207 @pranz1996 @EldertGrootenboer

.github/skills/azsdk-common-apiview-feedback-resolution/evals/eval.yaml

@@ -8,10 +8,10 @@ tags:
   area: azsdk-common-apiview-feedback-resolution
   type: ci-gate
 
-config:
+defaults:
   runs: 1
   timeout: "90s"
-  model: gpt-5.4
+  model: gpt-6.1-sol
   executor: copilot-sdk
 
 scoring:

.github/skills/azsdk-common-apiview-feedback-resolution/evals/trigger.eval.yaml

@@ -11,7 +11,7 @@ tags:
 defaults:
   runs: 1
   timeout: "90s"
-  model: gpt-5.4
+  model: gpt-6.1-sol
   executor: copilot-sdk
 
 scoring:

.github/skills/azsdk-common-generate-sdk-locally/evals/eval.yaml

@@ -8,10 +8,10 @@ tags:
   area: azsdk-common-generate-sdk-locally
   type: ci-gate
 
-config:
+defaults:
   runs: 1
   timeout: "90s"
-  model: gpt-5.4
+  model: gpt-6.1-sol
   executor: copilot-sdk
 
 scoring:

.github/skills/azsdk-common-generate-sdk-locally/evals/trigger.eval.yaml

@@ -20,6 +20,10 @@ scoring:
 stimuli:
   - name: trigger-generate-python-sdk-locally
     prompt: "Generate the Python SDK locally from my TypeSpec project at specification/compute/resource-manager/Microsoft.Compute/ComputeRP/tspconfig.yaml."
+    environment:
+      skills:
+        - ..
+        - ../../azsdk-common-sdk-breaking-change
     graders:
       - type: skill-invocation
         config:
@@ -28,7 +32,12 @@ stimuli:
   # Should NOT trigger
   - name: anti-trigger-mitigate-breaking-change
     prompt: "Fix the SDK breaking changes"
+    environment:
+      skills:
+        - ..
+        - ../../azsdk-common-sdk-breaking-change
     graders:
       - type: skill-invocation
         config:
+          required: ["azsdk-common-sdk-breaking-change"]
           disallowed: ["azsdk-common-generate-sdk-locally"]

.github/skills/azsdk-common-pipeline-analysis/evals/trigger.eval.yaml

@@ -11,7 +11,7 @@ tags:
 defaults:
   runs: 1
   timeout: "90s"
-  model: gpt-5.4
+  model: gpt-6.1-sol
   executor: copilot-sdk
 
 scoring:

.github/skills/azsdk-common-pipeline-fixer/evals/trigger.eval.yaml

@@ -11,11 +11,11 @@ tags:
 defaults:
   runs: 1
   # Stimuli with a resolvable build reference (URL or build ID) make the agent
-  # run the full analyze→fix→verify workflow (~90-180s under gpt-5.4),
+  # run the full analyze→fix→verify workflow (~90-180s under gpt-6.1-sol),
   # so the per-stimulus cap matches the Vally scenario evals (5m). Non-build-ref
   # routing prompts still complete in ~10-20s.
   timeout: "5m"
-  model: gpt-5.4
+  model: gpt-6.1-sol
   executor: copilot-sdk
 
 scoring:

.github/skills/azsdk-common-prepare-release-plan/evals/eval.yaml

@@ -8,10 +8,10 @@ tags:
   area: azsdk-common-prepare-release-plan
   type: ci-gate
 
-config:
+defaults:
   runs: 1
   timeout: "90s"
-  model: gpt-5.4
+  model: gpt-6.1-sol
   executor: copilot-sdk
 
 scoring:

.github/skills/azsdk-common-prepare-release-plan/evals/schedule-risk.eval.yaml

@@ -11,7 +11,7 @@ tags:
 defaults:
   runs: 1
   timeout: "120s"
-  model: gpt-5.4
+  model: gpt-6.1-sol
   executor: copilot-sdk
 
 scoring:
@@ -58,14 +58,16 @@ stimuli:
         config:
           substring: "https://github.com/Azure/azure-rest-api-specs/pull/12345"
 
+  # The new target stays future-proof; the mock's older plan supplies the warning.
   - name: create-relays-past-due-guidance
     environment:
       skills:
         - ..
     prompt: |
       Create a public preview release plan for TypeSpec project
       specification/contosowidgetmanager/Contoso.WidgetManager with target
-      release month June 2026, spec PR
+      release month next calendar month (resolve to an explicit month and year
+      using the current date), spec PR
       https://github.com/Azure/azure-rest-api-specs/pull/38387, service tree ID
       a7f2b8e4-9c1d-4a3e-b6f9-2d8e5a7c3b1f, and product tree ID
       f1a8c5d2-6e4b-4f7a-9c2d-8b5e1f3a6c9e. Use the Azure SDK MCP tools.

.github/skills/azsdk-common-prepare-release-plan/evals/trigger.eval.yaml

@@ -11,7 +11,7 @@ tags:
 defaults:
   runs: 1
   timeout: "90s"
-  model: gpt-5.4
+  model: gpt-6.1-sol
   executor: copilot-sdk
 
 scoring:

.github/skills/azsdk-common-sdk-breaking-change/evals/trigger.eval.yaml

@@ -20,6 +20,9 @@ scoring:
 stimuli:
   - name: trigger-detect-sdk-breaking-changes-for-service
     prompt: "Detect and mitigate SDK breaking changes for the service webpubsub"
+    environment:
+      skills:
+        - ..
     graders:
       - type: skill-invocation
         config:

.github/skills/azsdk-common-sdk-release/evals/eval.yaml

@@ -8,10 +8,10 @@ tags:
   area: azsdk-common-sdk-release
   type: ci-gate
 
-config:
+defaults:
   runs: 1
   timeout: "90s"
-  model: gpt-5.4
+  model: gpt-6.1-sol
   executor: copilot-sdk
 
 scoring:
@@ -60,12 +60,16 @@ stimuli:
 
   - name: basic-trigger
     prompt: "I need to release a new version of my Azure SDK package. Walk me through the process."
+    environment:
+      skills:
+        - ..
     graders:
       - type: output-contains
         config:
           substring: "release"
-    constraints:
-      expect_skills: ["azsdk-common-sdk-release"]
+      - type: skill-invocation
+        config:
+          required: ["azsdk-common-sdk-release"]
 
   - name: anti-trigger
     prompt: "How do I write unit tests for my Azure SDK client?"

.github/skills/azsdk-common-sdk-release/evals/trigger.eval.yaml

@@ -11,7 +11,7 @@ tags:
 defaults:
   runs: 1
   timeout: "90s"
-  model: gpt-5.4
+  model: gpt-6.1-sol
   executor: copilot-sdk
 
 scoring:

.github/skills/azsdk-python-mgmt-pr-triage/SKILL.md

@@ -0,0 +1,117 @@
+---
+name: azsdk-python-mgmt-pr-triage
+description: "Quickly list open Python management SDK AutoPRs for release rotators: automated review needs triggering, review already active, human review needed, changes after approval, and author follow-up after approval. Read-only; verify workflow activity before recommending a review trigger."
+---
+
+# Python management SDK PR triage
+
+Use this skill when a rotator asks for management SDK PR queues, PRs needing
+attention, or whether an automated management review is already active.
+Follow the [release rotation runbook](../../../doc/dev/mgmt/mgmt-release-rotation-runbook.md)
+for review and release decisions; this skill only helps find PRs.
+
+## Prerequisites
+
+- Python 3.10+ and authenticated GitHub CLI (`gh`) on PATH.
+- Read access to repository contents, pull requests, and Actions runs.
+- Read access to CODEOWNERS team membership when team owners apply, except
+  the optional `Azure/azure-arm-sdk-reviewers` lookup described below.
+
+No SDK installation or local repository checkout is needed to run the bundled
+script. In Copilot, ask: **"Use azsdk-python-mgmt-pr-triage to show management SDK
+PRs needing attention."** If skills are not available in the current client,
+run the script directly.
+
+## Run
+
+```powershell
+python <skill-dir>\scripts\triage_prs.py
+```
+
+Optional filters:
+
+```powershell
+python <skill-dir>\scripts\triage_prs.py --package azure-mgmt-iothub
+python <skill-dir>\scripts\triage_prs.py --version 1.0.0b1
+python <skill-dir>\scripts\triage_prs.py --repo Azure/azure-sdk-for-python --limit 500
+```
+
+Defaults: `Azure/azure-sdk-for-python`, at most 500 initially listed PRs, open
+non-draft titles starting with `[AutoPR azure-mgmt-`. Include first releases.
+Package and version filters are exact matches. Unknown versions are shown as
+`unknown`; a version-filtered scan warns when it cannot classify a version.
+
+## Report
+
+Return the script's Markdown report and any diagnostic warnings, without
+reinterpreting evidence as permission to approve or release. Preserve these
+section numbers, omit empty sections, and sort each queue by most recently updated:
+
+1. **Automated review needs triggering**: the bot review is missing or its
+   linked run targets an older head, and no active review was detected.
+   Recommend adding `mgmt-review-needed`, or removing/reapplying it when present.
+2. **Automated review active**: link queued, requested, waiting, pending, or
+   in-progress management review runs. Wait; do not request a duplicate,
+   including when the active run targets an older revision.
+3. **Human review needed**: no effective approval from applicable CODEOWNERS,
+   or GitHub's review decision still requires review/changes.
+4. **Changes after approval**: the current head differs from the effective
+   approved commit. Inspect the changes and current review requirements;
+   re-approve only if required.
+5. **Author follow-up after approval**: link newer PR-author issue comments,
+   inline review comments, or submitted review bodies. Read and respond or
+   route the request; a comment does not itself require re-approval.
+
+Entries include PR link, package/version, reason, and next action. A PR may
+appear in multiple queues. CODEOWNERS use GitHub file precedence and the last
+matching rule for changed package files at the PR's base commit. Resolve team
+members and use each maintainer's latest opinionated review; a later ordinary
+comment does not invalidate an approval.
+
+If the `Azure/azure-arm-sdk-reviewers` membership lookup returns HTTP 403,
+silently skip that team lookup and cache the failure for the scan. Keep
+approvals from individually named CODEOWNERS and other readable teams. Use
+GitHub's review decision for the human-review queue when a team-only approval
+cannot be verified; do not claim an approval is missing solely because this
+team is unreadable. Changes and author follow-ups after a team-only approval
+cannot be classified unless the approver is also a verified maintainer.
+Other team errors and API failures still produce verification warnings.
+
+## Evidence and limitations
+
+- Query the management review workflow, not generic CI. Use its run's explicit
+  `pull_requests` associations, not timestamps, title guesses, or `head_sha`
+  alone (`pull_request_target` can use a base revision).
+- Fetch workflow runs with status-independent pagination and filter completed
+  runs locally, so transitions between active statuses do not hide a run.
+- Compare the initial listing's `updatedAt` with the first PR read, then check
+  for changes again after collecting evidence. Reject changed snapshots rather
+  than combine an old review decision with newer reviews.
+- Active runs without a PR association make activity verification incomplete.
+  Show **Review activity unknown** and the run links; never recommend
+  retriggering while activity cannot be verified.
+- Identify the latest review comment by the GitHub Actions account, review
+  heading, and workflow marker/footer. Check the linked run's workflow identity
+  and associated PR head for freshness. An absent/unusable run link or head
+  makes freshness unknown, not outdated. Incomplete bot results remain for
+  human review; do not automatically rerun a current partial result.
+- Activity is a point-in-time observation, not a lock. Follow the run link and
+  confirm no review is active immediately before changing a label.
+- Unknown ownership, inaccessible APIs, scan limits, changed PRs during
+  collection, and missing version metadata produce explicit verification
+  warnings. A partial scan must not claim that no PRs need attention.
+- Exit code `0` means collection completed without verification warnings;
+  `2` means the report is partial/unverified or collection failed. Read the
+  report and stderr rather than treating an incomplete scan as an empty queue.
+
+Never change labels, request reviews, post comments, approve, merge, or publish.
+Holds, CI, release plans, release intent, and post-merge publication remain
+manual runbook checks. Absence from a queue is not proof of release readiness.
+
+## Development
+
+Run fixture-based tests without GitHub access:
+
+```powershell
+python -m unittest discover -s .github\skills\azsdk-python-mgmt-pr-triage\tests -v
+```