Point typespec-ts generator references to Azure/typespec-azure; drop legacy autorest promotion

Co-authored-by: jeremymeng <7583839+jeremymeng@users.noreply.github.com>

Author: Copilot

.github/PULL_REQUEST_TEMPLATE/pull_request_template.md

@@ -20,5 +20,5 @@
 
 ### Checklists
 - [ ] Added impacted package name to the issue description.
-- [ ] Does this PR need any fixes in the SDK Generator?** _(If so, create an Issue in the [Autorest/typescript](https://github.com/Azure/autorest.typescript) repository and link it here.)_
+- [ ] Does this PR need any fixes in the SDK Generator?** _(If so, create an Issue in the [typespec-ts](https://github.com/Azure/typespec-azure) repository and link it here.)_
 - [ ] Added a changelog (if necessary).

.github/instructions/reviewer/mgmt-sdk.instructions.md

@@ -28,7 +28,7 @@ Breaking changes are acceptable in mgmt SDKs with proper CHANGELOG documentation
 **Root-cause analysis:** Trace breaking changes to their source:
 - API version change in spec → expected, document in changelog
 - TypeSpec migration artifact → may be approved pattern, check with architects
-- Emitter/tooling bug → report to autorest.typescript
+- Emitter/tooling bug → report to typespec-ts
 - Do NOT flag cosmetic changes: `XxxOptionalParams→XxxOptions`, response wrapper removal
 
 **Changelog alignment:** Public API changes in `review/*.api.md` must be documented:
@@ -76,6 +76,6 @@ Flag patterns indicating spec problems:
 - Do NOT post the same comment on every file that has the same issue
 
 ## Issue Types
-**🔴 Tool Issue:** Generation bug → fix + report to [autorest.typescript](https://github.com/Azure/autorest.typescript/issues)
+**🔴 Tool Issue:** Generation bug → fix + report to [typespec-ts](https://github.com/Azure/typespec-azure/issues)
 **🔴 Design Issue:** API problem → `@clientName`/`@override` in spec repo
 **🔵 Suggestion:** Optional improvement

.github/prompts/mgmt-review-guidelines.md

@@ -80,7 +80,7 @@ However we should report the following cases:
 
 Spec Issue Comment: Review comments on public API often request changes to the generated API surface — renaming types, renaming properties, or changing property types to be more user-friendly. These changes are made in the spec repo's `client.tsp` using TypeSpec decorators (primarily `@clientName`). For these comments, do NOT request changes to generated code; instead, suggest updating the specification repository and triggering SDK regeneration.
 
-Tool Issue Comment: For issues that do not require spec changes, use the validation rules to detect tool issues. We can directly suggest changes in generated code and recommend reporting issues in the [generation tool repository](https://github.com/Azure/autorest.typescript/issues).
+Tool Issue Comment: For issues that do not require spec changes, use the validation rules to detect tool issues. We can directly suggest changes in generated code and recommend reporting issues in the [generation tool repository](https://github.com/Azure/typespec-azure/issues).
 
 ### Format
 
@@ -107,7 +107,7 @@ If the API surface and tool validation look good, say so explicitly in one sente
 > 🔴 **Tool Issue** — `CHANGELOG.md:42`
 > `Compared with 1.0.0-alpha.20260311.1:`.
 > We should not compare with alpha versions in `CHANGELOG.md`; this suggests a tooling bug.
-> **Fix:** Update the changelog to compare with the latest preview or stable version, and report the issue in the [generation tool repository](https://github.com/Azure/autorest.typescript/issues).
+> **Fix:** Update the changelog to compare with the latest preview or stable version, and report the issue in the [generation tool repository](https://github.com/Azure/typespec-azure/issues).
 
 ### Bad finding (too noisy — do NOT flag these)
 

.github/pull_request_template.md

@@ -21,5 +21,5 @@
 
 ### Checklists
 - [ ] Added impacted package name to the issue description
-- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so, create an Issue in the [Autorest/typescript](https://github.com/Azure/autorest.typescript) repository and link it here)_
+- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so, create an Issue in the [typespec-ts](https://github.com/Azure/typespec-azure) repository and link it here)_
 - [ ] Added a changelog (if necessary)

.github/workflows/mgmt-review.md

@@ -152,7 +152,7 @@ line using `create-pull-request-review-comment`:
 > 🔴 **Tool Issue** — `CHANGELOG.md:42`
 > `Compared with 1.0.0-alpha.20260311.1:`.
 > We should not compare with alpha versions in `CHANGELOG.md`; this suggests a tooling bug.
-> **Fix:** Update `CHANGELOG.md` to compare with the latest preview or stable version, and report the issue in the [generation tool repository](https://github.com/Azure/autorest.typescript/issues).
+> **Fix:** Update `CHANGELOG.md` to compare with the latest preview or stable version, and report the issue in the [generation tool repository](https://github.com/Azure/typespec-azure/issues).
 
 After all inline comments, **submit the review** using
 `submit-pull-request-review` with:

sdk/core/README.md

@@ -24,7 +24,7 @@ For more information, refer to https://github.com/Azure/azure-sdk-for-js/tree/ma
 
 ### ServiceClient
 
-Client libraries come in two flavors: authored and generated. Generated clients are produced by [AutoRest](#autorest-and-generated-clients) whereas authored clients are written by hand. Typically, authored clients wrap generated clients and extend them with custom API surface.
+Client libraries come in two flavors: authored and generated. Generated clients are produced by a [code generator](#code-generation-and-generated-clients) whereas authored clients are written by hand. Typically, authored clients wrap generated clients and extend them with custom API surface.
 
 `ServiceClient` is the base class of all generated clients. It builds on top of the HTTP Pipeline in order to make requests to services.
 
@@ -161,11 +161,9 @@ AzureLogger.log = (...args) => {
 };
 ```
 
-## AutoRest and Generated Clients
+## Code Generation and Generated Clients
 
-[AutoRest](https://github.com/Azure/autorest) is a generation tool for creating a client library using an [OpenAPI Specification](https://github.com/OAI/OpenAPI-Specification) (formerly known as "Swagger".)
-
-AutoRest is used in conjunction with the [autorest.typescript extension](https://github.com/Azure/autorest.typescript) to generate client libraries for JS/TS consumers. While the generated code tries as much as possible to fulfill the [TS design guidelines](https://azure.github.io/azure-sdk/typescript_introduction.html), it is often necessary to wrap the generated client classes in what are known as "convenience clients."
+Client libraries for JS/TS consumers are generated from [TypeSpec](https://typespec.io) specifications using the [`@azure-tools/typespec-ts`](https://github.com/Azure/typespec-azure/tree/main/packages/typespec-ts) emitter. While the generated code tries as much as possible to fulfill the [TS design guidelines](https://azure.github.io/azure-sdk/typescript_introduction.html), it is often necessary to wrap the generated client classes in what are known as "convenience clients."
 
 A convenience client extends the shape of a generated client in ways that make it more approachable to the consumer, such as simplifying the return shape of methods or adding helper functions for common operations.
 

sdk/core/core-client-rest/README.md

@@ -1,6 +1,6 @@
 # Azure Rest Core client library for JavaScript
 
-This library is primarily intended to be used in code generated by [AutoRest](https://github.com/Azure/Autorest) and [`autorest.typescript`](https://github.com/Azure/autorest.typescript). Specifically for rest level clients
+This library is primarily intended to be used in code generated by the [TypeSpec](https://typespec.io) [`@azure-tools/typespec-ts`](https://github.com/Azure/typespec-azure/tree/main/packages/typespec-ts) emitter. Specifically for rest level clients
 
 ## Getting started
 
@@ -27,7 +27,7 @@ Examples can be found in the `samples` folder.
 
 You can build and run the tests locally by executing `npm run test`. Explore the `test` folder to see advanced usage and behavior of the public classes.
 
-Learn more about [AutoRest](https://github.com/Azure/autorest) and the [autorest.typescript extension](https://github.com/Azure/autorest.typescript) for generating a compatible client on top of this package.
+Learn more about the [TypeSpec](https://typespec.io) [`@azure-tools/typespec-ts`](https://github.com/Azure/typespec-azure/tree/main/packages/typespec-ts) emitter for generating a compatible client on top of this package.
 
 ## Troubleshooting
 

sdk/core/core-client/README.md

@@ -1,6 +1,6 @@
 # Azure Core Service client library for JavaScript
 
-This library is primarily intended to be used in code generated by [AutoRest](https://github.com/Azure/Autorest) and [`autorest.typescript`](https://github.com/Azure/autorest.typescript).
+This library is primarily intended to be used in code generated by the [TypeSpec](https://typespec.io) [`@azure-tools/typespec-ts`](https://github.com/Azure/typespec-azure/tree/main/packages/typespec-ts) emitter.
 
 ## Getting started
 
@@ -39,7 +39,7 @@ The method `createSerializer` creates a `Serializer` that is used to do the bulk
 
 You can build and run the tests locally by executing `npm run test`. Explore the [test](https://github.com/Azure/azure-sdk-for-js/tree/main/sdk/core/core-client/test) folder to see advanced usage and behavior of the public classes.
 
-Learn more about [AutoRest](https://github.com/Azure/autorest) and the [autorest.typescript extension](https://github.com/Azure/autorest.typescript) for generating a compatible client on top of this package.
+Learn more about the [TypeSpec](https://typespec.io) [`@azure-tools/typespec-ts`](https://github.com/Azure/typespec-azure/tree/main/packages/typespec-ts) emitter for generating a compatible client on top of this package.
 
 ## Troubleshooting
 

sdk/core/core-lro/README.md

@@ -1,6 +1,6 @@
 # Azure Core LRO client library for JavaScript
 
-This is the default implementation of long running operations in Azure SDK JavaScript client libraries which work in both the browser and NodeJS. This library is primarily intended to be used in code generated by [AutoRest](https://github.com/Azure/Autorest) and [`autorest.typescript`](https://github.com/Azure/autorest.typescript).
+This is the default implementation of long running operations in Azure SDK JavaScript client libraries which work in both the browser and NodeJS. This library is primarily intended to be used in code generated by the [TypeSpec](https://typespec.io) [`@azure-tools/typespec-ts`](https://github.com/Azure/typespec-azure/tree/main/packages/typespec-ts) emitter.
 
 `@azure/core-lro` follows [The Azure SDK Design Guidelines for Long Running Operations](https://azure.github.io/azure-sdk/typescript_design.html#ts-lro)
 

sdk/core/core-rest-pipeline/README.md

@@ -1,6 +1,6 @@
 # Azure Core HTTP client library for JavaScript
 
-This is the core HTTP pipeline for Azure SDK JavaScript libraries which work in the browser and Node.js. This library is primarily intended to be used in code generated by [AutoRest](https://github.com/Azure/Autorest) and [`autorest.typescript`](https://github.com/Azure/autorest.typescript).
+This is the core HTTP pipeline for Azure SDK JavaScript libraries which work in the browser and Node.js. This library is primarily intended to be used in code generated by the [TypeSpec](https://typespec.io) [`@azure-tools/typespec-ts`](https://github.com/Azure/typespec-azure/tree/main/packages/typespec-ts) emitter.
 
 ## Getting started