📝 Document pi-lsp tooling and agent usage

README § Tooling and § Tooling decisions record the extension and the
reasoning behind it: read-only by design, auto-detects TypeScript 7,
and never a correctness gate — verify is. AGENTS.md § First action tells
agents the lsp_* tools exist, to prefer lsp_references over grep -w for
colliding identifiers, and to treat empty LSP output as inconclusive.

Close the backlog evaluation task with a resolved note, and allowlist
the tsgo/tsserver tool names for cspell.

backlog.tasks

@@ -11,6 +11,12 @@ Setup:
 ✔ Document branching model @done
     ✔ Describe branching model: when to branch, base branch, naming @done
     ✔ Clarify release workflow: who pushes `main`, CI as post-merge gate, drop PR usage @done (9/8/2026, 2:54:32 PM)
+✔ Evaluate connecting the agent to lsp typescript server @done
+    - might be more difficult with TS7, since LSP Server has changed from 6
+    - but since vscode is running TS7, maybe it is possible to connect to the TS7 LSP server of vscode
+    - LSP servers in general?
+    - maybe skills?
+    → resolved: adopted @spences10/pi-lsp@0.0.46 as a project-local pi extension (`.pi/settings.json`). It auto-detects the repo's TypeScript 7 (no `lib/tsserver.js`) and spawns `tsc --lsp --stdio` — the same tsgo binary VS Code's native-preview uses. Read-only: hover / definition / references / symbols / diagnostics. No skill; skills don't own persistent processes.
 
 v1.0:
 ☐ API surface is stable and fully typed