Merge branch 'main' into copilot/fix-tagmetadata-generation

Author: markcowl

.chronus/changes/examples-multi-response-2026-3-28-14-36-55.md

@@ -0,0 +1,8 @@
+---
+# Change versionKind to one of: internal, fix, dependencies, feature, deprecation, breaking
+changeKind: feature
+packages:
+  - "@typespec/http"
+---
+
+[API] Operation returning a union of types without status code or content type will be treated as a single response

.chronus/changes/examples-multi-response-2026-3-29-16-25-39.md

@@ -0,0 +1,8 @@
+---
+# Change versionKind to one of: internal, fix, dependencies, feature, deprecation, breaking
+changeKind: fix
+packages:
+  - "@typespec/openapi3"
+---
+
+Fix examples when operation return type have union of response mapping to same status code

.chronus/changes/feature-http-client-js-playground-2026-2-26-18-19-36.md

@@ -0,0 +1,8 @@
+---
+# Change versionKind to one of: internal, fix, dependencies, feature, deprecation, breaking
+changeKind: feature
+packages:
+  - "@typespec/bundler"
+---
+
+Add support for alloy based emitters

.chronus/changes/fix-compiler-server-null-crashes-2026-4-30-7-30-0.md

@@ -0,0 +1,7 @@
+---
+changeKind: fix
+packages:
+  - "@typespec/compiler"
+---
+
+Fix server crashes caused by undefined symbol declarations: add null checks for `getSymNode()` in hover, completion, type-details, and type-signature handlers, and use fallback name for empty DocumentSymbol names

.chronus/changes/fix-implicit-optionality-no-op-is-warn-2026-4-5-13-43-12.md

@@ -0,0 +1,7 @@
+---
+changeKind: internal
+packages:
+  - "@typespec/http"
+---
+
+Do not emit deprecated-implicit-optionality on op is

.chronus/changes/fix-keep-setup-py-coercion-2026-4-30-5-30-0.md

@@ -0,0 +1,7 @@
+---
+changeKind: internal
+packages:
+  - "@typespec/http-client-python"
+---
+
+Fix `run_batch.py` passing string `"true"`/`"false"` values to pygen, which caused `keep-setup-py="false"` to be treated as truthy and generate `setup.py` instead of `pyproject.toml` for all regenerated test packages.

.chronus/changes/fix-lsp-unhandled-exceptions-2026-4-30-7-30-0.md

@@ -0,0 +1,7 @@
+---
+changeKind: fix
+packages:
+  - typespec-vscode
+---
+
+Handle unhandled exceptions in VS Code extension: add custom error handler for server crashes with restart notification, wrap commands with graceful exception handling, and add null guards to prevent extension host errors when LSP client is unavailable

.chronus/changes/fix-tspd-linter-rule-link-2026-4-27-8-54-0.md

@@ -0,0 +1,7 @@
+---
+changeKind: fix
+packages:
+  - "@typespec/tspd"
+---
+
+Fix broken (404) links to linter rule pages on auto-generated linter reference pages. The links no longer drop the website base path.

.chronus/changes/linter-rule-options-2026-3-13-12-45-46.md

@@ -0,0 +1,42 @@
+---
+changeKind: feature
+packages:
+  - "@typespec/compiler"
+---
+
+Add support for configurable options on linter rules
+
+Linter rules can now define typed options with defaults using `defaultOptions`, and users can pass options when enabling rules in `tspconfig.yaml` or rulesets.
+
+**Defining a rule with options:**
+
+```ts
+const myRule = createRule({
+  name: "no-model-with-name",
+  severity: "warning",
+  description: "Bans models with a specific name",
+  messages: { default: "This model name is not allowed" },
+  defaultOptions: { bannedName: "Foo" },
+  create(context) {
+    return {
+      model: (target) => {
+        if (target.name === context.options.bannedName) {
+          context.reportDiagnostic({ target });
+        }
+      },
+    };
+  },
+});
+```
+
+**Configuring options in `tspconfig.yaml`:**
+
+```yaml
+linter:
+  enable:
+    # Enable with default options
+    "@typespec/my-lib/no-model-with-name": true
+    # Enable with custom options
+    "@typespec/my-lib/no-model-with-name":
+      bannedName: "Bar"
+```

.chronus/changes/protobuf-optional-2026-4-5-12-8-31.md

@@ -0,0 +1,11 @@
+---
+changeKind: feature
+packages:
+  - "@typespec/protobuf"
+---
+
+Map TypeSpec optionality (`?`) to protobuf `optional` where appropriate.
+
+- `optional` is applied to fields with protobuf scalar types to set explicit presence.
+- `optional` is _not_ applied to fields with message types, because they _always_ have explicit presence.
+- Attempting to convert a TypeSpec optional property where the type is an array or `Protobuf.Map` instance produces a warning, because protobuf cannot differentiate between "empty" and "unset" `repeated`/`map`-typed fields.