@askdkc/dsh-lsp-server 0.1.10 → 0.1.11

package/README.md

@@ -1,33 +1,32 @@
 # @askdkc/dsh-lsp-server
 
-An LSP plugin for [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness), providing code navigation, diagnostics, and completion without applying edits.
+A read-only LSP plugin for DeepSeek Harness. It provides code navigation, diagnostics, and completion for PHP/Blade, TypeScript/JavaScript, Svelte, HTML, CSS, and Tailwind.
 
-Supports PHP/Blade via **PHPantom**, TypeScript/JavaScript, Svelte, HTML, CSS, and Tailwind.
+## Requirements
 
-## Install
+- Node.js 22.19+ (22.x) or 24+
+- DSH providing the `fs`, `subprocess`, `tools`, and `systemPrompt` services
+- PHPantom for PHP/Blade support (`phpantom_lsp` must be in `PATH`)
+
+This plugin imposes no DSH version range at startup: imports and initialization report actual failures. This does not guarantee compatibility with every future DSH API.
 
-Requires Node.js **22.19+ (22.x) or 24+** and DSH **0.2.0-rc.2**. The DSH LSP packages and Node language servers install with this plugin. For PHP/Blade, install **PHPantom** so `phpantom_lsp` is in `PATH`.
+## Install
 
-Install from npm into the Web profile:
+Run this from the DeepSeek Harness project root, after the updated npm release is available:
 
 ```sh
-dsh plugin --profile web add @askdkc/dsh-lsp-server@latest
+pnpm dsh plugin --profile web add @askdkc/dsh-lsp-server@latest
 ```
 
-Do not install this plugin with `github:askdkc/dsh-lsp-server`. Git installs must build the untracked `lib` files through `prepare`, which pnpm blocks unless the exact Git dependency is allowed in the Web profile's `allowBuilds`. The published npm package includes the built files.
+`@latest` selects the npm `latest` tag. Older releases declared exact DSH host peers and can be skipped after a DSH update. Local source changes do not update the published package.
 
-If `plugin add` stops with `ERR_PNPM_IGNORED_BUILDS` for `core-js`, set the build decision in the **Web profile's** `~/.dsh/profiles/web/pnpm-workspace.yaml`. Running `pnpm approve-builds` from the harness project does not configure that profile. To skip the script, add or update:
+Start or restart Web without opening a browser, from the same project root:
 
-```yaml
-allowBuilds:
-  core-js: false
+```sh
+pnpm dsh web --no-open
 ```
 
-If the failed add already wrote the dependency, remove it with `dsh plugin --profile web remove @askdkc/dsh-lsp-server`, then repeat the add command using the same `dsh` launcher (for example, `pnpm dsh`). A dependency alone does not activate the plugin: confirm `@askdkc/dsh-lsp-server` appears in `dsh.profile.bundles` in the profile's `package.json`. See [installation troubleshooting](docs/usage.md#install) for details.
-
-Version `0.1.9` is skipped on DSH 0.2.0-rc.2 because it declares DSH `0.2.0-rc.1` host peers. After installing a compatible release, use the explicit `@latest` above to update an existing dependency; an unqualified `plugin add @askdkc/dsh-lsp-server` can leave its locked old version installed with `Already up to date`. The version exemption is not a compatibility fix. Start or restart Web with `dsh web`.
-
-[Configuration, tool usage, and troubleshooting](docs/usage.md)
+Install the published npm package, not a Git dependency. The npm package includes its built files; a Git install must build them during `prepare` and may be blocked by the Web profile's `allowBuilds` policy. For install recovery and configuration, see [Usage and configuration](docs/usage.md).
 
 ## License
 

package/cordis.patch.yml

@@ -1,6 +1,6 @@
 - insert:
     - id: lsp
-      name: '@deepseek-ai/dsh-lsp'
+      name: '@askdkc/dsh-lsp-server/lsp'
 
     - id: lsp-webstack-provider
       name: '@askdkc/dsh-lsp-server/provider'
@@ -14,7 +14,7 @@
             args: ['--stdio']
 
     - id: tool-lsp
-      name: '@deepseek-ai/dsh-tool-lsp'
+      name: '@askdkc/dsh-lsp-server/tool-lsp'
       config:
         maxLocations: 200
         maxResultChars: 32000

package/docs/usage.md

@@ -18,17 +18,17 @@ The five Node language servers and TypeScript are package dependencies. PHPantom
 
 See the [installation commands](../README.md#install).
 
-Specify `@latest` when upgrading an existing installation. A bare `plugin add @askdkc/dsh-lsp-server` can keep a locked older version and report `Already up to date`; verify the installed version in the Web profile before restarting DSH.
+Run DSH commands from the DeepSeek Harness project root. After a updated npm release is published, use `@latest` to install or upgrade; an unqualified add can keep a locked older version and report `Already up to date`. A local `package.json` version change does not update npm's `latest` tag.
 
 ```sh
