fix(ci): align engines.vscode to ^1.104.0 to match @types/vscode; update README requirement

Author: masterkain

README.md

@@ -18,7 +18,7 @@
 
 ## Requirements
 
-- Visual Studio Code 1.100.0 or higher
+- Visual Studio Code 1.104.0 or higher
 - Node.js (for extension development, if building from source)
 
 ## Installation
@@ -62,9 +62,23 @@
 
 ## Configuration
 
-Right now, the extension offers limited customization. You can modify the code to:
+You can customize the comment prefix per file extension via Settings:
 
-- **Adjust Supported File Types** by editing the `commentSyntaxMap` in [extension.ts](./src/extension.ts).
+- Setting: `autopathcomment.commentSyntaxMap`
+- Keys are file extensions (include the dot), values are single-line comment prefixes.
+
+Examples:
+
+```jsonc
+// settings.json
+{
+  "autopathcomment.commentSyntaxMap": {
+    ".sh": "#",
+    ".kt": "//",
+    ".zig": "//"
+  }
+}
+```
 
 ## Known Issues / Limitations
 

package.json

@@ -10,7 +10,7 @@
     "url": "https://github.com/icoretech/autopathcomment.git"
   },
   "engines": {
-    "vscode": "^1.100.0"
+    "vscode": "^1.104.0"
   },
   "categories": [
     "Other"
@@ -19,7 +19,21 @@
     "onStartupFinished"
   ],
   "main": "./dist/extension.js",
-  "contributes": {},
+  "contributes": {
+    "configuration": {
+      "title": "AutoPathComment",
+      "properties": {
+        "autopathcomment.commentSyntaxMap": {
+          "type": "object",
+          "markdownDescription": "Custom mapping of file extensions to single-line comment prefixes. Keys must include the dot (e.g. `.ts`) and values are prefixes like `//` or `#`. User values override built-in defaults.",
+          "default": {},
+          "additionalProperties": {
+            "type": "string"
+          }
+        }
+      }
+    }
+  },
   "scripts": {
     "vscode:prepublish": "npm run package",
     "compile": "npm run check-types && npm run lint && node esbuild.js",