Documentation Accuracy Issues - 2026-04-15

## Documentation Accuracy Issues

Automated validation of `packages/website/docs/01-project-setup.md` against [Effect Language Service README](https://github.com/Effect-TS/language-service/blob/main/README.md).

---

### HIGH: Incorrect `$schema` path in tsconfig.json example

**Local docs instruct:**
\`\`\`json
{
"$schema": "https://raw.githubusercontent.com/Effect-TS/language-service/refs/heads/main/schema.json",
"compilerOptions": { ... }
}
\`\`\`

**Source README specifies:**
\`\`\`json
{
"$schema": "./node_modules/@effect/language-service/schema.json",
"compilerOptions": { ... }
}
\`\`\`

**Why this matters:**
- The remote URL always points to the HEAD of `main`, which may not match the installed package version. If the schema has changed between releases, users get incorrect autocomplete/validation.
- The local path (`./node_modules/...`) reflects the actually-installed version, which is what the source recommends.
- The remote URL requires internet access; the local path works offline.

**Fix:** Replace the remote `$schema` URL with `"./node_modules/@effect/language-service/schema.json"` in the tsconfig example.

---

*Validated by automated documentation accuracy check.*

Update the tsconfig.json example in packages/website/docs/01-project-setup.md, using the Effect Language Service README as the reference. Replace the remote $schema URL with the local node_modules path, then run the repository's automated documentation accuracy check to confirm the example matches the source README.

Written by the indexing model from the issue text.