### Setup

Source: https://github.com/mcphailtom/pi-lsp-lite/blob/main/docs/CONTRIBUTING.md

Clone the repository, navigate to the project directory, and install dependencies.

```bash
git clone https://github.com/mcphailtom/pi-lsp-lite
cd pi-lsp-lite
npm install
```

--------------------------------

### Install pi-lsp-lite

Source: https://github.com/mcphailtom/pi-lsp-lite/blob/main/README.md

Install the pi-lsp-lite extension using the pi package manager.

```bash
pi install npm:pi-lsp-lite
```

--------------------------------

### Diagnostic Handling Example

Source: https://github.com/mcphailtom/pi-lsp-lite/blob/main/docs/ARCHITECTURE.md

An example illustrating the snapshot-diff and quiescence-based settling mechanism for handling diagnostics, including cross-file impacts.

```plaintext
handleEdit(lib.ts):
  snapshot: { caller.ts: {errors:0} }
  send didChange(lib.ts)
  │
  ├─ server publishes for caller.ts: [{error}]
  │  crossFileCallback: pre={errors:0}, post={errors:1} → CHANGED
  │  → start 200ms quiescence
  │
  ├─ server publishes for type_error.ts: [] (stale re-publish)
  │  crossFileCallback: pre={errors:0}, post={errors:0} → UNCHANGED
  │  → ignored
  │
  ├─ 200ms pass, no more publishes
  │  → settle("ok")
  │
  └─ result: { status:"ok", diagnostics:[], otherFiles:[{caller.ts, errors:1}] }

```

--------------------------------

### Example of what you see with diagnostics

Source: https://github.com/mcphailtom/pi-lsp-lite/blob/main/README.md

An example of how language server diagnostics are displayed in the terminal.

```text
  edit ─ src/main.go
  ✓ Edited src/main.go (replaced 2 lines)

  ⚠ LSP diagnostics for src/main.go (2 errors):
    error 12:5 [compiler] undefined: foo
    error 18:2 [compiler] too many arguments in call to bar
    + 1 diagnostic in 1 other file
```

--------------------------------

### Example .pi-lsp-lite.json for adding a language

Source: https://github.com/mcphailtom/pi-lsp-lite/blob/main/docs/ARCHITECTURE.md

This JSON snippet shows how to define a new language server configuration in a .pi-lsp-lite.json file, specifying extensions, command, arguments, and root patterns.

```json
{
  "servers": {
    "python": {
      "extensions": [".py"],
      "command": "pylsp",
      "args": [],
      "rootPatterns": ["pyproject.toml", "setup.py"]
    }
  }
}
```

--------------------------------

### Development commands

Source: https://github.com/mcphailtom/pi-lsp-lite/blob/main/README.md

Commands for cloning the repository, installing dependencies, and running checks/tests during development.

```bash
git clone https://github.com/mcphailtom/pi-lsp-lite
cd pi-lsp-lite && npm install
npm run check              # typecheck
npm test                   # unit tests (106, no servers needed)
npm run test:integration   # real server tests (needs servers on PATH)
```

--------------------------------

### Running integration tests

Source: https://github.com/mcphailtom/pi-lsp-lite/blob/main/docs/CONTRIBUTING.md

Command to run integration tests, which require real language servers to be installed.

```bash
npm run test:integration
```

--------------------------------

### Add a new language server configuration

Source: https://github.com/mcphailtom/pi-lsp-lite/blob/main/README.md

Example JSON configuration for adding a new language server (Haskell) to pi-lsp-lite.

```json
{
  "servers": {
    "haskell": {
      "extensions": ["\.hs"],
      "command": "haskell-language-server-wrapper",
      "args": ["--lsp"],
      "rootPatterns": ["cabal.project", "stack.yaml"]
    }
  }
}
```

--------------------------------

### Development workflow commands

Source: https://github.com/mcphailtom/pi-lsp-lite/blob/main/docs/CONTRIBUTING.md

Commands for type checking, running unit tests, and integration tests.

```bash
# typecheck
npm run check

# unit tests (no servers required, 106 tests)
npm test

# integration tests (requires gopls, rust-analyzer, typescript-language-server, pylsp, clangd on PATH)
npm run test:integration

# test in pi
pi -e ./index.ts
```

--------------------------------

### Running checks before pushing

Source: https://github.com/mcphailtom/pi-lsp-lite/blob/main/docs/CONTRIBUTING.md

Commands to run type checking and unit tests before submitting changes.

```bash
npm run check && npm test
```

--------------------------------

### Module Layout

Source: https://github.com/mcphailtom/pi-lsp-lite/blob/main/docs/ARCHITECTURE.md

The directory structure and purpose of each module within the pi-lsp-lite extension.

```plaintext
index.ts               → extension entry point
src/
  config.ts            → config file loading, merge, and write
  languages.ts         → built-in language server defaults
  install-registry.ts  → known install commands for built-in servers
  client.ts            → LSP protocol client (JSON-RPC over stdio)
  server-manager.ts    → server lifecycle and edit orchestration
  format.ts            → diagnostic formatting for agent consumption
  util.ts              → file URI, binary lookup, workspace root detection
test/
  fake-server.ts       → minimal LSP server for unit tests
  *.test.ts            → unit tests (no real servers)
  integration/         → real server tests (guarded by INTEGRATION env)

```

--------------------------------

### Data Flow

Source: https://github.com/mcphailtom/pi-lsp-lite/blob/main/docs/ARCHITECTURE.md

The sequence of events and component interactions from an agent's tool call to the final tool result.

```plaintext
agent calls write/edit
  → pi executes the tool, writes the file
  → tool_result event fires
  → index.ts: check file extension, resolve absolute path, enforce cwd boundary
  → server-manager.ts: find workspace root, ensure server, queue edit
  → client.ts: send didOpen/didChange, wait for publishDiagnostics
  → format.ts: filter to errors+warnings, format text, add cross-file footer
  → index.ts: append formatted text to tool_result content

```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.