chore(docs): Upgrade Docusaurus and refresh documentation assets

.changeset/docs-tooling-refresh.md

@@ -0,0 +1,5 @@
+---
+"layne": patch
+---
+
+Upgrade documentation tooling to Docusaurus 3.10.0, refresh the Claude illustration, and repair local development links.

.github/workflows/ci-test.yml

@@ -12,7 +12,7 @@ jobs:
       - uses: actions/setup-node@53b83947a5a98c8d113130e565377fae1a50d02f  # v6.3.0
         with:
           node-version: '22'
-      - run: rm -f package-lock.json && npm install
+      - run: npm ci
       - run: npm run build
       - run: npm run lint
       - run: npm run validate-config

website/docs/local-development.md

@@ -35,7 +35,7 @@ You need a GitHub App to receive webhooks and post Check Runs. Create a **separa
 |---|---|
 | **GitHub App name** | `Layne Dev` (any name - just avoid reusing the production name) |
 | **Homepage URL** | `http://localhost:3000` (required by GitHub, not actually used in dev) |
-| **Webhook URL** | Leave blank for now - you will fill this in during [Step 5](#step-5--receive-live-webhooks-via-smeeio) |
+| **Webhook URL** | Leave blank for now - you will fill this in during [Step 5](#step-5---receive-live-webhooks-via-smeeio-or-ngrok) |
 | **Webhook secret** | Run `openssl rand -hex 32` in your terminal, paste the output here, and **save it** - you will need it in your `.env` |
 
 ### 1.3 Set repository permissions
@@ -278,7 +278,7 @@ Open `fixtures/webhooks/pr_opened.json` and update:
 | `repository.owner.login` | `"your-org"` |
 | `repository.clone_url` | `"https://github.com/your-org/your-repo.git"` |
 | `pull_request.head.repo.clone_url` | same clone URL |
-| `installation.id` | your installation ID from [Step 2](#step-2--install-the-app-on-a-test-repository) |
+| `installation.id` | your installation ID from [Step 2](#step-2---install-the-app-on-a-test-repository) |
 | `pull_request.head.sha` | a real commit SHA from your test repo |
 | `pull_request.base.sha` | a real base commit SHA from your test repo |
 

website/docs/scanners/claude.md

@@ -1,7 +1,7 @@
 # Claude
 
 <div style={{textAlign: 'center'}}>
-  <img src="/img/claude.png" alt="Claude" width="160" />
+  <img src="/img/claude.svg" alt="Claude" width="160" />
 </div>
 
 The Claude scanner uses Anthropic's Claude LLM to analyze changed code. By default it looks for **malicious intent** - reverse shells, backdoors, obfuscated payloads, and supply-chain attacks. That is a starting point, not a fixed ruleset. Security engineers implementing Layne should adapt the system prompt (or build a skill) to reflect their threat model and use cases - the scanner is a framework for AI-assisted code review, not a prescribed detector.

website/package.json

@@ -14,17 +14,18 @@
     "write-heading-ids": "docusaurus write-heading-ids"
   },
   "dependencies": {
-    "@docusaurus/core": "3.9.2",
-    "@docusaurus/preset-classic": "3.9.2",
+    "@docusaurus/core": "3.10.0",
+    "@docusaurus/faster": "3.10.0",
+    "@docusaurus/preset-classic": "3.10.0",
     "@mdx-js/react": "^3.1.1",
     "clsx": "^2.1.1",
     "prism-react-renderer": "^2.4.1",
     "react": "^19.2.4",
     "react-dom": "^19.2.4"
   },
   "devDependencies": {
-    "@docusaurus/module-type-aliases": "3.9.2",
-    "@docusaurus/types": "3.9.2"
+    "@docusaurus/module-type-aliases": "3.10.0",
+    "@docusaurus/types": "3.10.0"
   },
   "browserslist": {
     "production": [