GLSP-1636: Migrate to pnpm (#517)

- Replace yarn and lerna with pnpm workspaces as the package manager
- Use pnpm's built-in workspace management and the glsp CLI for
  publishing in place of lerna run/publish
- Adapt CI workflows, VS Code tasks, and project docs to pnpm

Also:
- Remove verify skill and improve fix skill
- Reformat code base for updated prettier formatting alignment
- Remove unused e2e-server-pr workflow
- Remove outdated/unused watch vscode task

Part-of: eclipse-glsp/glsp#1636

Author: tortmayr

.claude/skills/fix/SKILL.md

@@ -1,12 +1,33 @@
 ---
 name: fix
-description: Auto-fix all lint, formatting, and copyright header issues across the workspace. Use when validation (`/verify`) fails or when explicitly requested.
+description: Run the fix-and-verify suite for the workspace (compile, auto-fix lint/format/headers, test). IMPORTANT - Proactively invoke this skill after completing any code changes (new features, bug fixes, refactors) before reporting completion. Re-run it after manually addressing anything it could not auto-fix.
 ---
 
-Run the full auto-fix suite for the GLSP Client monorepo from the repository root:
+Run the auto-fix and validation suite for the GLSP Client monorepo from the repository root.
+
+1. Build first. This is a hard gate: if the build fails, stop immediately, report the build errors, and do not run any of the following steps. 
+The build must pass before anything else runs. 
+
+```bash
+pnpm build
+```
+
+2. Auto-fix lint, formatting, and copyright headers. Run all three even if an earlier one reports remaining problems (they are independent):
 
 ```bash
-yarn lint:fix && yarn format && yarn headers:fix
+pnpm lint:fix
+pnpm format
+pnpm headers:fix -t changes
 ```
 
-After fixing, report what changed. If any issues remain that couldn't be auto-fixed, list them and suggest manual fixes.
+3. Run the test suite to validate behavior (tests are not auto-fixable):
+
+```bash
+pnpm test
+```
+
+Then:
+
+- If `pnpm build` failed, fix the compile errors and re-run this skill.
+- If `pnpm lint:fix` reported lint errors it could not fix, or `pnpm test` failed, fix them manually and re-run this skill.
+- Otherwise everything is clean (compile succeeds, formatting and headers are corrected in place, lint has no remaining errors, tests pass) — report completion.

.claude/skills/generate-changelog/SKILL.md

@@ -102,42 +102,42 @@ Pick the most fitting tag from the vocabulary (Step 1.2) based on PR title and b
 
 **Formatting:**
 
--   Entry prefix: `-   ` (dash + exactly 3 spaces)
--   Sub-item indent: 4 spaces + `-   ` (4 spaces from parent dash)
--   Sub-sub-item indent: 8 spaces + `-   `
--   Single space between `[tag]` and description text
--   Single space before PR link at end of line
--   PR links are mandatory, full URLs: `[#123](https://github.com/OWNER/REPO/pull/123)`
+- Entry prefix: `-   ` (dash + exactly 3 spaces)
+- Sub-item indent: 4 spaces + `-   ` (4 spaces from parent dash)
+- Sub-sub-item indent: 8 spaces + `-   `
+- Single space between `[tag]` and description text
+- Single space before PR link at end of line
+- PR links are mandatory, full URLs: `[#123](https://github.com/OWNER/REPO/pull/123)`
 
 **Wording:**
 
--   Always start with a **present tense imperative verb** (not past tense)
--   Common verbs: Fix, Improve, Add, Update, Extend, Ensure, Introduce, Remove, Refactor, Rename, Provide, Allow, Support
--   **Bug fixes**: "Fix a bug that caused/prevented...", "Fix X behavior"
--   **Features**: "Introduce...", "Add support for...", "Provide..."
--   **Enhancements**: "Improve...", "Extend...", "Ensure that..."
--   **Refactors**: "Refactor...", "Rework...", "Rename..."
--   Be specific — never "Fix various issues"
+- Always start with a **present tense imperative verb** (not past tense)
+- Common verbs: Fix, Improve, Add, Update, Extend, Ensure, Introduce, Remove, Refactor, Rename, Provide, Allow, Support
+- **Bug fixes**: "Fix a bug that caused/prevented...", "Fix X behavior"
+- **Features**: "Introduce...", "Add support for...", "Provide..."
+- **Enhancements**: "Improve...", "Extend...", "Ensure that..."
+- **Refactors**: "Refactor...", "Rework...", "Rename..."
+- Be specific — never "Fix various issues"
 
 **Capitalization:**
 
--   Tags are always lowercase: `[diagram]`, not `[Diagram]`
--   Description starts lowercase after the tag (unless proper noun or code element)
--   Section headers: Title Case (`### Potentially Breaking Changes`)
+- Tags are always lowercase: `[diagram]`, not `[Diagram]`
+- Description starts lowercase after the tag (unless proper noun or code element)
+- Section headers: Title Case (`### Potentially Breaking Changes`)
 
 **Description cleanup from PR title:**
 
--   Remove issue tracker prefixes (e.g. `GLSP-1234:`, `GH-123:`, `ISSUE-456:`)
--   Remove conventional commit prefixes: `fix:`, `feat:`, `chore:`
--   Rephrase bug-report style to changelog style:
-    -   BAD: "Edit label UI does not resize on graph zoom"
-    -   GOOD: "Fix edit label UI not resizing on graph zoom"
--   Keep concise — one line
+- Remove issue tracker prefixes (e.g. `GLSP-1234:`, `GH-123:`, `ISSUE-456:`)
+- Remove conventional commit prefixes: `fix:`, `feat:`, `chore:`
+- Rephrase bug-report style to changelog style:
+    - BAD: "Edit label UI does not resize on graph zoom"
+    - GOOD: "Fix edit label UI not resizing on graph zoom"
+- Keep concise — one line
 
 **Breaking changes:**
 
--   Describe what changed, why it's breaking, and how to migrate
--   Extract migration sub-items from the PR body's "What it does" section
+- Describe what changed, why it's breaking, and how to migrate
+- Extract migration sub-items from the PR body's "What it does" section
 
 ---
 
@@ -149,35 +149,35 @@ Read `CHANGELOG.md` in the repository root.
 
 **Active section detection:**
 
--   An active section has the `- active` suffix (e.g. `## v2.7.0 - active`)
--   If an active section exists → merge new entries into it
--   If the topmost section is a released version (no `- active` suffix) → create a new active section above it
+- An active section has the `- active` suffix (e.g. `## v2.7.0 - active`)
+- If an active section exists → merge new entries into it
+- If the topmost section is a released version (no `- active` suffix) → create a new active section above it
 
 **Creating a new section:**
 
--   Bump the minor version of `LAST_TAG` (e.g. `v2.6.0` → `v2.7.0`)
--   Insert after the title line, before the first `## ` heading:
+- Bump the minor version of `LAST_TAG` (e.g. `v2.6.0` → `v2.7.0`)
+- Insert after the title line, before the first `## ` heading:
 
 ```markdown
 ## v2.7.0 - active
 
 ### Changes
 
--   [tag] Entry [#N](url)
+- [tag] Entry [#N](url)
 
 ### Potentially Breaking Changes
 
--   [tag] Entry [#N](url)
-    -   Sub-item detail
+- [tag] Entry [#N](url)
+    - Sub-item detail
 ```
 
 Only include "Potentially Breaking Changes" if there are breaking entries.
 
 **Merging into existing active section:**
 
--   Check PR numbers against existing entries to avoid duplicates
--   Append new entries to the appropriate subsection
--   Create missing subsections as needed
+- Check PR numbers against existing entries to avoid duplicates
+- Append new entries to the appropriate subsection
+- Create missing subsections as needed
 
 ### Step 2.2: Write the updated CHANGELOG.md
 
@@ -205,9 +205,9 @@ Even if nothing is uncertain, ask:
 
 ### Step 3.3: Collect user feedback
 
--   **Approve as-is** → done (or proceed to Phase 4 if PR was requested)
--   **Request edits** → apply changes, show updated diff, ask again
--   **Resolve uncertain items** → apply, show updated diff
+- **Approve as-is** → done (or proceed to Phase 4 if PR was requested)
+- **Request edits** → apply changes, show updated diff, ask again
+- **Resolve uncertain items** → apply, show updated diff
 
 **Do NOT proceed to Phase 4 unless the user explicitly requests a PR.**
 

.claude/skills/verify/SKILL.md

@@ -25,5 +25,5 @@ to learn how to report vulnerabilities.
 
 <!-- Please check, when if it applies to your change. -->
 
--   [ ] This PR should be mentioned in the changelog
--   [ ] This PR introduces a breaking change (if yes, provide more details below for the changelog and the migration guide)
+- [ ] This PR should be mentioned in the changelog
+- [ ] This PR introduces a breaking change (if yes, provide more details below for the changelog and the migration guide)

.github/PULL_REQUEST_TEMPLATE.md

@@ -25,32 +25,26 @@ jobs:
     runs-on: ubuntu-22.04
     steps:
       - uses: actions/checkout@df4cb1c069e1874edd31b4311f1884172cec0e10 # v6.0.3
+      - uses: pnpm/action-setup@0e279bb959325dab635dd2c09392533439d90093 # v6.0.8
       - uses: actions/setup-node@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e # v6.4.0
         with:
           node-version: 22.x
+          cache: pnpm
       - name: Build
-        run: yarn install
-      - name: Check for uncommitted changes in yarn.lock
-        run: |
-          if git diff --name-only | grep -q "^yarn.lock"; then
-            echo "::error::The yarn.lock file has uncommitted changes!"
-            exit 1
-          fi
+        run: pnpm build
   test:
     name: Test
     timeout-minutes: 60
     runs-on: ubuntu-22.04
     steps:
       - uses: actions/checkout@df4cb1c069e1874edd31b4311f1884172cec0e10 # v6.0.3
+      - uses: pnpm/action-setup@0e279bb959325dab635dd2c09392533439d90093 # v6.0.8
       - uses: actions/setup-node@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e # v6.4.0
         with:
           node-version: 22.x
-      - name: Install
-        run: |
-          yarn install
+          cache: pnpm
       - name: Test
-        run: |
-          yarn test:ci
+        run: pnpm test:ci
       - name: Publish Test Report
         uses: ctrf-io/github-test-reporter@0f299074936c32ccaab5be5230511f6b2b9080aa # v1.0.28
         with:
@@ -64,15 +58,13 @@ jobs:
     runs-on: ubuntu-22.04
     steps:
       - uses: actions/checkout@df4cb1c069e1874edd31b4311f1884172cec0e10 # v6.0.3
+      - uses: pnpm/action-setup@0e279bb959325dab635dd2c09392533439d90093 # v6.0.8
       - uses: actions/setup-node@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e # v6.4.0
         with:
           node-version: 22.x
-      - name: Install
-        run: |
-          yarn install
+          cache: pnpm
       - name: Create eslint json report
-        run: |
-          yarn lint:ci
+        run: pnpm lint:ci
       - name: Create summary
         if: always()
         run: |
@@ -85,15 +77,13 @@ jobs:
     if: github.ref == 'refs/heads/master'
     steps:
       - uses: actions/checkout@df4cb1c069e1874edd31b4311f1884172cec0e10 # v6.0.3
+      - uses: pnpm/action-setup@0e279bb959325dab635dd2c09392533439d90093 # v6.0.8
       - uses: actions/setup-node@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e # v6.4.0
         with:
           node-version: 22.x
-      - name: Install
-        run: |
-          yarn install
+          cache: pnpm
       - name: Run Coverage Tests
-        run: |
-          yarn test:coverage:ci
+        run: pnpm test:coverage:ci
       - name: Upload Coverage Report
         uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a # v7.0.1
         with: