fix: resolve plugin installation failures for workspace resolution and missing dependencies

Add Vite resolve aliases for core subpath exports (schema, search, types)
to fix import resolution on Windows where Node.js package exports are not
properly followed by Vite's import analysis.

Bump version to 1.0.3.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

.claude-plugin/marketplace.json

@@ -9,7 +9,7 @@
     {
       "name": "understand-anything",
       "description": "Multi-agent codebase analysis with interactive dashboard, guided tours, and skill commands",
-      "version": "1.0.2",
+      "version": "1.0.3",
       "source": "./understand-anything-plugin"
     }
   ]

understand-anything-plugin/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@understand-anything/skill",
-  "version": "1.0.2",
+  "version": "1.0.3",
   "type": "module",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",

understand-anything-plugin/packages/dashboard/vite.config.ts

@@ -5,6 +5,13 @@ import path from "path";
 import fs from "fs";
 
 export default defineConfig({
+  resolve: {
+    alias: {
+      "@understand-anything/core/schema": path.resolve(__dirname, "../core/dist/schema.js"),
+      "@understand-anything/core/search": path.resolve(__dirname, "../core/dist/search.js"),
+      "@understand-anything/core/types": path.resolve(__dirname, "../core/dist/types.js"),
+    },
+  },
   plugins: [
     react(),
     tailwindcss(),