feat: Add database migration tools and fix Electron integration

- Add comprehensive IndexedDB to SQLite migration service (1,397 lines)
- Create migration UI with progress tracking and validation (1,492 lines)
- Fix Electron TypeScript compilation and SQLite plugin issues
- Expand migration system with detailed documentation and error handling
- Add development guide and coding standards

Resolves: #electron-startup #database-migration #typescript-errors
Impact: Enables user-friendly database migration with full data verification

.cursor/rules/development_guide.mdc

@@ -0,0 +1,31 @@
+---
+description: 
+globs: 
+alwaysApply: true
+---
+python script files must always have a blank line
+remove whitespace at the end of lines
+never git commit automatically.  always preview commit message to user allow copy and paste by the user
+use system date command to timestamp all interactions with accurate date and time
+✅ Preferred Commit Message Format
+
+    Short summary in the first line (concise and high-level).
+    Avoid long commit bodies unless truly necessary.
+
+✅ Valued Content in Commit Messages
+
+    Specific fixes or features.
+    Symptoms or problems that were fixed.
+    Notes about tests passing or TS/linting errors being resolved (briefly).
+
+❌ Avoid in Commit Messages
+
+    Vague terms: “improved”, “enhanced”, “better” — especially from AI.
+    Minor changes: small doc tweaks, one-liners, cleanup, or lint fixes.
+    Redundant blurbs: repeated across files or too generic.
+    Multiple overlapping purposes in a single commit — prefer narrow, focused commits.
+    Long explanations of what can be deduced from good in-line code comments.
+
+ Guiding Principle
+
+    Let code and inline documentation speak for themselves. Use commits to highlight what isn't obvious from reading the code.