Files
f4e7cd96f2 Migrate cspell config to per-service files ***NO_CI*** (#39307)
## What

Adopt the latest Azure SDK spellcheck guidance

([spellcheck.md](https://github.com/Azure/azure-sdk-tools/blob/main/doc/common/spellcheck.md#migrating-from-vscodecspelljson-to-sdkservicecspellyaml)):

- Move **service-scoped `overrides`** out of the central
`.vscode/cspell.json`
into per-service `sdk/<service>/cspell.yaml` files that `import` the
central
  config (the `import` is required).
- Convert legacy per-service `cspell.json` → `cspell.yaml`, add the
missing
`import` to existing per-service `cspell.yaml` files, and consolidate
each
  service down to a single `sdk/<service>/cspell.yaml`.
- Alphabetize word lists (case-insensitive) and dedupe.

Cross-cutting words stay in the central config (they have no reliable
per-service attribution).

## Why

Keeping service words in per-service files reduces merge conflicts in
the hot
central file and makes the lists easier to read — exactly what the
guidance now
recommends.

## Safety / validation

- `cspell` uses the **nearest** config for each file, so consolidating
package
configs up to the service directory preserves coverage (verified
empirically
  with cspell 10, the pinned version).
- **Conservation check:** the full case-insensitive word union is
identical
  before and after — **0 words lost**.
- Spot-checked affected files (e.g. voicelive/keyvault review docs,
storage &
  cosmos sources) still report **0 issues**.

## CI

Config-only change across many packages, so the commit is tagged
**`***NO_CI***`** ***NO_CI*** 
to avoid a repo-wide build storm. Opened as a **draft**.

Co-authored-by: Copilot <[email protected]>
Copilot-Session: 65188144-106d-4960-b150-a8faa13eef33
2026-07-27 15:18:10 -07:00
..
…