Merge branch 'main' into copilot/typespec-ts-fail-to-build-multi-client-packages

Author: kazrael2119

.chronus/changes/fix-mts-mjs-license-header-2026-07-23-11-08-30.md

@@ -0,0 +1,8 @@
+---
+# Change versionKind to one of: internal, fix, dependencies, feature, deprecation, breaking
+changeKind: fix
+packages:
+  - "@azure-tools/typespec-ts"
+---
+
+Add the license header to emitted `.mts`/`.mjs` files (e.g. the browser and react-native static helper variants such as `get-binary-stream-response-browser.mts`), which were previously skipped because the source-code detection only matched `.ts`/`.js` extensions.

.chronus/changes/fix-operation-name-conflict-multi-service-2026-07-22-15-15-00.md

@@ -0,0 +1,7 @@
+---
+changeKind: fix
+packages:
+  - "@azure-tools/typespec-client-generator-core"
+---
+
+Detect operation name conflicts when multiple services are combined into one client via `@client({service: [ServiceA, ServiceB]})`. Previously only same-namespace duplicates were caught; now cross-service operation name collisions emit the existing `duplicate-client-name` diagnostic.

.chronus/changes/fix-typespec-go-spector-coverage-path-2026-07-23-23-37-00.md

@@ -0,0 +1,7 @@
+---
+changeKind: internal
+packages:
+  - "@azure-tools/typespec-go"
+---
+
+Write the typespec-go spector coverage report to the shared `@azure-tools/azure-http-specs/spec-coverage.json` location so the CI coverage upload uses the same convention as other emitters.

.chronus/changes/go-module-identity-2026-6-22-17-4-52.md

@@ -0,0 +1,7 @@
+---
+changeKind: feature
+packages:
+  - "@azure-tools/typespec-go"
+---
+
+During SDK generation, if a go.mod file exists, its module identity is used as the source of truth, including any major version suffix. This alleviates the need to update tspconfig.yaml whenever a new major version is required.

.chronus/changes/standardize-spector-test-selection-2026-07-22-13-10-00.md

@@ -0,0 +1,10 @@
+---
+changeKind: internal
+packages:
+  - "@azure-tools/typespec-go"
+  - "@azure-tools/typespec-python"
+  - "@azure-tools/typespec-ts"
+  - "@azure-tools/typespec-java"
+---
+
+Introduce a standardized opt-in `spector.config.yaml` for selecting which spector tests each emitter generates, loaded by the shared `@azure-tools/spector-runner` package (with a JSON schema generated from TypeSpec). Wire it into the Go (`tspcompile.js`), Python (`regenerate.ts`), TypeScript (`gen-spector.js`) and Java (`Generate.ps1`) regenerators. No change to the set of generated specs.

.chronus/changes/tcgc-diagnostic-docs-2026-07-16-00-00-00.md

@@ -0,0 +1,7 @@
+---
+changeKind: internal
+packages:
+  - "@azure-tools/typespec-client-generator-core"
+---
+
+Add reference documentation for TCGC diagnostics so each diagnostic gets an auto-generated reference page.

.devcontainer/Dockerfile

@@ -1,6 +1,15 @@
-FROM mcr.microsoft.com/devcontainers/javascript-node:20
+FROM mcr.microsoft.com/devcontainers/base:ubuntu
 
-RUN corepack enable pnpm \
-  && echo 'alias pnpm="corepack pnpm"' >> /home/node/.bash_aliases
+# Install mise for toolchain management (node, pnpm, python, go, java, etc.)
+RUN curl https://mise.run | MISE_INSTALL_PATH=/usr/local/bin/mise sh \
+  && echo 'eval "$(/usr/local/bin/mise activate bash)"' >> /home/vscode/.bashrc \
+  && echo 'eval "$(/usr/local/bin/mise activate zsh)"' >> /home/vscode/.zshrc
+
+# Pre-install all toolchain versions pinned in mise.toml/mise.lock into the image
+COPY mise.toml mise.lock /tmp/mise-setup/
+RUN chown -R vscode:vscode /tmp/mise-setup
+USER vscode
+RUN cd /tmp/mise-setup && mise trust && mise install
+USER root
 
 RUN git config --global submodule.recurse true

.devcontainer/devcontainer.json

