add link instructions

Author: RubenHalman

files/docs/linkingcore.md

@@ -27,7 +27,7 @@
     "stryker": "npm i -g @stryker-mutator/core @stryker-mutator/jest-runner && stryker run"
   },
   "license": "MIT",
-  "description": "A specialized engine designed for conducting static analysis on Salesforce automation tools, with capabilities to scan and evaluate Flows, Process Builders, and Workflows.",
+  "description": "A purpose-built engine to assess and enhance Salesforce Flow automations.",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/Flow-Scanner/lightning-flow-scanner-core.git"
@@ -68,5 +68,19 @@
   },
   "volta": {
     "node": "20.13.1"
-  }
+  },
+  "keywords": [
+    "salesforce",
+    "flow",
+    "linter",
+    "static-analysis",
+    "static-code-analysis",
+    "flow-scanner",
+    "flow-analysis",
+    "flow-linter",
+    "metadata-scanner",
+    "security-scanner",
+    "best-practices",
+    "salesforce-flow"
+  ]
 }

package.json

@@ -189,7 +189,7 @@ Specifying exceptions allows you to exclude specific scenarios from rule enforce
 > curl https://get.volta.sh | bash
 > ```
 >
-> Once installed, Volta will automatically use the Node.js version defined in `package.json`.
+> Volta will automatically use the Node.js version defined in `package.json`.
 
 1. Clone the repo:
 
@@ -215,4 +215,19 @@ Specifying exceptions allows you to exclude specific scenarios from rule enforce
    npm run test
    ```
 
+5. Test as local dependency:
+   To test changes to the core module in the VS Code extension or SF CLI plugin locally, run:
+
+   ```bash
+   npm link
+   ```
+
+   b) Go to the dependent project (VSX or SF CLI) and use:
+
+   ```bash
+   npm link lightning-flow-scanner-core
+   ```
+
+   Your local core will now replace the installed dependency and update automatically on rebuild.
+
 Want to help improve Lightning Flow Scanner? See our [Contributing Guidelines](https://github.com/Flow-Scanner/lightning-flow-scanner-core/blob/main/CONTRIBUTING.md).