Vslokar sync release20250701 with main

.gitattributes

@@ -1,2 +1,4 @@
 # Use unix line endings always, even on Windows
 * text=auto eol=lf
+
+.github/workflows/*.lock.yml linguist-generated=true merge=ours

.github/.prettierignore

@@ -1,3 +1,3 @@
 # this file
 .prettierignore
 
@@ -8,10 +8,19 @@
 fixtures
 specification
 
+# auto-generated agentic workflow lock files
+workflows/*.lock.yml
+
 # unmanaged files and folders
 **/*instructions.md
 chatmodes
 ISSUE_TEMPLATE
 policies
 prompts
 PULL_REQUEST_TEMPLATE
+
+# lock files for agent workflows
+**/*.lock.yml
+
+# synced from external repos
+workflows/post-apiview.yml

.github/CODEOWNERS

@@ -15,6 +15,9 @@
 # PRLabel: %Cognitive Services
 /dev/cognitiveservices/data-plane/Language/ @assafi @rokulka @ChongTang @annatisch @heaths @deyaaeldeen @joseharriaga @minhanh-phan
 
+# PRLabel: %Foundry  %Client
+/specification/ai-foundry/data-plane/Foundry @johanste @trrwilson @glecaros @balapv @dargilco
+
 # PRLabel: %Analysis Services
 /specification/analysisservices/ @taiwu
 
@@ -62,7 +65,7 @@
 /specification/cdn/resource-manager/Microsoft.Cdn/EdgeActions/ @tundwed @anamikanupur
 
 # PRLabel: %Cognitive Services
-/specification/cognitiveservices/ @rkuthala @MattGal
+/specification/cognitiveservices/ @rkuthala @fmabroukmsft
 
 # PRLabel: %Cognitive Services - Form Recognizer
 /specification/cognitiveservices/data-plane/FormRecognizer/ @bojunehsu @nizi1127 @johanste
@@ -121,7 +124,7 @@
 /specification/deploymentmanager/ @netrock
 
 # PRLabel: %Device Registry
-/specification/deviceregistry/ @rohankhandelwal
+/specification/deviceregistry/ @atastrophic @siongithub @mryanlo @hmmorales @chgennar @sofia-geislinger @mfsmoot
 
 /specification/documentdb/ @dmakwana
 
@@ -304,12 +307,13 @@
 /scripts/           @weshaggard @mikeharder
 /specification/suppressions.yaml @weshaggard @mikeharder @benbp @raych1 @marygao @maririos @qiaozha
 /.github/CODEOWNERS @Azure/azure-sdk-eng
+/.github/skills     @Azure/azure-sdk-eng @chunyu3 @lirenhe @ArthurMa1978 @haolingdong-msft
 
 ## Copilot
 /.github/copilot-instructions.md @praveenkuttappan @maririos
 /.github/prompts/                @praveenkuttappan @maririos
 /.github/instructions/           @praveenkuttappan @maririos
-/.github/instructions/*arm*.md   @raosuhas
+/.github/instructions/*arm*.md   @praveenkuttappan @raosuhas @ravimeda @laxmankumar12
 /.github/chatmodes/              @praveenkuttappan @maririos
 
 # Add owners for notifications for specific pipelines

.github/actionlint.yaml

@@ -1,3 +1,9 @@
+self-hosted-runner:
+  labels:
+    - 1ES.Pool=azsdk-pool-github-runners
+    - azsdk-pool-github-test
+    - azsdk-pool-github-test-pr
+
 paths:
   .github/workflows/*.lock.yml:
     ignore:

.github/agents/hero-scenarios.agent.md

@@ -0,0 +1,9 @@
+---
+description: Expert in Azure API specifications who suggests hero scenarios — end-to-end developer workflows grounded in TypeSpec definitions that seed SDK samples, docs, and tests
+tools: ["read", "search", "bash"]
+---
+
+# Hero Scenarios Agent
+
+Before starting any work, read the detailed guidelines from
+`.github/prompts/hero-scenarios-guidelines.md` and follow them precisely.

.github/arm-leases/README.md

@@ -0,0 +1,97 @@
+# ARM Leases - Design Discussion Period
+
+## Overview
+
+This directory contains lease files that establish a time-limited design discussion period for Resource Providers (RPs) in the Azure REST API specifications repository. ARM leases provide a structured timeframe for Product Managers (PMs) and RP owners to collaborate on API design, review specifications.
+
+**Important**: Only Product Managers (PMs) are authorized to add lease.yaml files to this directory. Lease files should be added after conducting office hours discussions with RP owners. The reviewer field should contain the GitHub alias of a PM who has reviewed and approved the lease.
+
+## Code Owners and Contribution Guidelines
+
+This directory is intended to be governed via CODEOWNERS to ensure proper governance:
+
+- **Product Managers (PMs)**: Can add and modify `lease.yaml` files after office hours discussions with RP owners
+- **Engineers**: Can enhance and improve the validation workflow and related automation
+- **Approvals**: All changes should be reviewed and approved by designated code owners (PMs and engineers listed in CODEOWNERS, when configured)
+
+**Adding New PMs**: To grant a new PM access to add lease files, they should be added to the CODEOWNERS file for the `.github/arm-leases/` directory path when CODEOWNERS protection is configured.
+
+## Lease File Structure
+
+Each lease must be placed in the following directory structure:
+
+```
+.github/arm-leases/<orgName>/<rpNamespace>/[<serviceName> (optional)]/lease.yaml
+```
+
+### Path Requirements:
+
+- `<orgName>`: lowercase alphanumeric only (e.g., testservice, widgetservice)
+- `<rpNamespace>`: alphanumeric with dots, case-sensitive (e.g., Microsoft.TestRP, Azure.Widget)
+- `<serviceName>`: (optional) customer-facing service name within an RP (e.g., DiskRP, ComputeRP). Must not start with "stable" or "preview"
+
+### Lease File Format
+
+The `lease.yaml` file must follow this format:
+
+```yaml
+lease:
+  resource-provider: Microsoft.TestRP # Must match the rpNamespace folder name
+  startdate: 2026-01-07 # ISO 8601 format (YYYY-MM-DD)
+  duration: P180D # ISO 8601 duration (max 180 days, e.g., P180D, P90D, P5M)
+  reviewer: "@evanhissey" # GitHub alias of the approving reviewer
+```
+
+### Copy-Paste Template
+
+Create a file at `.github/arm-leases/<orgName>/<rpNamespace>/<serviceName>(optional)/lease.yaml` with the following content (replace the placeholder values):
+
+```yaml
+lease:
+  resource-provider: <rpNamespace>
+  startdate: <YYYY-MM-DD>
+  duration: P180D
+  reviewer: "@your-github-alias"
+```
+
+## Validation Rules
+
+All lease files are automatically validated with the following requirements:
+
+### 1. File Location
+
+- Only `lease.yaml` files are allowed in the `.github/arm-leases/` directory
+- Must follow the folder structure: `<orgName>/<rpNamespace>/[<serviceName> (optional)]/lease.yaml`
+
+### 2. Resource Provider Name
+
+- Must match the `<rpNamespace>` folder name exactly
+- Example: If folder is `Microsoft.TestRP`, then `resource-provider` must be `Microsoft.TestRP`
+
+### 3. Start Date
+
+- Must be in ISO 8601 format: `YYYY-MM-DD`
+- Must be a valid calendar date
+
+### 4. Duration
+
+- Required field that cannot be empty
+- Must be a valid ISO 8601 duration (e.g., `P180D`, `P90D`, `P5M`)
+- **Maximum duration is 180 days**
+- Supports day-based (`P90D`), month-based (`P5M`), and combined formats
+
+### 5. Reviewer
+
+- Required field that cannot be empty
+- Must be a GitHub alias starting with `@` (e.g., `@githubUsername`)
+
+## Troubleshooting
+
+If your PR check **"ARM Lease Validation"** is failing, review the error messages in the check output and fix the issues in your `lease.yaml` file. Common causes include:
+
+- **Invalid folder structure**: Ensure the path follows `<orgName>/<rpNamespace>/[<serviceName>]/lease.yaml` with lowercase org name
+- **Resource provider mismatch**: The `resource-provider` value must match the `<rpNamespace>` folder name exactly
+- **Past start date**: The `startdate` must be a valid date in `YYYY-MM-DD` format
+- **Invalid duration**: Use a valid ISO 8601 duration that does not exceed 180 days (e.g., `P180D`, `P90D`, `P5M`)
+- **Missing or empty fields**: All fields (`resource-provider`, `startdate`, `duration`, `reviewer`) are required
+- **Disallowed files**: Only `lease.yaml` and `README.md` files are permitted in `.github/arm-leases/`

.github/arm-leases/widget/Microsoft.Widget/Widget/lease.yaml

@@ -0,0 +1,5 @@
+lease:
+  resource-provider: Microsoft.Widget
+  startdate: "2026-04-15"
+  duration: P180D
+  reviewer: "@pshao25"

.github/aw/actions-lock.json

@@ -0,0 +1,34 @@
+{
+  "entries": {
+    "actions/checkout@v6.0.2": {
+      "repo": "actions/checkout",
+      "version": "v6.0.2",
+      "sha": "de0fac2e4500dabe0009e67214ff5f5447ce83dd"
+    },
+    "actions/github-script@v7": {
+      "repo": "actions/github-script",
+      "version": "v7",
+      "sha": "f28e40c7f34bde8b3046d885e986cb6290c5673b"
+    },
+    "actions/github-script@v8": {
+      "repo": "actions/github-script",
+      "version": "v8",
+      "sha": "ed597411d8f924073f98dfc5c65a23a2325f34cd"
+    },
+    "actions/github-script@v9": {
+      "repo": "actions/github-script",
+      "version": "v9",
+      "sha": "373c709c69115d41ff229c7e5df9f8788daa9553"
+    },
+    "actions/github-script@v9.0.0": {
+      "repo": "actions/github-script",
+      "version": "v9.0.0",
+      "sha": "d746ffe35508b1917358783b479e04febd2b8f71"
+    },
+    "github/gh-aw-actions/setup@v0.68.1": {
+      "repo": "github/gh-aw-actions/setup",
+      "version": "v0.68.1",
+      "sha": "2fe53acc038ba01c3bbdc767d4b25df31ca5bdfc"
+    }
+  }
+}

.github/copilot-instructions.md

@@ -1,14 +1,42 @@
+<!-- This file provides repository-level instructions for GitHub Copilot Chat.
+     It is automatically loaded when users interact with Copilot in this repo
+     (VS Code, GitHub.com, etc.) to guide responses for TypeSpec authoring,
+     SDK generation, API reviews, and other repo-specific workflows.
+
+     For GitHub Copilot Code Review (the feature that posts inline PR comments),
+     see copilot-review-instructions.md in this same directory.
+     Docs: https://docs.github.com/en/copilot/concepts/agents/code-review -->
+
 # New TypeSpec projects
 
 Refer to [new-typespec-project.instructions.md](./instructions/typespec-project.instructions.md) for detailed steps on:
- - how to create a new TypeSpec project.
- - converting a specification from swagger to typespec
- - troubleshooting tsp compile errors
+
+- how to create a new TypeSpec project.
+- converting a specification from swagger to typespec
+- troubleshooting tsp compile errors
 
 # Adding Language Emitters to Existing TypeSpec Projects
 
 Refer to [language-emitter.instructions.md](./instructions/language-emitter.instructions.md) for detailed steps on how to add language emitters to an existing `tspconfig.yaml` file in a TypeSpec project.
 
+# When to invoke the azure-typespec-author skill
+
+The `azure-typespec-author` skill **must** be invoked immediately in all modes (including plan mode) for any task that involves creating and modifying TypeSpec (`.tsp`) files except for `client.tsp` under the specification directory in this repository. This includes but is not limited to:
+
+- Adding, bumping, or promoting API versions (preview, stable)
+- Adding or modifying resources, operations, models, properties, or decorators
+- Changing visibility, constraints, breaking changes, LRO patterns, or suppressions
+- Defining or updating operationId, spread models, or extension resources
+- Converting Swagger to TypeSpec (post-conversion edits)
+
+**If you are unsure whether a user request involves TypeSpec authoring, ask the user to confirm before proceeding.** For example, if the request mentions API changes, versioning, resource definitions, or spec modifications but does not explicitly mention TypeSpec, prompt the user:
+
+> "This request may involve TypeSpec specification changes. Would you like me to use the azure-typespec-author skill to help with this?"
+
+If the user confirms, invoke the `azure-typespec-author` skill immediately. Do **not** build typespec authoring related plan or attempt to make `.tsp` file changes without invoking this skill first.
+
+**Do NOT use this skill for:** SDK generation, releasing SDK packages, `client.tsp` or code customization, or standalone MCP tool calls that do not involve editing `.tsp` files.
+
 # SDK generation from TypeSpec
 
 You must use Azure SDK MCP server to generate SDK from TypeSpec.
@@ -29,13 +57,14 @@
 
 # ARM Api Copilot Review Instructions
 
-Follow [armapi-review.instructions.md](./instructions/armapi-review.instructions.md) and [openapi-review.instructions.md](./instructions/openapi-review.instructions.md) for instructions to review ARM API specifications. Github Code review agent must prioritize these instructions over any other instruction files while performing code reviews.
+Follow [armapi-review.instructions.md](./instructions/armapi-review.instructions.md) and [openapi-review.instructions.md](./instructions/openapi-review.instructions.md) for instructions to review ARM API specifications. GitHub Code review agent must prioritize these instructions over any other instruction files while performing code reviews.
+
+Cross-cutting review rules (secret detection, property mutability, naming conventions, enum best practices, provisioning state, tracked resource lifecycle) are in the shared [azure-api-review skill](./skills/azure-api-review/SKILL.md). These are referenced by the instruction files and should not be duplicated elsewhere.
 
 # GitHub Actions Development
 
 Follow [github-actions.instructions.md](./instructions/github-actions.instructions.md) for instructions on developing and maintaining GitHub Actions code in this repository. This includes workflows, composite actions, and shared utilities.
 
-
 <!-- LINKS -->
 
 [contoso-widget-manager]: ../specification/contosowidgetmanager/Contoso.WidgetManager/
@@ -46,4 +75,4 @@
 [ci-fix]: ../documentation/ci-fix.md
 [url-type]: https://typespec.io/docs/language-basics/built-in-types#string-types
 [no-enum]: https://azure.github.io/typespec-azure/docs/libraries/azure-core/rules/no-enum
-[typespec-structure-guidelines]: ../documentation/typespec-structure-guidelines.md
+[typespec-structure-guidelines]: ../documentation/typespec-structure-guidelines.md