@@ -1,9 +1,10 @@
 {
   "name": "Standard",
   "build": {
-    "dockerfile": "Dockerfile"
+    "dockerfile": "Dockerfile",
+    "context": ".."
   },
-  "postCreateCommand": "git submodule update --recursive --init",
+  "postCreateCommand": "git submodule update --recursive --init && mise trust && pnpm install",
   "customizations": {
     // Configure properties specific to VS Code.
     "vscode": {

.github/CODEOWNERS

@@ -1,11 +1,11 @@
-* @bterlson @markcowl @timotheeguerin
+* @markcowl @timotheeguerin @xirzec
 
-/packages/typespec-client-generator-core @lmazuel @m-nash @iscai-msft @srnagar @joheredi
+/packages/typespec-client-generator-core @lmazuel @m-nash @iscai-msft
 /packages/typespec-ts @maorleger @qiaozha @MaryGao @JialinHuang803 @xirzec
-/packages/azure-http-specs/specs/ @iscai-msft @lmazuel @m-nash @joheredi @srnagar @weidongxu-microsoft @tadelesh @jhendrixMSFT 
+/packages/azure-http-specs/specs/ @iscai-msft @lmazuel @m-nash @weidongxu-microsoft @tadelesh @jhendrixMSFT @xirzec
 
-/docs/howtos/DataPlane*/ @lmazuel @m-nash @iscai-msft @srnagar @joheredi
+/docs/howtos/DataPlane*/ @lmazuel @m-nash @iscai-msft @xirzec
 
-/packages/typespec-python @iscai-msft @msyyc @tadelesh @l0lawrence @ChenxiJiang333 @kashifkhan
-/packages/typespec-java @weidongxu-microsoft @haolingdong-msft @XiaofeiCao @alzimmermsft
+/packages/typespec-python @iscai-msft @msyyc @tadelesh @l0lawrence @ChenxiJiang333 @kashifkhan @xirzec
+/packages/typespec-java @weidongxu-microsoft @haolingdong-msft @XiaofeiCao @alzimmermsft @jsquire
 /packages/typespec-go @jhendrixMSFT @HeathS @xirzec @lirenhe

.github/copilot-instructions.md

@@ -2,10 +2,21 @@
 
 This document serves as an index to task-specific instructions for GitHub Copilot. Each task has its own detailed instructions file in the `.github/prompts` directory.
 
+## Development Environment (mise)
+
+This repo pins its development tools with [mise](https://mise.jdx.dev) via `mise.toml` and `mise.lock`: Node.js, pnpm, Python, uv, Go, Java, and Maven.
+
+- Check for mise first (`mise --version`). If it is installed, prefer the mise-managed tools over whatever happens to be on `PATH` — a globally installed `node`/`pnpm`/`python` is often the wrong version or misconfigured.
+- A fresh clone or git worktree is untrusted, so mise refuses to load its config. If you see `Config files in ... are not trusted`, run `mise trust` from the repo root, then continue.
+- Run `mise install` from the repo root to install the pinned versions. It is a fast no-op (`mise all tools are installed`) when everything is already present, so it is safe to run before other setup.
+- Non-interactive shells (including the ones agents run commands in) usually do not have mise activated, so the pinned tools are not on `PATH`. Prefix commands with `mise exec --` (for example `mise exec -- pnpm install`, `mise exec -- pnpm build`, `mise exec -- python --version`). Without it, commands can fail with confusing errors such as `The packageManager dependency "pnpm@..." in pnpm-lock.yaml must use a registry package path`.
+- Use `mise ls --current` to confirm which tool versions are active for this repo.
+- If mise is not installed, fall back to the tools on `PATH`, but match the versions in `mise.toml` and the `packageManager` field in `package.json`.
+
 ## Install and Build
 
 - Packages are located in the `packages` folder
-- Use `pnpm` as the package manager
+- Use `pnpm` as the package manager (prefix with `mise exec --` when mise is installed but not activated in the shell)
 - Use `pnpm install` to install dependencies
 - Use `pnpm build` to build every package
 - Use `pnpm -r --filter "<pkgName>..." build` to build to a specific package `<pkgName>`
@@ -27,6 +38,7 @@ This document serves as an index to task-specific instructions for GitHub Copilo
 
 - When creating worktrees or branches for new work, base them off the main Azure fork's `main` branch (Azure/typespec-azure). Depending on the user's local git remote setup, this may be called `upstream` or `origin`.
 - When creating worktrees (which clone the repo), always clone recursively with `--recurse-submodules` and run `git submodule update --init` if the `core/` submodule is missing or not at the correct commit. See [CONTRIBUTING.md - Cloning recursively](https://github.com/Azure/typespec-azure/blob/main/CONTRIBUTING.md#cloning-recursively) for details.
+- A new clone or worktree also needs `mise trust` (and `mise install` if tools are missing) before `pnpm` and other tools will work — see [Development Environment (mise)](#development-environment-mise).
 - When pushing changes and creating pull requests, push to your personal fork and open PRs against the main Azure fork's `main` branch.
 
 ## Available Task Instructions