-dsh plugin --profile web list @askdkc/dsh-lsp-server --depth 0
+pnpm dsh plugin --profile web list @askdkc/dsh-lsp-server --depth 0
 ```
 
-pnpm may warn about missing DSH peer packages because the profile has peer auto-installation disabled. DSH resolves those host services from its own installation; do not add duplicate host packages to the profile just to silence pnpm. A DSH compatibility warning naming this bundle and an old version means the bundle itself still needs upgrading.
+pnpm may warn about missing DSH peer packages because the profile has peer auto-installation disabled. DSH resolves those host services from its own installation; do not add duplicate host packages to the profile just to silence pnpm. Older releases with exact host peers may still be skipped; install the updated release to remove that version gate.
 
 The bundle adds `lsp`, `lsp-webstack-provider`, `tool-lsp`, and `tool-lsp-extra` rows. Its `@deepseek-ai/dsh-lsp` and `@deepseek-ai/dsh-tool-lsp` dependencies are installed automatically; do not install them separately. The harness still provides the profile's `fs`, `subprocess`, `tools`, and `systemPrompt` services and the shared Cordis instance. Installing this package does not install the harness itself.
 
-This release pins the DSH LSP service, tool, and four required host services to `0.2.0-rc.2`. A registry `next` dependency could resolve an older prerelease from cached metadata and cause DSH to reject the installed plugin rows. The repository lockfile and packed-artifact test use the same DSH release.
+The four DSH host peers use `*`, including prereleases in DSH's compatibility evaluator. All four bundle rows resolve through this package's own entry points; `/lsp` and `/tool-lsp` re-export the upstream implementations without catching import or initialization errors. The LSP dependencies and development host packages remain pinned to `0.2.0-rc.2` for reproducible builds and tests; those pins do not restrict the host version at startup. Future API compatibility is not guaranteed.
 
 DSH may stop `plugin add` with `ERR_PNPM_IGNORED_BUILDS` for `core-js`, a dependency of the bundled HTML/CSS server. Decide whether to allow its build script in DSH's plugin manager. To **deny** the script from the CLI, set `allowBuilds.core-js: false` in the selected profile's `pnpm-workspace.yaml` before adding this bundle:
 
@@ -37,7 +37,14 @@ allowBuilds:
   core-js: false
 ```
 
-The packed-artifact test runs HTML/CSS servers with dependency scripts disabled. If an earlier CLI add stopped after writing the dependency, check that `@askdkc/dsh-lsp-server` appears in `dsh.profile.bundles` in that profile's `package.json`; a dependency entry alone does not activate the bundle. If it is absent, remove the package with `dsh plugin --profile web remove @askdkc/dsh-lsp-server`, set the build decision, then repeat the original add command. Use the same launcher prefix you use for `dsh web`.
+The packed-artifact test runs HTML/CSS servers with dependency scripts disabled. If an earlier add stopped after writing the dependency, check that `@askdkc/dsh-lsp-server` appears in `dsh.profile.bundles` in that profile's `package.json`; a dependency entry alone does not activate the bundle. If it is absent, remove the package, set the build decision, then add it again:
+
+```sh
+pnpm dsh plugin --profile web remove @askdkc/dsh-lsp-server
+pnpm dsh plugin --profile web add @askdkc/dsh-lsp-server@latest
+```
+
+Run both commands from the DeepSeek Harness project root, after a updated npm release is available.
 
 If you already enabled another LSP provider for these extensions, remove its overlapping mappings first: DSH intentionally rejects duplicate ownership with `LSP_CONFLICT`. If your profile already declares the `lsp` or `tool-lsp` rows, compose the provider and extra-tool rows manually instead of inserting the whole bundle twice.
 
