Add spector case for extensible enum with special word member names

[Copilot]

• Add extensible enum (union) with 33 special word member names to special-words/main.tsp
• Simplify to single @put operation per reviewer feedback
• Add ExtensibleString return type so mock API echoes back the sent value
• Simplify return type to putExtensibleStringValue(@body body: ExtensibleString): ExtensibleString;
• Add handler to dynamically extract request body and echo it back in response
• Remove explicit contentType headers (default application/json is sufficient)
• Remove redundant @doc decorators from union definition for consistency with rest of file
• Rename union Enum to union ExtensibleString to avoid blocking actual enum tests
• Rename interface Enums to ExtensibleStrings, route /enums to /extensible-strings, and operation putEnumValue to putExtensibleStringValue
• Regenerate spec-summary
• Add chronus changeset for @typespec/http-specs
• Build validated (61 scenarios pass)
• Format, code review, and security scan clean

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[msyyc]

@copilot check all changes of the PR to make sure they are consistent.

[Copilot]

@copilot check all changes of the PR to make sure they are consistent.

Reviewed all changes for consistency in f70bb68. Found and fixed one issue: the union Enum definition had redundant @doc decorators on the union itself and on every member, which was inconsistent with the rest of the file (no other types use @doc). Removed them, keeping just the JSDoc comment. All three changed files are now consistent:

• main.tsp: Union uses JSDoc only (matching existing models/operations), single @put op with Enum input/output, no explicit contentType
• mockapi.ts: Handler echoes req.body back in response, matching the TSP contract
• spec-summary.md: Auto-generated, matches the scenario definition

Build passes with 61 valid scenarios.

[msyyc]

@copilot fix ci error:

Run pnpm chronus verify --since main
There is undocummented changes. Run chronus add to add a changeset.

The following packages have changes but are not documented.
 - @typespec/http-specs

[Copilot]

@copilot fix ci error:

Run pnpm chronus verify --since main

...

Added the chronus changeset for @typespec/http-specs in 9b6d78f.

[Copilot]

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• telemetry.astro.build
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /home/REDACTED/work/typespec/typespec/website/node_modules/.bin/../astro/astro.js build sh .0/b�� ebsite/src/conte--llmstxt .json /.bin/sh ture 7b6e072b8b5df199/home/REDACTED/work/typespec/typespec/packages/http-specs/node_modules�� in/tsp sh pec/�� ../../website/src/content/docs/d--typekits node _modules/pnpm/dist/node-gyp-bin/sh /library-linter node tsconfig.build.j/home/REDACTED/work/typespec/typespec/packages/http-server-js/node_modules/.bin/..hint modules/@npmcli/doc node (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

[msyyc]

Hi @timotheeguerin pls help take a review, thanks!