pi-lsp-adapter 0.1.0 → 0.1.1

package/README.md

@@ -130,7 +130,7 @@ You can override these definitions or add new server definitions in config.
 Most users only need one file:
 
 ```text
-~/.pi/agents/lsp.json
+~/.pi/agent/lsp.json
 ```
 
 If that file does not exist, the extension behaves as if this config were present:
@@ -147,13 +147,13 @@ If that file does not exist, the extension behaves as if this config were presen
 
 ### Config files and merge order
 
-| Priority | Path                    | Purpose                                                                                                          |
-| -------- | ----------------------- | ---------------------------------------------------------------------------------------------------------------- |
-| 1        | built-in catalog        | Default server definitions for `vtsls`, `pyright`, `gopls`, `rust-analyzer`, `yamlls`, etc.                      |
-| 2        | `~/.pi/agents/lsp.json` | User-global config. Best place for executable, install, PATH, `installMode`, and `warmup`.                       |
-| 3        | `.pi/lsp.json`          | Project-local config. Safe server fields are honored before trust; process-starting fields require `/lsp trust`. |
+| Priority | Path                   | Purpose                                                                                                          |
+| -------- | ---------------------- | ---------------------------------------------------------------------------------------------------------------- |
+| 1        | built-in catalog       | Default server definitions for `vtsls`, `pyright`, `gopls`, `rust-analyzer`, `yamlls`, etc.                      |
+| 2        | `~/.pi/agent/lsp.json` | User-global config. Best place for executable, install, PATH, `installMode`, and `warmup`.                       |
+| 3        | `.pi/lsp.json`         | Project-local config. Safe server fields are honored before trust; process-starting fields require `/lsp trust`. |
 
-> Path gotcha: config uses `~/.pi/agents/lsp.json` (`agents` plural). Runtime state uses `~/.pi/agent/lsp/` (`agent` singular).
+> Path gotcha: config is the file `~/.pi/agent/lsp.json`. Runtime state lives under the directory `~/.pi/agent/lsp/`.
 
 ### Runtime paths
 
@@ -253,7 +253,7 @@ You do not need Pi to manage every language server. If you already have servers
 Prefer global config for executable overrides:
 
 ```text
-~/.pi/agents/lsp.json
+~/.pi/agent/lsp.json
 ```
 
 Example: use Mason.nvim's Pyright:
@@ -442,15 +442,16 @@ Run `/reload` in Pi after editing the extension.
 
 ## Release
 
-Publishing is tag-driven. Use `npm version` to bump `package.json` and `package-lock.json`, create the matching semver tag, then push the commit and tag. The GitHub Actions publish workflow verifies that the tag matches `package.json` before publishing.
+Publishing is tag-driven, but do not create release tags by hand. Use the release helper so `package.json` and `package-lock.json` are bumped before the matching semver tag is created. The GitHub Actions publish workflow is intentionally read-only: it verifies the tag against both version files and fails instead of patching tagged source during publish.
 
-Before the first release, configure npm publishing for this repository with either an `NPM_TOKEN` GitHub secret or npm Trusted Publishing.
+npm publishing uses Trusted Publishing for `.github/workflows/publish.yml`, so no npm token secret is required. The npm package must have a Trusted Publisher configured for `nikmmd/pi-lsp-adapter` and workflow filename `publish.yml`.
 
 ```bash
-npm version 0.1.0
-git push origin main --follow-tags
+npm run release -- 0.1.2 --push
 ```
 
+Omit `--push` to create the release commit and tag locally, then push with the command printed by the helper.
+
 Stable tags such as `v0.1.0` publish with the npm `latest` dist-tag. Prerelease tags such as `v0.2.0-beta.1` publish with the npm `next` dist-tag.
 
 ## Troubleshooting
@@ -481,7 +482,7 @@ This is the quickest way to see the final command, root markers, install state,
 
 ### Reuse Mason.nvim servers
 
-Configure the server as `type: "system"` in `~/.pi/agents/lsp.json` and point `command` at the Mason binary. Pi will use it but will not manage or uninstall it.
+Configure the server as `type: "system"` in `~/.pi/agent/lsp.json` and point `command` at the Mason binary. Pi will use it but will not manage or uninstall it.
 
 ### Start fresh for one server
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-lsp-adapter",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "Pi extension that gives coding agents Language Server Protocol tools for diagnostics, hover, definitions, references, and symbol search",
   "author": "Nikmmd",
   "license": "MIT",
@@ -38,7 +38,8 @@
     "test:watch": "vitest",
     "typecheck": "tsc --noEmit",
     "format": "prettier --write .",
-    "format:check": "prettier --check ."
+    "format:check": "prettier --check .",
+    "release": "bash scripts/release.sh"
   },
   "pi": {
     "extensions": [

package/src/config/paths.ts

@@ -50,7 +50,7 @@ export function getTrustStorePath(): string {
 }
 
 export function getUserConfigPath(): string {
-  return join(homedir(), ".pi", "agents", "lsp.json");
+  return join(homedir(), ".pi", "agent", "lsp.json");
 }
 
 export function getProjectConfigPath(projectRoot: string): string {