fix: resolve workflow conflicts and extension build paths

- Fix VS Code extension main entry path to match build output
- Bump version to 1.0.1 to avoid npm version conflict
- Prevent duplicate release workflows by excluding vscode tags
- VS Code extension now builds to correct location

Author: thegdsks

.github/workflows/release.yml

@@ -4,6 +4,7 @@ on:
   push:
     tags:
       - 'v*'
+      - '!vscode-v*'  # Exclude VS Code extension tags
   workflow_dispatch:
     inputs:
       version:

package.json

@@ -1,6 +1,6 @@
 {
   "name": "@typeweaver/commitweave",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "description": "A modern CLI to write smart, structured, and beautiful git commit messages with emoji support, conventional commit rules, AI-powered summaries (optional), and built-in hooks.",
   "main": "./dist/index.js",
   "module": "./dist/index.mjs",

vscode-extension/package.json

@@ -2,7 +2,7 @@
   "name": "commitweave",
   "displayName": "CommitWeave",
   "description": "Smart, structured, and beautiful git commits with AI assistance - by GLINR STUDIOS",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "publisher": "glincker",
   "engines": {
     "vscode": "^1.80.0"
@@ -23,7 +23,7 @@
     "onCommand:commitweave.ai",
     "onCommand:commitweave.configure"
   ],
-  "main": "./out/extension.js",
+  "main": "./out/src/extension.js",
   "contributes": {
     "commands": [
       {