chore: dependency bumps

.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,13 +1,12 @@
 ---
-name: Bug report
+name: Issue report
 about: Create a report to help us improve
-title: ''
-labels: bug
-assignees: ''
-
+title: ""
+labels: ""
+assignees: ""
 ---
 
-## 🐞 Bug Summary
+## Issue Summary
 
 Describe the issue you're experiencing with the core module, such as a rule not behaving as expected, incorrect scan output, or problems with configuration or parsing.
 
@@ -25,7 +24,7 @@ Steps to reproduce the bug:
 
 ## ✅ Expected Behavior
 
-Describe what *should* have happened. Be specific about expected rule evaluation or output.
+Describe what _should_ have happened. Be specific about expected rule evaluation or output.
 
 ---
 
@@ -41,11 +40,9 @@ If applicable, include:
 
 ## 📋 Environment
 
+- **Used via**: [Direct, VS Code extension, Salesforce CLI plugin]
 - **OS**: [e.g. macOS Ventura, Ubuntu 22.04]
-- **Node.js Version**: [e.g. 18.16.0]
-- **NPM Version**: [e.g. 9.5.1]
 - **Module Version**: [e.g. `lightning-flow-scanner-core` v1.4.0]
-- **Used via**: [Direct, VS Code extension, Salesforce CLI plugin]
 
 ---
 
@@ -55,4 +52,4 @@ Any other details? Paste relevant error logs, stack traces, or screenshots that
 
 ---
 
-> ⚠️ Note: If this issue affects the **VS Code Extension** or **Salesforce CLI Plugin**, please file it in the relevant repository instead.
+> ⚠️ Note: If this issue affects only one platform, such as the **VS Code Extension** or **Salesforce CLI Plugin**, please file it in the relevant repository instead.

.github/ISSUE_TEMPLATE/rule-request.md

@@ -1,23 +1,19 @@
 ---
 name: Rule request
 about: Suggest a new static analysis rule for flows
-title: ''
+title: ""
 labels: new rule
-assignees: ''
-
+assignees: ""
 ---
 
-**Is your rule request related to a specific problem or anti-pattern? Please describe.**  
+**Is your rule request related to a specific problem or anti-pattern? Please describe.**
 A clear and concise description of the issue this rule should detect. For example: "Flows using 'Get Records' with 'store all fields' should be flagged."
 
-**Describe the rule you'd like to see**  
+**Describe the rule you'd like to see**
 Outline the behavior the rule should enforce or detect.
 
-**Describe alternatives you've considered**  
-If there's another way to enforce this pattern today, mention it here.
-
-**Example flow behavior (optional)**  
+**Example flow behavior (optional)**
 If you can, describe or attach an example Flow structure or metadata where this rule would apply.
 
-**Additional context**  
+**Additional context**
 Add any other context, links to docs, or notes relevant to the rule idea.

.gitignore

@@ -4,9 +4,6 @@ node_modules
 **/.DS_Store
 .DS_Store
 
-# IDE files
-.vscode/**
-
 .yarn/**
 **.gz
 *.log

.vscode/extensions.json

@@ -0,0 +1,9 @@
+{
+  // See https://go.microsoft.com/fwlink/?LinkId=827846 to learn about workspace recommendations.
+  // Extension identifier format: ${publisher}.${name}. Example: vscode.csharp
+
+  // List of extensions which should be recommended for users of this workspace.
+  "recommendations": ["Orta.vscode-jest"],
+  // List of extensions recommended by VS Code that should not be recommended for users of this workspace.
+  "unwantedRecommendations": []
+}

.vscode/launch.json

@@ -0,0 +1,30 @@
+{
+  "version": "1.0.0",
+  "configurations": [
+    {
+      "command": "npm test",
+      "name": "Run npm test",
+      "request": "launch",
+      "type": "node-terminal"
+    },
+    {
+      "type": "node",
+      "name": "vscode-jest-tests.v2.lightning-flow-scanner-core",
+      "request": "launch",
+      "args": [
+        "test",
+        "--",
+        "--runInBand",
+        "--watchAll=false",
+        "--testNamePattern",
+        "${jest.testNamePattern}",
+        "--runTestsByPath",
+        "${jest.testFile}"
+      ],
+      "cwd": "${workspaceFolder}/lightning-flow-scanner-core",
+      "console": "integratedTerminal",
+      "internalConsoleOptions": "neverOpen",
+      "runtimeExecutable": "npm"
+    }
+  ]
+}

.vscode/settings.json

@@ -0,0 +1,3 @@
+{
+  "jest.runMode": "on-demand"
+}

CONTRIBUTING.md

@@ -17,7 +17,7 @@ If it's more specific like a bug or a new feature—use [GitHub Issues](https://
 
 ###### Core Engine - For issues or requests related to the core functionality of the scanner, use the following links to submit your request:
 
-- [Bug Report](https://github.com/Flow-Scanner/lightning-flow-scanner-core/issues/new?template=bug_report.md): Report a bug or issue
+- [Report Issue](https://github.com/Flow-Scanner/lightning-flow-scanner-core/issues/new?template=bug_report.md): Report a bug or issue.
 - [Rule Request](https://github.com/Flow-Scanner/lightning-flow-scanner-core/issues/new?template=rule-request.md): Submit a request for a new rule.
 - [Features/Other](https://github.com/Flow-Scanner/lightning-flow-scanner-core/issues/new): Suggest a new feature.
 

SECURITY.md

@@ -18,8 +18,6 @@ This project collects zero user data. No credentials, PII, payment info, or heal
 
 We actively track and maintain an up-to-date inventory of all third-party dependencies to ensure security and compatibility. Our dependencies include:
 
-| Package | License | Purpose |
-
+| Package       | License                                                                | Purpose                 |
 | ------------- | ---------------------------------------------------------------------- | ----------------------- |
-
 | `xmlbuilder2` | [MIT](https://github.com/oozcitak/xmlbuilder2/blob/master/LICENSE.txt) | XML builder for Node.js |