@@ -92,17 +99,21 @@ Bundled mode resolves executables on the Node host and is intended for local DSH
 
 ## Doctor
 
+Run from this repository's root after installing dependencies and building:
+
 ```sh
+pnpm install --frozen-lockfile
+pnpm build
 node lib/cli/doctor.js --json
-node lib/cli/doctor.js --config ./webstack-config.json --deep
 ```
 
-The JSON config file contains the provider configuration object above. Doctor checks package binaries and PATH availability without launching servers, and exits nonzero when an enabled server is missing. `--deep` adds an explicit read-only inspection summary; it is **not** a protocol handshake or a check of the running DSH profile. Runtime status is available through `lsp_extra`.
+Doctor checks package binaries and PATH availability without launching servers, and exits nonzero when an enabled server is missing. To inspect an existing JSON config, pass its path with `--config`; `--deep` adds a read-only summary, not a protocol handshake or check of the running DSH profile. Runtime status is available through `lsp_extra`.
 
 ## Verification
 
-`pnpm pack` builds the source through `prepare` and includes the built files in the tarball; npm releases also include those files. A direct Git dependency needs to run `prepare` in the Web profile and is blocked unless that exact Git dependency is listed in the profile's `allowBuilds`. Development dependencies provide the host services needed by the tests.
+From this repository root, `pnpm pack` builds the source through `prepare` and includes the built files in the tarball; npm releases also include those files. A direct Git dependency needs to run `prepare` in the Web profile and is blocked unless that exact Git dependency is listed in the profile's `allowBuilds`. Development dependencies provide the host services needed by the tests.
 
+Run these from this repository's root:
 ```sh
 pnpm install --frozen-lockfile
 pnpm check                 # types, deterministic/DSH integration tests, build, packed-artifact smoke test
@@ -110,13 +121,13 @@ pnpm test:e2e              # real TS/JS, HTML, CSS, Svelte, Tailwind v3/v4
 PHPANTOM_E2E=1 pnpm test:e2e # additionally tests installed PHPantom with PHP and Blade
 ```
 
-The packed-artifact test installs the archive into a fresh consumer with DSH's hoisted layout, peer auto-installation disabled, and dependency scripts disabled. It provides the host service packages but does not preinstall either LSP package, then verifies bundle imports, both tool registrations, and real TypeScript, HTML, and CSS queries. It also checks declaration paths and the executable doctor. The consumer install prefers cached packages but needs registry access for uncached packages or metadata. E2E needs working OS file watchers; sandboxed macOS watchers may fail with `EMFILE`.
+The packed-artifact test installs the archive into a fresh consumer with DSH's hoisted layout, peer auto-installation disabled, and dependency scripts disabled. It provides the host service packages but does not preinstall either LSP package, then verifies official profile composition and preflight, bundle imports, both tool registrations, and real TypeScript, HTML, and CSS queries on DSH `0.2.0-rc.2` and `0.2.1-alpha.1`. It also checks that import and initialization errors retain their original cause. It also checks declaration paths and the executable doctor. The consumer install prefers cached packages but needs registry access for uncached packages or metadata. E2E needs working OS file watchers; sandboxed macOS watchers may fail with `EMFILE`.
 
-Integration tests run against the published DSH service/tool packages and Cordis versions recorded in the lockfile. The full Web UI and a source-built upstream application are not exercised here.
+Integration tests run against the published DSH service/tool packages and Cordis versions recorded in the lockfile. The packed consumers use the published DSH runtimes named above. Future versions (`0.3.0-alpha.1` and `1.0.0`) are simulated only as version inputs to the official compatibility evaluator, not tested APIs. The full Web UI and a source-built upstream application are not exercised here.
 
 ### Dependency security
 
-This repository pins Vite to 6.4.3 (which uses patched esbuild 0.25.x) and overrides the Svelte Language Server's fallback compiler to Svelte 5.55.7. These versions address [Vite's Windows path bypass](https://github.com/advisories/GHSA-fx2h-pf6j-xcff) and the [Svelte SSR](https://github.com/advisories/GHSA-pr6f-5x2q-rwfp) / [DOM clobbering](https://github.com/advisories/GHSA-rcqx-6q8c-2c42) advisories. Run `pnpm audit` after dependency updates. The Svelte E2E tests exercise fallback compilation with both legacy and rune syntax, including diagnostics after edits.
+This repository pins Vite to 6.4.3 (which uses patched esbuild 0.25.x) and overrides the Svelte Language Server's fallback compiler to Svelte 5.55.7. These versions address [Vite's Windows path bypass](https://github.com/advisories/GHSA-fx2h-pf6j-xcff) and the [Svelte SSR](https://github.com/advisories/GHSA-pr6f-5x2q-rwfp) / [DOM clobbering](https://github.com/advisories/GHSA-rcqx-6q8c-2c42) advisories. Run `pnpm audit` from this repository root after dependency updates. The Svelte E2E tests exercise fallback compilation with both legacy and rune syntax, including diagnostics after edits.
 
 The pinned `svelte-language-server` still declares Svelte 4 as its dependency. Repository overrides and `pnpm-lock.yaml` do **not** propagate when this plugin is installed as a dependency. Until upstream changes that dependency, the host installation must apply its own override to obtain the patched fallback compiler. For npm, merge this into the installation root's `package.json`, reinstall, and run `npm audit`:
 

package/lib/lsp.js

@@ -0,0 +1,5 @@
+import dsh_lsp_default from "@deepseek-ai/dsh-lsp";
+
+export * from "@deepseek-ai/dsh-lsp"
+
+export { dsh_lsp_default as default };

package/lib/tool-lsp.js

@@ -0,0 +1,3 @@
+export * from "@deepseek-ai/dsh-tool-lsp"
+
+export {  };

package/lib/types/lsp.d.ts

@@ -0,0 +1,2 @@
+export { default } from '@deepseek-ai/dsh-lsp';
+export * from '@deepseek-ai/dsh-lsp';

package/lib/types/tool-lsp.d.ts

@@ -0,0 +1 @@
+export * from '@deepseek-ai/dsh-tool-lsp';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@askdkc/dsh-lsp-server",
-  "version": "0.1.10",
+  "version": "0.1.11",
   "description": "Composite read-only LSP provider for DeepSeek Harness web stacks",
   "type": "module",
   "main": "./lib/provider.js",
@@ -18,7 +18,15 @@
       "types": "./lib/types/extra-tool.d.ts",
       "default": "./lib/extra-tool.js"
     },
-    "./package.json": "./package.json"
+    "./package.json": "./package.json",
+    "./lsp": {
+      "types": "./lib/types/lsp.d.ts",
+      "default": "./lib/lsp.js"
+    },
+    "./tool-lsp": {
+      "types": "./lib/types/tool-lsp.d.ts",
+      "default": "./lib/tool-lsp.js"
+    }
   },
   "bin": {
     "dsh-lsp-webstack": "./lib/cli/doctor.js"
@@ -57,10 +65,10 @@
   },
   "peerDependencies": {
     "@deepseek-ai/cordis": "~4.0.4",
-    "@deepseek-ai/dsh-fs": "0.2.0-rc.2",
-    "@deepseek-ai/dsh-subprocess": "0.2.0-rc.2",
-    "@deepseek-ai/dsh-system-prompt": "0.2.0-rc.2",
-    "@deepseek-ai/dsh-tools": "0.2.0-rc.2",
+    "@deepseek-ai/dsh-fs": "*",
+    "@deepseek-ai/dsh-subprocess": "*",
+    "@deepseek-ai/dsh-system-prompt": "*",
+    "@deepseek-ai/dsh-tools": "*",
     "@deepseek-ai/schemastery": "~3.18.4"
   },
   "devDependencies": {