feat: add missing settings management functions

- Add getSettingsForAccount() to retrieve complete settings for any account DID
- Add getAccountSpecificSettings() to get account-specific settings without defaults
- Add mergeSettings() for consistent settings merging across SQLite and Dexie
- Update retrieveSettingsForActiveAccount() to use new mergeSettings() function
- Improve error handling and logging for settings operations
- Maintain backward compatibility with existing settings API

This provides better settings management capabilities for account switching,
debugging, and data validation while ensuring consistent behavior across
both SQLite and Dexie storage implementations.

.cursor-markdown-rules.md

@@ -1,310 +0,0 @@
-# Cursor Markdown Ruleset for TimeSafari Documentation
-
-## Overview
-
-This ruleset enforces consistent markdown formatting standards across all project
-documentation, ensuring readability, maintainability, and compliance with
-markdownlint best practices.
-
-## General Formatting Standards
-
-### Line Length
-
-- **Maximum line length**: 80 characters
-- **Exception**: Code blocks (JSON, shell, TypeScript, etc.) - no line length
-  enforcement
-- **Rationale**: Ensures readability across different screen sizes and terminal
-  widths
-
-### Blank Lines
-
-- **Headings**: Must be surrounded by blank lines above and below
-- **Lists**: Must be surrounded by blank lines above and below
-- **Code blocks**: Must be surrounded by blank lines above and below
-- **Maximum consecutive blank lines**: 1 (no multiple blank lines)
-- **File start**: No blank lines at the beginning of the file
-- **File end**: Single newline character at the end
-
-### Whitespace
-
-- **No trailing spaces**: Remove all trailing whitespace from lines
-- **No tabs**: Use spaces for indentation
-- **Consistent indentation**: 2 spaces for list items and nested content
-
-## Heading Standards
-
-### Format
-
-- **Style**: ATX-style headings (`#`, `##`, `###`, etc.)
-- **Case**: Title case for general headings
-- **Code references**: Use backticks for file names and technical terms
-  - ✅ `### Current package.json Scripts`
-  - ❌ `### Current Package.json Scripts`
-
-### Hierarchy
-
-- **H1 (#)**: Document title only
-- **H2 (##)**: Major sections
-- **H3 (###)**: Subsections
-- **H4 (####)**: Sub-subsections
-- **H5+**: Avoid deeper nesting
-
-## List Standards
-
-### Unordered Lists
-
-- **Marker**: Use `-` (hyphen) consistently
-- **Indentation**: 2 spaces for nested items
-- **Blank lines**: Surround lists with blank lines
-
-### Ordered Lists
-
-- **Format**: `1.`, `2.`, `3.` (sequential numbering)
-- **Indentation**: 2 spaces for nested items
-- **Blank lines**: Surround lists with blank lines
-
-### Task Lists
-
-- **Format**: `- [ ]` for incomplete, `- [x]` for complete
-- **Use case**: Project planning, checklists, implementation tracking
-
-## Code Block Standards
-
-### Fenced Code Blocks
-
-- **Syntax**: Triple backticks with language specification
-- **Languages**: `json`, `bash`, `typescript`, `javascript`, `yaml`, `markdown`
-- **Blank lines**: Must be surrounded by blank lines above and below
-- **Line length**: No enforcement within code blocks
-
-### Inline Code
-
-- **Format**: Single backticks for inline code references
-- **Use case**: File names, commands, variables, properties
-
-## Special Content Standards
-
-### JSON Examples
-
-```json
-{
-  "property": "value",
-  "nested": {
-    "property": "value"
-  }
-}
-```
-
-### Shell Commands
-
-```bash
-# Command with comment
-npm run build:web
-
-# Multi-line command
-VITE_GIT_HASH=`git log -1 --pretty=format:%h` \
-  vite build --config vite.config.web.mts
-```
-
-### TypeScript Examples
-
-```typescript
-// Function with JSDoc
-/**
- * Get environment configuration
- * @param env - Environment name
- * @returns Environment config object
- */
-const getEnvironmentConfig = (env: string) => {
-  switch (env) {
-    case 'prod':
-      return { /* production settings */ };
-    default:
-      return { /* development settings */ };
-  }
-};
-```
-
-## File Structure Standards
-
-### Document Header
-
-```markdown
-# Document Title
-
-**Author**: Matthew Raymer
-**Date**: YYYY-MM-DD
-**Status**: 🎯 **STATUS** - Brief description
-
-## Overview
-
-Brief description of the document's purpose and scope.
-```
-
-### Section Organization
-
-1. **Overview/Introduction**
-2. **Current State Analysis**
-3. **Implementation Plan**
-4. **Technical Details**
-5. **Testing & Validation**
-6. **Next Steps**
-
-## Markdownlint Configuration
-
-### Required Rules
-
-```json
-{
-  "MD013": { "code_blocks": false },
-  "MD012": true,
-  "MD022": true,
-  "MD031": true,
-  "MD032": true,
-  "MD047": true,
-  "MD009": true
-}
-```
-
-### Rule Explanations
-
-- **MD013**: Line length (disabled for code blocks)
-- **MD012**: No multiple consecutive blank lines
-- **MD022**: Headings should be surrounded by blank lines
-- **MD031**: Fenced code blocks should be surrounded by blank lines
-- **MD032**: Lists should be surrounded by blank lines
-- **MD047**: Files should end with a single newline
-- **MD009**: No trailing spaces
-
-## Validation Commands
-
-### Check Single File
-
-```bash
-npx markdownlint docs/filename.md
-```
-
-### Check All Documentation
-
-```bash
-npx markdownlint docs/
-```
-
-### Auto-fix Common Issues
-
-```bash
-# Remove trailing spaces
-sed -i 's/[[:space:]]*$//' docs/filename.md
-
-# Remove multiple blank lines
-sed -i '/^$/N;/^\n$/D' docs/filename.md
-
-# Add newline at end if missing
-echo "" >> docs/filename.md
-```
-
-## Common Patterns
-
-### Implementation Plans
-
-```markdown
-## Implementation Plan
-
-### Phase 1: Foundation (Day 1)
-
-#### 1.1 Component Setup
-
-- [ ] Create new component file
-- [ ] Add basic structure
-- [ ] Implement core functionality
-
-#### 1.2 Configuration
-
-- [ ] Update configuration files
-- [ ] Add environment variables
-- [ ] Test configuration loading
-```
-
-### Status Tracking
-
-```markdown
-**Status**: ✅ **COMPLETE** - All phases finished
-**Progress**: 75% (15/20 components)
-**Next**: Ready for testing phase
-```
-
-### Performance Metrics
-
-```markdown
-#### 📊 Performance Metrics
-- **Build Time**: 2.3 seconds (50% faster than baseline)
-- **Bundle Size**: 1.2MB (30% reduction)
-- **Success Rate**: 100% (no failures in 50 builds)
-```
-
-## Enforcement
-
-### Pre-commit Hooks
-
-- Run markdownlint on all changed markdown files
-- Block commits with linting violations
-- Auto-fix common issues when possible
-
-### CI/CD Integration
-
-- Include markdownlint in build pipeline
-- Generate reports for documentation quality
-- Fail builds with critical violations
-
-### Team Guidelines
-
-- All documentation PRs must pass markdownlint
-- Use provided templates for new documents
-- Follow established patterns for consistency
-
-## Templates
-
-### New Document Template
-
-```markdown
-# Document Title
-
-**Author**: Matthew Raymer
-**Date**: YYYY-MM-DD
-**Status**: 🎯 **PLANNING** - Ready for Implementation
-
-## Overview
-
-Brief description of the document's purpose and scope.
-
-## Current State
-
-Description of current situation or problem.
-
-## Implementation Plan
-
-### Phase 1: Foundation
-
-- [ ] Task 1
-- [ ] Task 2
-
-## Next Steps
-
-1. **Review and approve plan**
-2. **Begin implementation**
-3. **Test and validate**
-
----
-
-**Status**: Ready for implementation
-**Priority**: Medium
-**Estimated Effort**: X days
-**Dependencies**: None
-**Stakeholders**: Development team
-```
-
----
-
-**Last Updated**: 2025-07-09
-**Version**: 1.0
-**Maintainer**: Matthew Raymer

.cursor/rules/absurd-sql.mdc

@@ -1,23 +1,14 @@
 ---
-globs: **/db/databaseUtil.ts, **/interfaces/absurd-sql.d.ts, **/src/registerSQLWorker.js, **/
-services/AbsurdSqlDatabaseService.ts
-alwaysApply: false
+description: 
+globs: 
+alwaysApply: true
 ---
 # Absurd SQL - Cursor Development Guide
 
-**Author**: Matthew Raymer
-**Date**: 2025-08-19
-**Status**: 🎯 **ACTIVE** - Database development guidelines
-
 ## Project Overview
-
-Absurd SQL is a backend implementation for sql.js that enables persistent
-SQLite databases in the browser by using IndexedDB as a block storage system.
-This guide provides rules and best practices for developing with this project
-in Cursor.
+Absurd SQL is a backend implementation for sql.js that enables persistent SQLite databases in the browser by using IndexedDB as a block storage system. This guide provides rules and best practices for developing with this project in Cursor.
 
 ## Project Structure
-
 ```
 absurd-sql/
 ├── src/               # Source code
@@ -30,45 +21,36 @@ absurd-sql/
 ## Development Rules
 
 ### 1. Worker Thread Requirements
-
 - All SQL operations MUST be performed in a worker thread
 - Main thread should only handle worker initialization and communication
 - Never block the main thread with database operations
 
 ### 2. Code Organization
-
 - Keep worker code in separate files (e.g., `*.worker.js`)
 - Use ES modules for imports/exports
 - Follow the project's existing module structure
 
 ### 3. Required Headers
-
 When developing locally or deploying, ensure these headers are set:
-
 ```
 Cross-Origin-Opener-Policy: same-origin
 Cross-Origin-Embedder-Policy: require-corp
 ```
 
 ### 4. Browser Compatibility
-
 - Primary target: Modern browsers with SharedArrayBuffer support
 - Fallback mode: Safari (with limitations)
 - Always test in both modes
 
 ### 5. Database Configuration
-
 Recommended database settings:
-
 ```sql
 PRAGMA journal_mode=MEMORY;
 PRAGMA page_size=8192;  -- Optional, but recommended
 ```
 
 ### 6. Development Workflow
-
 1. Install dependencies:
-
    ```bash
    yarn add @jlongster/sql.js absurd-sql
    ```
@@ -79,20 +61,17 @@ PRAGMA page_size=8192;  -- Optional, but recommended
    - `yarn serve` - Start development server
 
 ### 7. Testing Guidelines
-
 - Write tests for both SharedArrayBuffer and fallback modes
 - Use Jest for testing
 - Include performance benchmarks for critical operations
 
 ### 8. Performance Considerations
-
 - Use bulk operations when possible
 - Monitor read/write performance
 - Consider using transactions for multiple operations
 - Avoid unnecessary database connections
 
 ### 9. Error Handling
-
 - Implement proper error handling for:
   - Worker initialization failures
   - Database connection issues
@@ -100,21 +79,18 @@ PRAGMA page_size=8192;  -- Optional, but recommended
   - Storage quota exceeded scenarios
 
 ### 10. Security Best Practices
-
 - Never expose database operations directly to the client
 - Validate all SQL queries
 - Implement proper access controls
 - Handle sensitive data appropriately
 
 ### 11. Code Style
-
 - Follow ESLint configuration
 - Use async/await for asynchronous operations
 - Document complex database operations
 - Include comments for non-obvious optimizations
 
 ### 12. Debugging
-
 - Use `jest-debug` for debugging tests
 - Monitor IndexedDB usage in browser dev tools
 - Check worker communication in console
@@ -123,7 +99,6 @@ PRAGMA page_size=8192;  -- Optional, but recommended
 ## Common Patterns
 
 ### Worker Initialization
-
 ```javascript
 // Main thread
 import { initBackend } from 'absurd-sql/dist/indexeddb-main-thread';
@@ -135,7 +110,6 @@ function init() {
 ```
 
 ### Database Setup
-
 ```javascript
 // Worker thread
 import initSqlJs from '@jlongster/sql.js';
@@ -157,7 +131,6 @@ async function setupDatabase() {
 ## Troubleshooting
 
 ### Common Issues
-
 1. SharedArrayBuffer not available
    - Check COOP/COEP headers
    - Verify browser support
@@ -174,20 +147,7 @@ async function setupDatabase() {
    - Verify transaction usage
 
 ## Resources
-
 - [Project Demo](https://priceless-keller-d097e5.netlify.app/)
 - [Example Project](https://github.com/jlongster/absurd-example-project)
 - [Blog Post](https://jlongster.com/future-sql-web)
-- [SQL.js Documentation](https://github.com/sql-js/sql.js/)
-
----
-
-**Status**: Active database development guidelines
-**Priority**: High
-**Estimated Effort**: Ongoing reference
-**Dependencies**: Absurd SQL, SQL.js, IndexedDB
-**Stakeholders**: Development team, Database team 
-- [Project Demo](https://priceless-keller-d097e5.netlify.app/)
-- [Example Project](https://github.com/jlongster/absurd-example-project)
-- [Blog Post](https://jlongster.com/future-sql-web)
-- [SQL.js Documentation](https://github.com/sql-js/sql.js/)
+- [SQL.js Documentation](https://github.com/sql-js/sql.js/) 

.cursor/rules/adr_template.mdc

@@ -1,65 +0,0 @@
-# ADR Template
-
-## ADR-XXXX-YY-ZZ: [Short Title]
-
-**Date:** YYYY-MM-DD
-**Status:** [PROPOSED | ACCEPTED | REJECTED | DEPRECATED | SUPERSEDED]
-**Deciders:** [List of decision makers]
-**Technical Story:** [Link to issue/PR if applicable]
-
-## Context
-
-[Describe the forces at play, including technological, political, social, and
-project local. These forces are probably in tension, and should be called out as
-such. The language in this section is value-neutral. It is simply describing facts.]
-
-## Decision
-
-[Describe our response to these forces. We will use the past tense ("We will...").]
-
-## Consequences
-
-### Positive
-- [List positive consequences]
-
-### Negative
-- [List negative consequences or trade-offs]
-
-### Neutral
-- [List neutral consequences or notes]
-
-## Alternatives Considered
-
-- **Alternative 1:** [Description] - [Why rejected]
-- **Alternative 2:** [Description] - [Why rejected]
-- **Alternative 3:** [Description] - [Why rejected]
-
-## Implementation Notes
-
-[Any specific implementation details, migration steps, or technical considerations]
-
-## References
-
-- [Link to relevant documentation]
-- [Link to related ADRs]
-- [Link to external resources]
-
-## Related Decisions
-
-- [List related ADRs or decisions]
-
----
-
-## Usage Guidelines
-
-1. **Copy this template** for new ADRs
-2. **Number sequentially** (ADR-001, ADR-002, etc.)
-3. **Use descriptive titles** that clearly indicate the decision
-4. **Include all stakeholders** in the deciders list
-5. **Link to related issues** and documentation
-6. **Update status** as decisions evolve
-7. **Store in** `doc/architecture-decisions/` directory
-description:
-globs:
-alwaysApply: false
----

.cursor/rules/app/architectural_decision_record.mdc

@@ -1,352 +0,0 @@
----
-description: when you need to understand the system architecture or make changes that impact the system architecture
-alwaysApply: false
----
-# TimeSafari Cross-Platform Architecture Guide
-
-**Author**: Matthew Raymer
-**Date**: 2025-08-19
-**Status**: 🎯 **ACTIVE** - Architecture guidelines
-
-## 1. Platform Support Matrix
-
-| Feature | Web (PWA) | Capacitor (Mobile) | Electron (Desktop) |
-|---------|-----------|--------------------|-------------------|
-| QR Code Scanning | WebInlineQRScanner | @capacitor-mlkit/barcode-scanning | Not Implemented |
-| Deep Linking | URL Parameters | App URL Open Events | Not Implemented |
-| File System | Limited (Browser API) | Capacitor Filesystem | Electron fs |
-| Camera Access | MediaDevices API | Capacitor Camera | Not Implemented |
-| Platform Detection | Web APIs | Capacitor.isNativePlatform() | process.env checks |
-
-## 2. Project Structure
-
-### Core Directories
-
-```
-src/
-├── components/     # Vue components
-├── services/       # Platform services and business logic
-├── views/          # Page components
-├── router/         # Vue router configuration
-├── types/          # TypeScript type definitions
-├── utils/          # Utility functions
-├── lib/            # Core libraries
-├── platforms/      # Platform-specific implementations
-├── electron/       # Electron-specific code
-├── constants/      # Application constants
-├── db/             # Database related code
-├── interfaces/     # TypeScript interfaces
-└── assets/         # Static assets
-```
-
-### Entry Points
-
-- `main.ts` → Base entry
-- `main.common.ts` → Shared init
-- `main.capacitor.ts` → Mobile entry
-- `main.electron.ts` → Electron entry
-- `main.web.ts` → Web entry
-
-## 3. Service Architecture
-
-### Service Organization
-
-```tree
-services/
-├── QRScanner/           
-│   ├── WebInlineQRScanner.ts
-│   └── interfaces.ts
-├── platforms/          
-│   ├── WebPlatformService.ts
-│   ├── CapacitorPlatformService.ts
-│   └── ElectronPlatformService.ts
-└── factory/           
-    └── PlatformServiceFactory.ts
-```
-
-### Factory Pattern
-
-Use a **singleton factory** to select platform services via
-`process.env.VITE_PLATFORM`.
-
-## 4. Feature Guidelines
-
-### QR Code Scanning
-
-- Define `QRScannerService` interface.
-- Implement platform-specific classes (`WebInlineQRScanner`, Capacitor,
-  etc).
-- Provide `addListener` and `onStream` hooks for composability.
-
-### Deep Linking
-
-- URL format: `timesafari://<route>[/<param>][?query=value]`
-- Web: `router.beforeEach` → parse query
-- Capacitor: `App.addListener("appUrlOpen", …)`
-
-## 5. Build Process
-
-- `vite.config.common.mts` → shared config
-- Platform configs: `vite.config.web.mts`, `.capacitor.mts`,
-  `.electron.mts`
-- Use `process.env.VITE_PLATFORM` for conditional loading.
-
-```bash
-npm run build:web
-npm run build:capacitor
-npm run build:electron
-```
-
-## 6. Testing Strategy
-
-- **Unit tests** for services.
-- **Playwright** for Web + Capacitor:
-  - `playwright.config-local.ts` includes web + Pixel 5.
-- **Electron tests**: add `spectron` or Playwright-Electron.
-- Mark tests with platform tags:
-
-  ```ts
-  test.skip(!process.env.MOBILE_TEST, "Mobile-only test");
-  ```
-
-> 🔗 **Human Hook:** Before merging new tests, hold a short sync (≤15
-> min) with QA to align on coverage and flaky test risks.
-
-## 7. Error Handling
-
-- Global Vue error handler → logs with component name.
-- Platform-specific wrappers log API errors with platform prefix
-  (`[Capacitor API Error]`, etc).
-- Use structured logging (not `console.log`).
-
-## 8. Best Practices
-
-- Keep platform code **isolated** in `platforms/`.
-- Always define a **shared interface** first.
-- Use feature detection, not platform detection, when possible.
-- Dependency injection for services → improves testability.
-- Maintain **Competence Hooks** in PRs (2–3 prompts for dev
-  discussion).
-
-## 9. Dependency Management
-
-- Key deps: `@capacitor/core`, `electron`, `vue`.
-- Use conditional `import()` for platform-specific libs.
-
-## 10. Security Considerations
-
-- **Permissions**: Always check + request gracefully.
-- **Storage**: Secure storage for sensitive data; encrypt when possible.
-- **Audits**: Schedule quarterly security reviews.
-
-## 11. ADR Process
-
-- All major architecture choices → log in `doc/adr/`.
-- Use ADR template with Context, Decision, Consequences, Status.
-- Link related ADRs in PR descriptions.
-
-> 🔗 **Human Hook:** When proposing a new ADR, schedule a 30-min
-> design sync for discussion, not just async review.
-
-## 12. Collaboration Hooks
-
-- **QR features**: Sync with Security before merging → permissions &
-  privacy.
-- **New platform builds**: Demo in team meeting → confirm UX
-  differences.
-- **Critical ADRs**: Present in guild or architecture review.
-
-## Self-Check
-
-- [ ] Does this feature implement a shared interface?
-- [ ] Are fallbacks + errors handled gracefully?
-- [ ] Have relevant ADRs been updated/linked?
-- [ ] Did I add competence hooks or prompts for the team?
-- [ ] Was human interaction (sync/review/demo) scheduled?
-
----
-
-**Status**: Active architecture guidelines
-**Priority**: High
-**Estimated Effort**: Ongoing reference
-**Dependencies**: Vue 3, Capacitor, Electron, Vite
-**Stakeholders**: Development team, Architecture team
-
-- [ ] Are fallbacks + errors handled gracefully?  
-- [ ] Have relevant ADRs been updated/linked?  
-- [ ] Did I add competence hooks or prompts for the team?  
-- [ ] Was human interaction (sync/review/demo) scheduled?  
-# TimeSafari Cross-Platform Architecture Guide
-
-**Author**: Matthew Raymer
-**Date**: 2025-08-19
-**Status**: 🎯 **ACTIVE** - Architecture guidelines
-
-## 1. Platform Support Matrix
-
-| Feature | Web (PWA) | Capacitor (Mobile) | Electron (Desktop) |
-|---------|-----------|--------------------|-------------------|
-| QR Code Scanning | WebInlineQRScanner | @capacitor-mlkit/barcode-scanning | Not Implemented |
-| Deep Linking | URL Parameters | App URL Open Events | Not Implemented |
-| File System | Limited (Browser API) | Capacitor Filesystem | Electron fs |
-| Camera Access | MediaDevices API | Capacitor Camera | Not Implemented |
-| Platform Detection | Web APIs | Capacitor.isNativePlatform() | process.env checks |
-
-## 2. Project Structure
-
-### Core Directories
-
-```
-src/
-├── components/     # Vue components
-├── services/       # Platform services and business logic
-├── views/          # Page components
-├── router/         # Vue router configuration
-├── types/          # TypeScript type definitions
-├── utils/          # Utility functions
-├── lib/            # Core libraries
-├── platforms/      # Platform-specific implementations
-├── electron/       # Electron-specific code
-├── constants/      # Application constants
-├── db/             # Database related code
-├── interfaces/     # TypeScript interfaces
-└── assets/         # Static assets
-```
-
-### Entry Points
-
-- `main.ts` → Base entry
-- `main.common.ts` → Shared init
-- `main.capacitor.ts` → Mobile entry
-- `main.electron.ts` → Electron entry
-- `main.web.ts` → Web entry
-
-## 3. Service Architecture
-
-### Service Organization
-
-```tree
-services/
-├── QRScanner/           
-│   ├── WebInlineQRScanner.ts
-│   └── interfaces.ts
-├── platforms/          
-│   ├── WebPlatformService.ts
-│   ├── CapacitorPlatformService.ts
-│   └── ElectronPlatformService.ts
-└── factory/           
-    └── PlatformServiceFactory.ts
-```
-
-### Factory Pattern
-
-Use a **singleton factory** to select platform services via
-`process.env.VITE_PLATFORM`.
-
-## 4. Feature Guidelines
-
-### QR Code Scanning
-
-- Define `QRScannerService` interface.
-- Implement platform-specific classes (`WebInlineQRScanner`, Capacitor,
-  etc).
-- Provide `addListener` and `onStream` hooks for composability.
-
-### Deep Linking
-
-- URL format: `timesafari://<route>[/<param>][?query=value]`
-- Web: `router.beforeEach` → parse query
-- Capacitor: `App.addListener("appUrlOpen", …)`
-
-## 5. Build Process
-
-- `vite.config.common.mts` → shared config
-- Platform configs: `vite.config.web.mts`, `.capacitor.mts`,
-  `.electron.mts`
-- Use `process.env.VITE_PLATFORM` for conditional loading.
-
-```bash
-npm run build:web
-npm run build:capacitor
-npm run build:electron
-```
-
-## 6. Testing Strategy
-
-- **Unit tests** for services.
-- **Playwright** for Web + Capacitor:
-  - `playwright.config-local.ts` includes web + Pixel 5.
-- **Electron tests**: add `spectron` or Playwright-Electron.
-- Mark tests with platform tags:
-
-  ```ts
-  test.skip(!process.env.MOBILE_TEST, "Mobile-only test");
-  ```
-
-> 🔗 **Human Hook:** Before merging new tests, hold a short sync (≤15
-> min) with QA to align on coverage and flaky test risks.
-
-## 7. Error Handling
-
-- Global Vue error handler → logs with component name.
-- Platform-specific wrappers log API errors with platform prefix
-  (`[Capacitor API Error]`, etc).
-- Use structured logging (not `console.log`).
-
-## 8. Best Practices
-
-- Keep platform code **isolated** in `platforms/`.
-- Always define a **shared interface** first.
-- Use feature detection, not platform detection, when possible.
-- Dependency injection for services → improves testability.
-- Maintain **Competence Hooks** in PRs (2–3 prompts for dev
-  discussion).
-
-## 9. Dependency Management
-
-- Key deps: `@capacitor/core`, `electron`, `vue`.
-- Use conditional `import()` for platform-specific libs.
-
-## 10. Security Considerations
-
-- **Permissions**: Always check + request gracefully.
-- **Storage**: Secure storage for sensitive data; encrypt when possible.
-- **Audits**: Schedule quarterly security reviews.
-
-## 11. ADR Process
-
-- All major architecture choices → log in `doc/adr/`.
-- Use ADR template with Context, Decision, Consequences, Status.
-- Link related ADRs in PR descriptions.
-
-> 🔗 **Human Hook:** When proposing a new ADR, schedule a 30-min
-> design sync for discussion, not just async review.
-
-## 12. Collaboration Hooks
-
-- **QR features**: Sync with Security before merging → permissions &
-  privacy.
-- **New platform builds**: Demo in team meeting → confirm UX
-  differences.
-- **Critical ADRs**: Present in guild or architecture review.
-
-## Self-Check
-
-- [ ] Does this feature implement a shared interface?
-- [ ] Are fallbacks + errors handled gracefully?
-- [ ] Have relevant ADRs been updated/linked?
-- [ ] Did I add competence hooks or prompts for the team?
-- [ ] Was human interaction (sync/review/demo) scheduled?
-
----
-
-**Status**: Active architecture guidelines
-**Priority**: High
-**Estimated Effort**: Ongoing reference
-**Dependencies**: Vue 3, Capacitor, Electron, Vite
-**Stakeholders**: Development team, Architecture team
-
-- [ ] Are fallbacks + errors handled gracefully?  
-- [ ] Have relevant ADRs been updated/linked?  
-- [ ] Did I add competence hooks or prompts for the team?  
-- [ ] Was human interaction (sync/review/demo) scheduled?  

.cursor/rules/app/timesafari.mdc

@@ -1,181 +0,0 @@
-# Time Safari Context
-
-**Author**: Matthew Raymer
-**Date**: 2025-08-19
-**Status**: 🎯 **ACTIVE** - Core application context
-
-## Project Overview
-
-Time Safari is an application designed to foster community building through
-gifts, gratitude, and collaborative projects. The app makes it easy and
-intuitive for users of any age and capability to recognize contributions,
-build trust networks, and organize collective action. It is built on services
-that preserve privacy and data sovereignty.
-
-## Core Goals
-
-1. **Connect**: Make it easy, rewarding, and non-threatening for people to
-   connect with others who have similar interests, and to initiate activities
-   together.
-
-2. **Reveal**: Widely advertise the great support and rewards that are being
-   given and accepted freely, especially non-monetary ones, showing the impact
-   gifts make in people's lives.
-
-## Technical Foundation
-
-### Architecture
-
-- **Privacy-preserving claims architecture** via endorser.ch
-- **Decentralized Identifiers (DIDs)**: User identities based on
-  public/private key pairs stored on devices
-- **Cryptographic Verification**: All claims and confirmations are
-  cryptographically signed
-- **User-Controlled Visibility**: Users explicitly control who can see their
-  identifiers and data
-- **Cross-Platform**: Web (PWA), Mobile (Capacitor), Desktop (Electron)
-
-### Current Database State
-
-- **Database**: SQLite via Absurd SQL (browser) and native SQLite
-  (mobile/desktop)
-- **Legacy Support**: IndexedDB (Dexie) for backward compatibility
-- **Status**: Modern database architecture fully implemented
-
-### Core Technologies
-
-- **Frontend**: Vue 3 + TypeScript + vue-facing-decorator
-- **Styling**: TailwindCSS
-- **Build**: Vite with platform-specific configs
-- **Testing**: Playwright E2E, Jest unit tests
-- **Database**: SQLite (Absurd SQL in browser), IndexedDB (legacy)
-- **State**: Pinia stores
-- **Platform Services**: Abstracted behind interfaces with factory pattern
-
-## Development Principles
-
-### Code Organization
-
-- **Platform Services**: Abstract platform-specific code behind interfaces
-- **Service Factory**: Use `PlatformServiceFactory` for platform selection
-- **Type Safety**: Strict TypeScript, no `any` types, use type guards
-- **Modern Architecture**: Use current platform service patterns
-
-### Architecture Patterns
-
-- **Dependency Injection**: Services injected via mixins and factory pattern
-- **Interface Segregation**: Small, focused interfaces over large ones
-- **Composition over Inheritance**: Prefer mixins and composition
-- **Single Responsibility**: Each component/service has one clear purpose
-
-### Testing Strategy
-
-- **E2E**: Playwright for critical user journeys
-- **Unit**: Jest with F.I.R.S.T. principles
-- **Platform Coverage**: Web + Capacitor (Pixel 5) in CI
-- **Quality Assurance**: Comprehensive testing and validation
-
-## Current Development Focus
-
-### Active Development
-
-- **Feature Development**: Build new functionality using modern platform
-  services
-- **Performance Optimization**: Improve app performance and user experience
-- **Platform Enhancement**: Leverage platform-specific capabilities
-- **Code Quality**: Maintain high standards and best practices
-
-### Development Metrics
-
-- **Code Quality**: High standards maintained across all platforms
-- **Performance**: Optimized for all target devices
-- **Testing**: Comprehensive coverage maintained
-- **User Experience**: Focus on intuitive, accessible interfaces
-
-## Platform-Specific Considerations
-
-### Web (PWA)
-
-- **QR Scanning**: WebInlineQRScanner
-- **Deep Linking**: URL parameters
-- **File System**: Limited browser APIs
-- **Build**: `npm run build:web` (development build)
-
-### Mobile (Capacitor)
-
-- **QR Scanning**: @capacitor-mlkit/barcode-scanning
-- **Deep Linking**: App URL open events
-- **File System**: Capacitor Filesystem
-- **Build**: `npm run build:capacitor`
-
-### Desktop (Electron)
-
-- **File System**: Node.js fs
-- **Build**: `npm run build:electron`
-- **Distribution**: AppImage, DEB, DMG packages
-
-## Development Workflow
-
-### Build Commands
-
-```bash
-# Web (development)
-npm run build:web
-
-# Mobile
-npm run build:capacitor
-npm run build:native
-
-# Desktop
-npm run build:electron
-npm run build:electron:appimage
-npm run build:electron:deb
-npm run build:electron:dmg
-```
-
-### Testing Commands
-
-```bash
-# Web E2E
-npm run test:web
-
-# Mobile
-npm run test:mobile
-npm run test:android
-npm run test:ios
-
-# Type checking
-npm run type-check
-npm run lint-fix
-```
-
-## Key Constraints
-
-1. **Privacy First**: User identifiers remain private except when explicitly
-   shared
-2. **Platform Compatibility**: Features must work across all target platforms
-3. **Performance**: Must remain performant on older/simpler devices
-4. **Modern Architecture**: New features should use current platform services
-5. **Offline Capability**: Key functionality should work offline when feasible
-
-## Use Cases to Support
-
-1. **Community Building**: Tools for finding others with shared interests
-2. **Project Coordination**: Easy proposal and collaboration on projects
-3. **Reputation Building**: Showcasing contributions and reliability
-4. **Governance**: Facilitating decision-making and collective governance
-
-## Resources
-
-- **Testing**: `docs/migration-testing/`
-- **Architecture**: `docs/architecture-decisions.md`
-- **Build Context**: `docs/build-modernization-context.md`
-
----
-
-## Status: Active application context
-
-- **Priority**: Critical
-- **Estimated Effort**: Ongoing reference
-- **Dependencies**: Vue 3, TypeScript, SQLite, Capacitor, Electron
-- **Stakeholders**: Development team, Product team

.cursor/rules/architectural_decision_record.mdc

@@ -0,0 +1,292 @@
+---
+description: 
+globs: 
+alwaysApply: true
+---
+# TimeSafari Cross-Platform Architecture Guide
+
+## 1. Platform Support Matrix
+
+| Feature | Web (PWA) | Capacitor (Mobile) | Electron (Desktop) | PyWebView (Desktop) |
+|---------|-----------|-------------------|-------------------|-------------------|
+| QR Code Scanning | WebInlineQRScanner | @capacitor-mlkit/barcode-scanning | Not Implemented | Not Implemented |
+| Deep Linking | URL Parameters | App URL Open Events | Not Implemented | Not Implemented |
+| File System | Limited (Browser API) | Capacitor Filesystem | Electron fs | PyWebView Python Bridge |
+| Camera Access | MediaDevices API | Capacitor Camera | Not Implemented | Not Implemented |
+| Platform Detection | Web APIs | Capacitor.isNativePlatform() | process.env checks | process.env checks |
+
+## 2. Project Structure
+
+### 2.1 Core Directories
+```
+src/
+├── components/     # Vue components
+├── services/       # Platform services and business logic
+├── views/         # Page components
+├── router/        # Vue router configuration
+├── types/         # TypeScript type definitions
+├── utils/         # Utility functions
+├── lib/           # Core libraries
+├── platforms/     # Platform-specific implementations
+├── electron/      # Electron-specific code
+├── constants/     # Application constants
+├── db/           # Database related code
+├── interfaces/    # TypeScript interfaces and type definitions
+└── assets/        # Static assets
+```
+
+### 2.2 Entry Points
+```
+src/
+├── main.ts              # Base entry
+├── main.common.ts       # Shared initialization
+├── main.capacitor.ts    # Mobile entry
+├── main.electron.ts     # Electron entry
+├── main.pywebview.ts    # PyWebView entry
+└── main.web.ts          # Web/PWA entry
+```
+
+### 2.3 Build Configurations
+```
+root/
+├── vite.config.common.mts    # Shared config
+├── vite.config.capacitor.mts # Mobile build
+├── vite.config.electron.mts  # Electron build
+├── vite.config.pywebview.mts # PyWebView build
+├── vite.config.web.mts      # Web/PWA build
+└── vite.config.utils.mts    # Build utilities
+```
+
+## 3. Service Architecture
+
+### 3.1 Service Organization
+```
+services/
+├── QRScanner/           # QR code scanning service
+│   ├── WebInlineQRScanner.ts
+│   └── interfaces.ts
+├── platforms/          # Platform-specific services
+│   ├── WebPlatformService.ts
+│   ├── CapacitorPlatformService.ts
+│   ├── ElectronPlatformService.ts
+│   └── PyWebViewPlatformService.ts
+└── factory/           # Service factories
+    └── PlatformServiceFactory.ts
+```
+
+### 3.2 Service Factory Pattern
+```typescript
+// PlatformServiceFactory.ts
+export class PlatformServiceFactory {
+  private static instance: PlatformService | null = null;
+
+  public static getInstance(): PlatformService {
+    if (!PlatformServiceFactory.instance) {
+      const platform = process.env.VITE_PLATFORM || "web";
+      PlatformServiceFactory.instance = createPlatformService(platform);
+    }
+    return PlatformServiceFactory.instance;
+  }
+}
+```
+
+## 4. Feature Implementation Guidelines
+
+### 4.1 QR Code Scanning
+
+1. **Service Interface**
+```typescript
+interface QRScannerService {
+  checkPermissions(): Promise<boolean>;
+  requestPermissions(): Promise<boolean>;
+  isSupported(): Promise<boolean>;
+  startScan(): Promise<void>;
+  stopScan(): Promise<void>;
+  addListener(listener: ScanListener): void;
+  onStream(callback: (stream: MediaStream | null) => void): void;
+  cleanup(): Promise<void>;
+}
+```
+
+2. **Platform-Specific Implementation**
+```typescript
+// WebInlineQRScanner.ts
+export class WebInlineQRScanner implements QRScannerService {
+  private scanListener: ScanListener | null = null;
+  private isScanning = false;
+  private stream: MediaStream | null = null;
+  private events = new EventEmitter();
+
+  // Implementation of interface methods
+}
+```
+
+### 4.2 Deep Linking
+
+1. **URL Structure**
+```typescript
+// Format: timesafari://<route>[/<param>][?queryParam1=value1]
+interface DeepLinkParams {
+  route: string;
+  params?: Record<string, string>;
+  query?: Record<string, string>;
+}
+```
+
+2. **Platform Handlers**
+```typescript
+// Capacitor
+App.addListener("appUrlOpen", handleDeepLink);
+
+// Web
+router.beforeEach((to, from, next) => {
+  handleWebDeepLink(to.query);
+});
+```
+
+## 5. Build Process
+
+### 5.1 Environment Configuration
+```typescript
+// vite.config.common.mts
+export function createBuildConfig(mode: string) {
+  return {
+    define: {
+      'process.env.VITE_PLATFORM': JSON.stringify(mode),
+      'process.env.VITE_PWA_ENABLED': JSON.stringify(!isNative),
+      __IS_MOBILE__: JSON.stringify(isCapacitor),
+      __USE_QR_READER__: JSON.stringify(!isCapacitor)
+    }
+  };
+}
+```
+
+### 5.2 Platform-Specific Builds
+
+```bash
+# Build commands from package.json
+"build:web": "vite build --config vite.config.web.mts",
+"build:capacitor": "vite build --config vite.config.capacitor.mts",
+"build:electron": "vite build --config vite.config.electron.mts",
+"build:pywebview": "vite build --config vite.config.pywebview.mts"
+```
+
+## 6. Testing Strategy
+
+### 6.1 Test Configuration
+```typescript
+// playwright.config-local.ts
+const config: PlaywrightTestConfig = {
+  projects: [
+    {
+      name: 'web',
+      use: { browserName: 'chromium' }
+    },
+    {
+      name: 'mobile',
+      use: { ...devices['Pixel 5'] }
+    }
+  ]
+};
+```
+
+### 6.2 Platform-Specific Tests
+```typescript
+test('QR scanning works on mobile', async ({ page }) => {
+  test.skip(!process.env.MOBILE_TEST, 'Mobile-only test');
+  // Test implementation
+});
+```
+
+## 7. Error Handling
+
+### 7.1 Global Error Handler
+```typescript
+function setupGlobalErrorHandler(app: VueApp) {
+  app.config.errorHandler = (err, instance, info) => {
+    logger.error("[App Error]", {
+      error: err,
+      info,
+      component: instance?.$options.name
+    });
+  };
+}
+```
+
+### 7.2 Platform-Specific Error Handling
+```typescript
+// API error handling for Capacitor
+if (process.env.VITE_PLATFORM === 'capacitor') {
+  logger.error(`[Capacitor API Error] ${endpoint}:`, {
+    message: error.message,
+    status: error.response?.status
+  });
+}
+```
+
+## 8. Best Practices
+
+### 8.1 Code Organization
+- Use platform-specific directories for unique implementations
+- Share common code through service interfaces
+- Implement feature detection before using platform capabilities
+- Keep platform-specific code isolated in dedicated directories
+- Use TypeScript interfaces for cross-platform compatibility
+
+### 8.2 Platform Detection
+```typescript
+const platformService = PlatformServiceFactory.getInstance();
+const capabilities = platformService.getCapabilities();
+
+if (capabilities.hasCamera) {
+  // Implement camera features
+}
+```
+
+### 8.3 Feature Implementation
+1. Define platform-agnostic interface
+2. Create platform-specific implementations
+3. Use factory pattern for instantiation
+4. Implement graceful fallbacks
+5. Add comprehensive error handling
+6. Use dependency injection for better testability
+
+## 9. Dependency Management
+
+### 9.1 Platform-Specific Dependencies
+```json
+{
+  "dependencies": {
+    "@capacitor/core": "^6.2.0",
+    "electron": "^33.2.1",
+    "vue": "^3.4.0"
+  }
+}
+```
+
+### 9.2 Conditional Loading
+```typescript
+if (process.env.VITE_PLATFORM === 'capacitor') {
+  await import('@capacitor/core');
+}
+```
+
+## 10. Security Considerations
+
+### 10.1 Permission Handling
+```typescript
+async checkPermissions(): Promise<boolean> {
+  if (platformService.isCapacitor()) {
+    return await checkNativePermissions();
+  }
+  return await checkWebPermissions();
+}
+```
+
+### 10.2 Data Storage
+- Use secure storage mechanisms for sensitive data
+- Implement proper encryption for stored data
+- Follow platform-specific security guidelines
+- Regular security audits and updates
+
+This document should be updated as new features are added or platform-specific implementations change. Regular reviews ensure it remains current with the codebase.

.cursor/rules/asset_configuration.mdc

@@ -1,61 +0,0 @@
----
-description: when doing anything with capacitor assets
-alwaysApply: false
----
-# Asset Configuration Directive
-
-**Author**: Matthew Raymer
-**Date**: 2025-08-19
-**Status**: 🎯 **ACTIVE** - Asset management guidelines
-
-*Scope: Assets Only (icons, splashes, image pipelines) — not overall build
-orchestration*
-
-## Intent
-
-- Version **asset configuration files** (optionally dev-time generated).
-- **Do not** version platform asset outputs (Android/iOS/Electron); generate
-  them **at build-time** with standard tools.
-- Keep existing per-platform build scripts unchanged.
-
-## Source of Truth
-
-- **Preferred (Capacitor default):** `resources/` as the single master source.
-- **Alternative:** `assets/` is acceptable **only** if `capacitor-assets` is
-  explicitly configured to read from it.
-- **Never** maintain both `resources/` and `assets/` as parallel sources.
-  Migrate and delete the redundant folder.
-
-## Config Files
-
-- Live under: `config/assets/` (committed).
-- Examples:
-  - `config/assets/capacitor-assets.config.json` (or the path the tool
-    expects)
-  - `config/assets/android.assets.json`
-  - `config/assets/ios.assets.json`
-  - `config/assets/common.assets.yaml` (optional shared layer)
-- **Dev-time generation allowed** for these configs; **build-time
-  generation is forbidden**.
-
-## Build-Time Behavior
-
-- Build generates platform assets (not configs) using the standard chain:
-
-```bash
-npm run build:capacitor        # web build via Vite (.mts)
-npx cap sync
-npx capacitor-assets generate  # produces platform assets; not committed
-# then platform-specific build steps
-```
-
----
-
-**Status**: Active asset management directive
-**Priority**: Medium
-**Estimated Effort**: Ongoing reference
-**Dependencies**: capacitor-assets toolchain
-**Stakeholders**: Development team, Build team
-
-  npx capacitor-assets generate  # produces platform assets; not committed
-  # then platform-specific build steps

.cursor/rules/base_context.mdc

@@ -1,154 +0,0 @@
----
-alwaysApply: true
----
-```json
-{
-  "coaching_level": "standard",
-  "socratic_max_questions": 7,
-  "verbosity": "normal",
-  "timebox_minutes": null,
-  "format_enforcement": "strict"
-}
-```
-
-# Base Context — Human Competence First
-
-**Author**: Matthew Raymer
-**Date**: 2025-08-19
-**Status**: 🎯 **ACTIVE** - Core interaction guidelines
-
-## Purpose
-
-All interactions must *increase the human's competence over time* while
-completing the task efficiently. The model may handle menial work and memory
-extension, but must also promote learning, autonomy, and healthy work habits.
-The model should also **encourage human interaction and collaboration** rather
-than replacing it — outputs should be designed to **facilitate human discussion,
-decision-making, and creativity**, not to atomize tasks into isolated, purely
-machine-driven steps.
-
-## Principles
-
-1. Competence over convenience: finish the task *and* leave the human more
-   capable next time.
-2. Mentorship, not lectures: be concise, concrete, and immediately applicable.
-3. Transparency: show assumptions, limits, and uncertainty; cite when
-   non-obvious.
-4. Optional scaffolding: include small, skimmable learning hooks that do not
-   bloat output.
-5. Time respect: default to **lean output**; offer opt-in depth via toggles.
-6. Psychological safety: encourage, never condescend; no medical/clinical
-   advice. No censorship!
-7. Reusability: structure outputs so they can be saved, searched, reused, and
-   repurposed.
-8. **Collaborative Bias**: Favor solutions that invite human review,
-   discussion, and iteration. When in doubt, ask "Who should this be shown
-   to?" or "Which human input would improve this?"
-
-## Toggle Definitions
-
-### coaching_level
-
-Determines the depth of learning support: `light` (short hooks),
-`standard` (balanced), `deep` (detailed).
-
-### socratic_max_questions
-
-The number of clarifying questions the model may ask before proceeding.
-If >0, questions should be targeted, minimal, and followed by reasonable
-assumptions if unanswered.
-
-### verbosity
-
-'terse' (just a sentence), `concise` (minimum commentary), `normal`
-(balanced explanation), or other project-defined levels.
-
-### timebox_minutes
-
-*integer or null* — When set to a positive integer (e.g., `5`), this acts
-as a **time budget** guiding the model to prioritize delivering the most
-essential parts of the task within that constraint.
-
-Behavior when set:
-
-1. **Prioritize Core Output** — Deliver the minimum viable solution or
-   result first.
-2. **Limit Commentary** — Competence Hooks and Collaboration Hooks must be
-   shorter than normal.
-3. **Signal Skipped Depth** — Omitted details should be listed under
-   *Deferred for depth*.
-4. **Order by Value** — Start with blocking or high-value items, then
-   proceed to nice-to-haves if budget allows.
-
-If `null`, there is no timebox — the model can produce full-depth
-responses.
-
-### format_enforcement
-
-`strict` (reject outputs with format drift) or `relaxed` (minor deviations
-acceptable).
-
-## Modes (select or combine)
-
-- **Doer**: produce the artifact fast, minimal commentary.
-- **Mentor**: add short "why/how" notes + next-step pointers.
-- **Socratic**: ask up to N targeted questions when requirements are
-  ambiguous.
-- **Pair-Programmer/Pair-Writer**: explain tradeoffs as you implement.
-- **Facilitator**: structure output to be reviewable, commentable, and
-  ready for group discussion.
-
-Default: Doer + short Mentor notes.
-
-## Competence & Collaboration Levers (keep lightweight)
-
-- "Why this works" (≤3 bullets)
-- "Common pitfalls" (≤3 bullets)
-- "Next skill unlock" (1 tiny action or reading)
-- "Teach-back" (1 sentence prompt the human can answer to self-check)
-- "Discussion prompts" (≤2 short questions for peers/stakeholders)
-
-## Output Contract (apply to every deliverable)
-
-- Clear **Objective** (1 line)
-- **Result** (artifact/code/answer)
-- **Use/Run** (how to apply/test)
-- **Competence Hooks** (the 4 learning levers above, kept terse)
-- **Collaboration Hooks** (discussion prompts or group review steps)
-- **Assumptions & Limits**
-- **References** (if used; links or titles)
-
-## Do-Not
-
-- No filler, hedging, or moralizing.
-- No medical/mental-health advice; keep "healthy habits" to general work
-  practices.
-- No invented facts; mark uncertainty plainly.
-- No censorship.
-- Avoid outputs that bypass human review when such review is valuable.
-
-## Related Rulesets
-
-- **software_development.mdc**: For software-specific development practices
-- **research_diagnostic.mdc**: For investigation and research workflows
-
-## Self-Check (model, before responding)
-
-- [ ] Task done *and* at least one competence lever included (≤120 words
-  total).
-- [ ] At least one collaboration/discussion hook present.
-- [ ] Output follows the **Output Contract** sections.
-- [ ] Toggles respected; verbosity remains concise.
-- [ ] Uncertainties/assumptions surfaced.
-- [ ] No disallowed content.
-
----
-
-**Status**: Active core guidelines
-**Priority**: Critical
-**Estimated Effort**: Ongoing reference
-**Dependencies**: None (base ruleset)
-**Stakeholders**: All AI interactions
-
-- [ ] Uncertainties/assumptions surfaced.
-- [ ] No disallowed content.

.cursor/rules/crowd-funder-for-time-pwa/docs/camera-implementation.mdc

@@ -1,13 +1,13 @@
 ---
-description: when dealing with cameras in the application
+description: 
+globs: 
 alwaysApply: false
 ---
 # Camera Implementation Documentation
 
 ## Overview
 
-This document describes how camera functionality is implemented across the
-TimeSafari application. The application uses cameras for two main purposes:
+This document describes how camera functionality is implemented across the TimeSafari application. The application uses cameras for two main purposes:
 
 1. QR Code scanning
 2. Photo capture
@@ -219,4 +219,4 @@ Desktop implementation (currently unimplemented).
 - Multiple browsers
 - iOS and Android devices
 - Desktop platforms
-- Various network conditions
+- Various network conditions 

.cursor/rules/database/legacy_dexie.mdc

@@ -1,8 +0,0 @@
----
-globs: **/databaseUtil.ts,**/AccountViewView.vue,**/ContactsView.vue,**/DatabaseMigration.vue,**/NewIdentifierView.vue
-alwaysApply: false
----
-# What to do with Dexie
-
-All references in the codebase to Dexie apply only to migration from IndexedDb to
-Sqlite and will be deprecated in future versions.

.cursor/rules/development/development_guide.mdc

@@ -1,9 +0,0 @@
----
-globs: **/src/**/*
-alwaysApply: false
----
-✅ use system date command to timestamp all interactions with accurate date and time
-✅ python script files must always have a blank line at their end
-✅ remove whitespace at the end of lines
-✅ use npm run lint-fix to check for warnings
-✅ do not use npm run dev let me handle running and supplying feedback

.cursor/rules/development/type_safety_guide.mdc

@@ -1,139 +0,0 @@
----
-description: when dealing with types and Typesript
-alwaysApply: false
----
-```json
-{
-  "coaching_level": "light",
-  "socratic_max_questions": 7,
-  "verbosity": "concise",
-  "timebox_minutes": null,
-  "format_enforcement": "strict"
-}
-```
-
-# TypeScript Type Safety Guidelines
-
-**Author**: Matthew Raymer
-**Date**: 2025-08-19
-**Status**: 🎯 **ACTIVE** - Type safety enforcement
-
-## Overview
-
-Practical rules to keep TypeScript strict and predictable. Minimize exceptions.
-
-## Core Rules
-
-1. **No `any`**
-   - Use explicit types. If unknown, use `unknown` and **narrow** via guards.
-
-2. **Error handling uses guards**
-   - Reuse guards from `src/interfaces/**` (e.g., `isDatabaseError`,
-     `isApiError`).
-   - Catch with `unknown`; never cast to `any`.
-
-3. **Dynamic property access is type‑safe**
-   - Use `keyof` + `in` checks:
-
-     ```ts
-     obj[k as keyof typeof obj]
-     ```
-
-   - Avoid `(obj as any)[k]`.
-
-## Type Safety Enforcement
-
-### Core Type Safety Rules
-
-- **No `any` Types**: Use explicit types or `unknown` with proper type guards
-- **Error Handling Uses Guards**: Implement and reuse type guards from `src/interfaces/**`
-- **Dynamic Property Access**: Use `keyof` + `in` checks for type-safe property access
-
-### Type Guard Patterns
-- **API Errors**: Use `isApiError(error)` guards for API error handling
-- **Database Errors**: Use `isDatabaseError(error)` guards for database operations
-- **Axios Errors**: Implement `isAxiosError(error)` guards for HTTP error handling
-
-### Implementation Guidelines
-- **Avoid Type Assertions**: Replace `as any` with proper type guards and interfaces
-- **Narrow Types Properly**: Use type guards to narrow `unknown` types safely
-- **Document Type Decisions**: Explain complex type structures and their purpose
-
-## Minimal Special Cases (document in PR when used)
-
-- **Vue refs / instances**: Use `ComponentPublicInstance` or specific
-  component types for dynamic refs.
-- **3rd‑party libs without types**: Narrow immediately to a **known
-  interface**; do not leave `any` hanging.
-
-## Patterns (short)
-
-### Database errors
-
-```ts
-try { await this.$addContact(contact); }
-catch (e: unknown) {
-  if (isDatabaseError(e) && e.message.includes("Key already exists")) {
-    /* handle duplicate */
-  }
-}
-```
-
-### API errors
-
-```ts
-try { await apiCall(); }
-catch (e: unknown) {
-  if (isApiError(e)) {
-    const msg = e.response?.data?.error?.message;
-  }
-}
-```
-
-### Dynamic keys
-
-```ts
-const keys = Object.keys(newSettings).filter(
-  k => k in newSettings && newSettings[k as keyof typeof newSettings] !== undefined
-);
-```
-
-## Checklists
-
-**Before commit**
-
-- [ ] No `any` (except documented, justified cases)
-- [ ] Errors handled via guards
-- [ ] Dynamic access uses `keyof`/`in`
-- [ ] Imports point to correct interfaces/types
-
-**Code review**
-
-- [ ] Hunt hidden `as any`
-- [ ] Guard‑based error paths verified
-- [ ] Dynamic ops are type‑safe
-- [ ] Prefer existing types over re‑inventing
-
-## Tools
-
-- `npm run lint-fix` — lint & auto‑fix
-- `npm run type-check` — strict type compilation (CI + pre‑release)
-- IDE: enable strict TS, ESLint/TS ESLint, Volar (Vue 3)
-
-## References
-
-- TS Handbook — https://www.typescriptlang.org/docs/
-- TS‑ESLint — https://typescript-eslint.io/rules/
-- Vue 3 + TS — https://vuejs.org/guide/typescript/
-
----
-
-**Status**: Active type safety guidelines
-**Priority**: High
-**Estimated Effort**: Ongoing reference
-**Dependencies**: TypeScript, ESLint, Vue 3
-**Stakeholders**: Development team
-
-- TS Handbook — https://www.typescriptlang.org/docs/
-- TS‑ESLint — https://typescript-eslint.io/rules/
-- Vue 3 + TS — https://vuejs.org/guide/typescript/

.cursor/rules/docs/documentation.mdc

@@ -1,14 +0,0 @@
----
-alwaysApply: true
----
-# Directive for Documentation Generation
-
-1. Produce a **small, focused set of documents** rather than an overwhelming volume.
-2. Ensure the content is **maintainable and worth preserving**, so that humans
-are motivated to keep it up to date.
-3. Prioritize **educational value**: the documents must clearly explain the
-workings of the system.
-4. Avoid **shallow, generic, or filler explanations** often found in
-AI-generated documentation.
-5. Aim for **clarity, depth, and usefulness**, so readers gain genuine understanding.
-6. Always check the local system date to determine current date.

.cursor/rules/docs/markdown.mdc

@@ -1,332 +0,0 @@
----
-globs: *.md
-alwaysApply: false
----
-# Cursor Markdown Ruleset for TimeSafari Documentation
-
-## Overview
-
-This ruleset enforces consistent markdown formatting standards across all project
-documentation, ensuring readability, maintainability, and compliance with
-markdownlint best practices.
-
-## General Formatting Standards
-
-### Line Length
-
-- **Maximum line length**: 80 characters
-- **Exception**: Code blocks (JSON, shell, TypeScript, etc.) - no line length
-  enforcement
-- **Rationale**: Ensures readability across different screen sizes and terminal
-  widths
-
-### Blank Lines
-
-- **Headings**: Must be surrounded by blank lines above and below
-- **Lists**: Must be surrounded by blank lines above and below
-- **Code blocks**: Must be surrounded by blank lines above and below
-- **Maximum consecutive blank lines**: 1 (no multiple blank lines)
-- **File start**: No blank lines at the beginning of the file
-- **File end**: Single newline character at the end
-
-### Whitespace
-
-- **No trailing spaces**: Remove all trailing whitespace from lines
-- **No tabs**: Use spaces for indentation
-- **Consistent indentation**: 2 spaces for list items and nested content
-
-## Heading Standards
-
-### Format
-
-- **Style**: ATX-style headings (`#`, `##`, `###`, etc.)
-- **Case**: Title case for general headings
-- **Code references**: Use backticks for file names and technical terms
-  - ✅ `### Current package.json Scripts`
-  - ❌ `### Current Package.json Scripts`
-
-### Hierarchy
-
-- **H1 (#)**: Document title only
-- **H2 (##)**: Major sections
-- **H3 (###)**: Subsections
-- **H4 (####)**: Sub-subsections
-- **H5+**: Avoid deeper nesting
-
-## List Standards
-
-### Unordered Lists
-
-- **Marker**: Use `-` (hyphen) consistently
-- **Indentation**: 2 spaces for nested items
-- **Blank lines**: Surround lists with blank lines
-
-### Ordered Lists
-
-- **Format**: `1.`, `2.`, `3.` (sequential numbering)
-- **Indentation**: 2 spaces for nested items
-- **Blank lines**: Surround lists with blank lines
-
-### Task Lists
-
-- **Format**: `- [ ]` for incomplete, `- [x]` for complete
-- **Use case**: Project planning, checklists, implementation tracking
-
-## Code Block Standards
-
-### Fenced Code Blocks
-
-- **Syntax**: Triple backticks with language specification
-- **Languages**: `json`, `bash`, `typescript`, `javascript`, `yaml`, `markdown`
-- **Blank lines**: Must be surrounded by blank lines above and below
-- **Line length**: No enforcement within code blocks
-
-### Inline Code
-
-- **Format**: Single backticks for inline code references
-- **Use case**: File names, commands, variables, properties
-
-## Special Content Standards
-
-### JSON Examples
-
-```json
-{
-  "property": "value",
-  "nested": {
-    "property": "value"
-  }
-}
-```
-
-### Shell Commands
-
-```bash
-# Command with comment
-npm run build:web
-
-# Multi-line command
-VITE_GIT_HASH=`git log -1 --pretty=format:%h` \
-  vite build --config vite.config.web.mts
-```
-
-### TypeScript Examples
-
-```typescript
-// Function with JSDoc
-/**
- * Get environment configuration
- * @param env - Environment name
- * @returns Environment config object
- */
-const getEnvironmentConfig = (env: string) => {
-  switch (env) {
-    case 'prod':
-      return { /* production settings */ };
-    default:
-      return { /* development settings */ };
-  }
-};
-```
-
-## File Structure Standards
-
-### Document Header
-
-```markdown
-# Document Title
-
-**Author**: Matthew Raymer
-**Date**: YYYY-MM-DD
-**Status**: 🎯 **STATUS** - Brief description
-
-## Overview
-
-Brief description of the document's purpose and scope.
-```
-
-### Section Organization
-
-1. **Overview/Introduction**
-2. **Current State Analysis**
-3. **Implementation Plan**
-4. **Technical Details**
-5. **Testing & Validation**
-6. **Next Steps**
-
-## Markdownlint Configuration
-
-### Required Rules
-
-```json
-{
-  "MD013": { "code_blocks": false },
-  "MD012": true,
-  "MD022": true,
-  "MD031": true,
-  "MD032": true,
-  "MD047": true,
-  "MD009": true
-}
-```
-
-### Rule Explanations
-
-- **MD013**: Line length (disabled for code blocks)
-- **MD012**: No multiple consecutive blank lines
-- **MD022**: Headings should be surrounded by blank lines
-- **MD031**: Fenced code blocks should be surrounded by blank lines
-- **MD032**: Lists should be surrounded by blank lines
-- **MD047**: Files should end with a single newline
-- **MD009**: No trailing spaces
-
-## Validation Commands
-
-### Check Single File
-
-```bash
-npx markdownlint docs/filename.md
-```
-
-### Check All Documentation
-
-```bash
-npx markdownlint docs/
-```
-
-### Auto-fix Common Issues
-
-```bash
-# Remove trailing spaces
-sed -i 's/[[:space:]]*$//' docs/filename.md
-
-# Remove multiple blank lines
-sed -i '/^$/N;/^\n$/D' docs/filename.md
-
-# Add newline at end if missing
-echo "" >> docs/filename.md
-```
-
-## Common Patterns
-
-### Implementation Plans
-
-```markdown
-## Implementation Plan
-
-### Phase 1: Foundation (Day 1)
-
-#### 1.1 Component Setup
-
-- [ ] Create new component file
-- [ ] Add basic structure
-- [ ] Implement core functionality
-
-#### 1.2 Configuration
-
-- [ ] Update configuration files
-- [ ] Add environment variables
-- [ ] Test configuration loading
-```
-
-### Status Tracking
-
-```markdown
-**Status**: ✅ **COMPLETE** - All phases finished
-**Progress**: 75% (15/20 components)
-**Next**: Ready for testing phase
-```
-
-### Performance Metrics
-
-```markdown
-#### 📊 Performance Metrics
-- **Build Time**: 2.3 seconds (50% faster than baseline)
-- **Bundle Size**: 1.2MB (30% reduction)
-- **Success Rate**: 100% (no failures in 50 builds)
-```
-
-## Enforcement
-
-### Pre-commit Hooks
-
-- Run markdownlint on all changed markdown files
-- Block commits with linting violations
-- Auto-fix common issues when possible
-
-### CI/CD Integration
-
-- Include markdownlint in build pipeline
-- Generate reports for documentation quality
-- Fail builds with critical violations
-
-### Team Guidelines
-
-- All documentation PRs must pass markdownlint
-- Use provided templates for new documents
-- Follow established patterns for consistency
-
-## Templates
-
-### New Document Template
-
-```markdown
-# Document Title
-
-**Author**: Matthew Raymer
-**Date**: YYYY-MM-DD
-**Status**: 🎯 **PLANNING** - Ready for Implementation
-
-## Overview
-
-Brief description of the document's purpose and scope.
-
-## Current State
-
-Description of current situation or problem.
-
-## Implementation Plan
-
-### Phase 1: Foundation
-
-- [ ] Task 1
-- [ ] Task 2
-
-## Next Steps
-
-1. **Review and approve plan**
-2. **Begin implementation**
-3. **Test and validate**
-
----
-
-**Status**: Ready for implementation
-**Priority**: Medium
-**Estimated Effort**: X days
-**Dependencies**: None
-**Stakeholders**: Development team
-```
-
----
-
-**Last Updated**: 2025-07-09
-**Version**: 1.0
-**Maintainer**: Matthew Raymer
-
-
-### Heading Uniqueness
-
-- **Rule**: No duplicate heading content at the same level
-- **Scope**: Within a single document
-- **Rationale**: Maintains clear document structure and navigation
-- **Example**:
-
-  ```markdown
-  ## Features        ✅
-  ### Authentication
-  ### Authorization
-
-  ## Features        ❌ (Duplicate heading)
-  ### Security
-  ### Performance
-  ```

.cursor/rules/investigation_report_example.mdc

@@ -1,117 +0,0 @@
-# Investigation Report Example
-
-**Author**: Matthew Raymer
-**Date**: 2025-08-19
-**Status**: 🎯 **ACTIVE** - Investigation methodology example
-
-## Investigation — Registration Dialog Test Flakiness
-
-## Objective
-
-Identify root cause of flaky tests related to registration dialogs in contact
-import scenarios.
-
-## System Map
-
-- User action → ContactInputForm → ContactsView.addContact() →
-  handleRegistrationPrompt()
-- setTimeout(1000ms) → Modal dialog → User response → Registration API call
-- Test execution → Wait for dialog → Assert dialog content → Click response
-  button
-
-## Findings (Evidence)
-
-- **1-second timeout causes flakiness** — evidence:
-  `src/views/ContactsView.vue:971-1000`; setTimeout(..., 1000) in
-  handleRegistrationPrompt()
-- **Import flow bypasses dialogs** — evidence:
-  `src/views/ContactImportView.vue:500-520`; importContacts() calls
-  $insertContact() directly, no handleRegistrationPrompt()
-- **Dialog only appears in direct add flow** — evidence:
-  `src/views/ContactsView.vue:774-800`; addContact() calls
-  handleRegistrationPrompt() after database insert
-
-## Hypotheses & Failure Modes
-
-- H1: 1-second timeout makes dialog appearance unpredictable; would fail when
-  tests run faster than 1000ms
-- H2: Test environment timing differs from development; watch for CI vs local
-  test differences
-
-## Corrections
-
-- Updated: "Multiple dialogs interfere with imports" → "Import flow never
-  triggers dialogs - they only appear in direct contact addition"
-- Updated: "Complex batch registration needed" → "Simple timeout removal and
-  test mode flag sufficient"
-
-## Diagnostics (Next Checks)
-
-- [ ] Repro on CI environment vs local
-- [ ] Measure actual dialog appearance timing
-- [ ] Test with setTimeout removed
-- [ ] Verify import flow doesn't call handleRegistrationPrompt
-
-## Risks & Scope
-
-- Impacted: Contact addition tests, registration workflow tests; Data: None;
-  Users: Test suite reliability
-
-## Decision / Next Steps
-
-- Owner: Development Team; By: 2025-01-28
-- Action: Remove 1-second timeout + add test mode flag; Exit criteria: Tests
-  pass consistently
-
-## References
-
-- `src/views/ContactsView.vue:971-1000`
-- `src/views/ContactImportView.vue:500-520`
-- `src/views/ContactsView.vue:774-800`
-
-## Competence Hooks
-
-- Why this works: Code path tracing revealed separate execution flows,
-  evidence disproved initial assumptions
-- Common pitfalls: Assuming related functionality without tracing execution
-  paths, over-engineering solutions to imaginary problems
-- Next skill: Learn to trace code execution before proposing architectural
-  changes
-- Teach-back: "What evidence shows that contact imports bypass registration
-  dialogs?"
-
-## Key Learning Points
-
-### Evidence-First Approach
-
-This investigation demonstrates the importance of:
-
-1. **Tracing actual code execution** rather than making assumptions
-2. **Citing specific evidence** with file:line references
-3. **Validating problem scope** before proposing solutions
-4. **Considering simpler alternatives** before complex architectural changes
-
-### Code Path Tracing Value
-
-By tracing the execution paths, we discovered:
-
-- Import flow and direct add flow are completely separate
-- The "multiple dialog interference" problem didn't exist
-- A simple timeout removal would solve the actual issue
-
-### Prevention of Over-Engineering
-
-The investigation prevented:
-
-- Unnecessary database schema changes
-- Complex batch registration systems
-- Migration scripts for non-existent problems
-- Architectural changes based on assumptions
-
----
-
-**Status**: Active investigation methodology
-**Priority**: High
-**Estimated Effort**: Ongoing reference
-**Dependencies**: software_development.mdc
-**Stakeholders**: Development team, QA team

.cursor/rules/logging_standards.mdc

@@ -1,222 +0,0 @@
-# Agent Contract — TimeSafari Logging (Unified, MANDATORY)
-
-**Author**: Matthew Raymer
-**Date**: 2025-08-19
-**Status**: 🎯 **ACTIVE** - Mandatory logging standards
-
-## Overview
-
-This document defines unified logging standards for the TimeSafari project,
-ensuring consistent, rest-parameter logging style using the project logger.
-No `console.*` methods are allowed in production code.
-
-## Scope and Goals
-
-**Scope**: Applies to all diffs and generated code in this workspace unless
-explicitly exempted below.
-
-**Goal**: One consistent, rest-parameter logging style using the project
-logger; no `console.*` in production code.
-
-## Non‑Negotiables (DO THIS)
-
-- You **MUST** use the project logger; **DO NOT** use any `console.*`
-  methods.
-- Import exactly as:
-  - `import { logger } from '@/utils/logger'`
-  - If `@` alias is unavailable, compute the correct relative path (do not
-    fail).
-- Call signatures use **rest parameters**: `logger.info(message, ...args)`
-- Prefer primitives/IDs and small objects in `...args`; **never build a
-  throwaway object** just to "wrap context".
-- Production defaults: Web = `warn+`, Electron = `error`, Dev/Capacitor =
-  `info+` (override via `VITE_LOG_LEVEL`).
-- **Database persistence**: `info|warn|error` are persisted; `debug` is not.
-  Use `logger.toDb(msg, level?)` for DB-only.
-
-## Available Logger API (Authoritative)
-
-- `logger.debug(message, ...args)` — verbose internals, timings, input/output
-  shapes
-- `logger.log(message, ...args)` — synonym of `info` for general info
-- `logger.info(message, ...args)` — lifecycle, state changes, success paths
-- `logger.warn(message, ...args)` — recoverable issues, retries, degraded mode
-- `logger.error(message, ...args)` — failures, thrown exceptions, aborts
-- `logger.toDb(message, level?)` — DB-only entry (default level = `info`)
-- `logger.toConsoleAndDb(message, isError)` — console + DB (use sparingly)
-- `logger.withContext(componentName)` — returns a scoped logger
-
-## Level Guidelines (Use These Heuristics)
-
-### DEBUG
-
-Use for method entry/exit, computed values, filters, loops, retries, and
-external call payload sizes.
-
-```typescript
-logger.debug('[HomeView] reloadFeedOnChange() called');
-logger.debug('[HomeView] Current filter settings', 
-  settings.filterFeedByVisible, 
-  settings.filterFeedByNearby, 
-  settings.searchBoxes?.length ?? 0);
-logger.debug('[FeedFilters] Toggling nearby filter', 
-  this.isNearby, this.settingChanged, this.activeDid);
-```
-
-**Avoid**: Vague messages (`'Processing data'`).
-
-### INFO
-
-Use for user-visible lifecycle and completed operations.
-
-```typescript
-logger.info('[StartView] Component mounted', process.env.VITE_PLATFORM);
-logger.info('[StartView] User selected new seed generation');
-logger.info('[SearchAreaView] Search box stored', 
-  searchBox.name, searchBox.bbox);
-logger.info('[ContactQRScanShowView] Contact registration OK', 
-  contact.did);
-```
-
-**Avoid**: Diagnostic details that belong in `debug`.
-
-### WARN
-
-Use for recoverable issues, fallbacks, unexpected-but-handled conditions.
-
-```typescript
-logger.warn('[ContactQRScanShowView] Invalid scan result – no value', 
-  resultType);
-logger.warn('[ContactQRScanShowView] Invalid QR format – no JWT in URL');
-logger.warn('[ContactQRScanShowView] JWT missing "own" field');
-```
-
-**Avoid**: Hard failures (those are `error`).
-
-### ERROR
-
-Use for unrecoverable failures, data integrity issues, and thrown
-exceptions.
-
-```typescript
-logger.error('[HomeView Settings] initializeIdentity() failed', err);
-logger.error('[StartView] Failed to load initialization data', error);
-logger.error('[ContactQRScanShowView] Error processing contact QR', 
-  error, rawValue);
-```
-
-**Avoid**: Expected user cancels (use `info`/`debug`).
-
-## Context Hygiene (Consistent, Minimal, Helpful)
-
-- **Component context**: Prefer scoped logger.
-
-```typescript
-const log = logger.withContext('UserService');
-log.info('User created', userId);
-log.error('Failed to create user', error);
-```
-
-If not using `withContext`, prefix message with `[ComponentName]`.
-
-- **Emojis**: Optional and minimal for visual scanning. Recommended set:
-  - Start/finish: 🚀 / ✅
-  - Retry/loop: 🔄
-  - External call: 📡
-  - Data/metrics: 📊
-  - Inspection: 🔍
-
-- **Sensitive data**: Never log secrets (tokens, keys, passwords) or
-  payloads >10KB. Prefer IDs over objects; redact/hash when needed.
-
-## Migration — Auto‑Rewrites (Apply Every Time)
-
-- Exact transforms:
-  - `console.debug(...)` → `logger.debug(...)`
-  - `console.log(...)` → `logger.log(...)` (or `logger.info(...)` when
-    clearly stateful)
-  - `console.info(...)` → `logger.info(...)`
-  - `console.warn(...)` → `logger.warn(...)`
-  - `console.error(...)` → `logger.error(...)`
-
-- Multi-arg handling:
-  - First arg becomes `message` (stringify safely if non-string).
-  - Remaining args map 1:1 to `...args`:
-    `console.info(msg, a, b)` → `logger.info(String(msg), a, b)`
-
-- Sole `Error`:
-  - `console.error(err)` → `logger.error(err.message, err)`
-
-- **Object-wrapping cleanup**: Replace `{{ userId, meta }}` wrappers with
-  separate args:
-  `logger.info('User signed in', userId, meta)`
-
-## DB Logging Rules
-
-- `debug` **never** persists automatically.
-- `info|warn|error` persist automatically.
-- For DB-only events (no console), call `logger.toDb('Message',
-  'info'|'warn'|'error')`.
-
-## Exceptions (Tightly Scoped)
-
-Allowed paths (still prefer logger):
-
-- `**/*.test.*`, `**/*.spec.*`
-- `scripts/dev/**`, `scripts/migrate/**`
-
-To intentionally keep `console.*`, add a pragma on the previous line:
-
-```typescript
-// cursor:allow-console reason="short justification"
-console.log('temporary output');
-```
-
-Without the pragma, rewrite to `logger.*`.
-
-## CI & Diff Enforcement
-
-- Do not introduce `console.*` anywhere outside allowed, pragma'd spots.
-- If an import is missing, insert it and resolve alias/relative path
-  correctly.
-- Enforce rest-parameter call shape in reviews; replace object-wrapped
-  context.
-- Ensure environment log level rules remain intact (`VITE_LOG_LEVEL`
-  respected).
-
-## Quick Before/After
-
-### **Before**
-
-```typescript
-console.log('User signed in', user.id, meta);
-console.error('Failed to update profile', err);
-console.info('Filter toggled', this.hasVisibleDid);
-```
-
-### **After**
-
-```typescript
-import { logger } from '@/utils/logger';
-
-logger.info('User signed in', user.id, meta);
-logger.error('Failed to update profile', err);
-logger.debug('[FeedFilters] Filter toggled', this.hasVisibleDid);
-```
-
-## Checklist (for every PR)
-
-- [ ] No `console.*` (or properly pragma'd in the allowed locations)
-- [ ] Correct import path for `logger`
-- [ ] Rest-parameter call shape (`message, ...args`)
-- [ ] Right level chosen (debug/info/warn/error)
-- [ ] No secrets / oversized payloads / throwaway context objects
-- [ ] Component context provided (scoped logger or `[Component]` prefix)
-
----
-
-**Status**: Active and enforced
-**Priority**: Critical
-**Estimated Effort**: Ongoing reference
-**Dependencies**: TimeSafari logger utility
-**Stakeholders**: Development team, Code review team

.cursor/rules/research_diagnostic.mdc

@@ -1,174 +0,0 @@
----
-description: Use this workflow when doing **pre-implementation research, defect investigations with uncertain repros, or clarifying system architecture and behaviors**.
-alwaysApply: false
----
-```json
-{
-  "coaching_level": "light",
-  "socratic_max_questions": 2,
-  "verbosity": "concise",
-  "timebox_minutes": null,
-  "format_enforcement": "strict"
-}
-```
-
-# Research & Diagnostic Workflow (R&D)
-
-## Purpose
-
-Provide a **repeatable, evidence-first** workflow to investigate features and
-defects **before coding**. Outputs are concise reports, hypotheses, and next
-steps—**not** code changes.
-
-## When to Use
-
-- Pre-implementation research for new features
-- Defect investigations (repros uncertain, user-specific failures)
-- Architecture/behavior clarifications (e.g., auth flows, merges, migrations)
-
----
-
-## Enhanced with Software Development Ruleset
-
-When investigating software issues, also apply:
-
-- **Code Path Tracing**: Required for technical investigations
-- **Evidence Validation**: Ensure claims are code-backed
-- **Solution Complexity Assessment**: Justify architectural changes
-
----
-
-## Output Contract (strict)
-
-1) **Objective** — 1–2 lines
-2) **System Map (if helpful)** — short diagram or bullet flow (≤8 bullets)
-3) **Findings (Evidence-linked)** — bullets; each with file/function refs
-4) **Hypotheses & Failure Modes** — short list, each testable
-5) **Corrections** — explicit deltas from earlier assumptions (if any)
-6) **Diagnostics** — what to check next (logs, DB, env, repro steps)
-7) **Risks & Scope** — what could break; affected components
-8) **Decision/Next Steps** — what we'll do, who's involved, by when
-9) **References** — code paths, ADRs, docs
-10) **Competence & Collaboration Hooks** — brief, skimmable
-
-> Keep total length lean. Prefer links and bullets over prose.
-
----
-
-## Quickstart Template
-
-Copy/paste and fill:
-
-```md
-# Investigation — <short title>
-
-## Objective
-<one or two lines>
-
-## System Map
-- <module> → <function> → <downstream>
-- <data path> → <db table> → <api>
-
-## Findings (Evidence)
-- <claim> — evidence: `src/path/file.ts:function` (lines X–Y); log snippet/trace id
-- <claim> — evidence: `...`
-
-## Hypotheses & Failure Modes
-- H1: <hypothesis>; would fail when <condition>
-- H2: <hypothesis>; watch for <signal>
-
-## Corrections
-- Updated: <old statement> → <new statement with evidence>
-
-## Diagnostics (Next Checks)
-- [ ] Repro on <platform/version>
-- [ ] Inspect <table/store> for <record>
-- [ ] Capture <log/trace>
-
-## Risks & Scope
-- Impacted: <areas/components>; Data: <tables/keys>; Users: <segments>
-
-## Decision / Next Steps
-- Owner: <name>; By: <date> (YYYY-MM-DD)
-- Action: <spike/bugfix/ADR>; Exit criteria: <binary checks>
-
-## References
-- `src/...`
-- ADR: `docs/adr/xxxx-yy-zz-something.md`
-- Design: `docs/...`
-
-## Competence Hooks
-- Why this works: <≤3 bullets>
-- Common pitfalls: <≤3 bullets>
-- Next skill: <≤1 item>
-- Teach-back: "<one question>"
-```
-
----
-
-## Evidence Quality Bar
-
-- **Cite the source** (file:func, line range if possible).
-- **Prefer primary evidence** (code, logs) over inference.
-- **Disambiguate platform** (Web/Capacitor/Electron) and **state** (migration, auth).
-- **Note uncertainty** explicitly.
-
----
-
-## Code Path Tracing (Required for Software Investigations)
-
-Before proposing solutions, trace the actual execution path:
-
-- [ ] **Entry Points**: Identify where the flow begins (user action, API call, etc.)
-- [ ] **Component Flow**: Map which components/methods are involved
-- [ ] **Data Path**: Track how data moves through the system
-- [ ] **Exit Points**: Confirm where the flow ends and what results
-- [ ] **Evidence Collection**: Gather specific code citations for each step
-
----
-
-## Collaboration Hooks
-
-- **Syncs:** 10–15m with QA/Security/Platform owners for high-risk areas.
-- **ADR:** Record major decisions; link here.
-- **Review:** Share repro + diagnostics checklist in PR/issue.
-
----
-
-## Integration with Other Rulesets
-
-### With software_development.mdc
-
-- **Enhanced Evidence Validation**: Use code path tracing for technical investigations
-- **Architecture Assessment**: Apply complexity justification to proposed solutions
-- **Impact Analysis**: Assess effects on existing systems before recommendations
-
-### With base_context.mdc
-
-- **Competence Building**: Focus on technical investigation skills
-- **Collaboration**: Structure outputs for team review and discussion
-
----
-
-## Self-Check (model, before responding)
-
-- [ ] Output matches the **Output Contract** sections.
-- [ ] Each claim has **evidence** or **uncertainty** is flagged.
-- [ ] Hypotheses are testable; diagnostics are actionable.
-- [ ] Competence + collaboration hooks present (≤120 words total).
-- [ ] Respect toggles; keep it concise.
-- [ ] **Code path traced** (for software investigations).
-- [ ] **Evidence validated** against actual code execution.
-
----
-
-## Optional Globs (examples)
-
-> Uncomment `globs` in the header if you want auto-attach behavior.
-
-- `src/platforms/**`, `src/services/**` — attach during service/feature investigations
-- `docs/adr/**` — attach when editing ADRs
-
-## Referenced Files
-
-- Consider including templates as context: `@adr_template.mdc`, `@investigation_report_example.mdc`

.cursor/rules/software_development.mdc

@@ -1,225 +0,0 @@
-
-# Software Development Ruleset
-
-**Author**: Matthew Raymer
-**Date**: 2025-08-19
-**Status**: 🎯 **ACTIVE** - Core development guidelines
-
-## Purpose
-
-Specialized guidelines for software development tasks including code review,
-debugging, architecture decisions, and testing.
-
-## Core Principles
-
-### 1. Evidence-First Development
-
-- **Code Citations Required**: Always cite specific file:line references when
-  making claims
-- **Execution Path Tracing**: Trace actual code execution before proposing
-  architectural changes
-- **Assumption Validation**: Flag assumptions as "assumed" vs "evidence-based"
-
-### 2. Code Review Standards
-
-- **Trace Before Proposing**: Always trace execution paths before suggesting
-  changes
-- **Evidence Over Inference**: Prefer code citations over logical deductions
-- **Scope Validation**: Confirm the actual scope of problems before proposing
-  solutions
-
-### 3. Problem-Solution Validation
-
-- **Problem Scope**: Does the solution address the actual problem?
-- **Evidence Alignment**: Does the solution match the evidence?
-- **Complexity Justification**: Is added complexity justified by real needs?
-- **Alternative Analysis**: What simpler solutions were considered?
-
-### 4. Dependency Management & Environment Validation
-
-- **Pre-build Validation**: Always validate critical dependencies before executing
-  build scripts
-- **Environment Consistency**: Ensure team members have identical development
-  environments
-- **Dependency Verification**: Check that required packages are installed and
-  accessible
-- **Path Resolution**: Use `npx` for local dependencies to avoid PATH issues
-
-## Required Workflows
-
-### Before Proposing Changes
-
-- [ ] **Code Path Tracing**: Map execution flow from entry to exit
-- [ ] **Evidence Collection**: Gather specific code citations and logs
-- [ ] **Assumption Surfacing**: Identify what's proven vs. inferred
-- [ ] **Scope Validation**: Confirm the actual extent of the problem
-- [ ] **Dependency Validation**: Verify all required dependencies are available
-  and accessible
-
-### During Solution Design
-
-- [ ] **Evidence Alignment**: Ensure solution addresses proven problems
-- [ ] **Complexity Assessment**: Justify any added complexity
-- [ ] **Alternative Evaluation**: Consider simpler approaches first
-- [ ] **Impact Analysis**: Assess effects on existing systems
-- [ ] **Environment Impact**: Assess how changes affect team member setups
-
-## Software-Specific Competence Hooks
-
-### Evidence Validation
-
-- **"What code path proves this claim?"**
-- **"How does data actually flow through the system?"**
-- **"What am I assuming vs. what can I prove?"**
-
-### Code Tracing
-
-- **"What's the execution path from user action to system response?"**
-- **"Which components actually interact in this scenario?"**
-- **"Where does the data originate and where does it end up?"**
-
-### Architecture Decisions
-
-- **"What evidence shows this change is necessary?"**
-- **"What simpler solution could achieve the same goal?"**
-- **"How does this change affect the existing system architecture?"**
-
-### Dependency & Environment Management
-
-- **"What dependencies does this feature require and are they properly
-  declared?"**
-- **"How will this change affect team member development environments?"**
-- **"What validation can we add to catch dependency issues early?"**
-
-## Dependency Management Best Practices
-
-### Pre-build Validation
-
-- **Check Critical Dependencies**: Validate essential tools before executing build
-  scripts
-- **Use npx for Local Dependencies**: Prefer `npx tsx` over direct `tsx` to
-  avoid PATH issues
-- **Environment Consistency**: Ensure all team members have identical dependency
-  versions
-
-### Common Pitfalls
-
-- **Missing npm install**: Team members cloning without running `npm install`
-- **PATH Issues**: Direct command execution vs. npm script execution differences
-- **Version Mismatches**: Different Node.js/npm versions across team members
-
-### Validation Strategies
-
-- **Dependency Check Scripts**: Implement pre-build validation for critical
-  dependencies
-- **Environment Requirements**: Document and enforce minimum Node.js/npm versions
-- **Onboarding Checklist**: Standardize team member setup procedures
-
-### Error Messages and Guidance
-
-- **Specific Error Context**: Provide clear guidance when dependency issues occur
-- **Actionable Solutions**: Direct users to specific commands (`npm install`,
-  `npm run check:dependencies`)
-- **Environment Diagnostics**: Implement comprehensive environment validation
-  tools
-
-### Build Script Enhancements
-
-- **Early Validation**: Check dependencies before starting build processes
-- **Graceful Degradation**: Continue builds when possible but warn about issues
-- **Helpful Tips**: Remind users about dependency management best practices
-
-## Integration with Other Rulesets
-
-### With base_context.mdc
-
-- Inherits generic competence principles
-- Adds software-specific evidence requirements
-- Maintains collaboration and learning focus
-
-### With research_diagnostic.mdc
-
-- Enhances investigation with code path tracing
-- Adds evidence validation to diagnostic workflow
-- Strengthens problem identification accuracy
-
-## Usage Guidelines
-
-### When to Use This Ruleset
-
-- Code reviews and architectural decisions
-- Bug investigation and debugging
-- Performance optimization
-- Feature implementation planning
-- Testing strategy development
-
-### When to Combine with Others
-
-- **base_context + software_development**: General development tasks
-- **research_diagnostic + software_development**: Technical investigations
-- **All three**: Complex architectural decisions or major refactoring
-
-## Self-Check (model, before responding)
-
-- [ ] Code path traced and documented
-- [ ] Evidence cited with specific file:line references
-- [ ] Assumptions clearly flagged as proven vs. inferred
-- [ ] Solution complexity justified by evidence
-- [ ] Simpler alternatives considered and documented
-- [ ] Impact on existing systems assessed
-- [ ] Dependencies validated and accessible
-- [ ] Environment impact assessed for team members
-- [ ] Pre-build validation implemented where appropriate
-
-## Additional Core Principles
-
-### 4. Dependency Management & Environment Validation
-- **Pre-build Validation**: Always validate critical dependencies before executing build scripts
-- **Environment Consistency**: Ensure team members have identical development environments
-- **Dependency Verification**: Check that required packages are installed and accessible
-- **Path Resolution**: Use `npx` for local dependencies to avoid PATH issues
-
-## Additional Required Workflows
-
-### Dependency Validation (Before Proposing Changes)
-- [ ] **Dependency Validation**: Verify all required dependencies are available and accessible
-
-### Environment Impact Assessment (During Solution Design)
-- [ ] **Environment Impact**: Assess how changes affect team member setups
-
-## Additional Competence Hooks
-
-### Dependency & Environment Management
-- **"What dependencies does this feature require and are they properly declared?"**
-- **"How will this change affect team member development environments?"**
-- **"What validation can we add to catch dependency issues early?"**
-
-## Dependency Management Best Practices
-
-### Pre-build Validation
-- **Check Critical Dependencies**: Validate essential tools before executing build scripts
-- **Use npx for Local Dependencies**: Prefer `npx tsx` over direct `tsx` to avoid PATH issues
-- **Environment Consistency**: Ensure all team members have identical dependency versions
-
-### Common Pitfalls
-- **Missing npm install**: Team members cloning without running `npm install`
-- **PATH Issues**: Direct command execution vs. npm script execution differences
-- **Version Mismatches**: Different Node.js/npm versions across team members
-
-### Validation Strategies
-- **Dependency Check Scripts**: Implement pre-build validation for critical dependencies
-- **Environment Requirements**: Document and enforce minimum Node.js/npm versions
-- **Onboarding Checklist**: Standardize team member setup procedures
-
-### Error Messages and Guidance
-- **Specific Error Context**: Provide clear guidance when dependency issues occur
-- **Actionable Solutions**: Direct users to specific commands (`npm install`, `npm run check:dependencies`)
-- **Environment Diagnostics**: Implement comprehensive environment validation tools
-
-### Build Script Enhancements
-- **Early Validation**: Check dependencies before starting build processes
-- **Graceful Degradation**: Continue builds when possible but warn about issues
-- **Helpful Tips**: Remind users about dependency management best practices
-
-- **Narrow Types Properly**: Use type guards to narrow `unknown` types safely
-- **Document Type Decisions**: Explain complex type structures and their purpose

.cursor/rules/time.mdc

@@ -1,329 +0,0 @@
----
-alwaysApply: true
----
-# Time Handling in Development Workflow
-
-**Author**: Matthew Raymer
-**Date**: 2025-08-17
-**Status**: 🎯 **ACTIVE** - Production Ready
-
-## Overview
-
-This guide establishes **how time should be referenced and used** across the
-development workflow. It is not tied to any one project, but applies to **all
-feature development, issue investigations, ADRs, and documentation**.
-
-## General Principles
-
-- **Explicit over relative**: Always prefer absolute dates (`2025-08-17`) over
-  relative references like "last week."
-- **ISO 8601 Standard**: Use `YYYY-MM-DD` format for all date references in
-  docs, issues, ADRs, and commits.
-- **Time zones**: Default to **UTC** unless explicitly tied to user-facing
-  behavior.
-- **Precision**: Only specify as much precision as needed (date vs. datetime vs.
-  timestamp).
-- **Consistency**: Align time references across ADRs, commits, and investigation
-  reports.
-
-## In Documentation & ADRs
-
-- Record decision dates using **absolute ISO dates**.
-- For ongoing timelines, state start and end explicitly (e.g., `2025-08-01` →
-  `2025-08-17`).
-- Avoid ambiguous terms like *recently*, *last month*, or *soon*.
-- For time-based experiments (e.g., A/B tests), always include:
-
-  - Start date
-  - Expected duration
-  - Review date checkpoint
-
-## In Code & Commits
-
-- Use **UTC timestamps** in logs, DB migrations, and serialized formats.
-- In commits, link changes to **date-bound ADRs or investigation docs**.
-- For migrations, include both **applied date** and **intended version window**.
-- Use constants for known fixed dates; avoid hardcoding arbitrary strings.
-
-## In Investigations & Research
-
-- Capture **when** an issue occurred (absolute time or version tag).
-- When describing failures: note whether they are **time-sensitive** (e.g., after
-  migrations, cache expirations).
-- Record diagnostic timelines in ISO format (not relative).
-- For performance regressions, annotate both **baseline timeframe** and
-  **measurement timeframe**.
-
-## Collaboration Hooks
-
-- During reviews, verify **time references are clear, absolute, and
-  standardized**.
-- In syncs, reframe relative terms ("this week") into shared absolute
-  references.
-- Tag ADRs with both **date created** and **review by** checkpoints.
-
-## Self-Check Before Submitting
-
-- [ ] Did I check the time using the **developer's actual system time and
-      timezone**?
-- [ ] Am I using absolute ISO dates?
-- [ ] Is UTC assumed unless specified otherwise?
-- [ ] Did I avoid ambiguous relative terms?
-- [ ] If duration matters, did I specify both start and end?
-- [ ] For future work, did I include a review/revisit date?
-
-## Real-Time Context in Developer Interactions
-
-- The model must always resolve **"current time"** using the **developer's
-  actual system time and timezone**.
-- When generating timestamps (e.g., in investigation logs, ADRs, or examples),
-  the model should:
-
-  - Use the **developer's current local time** by default.
-  - Indicate the timezone explicitly (e.g., `2025-08-17T10:32-05:00`).
-  - Optionally provide UTC alongside if context requires cross-team clarity.
-
-- When interpreting relative terms like *now*, *today*, *last week*:
-
-  - Resolve them against the **developer's current time**.
-  - Convert them into **absolute ISO-8601 values** in the output.
-
-## LLM Time Checking Instructions
-
-**CRITICAL**: The LLM must actively query the system for current time rather
-than assuming or inventing times.
-
-### How to Check Current Time
-
-#### 1. **Query System Time (Required)**
-
-- **Always start** by querying the current system time using available tools
-- **Never assume** what the current time is
-- **Never use** placeholder values like "current time" or "now"
-
-#### 2. **Available Time Query Methods**
-
-- **System Clock**: Use `date` command or equivalent system time function
-- **Programming Language**: Use language-specific time functions (e.g.,
-  `Date.now()`, `datetime.now()`)
-- **Environment Variables**: Check for time-related environment variables
-- **API Calls**: Use time service APIs if available
-
-#### 3. **Required Time Information**
-
-When querying time, always obtain:
-
-- **Current Date**: YYYY-MM-DD format
-- **Current Time**: HH:MM:SS format (24-hour)
-- **Timezone**: Current system timezone or UTC offset
-- **UTC Equivalent**: Convert local time to UTC for cross-team clarity
-
-#### 4. **Time Query Examples**
-
-```bash
-# Example: Query system time
-$ date
-# Expected output: Mon Aug 17 10:32:45 EDT 2025
-
-# Example: Query UTC time
-$ date -u
-# Expected output: Mon Aug 17 14:32:45 UTC 2025
-```
-
-```python
-# Example: Python time query
-import datetime
-current_time = datetime.datetime.now()
-utc_time = datetime.datetime.utcnow()
-print(f"Local: {current_time}")
-print(f"UTC: {utc_time}")
-```
-
-```javascript
-// Example: JavaScript time query
-const now = new Date();
-const utc = new Date().toISOString();
-console.log(`Local: ${now}`);
-console.log(`UTC: ${utc}`);
-```
-
-#### 5. **LLM Time Checking Workflow**
-
-1. **Query**: Actively query system for current time
-2. **Validate**: Confirm time data is reasonable and current
-3. **Format**: Convert to ISO 8601 format
-4. **Context**: Provide both local and UTC times when helpful
-5. **Document**: Show the source of time information
-
-#### 6. **Error Handling for Time Queries**
-
-- **If time query fails**: Ask user for current time or use "unknown time"
-  with explanation
-- **If timezone unclear**: Default to UTC and ask for clarification
-- **If time seems wrong**: Verify with user before proceeding
-- **Always log**: Record when and how time was obtained
-
-#### 7. **Time Query Verification**
-
-Before using queried time, verify:
-
-- [ ] Time is recent (within last few minutes)
-- [ ] Timezone information is available
-- [ ] UTC conversion is accurate
-- [ ] Format follows ISO 8601 standard
-
-## Model Behavior Rules
-
-- **Never invent a "fake now"**: All "current time" references must come from
-  the real system clock available at runtime.
-- **Check developer time zone**: If ambiguous, ask for clarification (e.g.,
-  "Should I use UTC or your local timezone?").
-- **Format for clarity**:
-
-  - Local time: `YYYY-MM-DDTHH:mm±hh:mm`
-  - UTC equivalent (if needed): `YYYY-MM-DDTHH:mmZ`
-
-## Examples
-
-### Good
-
-- "Feature flag rollout started on `2025-08-01` and will be reviewed on
-  `2025-08-21`."
-- "Migration applied on `2025-07-15T14:00Z`."
-- "Issue reproduced on `2025-08-17T09:00-05:00 (local)` /
-  `2025-08-17T14:00Z (UTC)`."
-
-### Bad
-
-- "Feature flag rolled out last week."
-- "Migration applied recently."
-- "Now is August, so we assume this was last month."
-
-### More Examples
-
-#### Issue Reports
-
-- ✅ **Good**: "User reported login failure at `2025-08-17T14:30:00Z`. Issue
-  persisted until `2025-08-17T15:45:00Z`."
-- ❌ **Bad**: "User reported login failure earlier today. Issue lasted for a
-  while."
-
-#### Release Planning
-
-- ✅ **Good**: "Feature X scheduled for release on `2025-08-25`. Testing
-  window: `2025-08-20` to `2025-08-24`."
-- ❌ **Bad**: "Feature X will be released next week after testing."
-
-#### Performance Monitoring
-
-- ✅ **Good**: "Baseline performance measured on `2025-08-10T09:00:00Z`.
-  Regression detected on `2025-08-15T14:00:00Z`."
-- ❌ **Bad**: "Performance was good last week but got worse this week."
-
-## Technical Implementation Notes
-
-### UTC Storage Principle
-
-- **Store all timestamps in UTC** in databases, logs, and serialized formats
-- **Convert to local time only for user display**
-- **Use ISO 8601 format** for all storage: `YYYY-MM-DDTHH:mm:ss.sssZ`
-
-### Common Implementation Patterns
-
-#### Database Storage
-
-```sql
--- ✅ Good: Store in UTC
-created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
-updated_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP
-
--- ❌ Bad: Store in local time
-created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
-updated_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP
-```
-
-#### API Responses
-
-```json
-// ✅ Good: Include both UTC and local time
-{
-  "eventTime": "2025-08-17T14:00:00Z",
-  "localTime": "2025-08-17T10:00:00-04:00",
-  "timezone": "America/New_York"
-}
-
-// ❌ Bad: Only local time
-{
-  "eventTime": "2025-08-17T10:00:00-04:00"
-}
-```
-
-#### Logging
-
-```python
-# ✅ Good: Log in UTC with timezone info
-logger.info(f"User action at {datetime.utcnow().isoformat()}Z (UTC)")
-
-# ❌ Bad: Log in local time
-logger.info(f"User action at {datetime.now()}")
-```
-
-### Timezone Handling Best Practices
-
-#### 1. Always Store Timezone Information
-
-- Include IANA timezone identifier (e.g., `America/New_York`)
-- Store UTC offset at time of creation
-- Handle daylight saving time transitions automatically
-
-#### 2. User Display Considerations
-
-- Convert UTC to user's preferred timezone
-- Show timezone abbreviation when helpful
-- Use relative time for recent events ("2 hours ago")
-
-#### 3. Edge Case Handling
-
-- **Daylight Saving Time**: Use timezone-aware libraries
-- **Leap Seconds**: Handle gracefully (rare but important)
-- **Invalid Times**: Validate before processing
-
-### Common Mistakes to Avoid
-
-#### 1. Timezone Confusion
-
-- ❌ **Don't**: Assume server timezone is user timezone
-- ✅ **Do**: Always convert UTC to user's local time for display
-
-#### 2. Format Inconsistency
-
-- ❌ **Don't**: Mix different time formats in the same system
-- ✅ **Do**: Standardize on ISO 8601 for all storage
-
-#### 3. Relative Time References
-
-- ❌ **Don't**: Use relative terms in persistent storage
-- ✅ **Do**: Convert relative terms to absolute timestamps immediately
-
-## References
-
-- [ISO 8601 Date and Time Standard](https://en.wikipedia.org/wiki/ISO_8601)
-- [IANA Timezone Database](https://www.iana.org/time-zones)
-- [ADR Template](./adr_template.md)
-- [Research & Diagnostic Workflow](./research_diagnostic.mdc)
-
----
-
-**Rule of Thumb**: Every time reference in development artifacts should be
-**clear in 6 months without context**, and aligned to the **developer's actual
-current time**.
-
-**Technical Rule of Thumb**: **Store in UTC, display in local time, always
-include timezone context.**
-
----
-
-**Status**: Active
-**Version**: 1.0
-**Maintainer**: Matthew Raymer
-**Next Review**: 2025-09-17

.cursor/rules/timesafari.mdc

@@ -0,0 +1,276 @@
+---
+description: 
+globs: 
+alwaysApply: true
+---
+---
+description: 
+globs: 
+alwaysApply: true
+---
+# Time Safari Context
+
+## Project Overview
+
+Time Safari is an application designed to foster community building through gifts, gratitude, and collaborative projects. The app should make it extremely easy and intuitive for users of any age and capability to recognize contributions, build trust networks, and organize collective action. It is built on services that preserve privacy and data sovereignty.
+
+The ultimate goals of Time Safari are two-fold:
+
+1. **Connect** Make it easy, rewarding, and non-threatening for people to connect with others who have similar interests, and to initiate activities together. This helps people accomplish and learn from other individuals in less-structured environments; moreover, it helps them discover who they want to continue to support and with whom they want to maintain relationships.
+
+2. **Reveal** Widely advertise the great support and rewards that are being given and accepted freely, especially non-monetary ones. Using visuals and text, display the kind of impact that gifts are making in the lives of others. Also show useful and engaging reports of project statistics and personal accomplishments.
+
+
+## Core Approaches
+
+Time Safari should help everyday users build meaningful connections and organize collective efforts by:
+
+1. **Recognizing Contributions**: Creating permanent, verifiable records of gifts and contributions people give to each other and their communities.
+
+2. **Facilitating Collaboration**: Making it ridiculously easy for people to ask for or propose help on projects and interests that matter to them.
+
+3. **Building Trust Networks**: Enabling users to maintain their network and activity visibility. Developing reputation through verified contributions and references, which can be selectively shown to others outside the network.
+
+4. **Preserving Privacy**: Ensuring personal identifiers are only shared with explicitly authorized contacts, allowing private individuals including children to participate safely.
+
+5. **Engaging Content**: Displaying people's records in compelling stories, and highlighting those projects that are lifting people's lives long-term, both in physical support and in emotional-spiritual-creative thriving.
+
+
+## Technical Foundation
+
+This application is built on a privacy-preserving claims architecture (via endorser.ch) with these key characteristics:
+
+- **Decentralized Identifiers (DIDs)**: User identities are based on public/private key pairs stored on their devices
+- **Cryptographic Verification**: All claims and confirmations are cryptographically signed
+- **User-Controlled Visibility**: Users explicitly control who can see their identifiers and data
+- **Merkle-Chained Claims**: Claims are cryptographically chained for verification and integrity
+- **Native and Web App**: Works on Capacitor (iOS, Android), Desktop (Electron and CEFPython), and web browsers
+
+## User Journey
+
+The typical progression of usage follows these stages:
+
+1. **Gratitude & Recognition**: Users begin by expressing and recording gratitude for gifts received, building a foundation of acknowledgment.
+
+2. **Project Proposals**: Users propose projects and ideas, reaching out to connect with others who share similar interests.
+
+3. **Action Triggers**: Offers of help serve as triggers and motivations to execute proposed projects, moving from ideas to action.
+
+## Context for LLM Development
+
+When developing new functionality for Time Safari, consider these design principles:
+
+1. **Accessibility First**: Features should be usable by non-technical users with minimal learning curve.
+
+2. **Privacy by Design**: All features must respect user privacy and data sovereignty.
+
+3. **Progressive Enhancement**: Core functionality should work across all devices, with richer experiences where supported.
+
+4. **Voluntary Collaboration**: The system should enable but never coerce participation.
+
+5. **Trust Building**: Features should help build verifiable trust between users.
+
+6. **Network Effects**: Consider how features scale as more users join the platform.
+
+7. **Low Resource Requirements**: The system should be lightweight enough to run on inexpensive devices users already own.
+
+## Use Cases to Support
+
+LLM development should focus on enhancing these key use cases:
+
+1. **Community Building**: Tools that help people find others with shared interests and values.
+
+2. **Project Coordination**: Features that make it easy to propose collaborative projects and to submit suggestions and offers to existing ones.
+
+3. **Reputation Building**: Methods for users to showcase their contributions and reliability, in contexts where they explicitly reveal that information.
+
+4. **Governance Experimentation**: Features that facilitate decision-making and collective governance.
+
+## Constraints
+
+When developing new features, be mindful of these constraints:
+
+1. **Privacy Preservation**: User identifiers must remain private except when explicitly shared.
+
+2. **Platform Limitations**: Features must work within the constraints of the target app platforms, while aiming to leverage the best platform technology available.
+
+3. **Endorser API Limitations**: Backend features are constrained by the endorser.ch API capabilities.
+
+4. **Performance on Low-End Devices**: The application should remain performant on older/simpler devices.
+
+5. **Offline-First When Possible**: Key functionality should work offline when feasible.
+
+## Project Technologies
+
+- Typescript using ES6 classes using vue-facing-decorator
+- TailwindCSS
+- Vite Build Tool
+- Playwright E2E testing
+- IndexDB
+- Camera, Image uploads, QR Code reader, ...
+
+## Mobile Features
+
+- Deep Linking
+- Local Notifications via a custom Capacitor plugin
+
+## Project Architecture
+
+- The application must work on web browser, PWA (Progressive Web Application), desktop via Electron, and mobile via Capacitor
+- Building for each platform is managed via Vite
+
+## Core Development Principles
+
+### DRY development
+- **Code Reuse**
+  - Extract common functionality into utility functions
+  - Create reusable components for UI patterns
+  - Implement service classes for shared business logic
+  - Use mixins for cross-cutting concerns
+  - Leverage TypeScript interfaces for shared type definitions
+
+- **Component Patterns**
+  - Create base components for common UI elements
+  - Implement higher-order components for shared behavior
+  - Use slot patterns for flexible component composition
+  - Create composable services for business logic
+  - Implement factory patterns for component creation
+
+- **State Management**
+  - Centralize state in Pinia stores
+  - Use computed properties for derived state
+  - Implement shared state selectors
+  - Create reusable state mutations
+  - Use action creators for common operations
+
+- **Error Handling**
+  - Implement centralized error handling
+  - Create reusable error components
+  - Use error boundary components
+  - Implement consistent error logging
+  - Create error type definitions
+
+- **Type Definitions**
+  - Create shared interfaces for common data structures
+  - Use type aliases for complex types
+  - Implement generic types for reusable components
+  - Create utility types for common patterns
+  - Use discriminated unions for state management
+
+- **API Integration**
+  - Create reusable API client classes
+  - Implement request/response interceptors
+  - Use consistent error handling patterns
+  - Create type-safe API endpoints
+  - Implement caching strategies
+
+- **Platform Services**
+  - Abstract platform-specific code behind interfaces
+  - Create platform-agnostic service layers
+  - Implement feature detection
+  - Use dependency injection for services
+  - Create service factories
+
+- **Testing**
+  - Create reusable test utilities
+  - Implement test factories
+  - Use shared test configurations
+  - Create reusable test helpers
+  - Implement consistent test patterns
+  
+### SOLID Principles
+- **Single Responsibility**: Each class/component should have only one reason to change
+  - Components should focus on one specific feature (e.g., QR scanning, DID management)
+  - Services should handle one type of functionality (e.g., platform services, crypto services)
+  - Utilities should provide focused helper functions
+
+- **Open/Closed**: Software entities should be open for extension but closed for modification
+  - Use interfaces for service definitions
+  - Implement plugin architecture for platform-specific features
+  - Allow component behavior extension through props and events
+
+- **Liskov Substitution**: Objects should be replaceable with their subtypes
+  - Platform services should work consistently across web/mobile
+  - Authentication providers should be interchangeable
+  - Storage implementations should be swappable
+
+- **Interface Segregation**: Clients shouldn't depend on interfaces they don't use
+  - Break down large service interfaces into smaller, focused ones
+  - Component props should be minimal and purposeful
+  - Event emissions should be specific and targeted
+
+- **Dependency Inversion**: High-level modules shouldn't depend on low-level modules
+  - Use dependency injection for services
+  - Abstract platform-specific code behind interfaces
+  - Implement factory patterns for component creation
+
+### Law of Demeter
+- Components should only communicate with immediate dependencies
+- Avoid chaining method calls (e.g., `this.service.getUser().getProfile().getName()`)
+- Use mediator patterns for complex component interactions
+- Implement facade patterns for subsystem access
+- Keep component communication through defined events and props
+
+### Composition over Inheritance
+- Prefer building components through composition
+- Use mixins for shared functionality
+- Implement feature toggles through props
+- Create higher-order components for common patterns
+- Use service composition for complex features
+
+### Interface Segregation
+- Define clear interfaces for services
+- Keep component APIs minimal and focused
+- Split large interfaces into smaller, specific ones
+- Use TypeScript interfaces for type definitions
+- Implement role-based interfaces for different use cases
+
+### Fail Fast
+- Validate inputs early in the process
+- Use TypeScript strict mode
+- Implement comprehensive error handling
+- Add runtime checks for critical operations
+- Use assertions for development-time validation
+
+### Principle of Least Astonishment
+- Follow Vue.js conventions consistently
+- Use familiar naming patterns
+- Implement predictable component behaviors
+- Maintain consistent error handling
+- Keep UI interactions intuitive
+
+### Information Hiding
+- Encapsulate implementation details
+- Use private class members
+- Implement proper access modifiers
+- Hide complex logic behind simple interfaces
+- Use TypeScript's access modifiers effectively
+
+### Single Source of Truth
+- Use Pinia for state management
+- Maintain one source for user data
+- Centralize configuration management
+- Use computed properties for derived state
+- Implement proper state synchronization
+
+### Principle of Least Privilege
+- Implement proper access control
+- Use minimal required permissions
+- Follow privacy-by-design principles
+- Restrict component access to necessary data
+- Implement proper authentication/authorization
+
+### Continuous Integration/Continuous Deployment (CI/CD)
+- Automated testing on every commit
+- Consistent build process across platforms
+- Automated deployment pipelines
+- Quality gates for code merging
+- Environment-specific configurations
+
+This expanded documentation provides:
+1. Clear principles for development
+2. Practical implementation guidelines
+3. Real-world examples
+4. TypeScript integration
+5. Best practices for Time Safari
+

.cursor/rules/wa-sqlite.mdc

@@ -0,0 +1,267 @@
+---
+description: 
+globs: 
+alwaysApply: true
+---
+# wa-sqlite Usage Guide
+
+## Table of Contents
+- [1. Overview](#1-overview)
+- [2. Installation](#2-installation)
+- [3. Basic Setup](#3-basic-setup)
+  - [3.1 Import and Initialize](#31-import-and-initialize)
+  - [3.2 Basic Database Operations](#32-basic-database-operations)
+- [4. Virtual File Systems (VFS)](#4-virtual-file-systems-vfs)
+  - [4.1 Available VFS Options](#41-available-vfs-options)
+  - [4.2 Using a VFS](#42-using-a-vfs)
+- [5. Best Practices](#5-best-practices)
+  - [5.1 Error Handling](#51-error-handling)
+  - [5.2 Transaction Management](#52-transaction-management)
+  - [5.3 Prepared Statements](#53-prepared-statements)
+- [6. Performance Considerations](#6-performance-considerations)
+- [7. Common Issues and Solutions](#7-common-issues-and-solutions)
+- [8. TypeScript Support](#8-typescript-support)
+
+## 1. Overview
+wa-sqlite is a WebAssembly build of SQLite that enables SQLite database operations in web browsers and JavaScript environments. It provides both synchronous and asynchronous builds, with support for custom virtual file systems (VFS) for persistent storage.
+
+## 2. Installation
+```bash
+npm install wa-sqlite
+# or
+yarn add wa-sqlite
+```
+
+## 3. Basic Setup
+
+### 3.1 Import and Initialize
+```javascript
+// Choose one of these imports based on your needs:
+// - wa-sqlite.mjs: Synchronous build
+// - wa-sqlite-async.mjs: Asynchronous build (required for async VFS)
+// - wa-sqlite-jspi.mjs: JSPI-based async build (experimental, Chromium only)
+import SQLiteESMFactory from 'wa-sqlite/dist/wa-sqlite.mjs';
+import * as SQLite from 'wa-sqlite';
+
+async function initDatabase() {
+  // Initialize SQLite module
+  const module = await SQLiteESMFactory();
+  const sqlite3 = SQLite.Factory(module);
+  
+  // Open database (returns a Promise)
+  const db = await sqlite3.open_v2('myDatabase');
+  return { sqlite3, db };
+}
+```
+
+### 3.2 Basic Database Operations
+```javascript
+async function basicOperations() {
+  const { sqlite3, db } = await initDatabase();
+  
+  try {
+    // Create a table
+    await sqlite3.exec(db, `
+      CREATE TABLE IF NOT EXISTS users (
+        id INTEGER PRIMARY KEY,
+        name TEXT NOT NULL,
+        email TEXT UNIQUE
+      )
+    `);
+    
+    // Insert data
+    await sqlite3.exec(db, `
+      INSERT INTO users (name, email) 
+      VALUES ('John Doe', 'john@example.com')
+    `);
+    
+    // Query data
+    const results = [];
+    await sqlite3.exec(db, 'SELECT * FROM users', (row, columns) => {
+      results.push({ row, columns });
+    });
+    
+    return results;
+  } finally {
+    // Always close the database when done
+    await sqlite3.close(db);
+  }
+}
+```
+
+## 4. Virtual File Systems (VFS)
+
+### 4.1 Available VFS Options
+wa-sqlite provides several VFS implementations for persistent storage:
+
+1. **IDBBatchAtomicVFS** (Recommended for general use)
+   - Uses IndexedDB with batch atomic writes
+   - Works in all contexts (Window, Worker, Service Worker)
+   - Supports WAL mode
+   - Best performance with `PRAGMA synchronous=normal`
+
+2. **IDBMirrorVFS**
+   - Keeps files in memory, persists to IndexedDB
+   - Works in all contexts
+   - Good for smaller databases
+
+3. **OPFS-based VFS** (Origin Private File System)
+   - Various implementations available:
+     - AccessHandlePoolVFS
+     - OPFSAdaptiveVFS
+     - OPFSCoopSyncVFS
+     - OPFSPermutedVFS
+   - Better performance but limited to Worker contexts
+
+### 4.2 Using a VFS
+```javascript
+import { IDBBatchAtomicVFS } from 'wa-sqlite/src/examples/IDBBatchAtomicVFS.js';
+import SQLiteESMFactory from 'wa-sqlite/dist/wa-sqlite-async.mjs';
+import * as SQLite from 'wa-sqlite';
+
+async function initDatabaseWithVFS() {
+  const module = await SQLiteESMFactory();
+  const sqlite3 = SQLite.Factory(module);
+  
+  // Register VFS
+  const vfs = await IDBBatchAtomicVFS.create('myApp', module);
+  sqlite3.vfs_register(vfs, true);
+  
+  // Open database with VFS
+  const db = await sqlite3.open_v2('myDatabase');
+  
+  // Configure for better performance
+  await sqlite3.exec(db, 'PRAGMA synchronous = normal');
+  await sqlite3.exec(db, 'PRAGMA journal_mode = WAL');
+  
+  return { sqlite3, db };
+}
+```
+
+## 5. Best Practices
+
+### 5.1 Error Handling
+```javascript
+async function safeDatabaseOperation() {
+  const { sqlite3, db } = await initDatabase();
+  
+  try {
+    await sqlite3.exec(db, 'SELECT * FROM non_existent_table');
+  } catch (error) {
+    if (error.code === SQLite.SQLITE_ERROR) {
+      console.error('SQL error:', error.message);
+    } else {
+      console.error('Database error:', error);
+    }
+  } finally {
+    await sqlite3.close(db);
+  }
+}
+```
+
+### 5.2 Transaction Management
+```javascript
+async function transactionExample() {
+  const { sqlite3, db } = await initDatabase();
+  
+  try {
+    await sqlite3.exec(db, 'BEGIN TRANSACTION');
+    
+    // Perform multiple operations
+    await sqlite3.exec(db, 'INSERT INTO users (name) VALUES (?)', ['Alice']);
+    await sqlite3.exec(db, 'INSERT INTO users (name) VALUES (?)', ['Bob']);
+    
+    await sqlite3.exec(db, 'COMMIT');
+  } catch (error) {
+    await sqlite3.exec(db, 'ROLLBACK');
+    throw error;
+  } finally {
+    await sqlite3.close(db);
+  }
+}
+```
+
+### 5.3 Prepared Statements
+```javascript
+async function preparedStatementExample() {
+  const { sqlite3, db } = await initDatabase();
+  
+  try {
+    // Prepare statement
+    const stmt = await sqlite3.prepare(db, 'SELECT * FROM users WHERE id = ?');
+    
+    // Execute with different parameters
+    await sqlite3.bind(stmt, 1, 1);
+    while (await sqlite3.step(stmt) === SQLite.SQLITE_ROW) {
+      const row = sqlite3.row(stmt);
+      console.log(row);
+    }
+    
+    // Reset and reuse
+    await sqlite3.reset(stmt);
+    await sqlite3.bind(stmt, 1, 2);
+    // ... execute again
+    
+    await sqlite3.finalize(stmt);
+  } finally {
+    await sqlite3.close(db);
+  }
+}
+```
+
+## 6. Performance Considerations
+
+1. **VFS Selection**
+   - Use IDBBatchAtomicVFS for general-purpose applications
+   - Consider OPFS-based VFS for better performance in Worker contexts
+   - Use MemoryVFS for temporary databases
+
+2. **Configuration**
+   - Set appropriate page size (default is usually fine)
+   - Use WAL mode for better concurrency
+   - Consider `PRAGMA synchronous=normal` for better performance
+   - Adjust cache size based on your needs
+
+3. **Concurrency**
+   - Use transactions for multiple operations
+   - Be aware of VFS-specific concurrency limitations
+   - Consider using Web Workers for heavy database operations
+
+## 7. Common Issues and Solutions
+
+1. **Database Locking**
+   - Use appropriate transaction isolation levels
+   - Implement retry logic for busy errors
+   - Consider using WAL mode
+
+2. **Storage Limitations**
+   - Be aware of browser storage quotas
+   - Implement cleanup strategies
+   - Monitor database size
+
+3. **Cross-Context Access**
+   - Use appropriate VFS for your context
+   - Consider message passing for cross-context communication
+   - Be aware of storage access limitations
+
+## 8. TypeScript Support
+wa-sqlite includes TypeScript definitions. The main types are:
+
+```typescript
+type SQLiteCompatibleType = number | string | Uint8Array | Array<number> | bigint | null;
+
+interface SQLiteAPI {
+  open_v2(filename: string, flags?: number, zVfs?: string): Promise<number>;
+  exec(db: number, sql: string, callback?: (row: any[], columns: string[]) => void): Promise<number>;
+  close(db: number): Promise<number>;
+  // ... other methods
+}
+```
+
+## Additional Resources
+
+- [Official GitHub Repository](https://github.com/rhashimoto/wa-sqlite)
+- [Online Demo](https://rhashimoto.github.io/wa-sqlite/demo/)
+- [API Reference](https://rhashimoto.github.io/wa-sqlite/docs/)
+- [FAQ](https://github.com/rhashimoto/wa-sqlite/issues?q=is%3Aissue+label%3Afaq+)
+- [Discussion Forums](https://github.com/rhashimoto/wa-sqlite/discussions) 

.cursor/rules/workflow/version_control.mdc

@@ -1,335 +0,0 @@
----
-description: interacting with git
-alwaysApply: false
----
-# Directive: Peaceful Co-Existence with Developers
-
-**Author**: Matthew Raymer
-**Date**: 2025-08-19
-**Status**: 🎯 **ACTIVE** - Version control guidelines
-
-## 1) Version-Control Ownership
-
-- **MUST NOT** run `git add`, `git commit`, or any write action.
-- **MUST** leave staging/committing to the developer.
-
-## 2) Source of Truth for Commit Text
-
-- **MUST** derive messages **only** from:
-  - files **staged** for commit (primary), and
-  - files **awaiting staging** (context).
-- **MUST** use the **diffs** to inform content.
-- **MUST NOT** invent changes or imply work not present in diffs.
-
-## 3) Mandatory Preview Flow
-
-- **ALWAYS** present, before any real commit:
-  - file list + brief per-file notes,
-  - a **draft commit message** (copy-paste ready),
-  - nothing auto-applied.
-
-## 4) Version Synchronization Requirements
-
-- **MUST** check for version changes in `package.json` before committing
-- **MUST** ensure `CHANGELOG.md` is updated when `package.json` version
-  changes
-- **MUST** validate version format consistency between both files
-- **MUST** include version bump commits in changelog with proper semantic
-  versioning
-
-### Version Sync Checklist (Before Commit)
-
-- [ ] `package.json` version matches latest `CHANGELOG.md` entry
-- [ ] New version follows semantic versioning
-  (MAJOR.MINOR.PATCH[-PRERELEASE])
-- [ ] Changelog entry includes all significant changes since last version
-- [ ] Version bump commit message follows `build(version): bump to X.Y.Z`
-  format
-- [ ] Breaking changes properly documented with migration notes
-- [ ] Alert developer in chat message that version has been updated
-
-### Version Change Detection
-
-- **Check for version changes** in staged/unstaged `package.json`
-- **Alert developer** if version changed but changelog not updated
-- **Suggest changelog update** with proper format and content
-- **Validate semantic versioning** compliance
-
-### Implementation Notes
-
-- **Version Detection**: Compare `package.json` version field with latest
-  changelog entry
-- **Semantic Validation**: Ensure version follows `X.Y.Z[-PRERELEASE]`
-  format
-- **Changelog Format**: Follow [Keep a Changelog](https://keepachangelog.com/)
-  standards
-- **Breaking Changes**: Use `!` in commit message and `BREAKING CHANGE:`
-  in changelog
-- **Pre-release Versions**: Include beta/alpha/rc suffixes in both files
-  consistently
-
-## Commit Message Format (Normative)
-
-### A. Subject Line (required)
-
-```
-<type>(<scope>)<!>: <summary>
-```
-
-- **type** (lowercase, Conventional Commits):
-  `feat|fix|refactor|perf|docs|test|build|chore|ci|revert`
-- **scope**: optional module/package/area (e.g., `api`, `ui/login`, `db`)
-- **!**: include when a breaking change is introduced
-- **summary**: imperative mood, ≤ 72 chars, no trailing period
-
-**Examples**
-
-- `fix(api): handle null token in refresh path`
-- `feat(ui/login)!: require OTP after 3 failed attempts`
-
-### B. Body (optional, when it adds non-obvious value)
-
-- One blank line after subject.
-- Wrap at ~72 chars.
-- Explain **what** and **why**, not line-by-line "how".
-- Include brief notes like tests passing or TS/lint issues resolved
-  **only if material**.
-
-**Body checklist**
-
-- [ ] Problem/symptom being addressed
-- [ ] High-level approach or rationale
-- [ ] Risks, tradeoffs, or follow-ups (if any)
-
-### C. Footer (optional)
-
-- Issue refs: `Closes #123`, `Refs #456`
-- Breaking change (alternative to `!`):
-  `BREAKING CHANGE: <impact + migration note>`
-- Authors: `Co-authored-by: Name <email>`
-- Security: `CVE-XXXX-YYYY: <short note>` (if applicable)
-
-## Content Guidance
-
-### Include (when relevant)
-
-- Specific fixes/features delivered
-- Symptoms/problems fixed
-- Brief note that tests passed or TS/lint errors resolved
-
-### Avoid
-
-- Vague: *improved, enhanced, better*
-- Trivialities: tiny docs, one-liners, pure lint cleanups (separate,
-  focused commits if needed)
-- Redundancy: generic blurbs repeated across files
-- Multi-purpose dumps: keep commits **narrow and focused**
-- Long explanations that good inline code comments already cover
-
-**Guiding Principle:** Let code and inline docs speak. Use commits to
-highlight what isn't obvious.
-
-## Copy-Paste Templates
-
-### Minimal (no body)
-
-```text
-<type>(<scope>): <summary>
-```
-
-### Standard (with body & footer)
-
-```text
-<type>(<scope>)<!>: <summary>
-
-<why-this-change?>
-<what-it-does?>
-<risks-or-follow-ups?>
-
-Closes #<id>
-BREAKING CHANGE: <impact + migration>
-Co-authored-by: <Name> <email>
-```
-
-## Assistant Output Checklist (before showing the draft)
-
-- [ ] List changed files + 1–2 line notes per file
-- [ ] Provide **one** focused draft message (subject/body/footer)
-- [ ] Subject ≤ 72 chars, imperative mood, correct `type(scope)!` syntax
-- [ ] Body only if it adds non-obvious value
-- [ ] No invented changes; aligns strictly with diffs
-- [ ] Render as a single copy-paste block for the developer
-
----
-
-**Status**: Active version control guidelines
-**Priority**: High
-**Estimated Effort**: Ongoing reference
-**Dependencies**: git, package.json, CHANGELOG.md
-**Stakeholders**: Development team, AI assistants
-
-- [ ] No invented changes; aligns strictly with diffs
-- [ ] Render as a single copy-paste block for the developer
-
-## 1) Version-Control Ownership
-
-- **MUST NOT** run `git add`, `git commit`, or any write action.
-- **MUST** leave staging/committing to the developer.
-
-## 2) Source of Truth for Commit Text
-
-- **MUST** derive messages **only** from:
-  - files **staged** for commit (primary), and
-  - files **awaiting staging** (context).
-- **MUST** use the **diffs** to inform content.
-- **MUST NOT** invent changes or imply work not present in diffs.
-
-## 3) Mandatory Preview Flow
-
-- **ALWAYS** present, before any real commit:
-  - file list + brief per-file notes,
-  - a **draft commit message** (copy-paste ready),
-  - nothing auto-applied.
-
-## 4) Version Synchronization Requirements
-
-- **MUST** check for version changes in `package.json` before committing
-- **MUST** ensure `CHANGELOG.md` is updated when `package.json` version
-  changes
-- **MUST** validate version format consistency between both files
-- **MUST** include version bump commits in changelog with proper semantic
-  versioning
-
-### Version Sync Checklist (Before Commit)
-
-- [ ] `package.json` version matches latest `CHANGELOG.md` entry
-- [ ] New version follows semantic versioning
-  (MAJOR.MINOR.PATCH[-PRERELEASE])
-- [ ] Changelog entry includes all significant changes since last version
-- [ ] Version bump commit message follows `build(version): bump to X.Y.Z`
-  format
-- [ ] Breaking changes properly documented with migration notes
-- [ ] Alert developer in chat message that version has been updated
-
-### Version Change Detection
-
-- **Check for version changes** in staged/unstaged `package.json`
-- **Alert developer** if version changed but changelog not updated
-- **Suggest changelog update** with proper format and content
-- **Validate semantic versioning** compliance
-
-### Implementation Notes
-
-- **Version Detection**: Compare `package.json` version field with latest
-  changelog entry
-- **Semantic Validation**: Ensure version follows `X.Y.Z[-PRERELEASE]`
-  format
-- **Changelog Format**: Follow [Keep a Changelog](https://keepachangelog.com/)
-  standards
-- **Breaking Changes**: Use `!` in commit message and `BREAKING CHANGE:`
-  in changelog
-- **Pre-release Versions**: Include beta/alpha/rc suffixes in both files
-  consistently
-
-## Commit Message Format (Normative)
-
-### A. Subject Line (required)
-
-```
-<type>(<scope>)<!>: <summary>
-```
-
-- **type** (lowercase, Conventional Commits):
-  `feat|fix|refactor|perf|docs|test|build|chore|ci|revert`
-- **scope**: optional module/package/area (e.g., `api`, `ui/login`, `db`)
-- **!**: include when a breaking change is introduced
-- **summary**: imperative mood, ≤ 72 chars, no trailing period
-
-**Examples**
-
-- `fix(api): handle null token in refresh path`
-- `feat(ui/login)!: require OTP after 3 failed attempts`
-
-### B. Body (optional, when it adds non-obvious value)
-
-- One blank line after subject.
-- Wrap at ~72 chars.
-- Explain **what** and **why**, not line-by-line "how".
-- Include brief notes like tests passing or TS/lint issues resolved
-  **only if material**.
-
-**Body checklist**
-
-- [ ] Problem/symptom being addressed
-- [ ] High-level approach or rationale
-- [ ] Risks, tradeoffs, or follow-ups (if any)
-
-### C. Footer (optional)
-
-- Issue refs: `Closes #123`, `Refs #456`
-- Breaking change (alternative to `!`):
-  `BREAKING CHANGE: <impact + migration note>`
-- Authors: `Co-authored-by: Name <email>`
-- Security: `CVE-XXXX-YYYY: <short note>` (if applicable)
-
-## Content Guidance
-
-### Include (when relevant)
-
-- Specific fixes/features delivered
-- Symptoms/problems fixed
-- Brief note that tests passed or TS/lint errors resolved
-
-### Avoid
-
-- Vague: *improved, enhanced, better*
-- Trivialities: tiny docs, one-liners, pure lint cleanups (separate,
-  focused commits if needed)
-- Redundancy: generic blurbs repeated across files
-- Multi-purpose dumps: keep commits **narrow and focused**
-- Long explanations that good inline code comments already cover
-
-**Guiding Principle:** Let code and inline docs speak. Use commits to
-highlight what isn't obvious.
-
-## Copy-Paste Templates
-
-### Minimal (no body)
-
-```text
-<type>(<scope>): <summary>
-```
-
-### Standard (with body & footer)
-
-```text
-<type>(<scope>)<!>: <summary>
-
-<why-this-change?>
-<what-it-does?>
-<risks-or-follow-ups?>
-
-Closes #<id>
-BREAKING CHANGE: <impact + migration>
-Co-authored-by: <Name> <email>
-```
-
-## Assistant Output Checklist (before showing the draft)
-
-- [ ] List changed files + 1–2 line notes per file
-- [ ] Provide **one** focused draft message (subject/body/footer)
-- [ ] Subject ≤ 72 chars, imperative mood, correct `type(scope)!` syntax
-- [ ] Body only if it adds non-obvious value
-- [ ] No invented changes; aligns strictly with diffs
-- [ ] Render as a single copy-paste block for the developer
-
----
-
-**Status**: Active version control guidelines
-**Priority**: High
-**Estimated Effort**: Ongoing reference
-**Dependencies**: git, package.json, CHANGELOG.md
-**Stakeholders**: Development team, AI assistants
-
-* [ ] No invented changes; aligns strictly with diffs
-* [ ] Render as a single copy-paste block for the developer

.dockerignore

@@ -1,171 +0,0 @@
-# TimeSafari Docker Ignore File
-# Author: Matthew Raymer
-# Description: Excludes unnecessary files from Docker build context
-#
-# Benefits:
-# - Faster build times
-# - Smaller build context
-# - Reduced image size
-# - Better security (excludes sensitive files)
-
-# Dependencies
-node_modules
-npm-debug.log*
-yarn-debug.log*
-yarn-error.log*
-
-# Build outputs
-# dist - Allow dist directory for Docker builds (contains pre-built assets)
-dist-*
-build
-*.tsbuildinfo
-
-# Development files
-.git
-.gitignore
-README.md
-CHANGELOG.md
-CONTRIBUTING.md
-BUILDING.md
-LICENSE
-
-# IDE and editor files
-.vscode
-.idea
-*.swp
-*.swo
-*~
-
-# OS generated files
-.DS_Store
-.DS_Store?
-._*
-.Spotlight-V100
-.Trashes
-ehthumbs.db
-Thumbs.db
-
-# Logs
-logs
-*.log
-
-# Runtime data
-pids
-*.pid
-*.seed
-*.pid.lock
-
-# Coverage directory used by tools like istanbul
-coverage
-*.lcov
-
-# nyc test coverage
-.nyc_output
-
-# Dependency directories
-jspm_packages/
-
-# Optional npm cache directory
-.npm
-
-# Optional eslint cache
-.eslintcache
-
-# Optional REPL history
-.node_repl_history
-
-# Output of 'npm pack'
-*.tgz
-
-# Yarn Integrity file
-.yarn-integrity
-
-# dotenv environment variables file
-.env
-.env.local
-.env.development.local
-.env.test.local
-.env.production.local
-
-# parcel-bundler cache (https://parceljs.org/)
-.cache
-.parcel-cache
-
-# next.js build output
-.next
-
-# nuxt.js build output
-.nuxt
-
-# vuepress build output
-.vuepress/dist
-
-# Serverless directories
-.serverless
-
-# FuseBox cache
-.fusebox/
-
-# DynamoDB Local files
-.dynamodb/
-
-# TernJS port file
-.tern-port
-
-# Stores VSCode versions used for testing VSCode extensions
-.vscode-test
-
-# Test files
-test-playwright
-test-playwright-results
-test-results
-test-scripts
-
-# Documentation
-doc
-
-# Scripts (keep only what's needed for build)
-scripts/test-*.sh
-scripts/*.js
-scripts/README.md
-
-# Platform-specific files
-android
-ios
-electron
-
-# Docker files (avoid recursive copying)
-Dockerfile*
-docker-compose*
-.dockerignore
-
-# CI/CD files
-.github
-.gitlab-ci.yml
-.travis.yml
-.circleci
-
-# Temporary files
-tmp
-temp
-
-# Backup files
-*.bak
-*.backup
-
-# Archive files
-*.tar
-*.tar.gz
-*.zip
-*.rar
-
-# Certificate files
-*.pem
-*.key
-*.crt
-*.p12
-
-# Configuration files that might contain secrets
-*.secrets
-secrets.json
-config.local.json 

.env.development

@@ -1,14 +1,9 @@
 # Only the variables that start with VITE_ are seen in the application import.meta.env in Vue.
 
-# Logging Configuration - Development environment gets maximum visibility
-VITE_LOG_LEVEL=debug
-
 # iOS doesn't like spaces in the app title.
 TIME_SAFARI_APP_TITLE="TimeSafari_Dev"
 VITE_APP_SERVER=http://localhost:8080
-# This is the claim ID for actions in the BVC project, with the JWT ID on this environment (not
-
-
+# This is the claim ID for actions in the BVC project, with the JWT ID on this environment (not production).
 VITE_BVC_MEETUPS_PROJECT_CLAIM_ID=https://endorser.ch/entity/01HWE8FWHQ1YGP7GFZYYPS272F
 VITE_DEFAULT_ENDORSER_API_SERVER=http://localhost:3000
 # Using shared server by default to ease setup, which works for shared test users.

.env.production

@@ -1,7 +1,6 @@
 # Only the variables that start with VITE_ are seen in the application import.meta.env in Vue.
 
-# Logging Configuration - Production environment gets minimal logging for performance
-VITE_LOG_LEVEL=warn
+
 
 VITE_APP_SERVER=https://timesafari.app
 # This is the claim ID for actions in the BVC project.

.env.staging

@@ -1,14 +1,9 @@
 # Only the variables that start with VITE_ are seen in the application import.meta.env in Vue.
 
-# Logging Configuration - Test environment gets balanced logging for debugging
-VITE_LOG_LEVEL=info
-
 # iOS doesn't like spaces in the app title.
 TIME_SAFARI_APP_TITLE="TimeSafari_Test"
 VITE_APP_SERVER=https://test.timesafari.app
-# This is the claim ID for actions in the BVC project, with the JWT ID on this environment (not
- production).
-
+# This is the claim ID for actions in the BVC project, with the JWT ID on this environment (not production).
 VITE_BVC_MEETUPS_PROJECT_CLAIM_ID=https://endorser.ch/entity/01HWE8FWHQ1YGP7GFZYYPS272F
 VITE_DEFAULT_ENDORSER_API_SERVER=https://test-api.endorser.ch
 

.eslintrc.js

@@ -30,7 +30,7 @@ module.exports = {
     }],
     "no-console": process.env.NODE_ENV === "production" ? "error" : "warn",
     "no-debugger": process.env.NODE_ENV === "production" ? "error" : "warn",
-    "@typescript-eslint/no-explicit-any": "error",
+    "@typescript-eslint/no-explicit-any": "warn",
     "@typescript-eslint/explicit-function-return-type": "off",
     "@typescript-eslint/no-unnecessary-type-constraint": "off",
     "@typescript-eslint/no-unused-vars": ["error", { "argsIgnorePattern": "^_" }]

.github/workflows/asset-validation.yml

@@ -1,142 +0,0 @@
-name: Asset Validation & CI Safeguards
-
-on:
-  pull_request:
-    paths:
-      - 'resources/**'
-      - 'config/assets/**'
-      - 'capacitor-assets.config.json'
-      - 'capacitor.config.ts'
-      - 'capacitor.config.json'
-  push:
-    branches: [main, develop]
-    paths:
-      - 'resources/**'
-      - 'config/assets/**'
-      - 'capacitor-assets.config.json'
-      - 'capacitor.config.ts'
-      - 'capacitor.config.json'
-
-jobs:
-  asset-validation:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout code
-        uses: actions/checkout@v4
-
-      - name: Setup Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version-file: '.nvmrc'
-          cache: 'npm'
-
-      - name: Install dependencies
-        run: npm ci
-
-      - name: Validate asset configuration
-        run: npm run assets:validate
-
-      - name: Check for committed platform assets (Android)
-        run: |
-          if git ls-files -z android/app/src/main/res | grep -E '(AppIcon.*\.png|Splash.*\.png|mipmap-.*/ic_launcher.*\.png)' > /dev/null; then
-            echo "❌ Android platform assets found in VCS - these should be generated at build-time"
-            git ls-files -z android/app/src/main/res | grep -E '(AppIcon.*\.png|Splash.*\.png|mipmap-.*/ic_launcher.*\.png)'
-            exit 1
-          fi
-          echo "✅ No Android platform assets committed"
-
-      - name: Check for committed platform assets (iOS)
-        run: |
-          if git ls-files -z ios/App/App/Assets.xcassets | grep -E '(AppIcon.*\.png|Splash.*\.png)' > /dev/null; then
-            echo "❌ iOS platform assets found in VCS - these should be generated at build-time"
-            git ls-files -z ios/App/App/Assets.xcassets | grep -E '(AppIcon.*\.png|Splash.*\.png)'
-            exit 1
-          fi
-          echo "✅ No iOS platform assets committed"
-
-      - name: Test asset generation
-        run: |
-          echo "🧪 Testing asset generation workflow..."
-          npm run build:capacitor
-          npx cap sync
-          npx capacitor-assets generate --dry-run || npx capacitor-assets generate
-          echo "✅ Asset generation test completed"
-
-      - name: Verify clean tree after build
-        run: |
-          if [ -n "$(git status --porcelain)" ]; then
-            echo "❌ Dirty tree after build - asset configs were modified"
-            git status
-            git diff
-            exit 1
-          fi
-          echo "✅ Build completed with clean tree"
-
-  schema-validation:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout code
-        uses: actions/checkout@v4
-
-      - name: Setup Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version-file: '.nvmrc'
-          cache: 'npm'
-
-      - name: Install dependencies
-        run: npm ci
-
-      - name: Validate schema compliance
-        run: |
-          echo "🔍 Validating schema compliance..."
-          node -e "
-            const fs = require('fs');
-            const config = JSON.parse(fs.readFileSync('capacitor-assets.config.json', 'utf8'));
-            const schema = JSON.parse(fs.readFileSync('config/assets/schema.json', 'utf8'));
-            
-            // Basic schema validation
-            if (!config.icon || !config.splash) {
-              throw new Error('Missing required sections: icon and splash');
-            }
-            
-            if (!config.icon.source || !config.splash.source) {
-              throw new Error('Missing required source fields');
-            }
-            
-            if (!/^resources\/.*\.(png|svg)$/.test(config.icon.source)) {
-              throw new Error('Icon source must be in resources/ directory');
-            }
-            
-            if (!/^resources\/.*\.(png|svg)$/.test(config.splash.source)) {
-              throw new Error('Splash source must be in resources/ directory');
-            }
-            
-            console.log('✅ Schema validation passed');
-          "
-
-      - name: Check source file existence
-        run: |
-          echo "📁 Checking source file existence..."
-          node -e "
-            const fs = require('fs');
-            const config = JSON.parse(fs.readFileSync('capacitor-assets.config.json', 'utf8'));
-            
-            const requiredFiles = [
-              config.icon.source,
-              config.splash.source
-            ];
-            
-            if (config.splash.darkSource) {
-              requiredFiles.push(config.splash.darkSource);
-            }
-            
-            const missingFiles = requiredFiles.filter(file => !fs.existsSync(file));
-            
-            if (missingFiles.length > 0) {
-              console.error('❌ Missing source files:', missingFiles);
-              process.exit(1);
-            }
-            
-            console.log('✅ All source files exist');
-          "

.gitignore

@@ -54,90 +54,4 @@ build_logs/
 # PWA icon files generated by capacitor-assets
 icons
 
-*.log
 
-# Build outputs
-dist/
-build/
-
-# Generated Android assets and resources (should be generated during build)
-android/app/src/main/assets/public/
-
-# Generated Android resources (icons, splash screens, etc.)
-android/app/src/main/res/drawable*/
-android/app/src/main/res/mipmap*/
-android/app/src/main/res/values/ic_launcher_background.xml
-
-# Android generated assets (deny-listed in CI)
-android/app/src/main/res/mipmap-*/ic_launcher*.png
-android/app/src/main/res/drawable*/splash*.png
-
-# iOS generated assets (deny-listed in CI)
-ios/App/App/Assets.xcassets/**/AppIcon*.png
-ios/App/App/Assets.xcassets/**/Splash*.png
-
-# Keep these Android configuration files in version control:
-# - android/app/src/main/assets/capacitor.plugins.json
-# - android/app/src/main/res/values/strings.xml
-# - android/app/src/main/res/values/styles.xml
-# - android/app/src/main/res/layout/activity_main.xml
-# - android/app/src/main/res/xml/config.xml
-# - android/app/src/main/res/xml/file_paths.xml
-
-sql-wasm.wasm
-
-# Temporary and generated files
-temp.*
-*.tmp
-*.temp
-*.bak
-*.cache
-git.diff.*
-*.har
-
-# Development artifacts
-dev-dist/
-*.map
-
-# OS generated files
-Thumbs.db
-ehthumbs.db
-Desktop.ini
-
-# Capacitor build outputs and generated files
-android/app/build/
-android/capacitor-cordova-android-plugins/build/
-ios/App/App/public/assets/
-ios/App/App/build/
-ios/App/build/
-
-# Capacitor build artifacts (covered by android/app/build/ above)
-
-# Keep these Capacitor files in version control:
-# - capacitor.config.json (root, electron, ios)
-# - src/main.capacitor.ts
-# - vite.config.capacitor.mts
-# - android/capacitor.settings.gradle
-# - android/app/capacitor.build.gradle
-# - android/app/src/main/assets/capacitor.plugins.json
-
-# Electron build outputs and generated files
-electron/build/
-electron/app/
-electron/dist/
-electron/out/
-
-# Keep these Electron files in version control:
-# - electron/src/preload.ts (source)
-# - electron/src/index.ts (source)
-# - electron/src/setup.ts (source)
-# - electron/package.json
-# - electron/electron-builder.config.json
-# - electron/build-packages.sh
-# - electron/live-runner.js
-# - electron/resources/electron-publisher-custom.js
-
-# Gradle cache files
-android/.gradle/file-system.probe
-android/.gradle/caches/
-coverage

.markdownlint.json

@@ -1 +0,0 @@
-{"MD013": {"code_blocks": false}}

.node-version

@@ -1 +0,0 @@
-18.19.0

.npmrc

@@ -1 +0,0 @@
-@jsr:registry=https://npm.jsr.io

.nvmrc

@@ -1 +0,0 @@
-18.19.0

CHANGELOG.md

@@ -5,55 +5,6 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
-## [1.0.7] - 2025.08.18
-### Fixed
-- Deep link for onboard-meeting-members
-
-
-## [1.0.6] - 2025.08.09
-### Fixed
-- Deep link errors where none would validate
-
-
-## [1.0.5] - 2025.07.24
-### Fixed
-- Export & import of contacts corrupted contact methods
-
-
-## [1.0.4] - 2025.07.20 - 002f2407208d56cc59c0aa7c880535ae4cbace8b
-### Fixed
-- Deep link for invite-one-accept
-
-
-## [1.0.3] - 2025.07.12 - a9a8ba217cd6015321911e98e6843e988dc2c4ae
-### Changed
-- Photo is pinned to profile mode
-### Fixed
-- Deep link URLs (and other prod settings)
-- Error in BVC begin view
-
-
-## [1.0.2] - 2025.06.20 - 276e0a741bc327de3380c4e508cccb7fee58c06d
-### Added
-- Version on feed title
-
-
-## [1.0.1] - 2025.06.20
-### Added
-- Allow a user to block someone else's content from view
-
-
-## [1.0.0] - 2025.06.20 - 5aa693de6337e5dbb278bfddc6bd39094bc14f73
-### Added
-- Web-oriented migration from IndexedDB to SQLite
-
-
-## [0.5.8]
-### Added
-- /deep-link/ path for URLs that are shared with people
-### Changed
-- External links now go to /deep-link/...
-- Feed visuals now have arrow imagery from giver to receiver
 
 
 ## [0.4.7]

Dockerfile

@@ -1,170 +1,36 @@
-# TimeSafari Docker Build
-# Author: Matthew Raymer
-# Description: Multi-stage Docker build for TimeSafari web application
-# 
-# Build Process:
-# 1. Base stage: Node.js with build dependencies
-# 2. Builder stage: Copy pre-built web assets from host
-# 3. Production stage: Nginx server with optimized assets
-# 
-# Note: Web assets are built on the host using npm scripts before Docker build
-#
-# Security Features:
-# - Non-root user execution
-# - Minimal attack surface with Alpine Linux
-# - Multi-stage build to reduce image size
-# - No build dependencies in final image
-#
-# Usage:
-#   IMPORTANT: Build web assets first, then build Docker image
-#   
-#   Using npm scripts (recommended):
-#   Production: npm run build:web:docker:prod
-#   Test: npm run build:web:docker:test
-#   Development: npm run build:web:docker
-#   
-#   Manual workflow:
-#   1. Build web assets: npm run build:web:build -- --mode production
-#   2. Build Docker: docker build -t timesafari:latest .
-#   
-#   Note: For development, use npm run build:web directly (no Docker needed)
-#
-# Build Arguments:
-#   BUILD_MODE: development, test, or production (default: production)
-#   NODE_ENV: node environment (default: production)
-#
-# Environment Variables:
-#   NODE_ENV: Build environment (development/production)
-#   BUILD_MODE: Build mode for asset selection (development/test/production)
-#
-# Build Context:
-#   This Dockerfile is designed to work when the build context is set to
-#   ./crowd-funder-for-time-pwa from the parent directory (where docker-compose.yml is located)
+# Build stage
+FROM node:22-alpine3.20 AS builder
 
-# =============================================================================
-# BASE STAGE - Common dependencies and setup
-# =============================================================================
-FROM node:22-alpine3.20 AS base
+# Install build dependencies
 
-# Install system dependencies for build process
-RUN apk add --no-cache \
-    bash \
-    git \
-    python3 \
-    py3-pip \
-    py3-setuptools \
-    make \
-    g++ \
-    gcc \
-    && rm -rf /var/cache/apk/*
-
-# Create non-root user for security
-RUN addgroup -g 1001 -S nodejs && \
-    adduser -S nextjs -u 1001
+RUN apk add --no-cache bash git python3 py3-pip py3-setuptools make g++ gcc
 
 # Set working directory
 WORKDIR /app
 
-# Copy package files for dependency installation
-# Note: These files are in the project root (crowd-funder-for-time-pwa directory)
+# Copy package files
 COPY package*.json ./
 
-# Install dependencies with security audit
-RUN npm ci --only=production --audit --fund=false && \
-    npm audit fix --audit-level=moderate || true
+# Install dependencies
+RUN npm ci
 
-# =============================================================================
-# BUILDER STAGE - Copy pre-built assets
-# =============================================================================
-FROM base AS builder
+# Copy source code
+COPY . .
 
-# Define build arguments with defaults
-ARG BUILD_MODE=production
-ARG NODE_ENV=production
+# Build the application
+RUN npm run build:web
 
-# Set environment variables from build arguments
-ENV BUILD_MODE=${BUILD_MODE}
-ENV NODE_ENV=${NODE_ENV}
-
-# Copy pre-built assets from host
-# Note: dist/ directory is in the project root (crowd-funder-for-time-pwa directory)
-COPY dist/ ./dist/
-
-# Verify build output exists
-RUN ls -la dist/ || (echo "Build output not found in dist/ directory" && exit 1)
-
-# =============================================================================
-# PRODUCTION STAGE - Nginx server
-# =============================================================================
-FROM nginx:alpine AS production
-
-# Define build arguments for production stage
-ARG BUILD_MODE=production
-ARG NODE_ENV=production
-
-# Set environment variables
-ENV BUILD_MODE=${BUILD_MODE}
-ENV NODE_ENV=${NODE_ENV}
-
-# Install security updates and clean cache
-RUN apk update && \
-    apk upgrade && \
-    apk add --no-cache \
-    curl \
-    && rm -rf /var/cache/apk/*
-
-# Use existing nginx user from base image (nginx user and group already exist)
-# No need to create new user as nginx:alpine already has nginx user
-
-# Copy main nginx configuration
-COPY docker/nginx.conf /etc/nginx/nginx.conf
-
-# Copy production nginx configuration
-COPY docker/default.conf /etc/nginx/conf.d/default.conf
+# Production stage
+FROM nginx:alpine
 
 # Copy built assets from builder stage
-COPY --from=builder --chown=nginx:nginx /app/dist /usr/share/nginx/html
+COPY --from=builder /app/dist /usr/share/nginx/html
 
-# Create necessary directories with proper permissions
-RUN mkdir -p /var/cache/nginx /var/log/nginx /tmp && \
-    chown -R nginx:nginx /var/cache/nginx /var/log/nginx /tmp && \
-    chown -R nginx:nginx /usr/share/nginx/html
-
-# Switch to non-root user
-USER nginx
+# Copy nginx configuration if needed
+# COPY nginx.conf /etc/nginx/conf.d/default.conf
 
 # Expose port 80
 EXPOSE 80
 
-# Health check
-HEALTHCHECK --interval=30s --timeout=3s --start-period=5s --retries=3 \
-    CMD curl -f http://localhost/ || exit 1
-
-# Start nginx with proper signal handling
-CMD ["nginx", "-g", "daemon off;"]
-
-# =============================================================================
-# TEST STAGE - For test environment testing
-# =============================================================================
-FROM production AS test
-
-# Define build arguments for test stage
-ARG BUILD_MODE=test
-ARG NODE_ENV=test
-
-# Set environment variables
-ENV BUILD_MODE=${BUILD_MODE}
-ENV NODE_ENV=${NODE_ENV}
-
-# Copy test-specific nginx configuration
-COPY docker/staging.conf /etc/nginx/conf.d/default.conf
-
-# Expose port 80
-EXPOSE 80
-
-# Health check for staging
-HEALTHCHECK --interval=30s --timeout=3s --start-period=5s --retries=3 \
-    CMD curl -f http://localhost/health || exit 1
-
 # Start nginx
 CMD ["nginx", "-g", "daemon off;"] 

Gemfile

@@ -1,4 +1,5 @@
 source "https://rubygems.org"
 
+gem "fastlane"
 gem "cocoapods"
 

Gemfile.lock

@@ -22,7 +22,26 @@ GEM
     algoliasearch (1.27.5)
       httpclient (~> 2.8, >= 2.8.3)
       json (>= 1.5.1)
+    artifactory (3.0.17)
     atomos (0.1.3)
+    aws-eventstream (1.3.2)
+    aws-partitions (1.1066.0)
+    aws-sdk-core (3.220.1)
+      aws-eventstream (~> 1, >= 1.3.0)
+      aws-partitions (~> 1, >= 1.992.0)
+      aws-sigv4 (~> 1.9)
+      base64
+      jmespath (~> 1, >= 1.6.1)
+    aws-sdk-kms (1.99.0)
+      aws-sdk-core (~> 3, >= 3.216.0)
+      aws-sigv4 (~> 1.5)
+    aws-sdk-s3 (1.182.0)
+      aws-sdk-core (~> 3, >= 3.216.0)
+      aws-sdk-kms (~> 1)
+      aws-sigv4 (~> 1.5)
+    aws-sigv4 (1.11.0)
+      aws-eventstream (~> 1, >= 1.0.2)
+    babosa (1.0.4)
     base64 (0.2.0)
     benchmark (0.4.0)
     bigdecimal (3.1.9)
@@ -64,13 +83,96 @@ GEM
       nap (>= 0.8, < 2.0)
       netrc (~> 0.11)
     cocoapods-try (1.2.0)
+    colored (1.2)
     colored2 (3.1.2)
+    commander (4.6.0)
+      highline (~> 2.0.0)
     concurrent-ruby (1.3.5)
     connection_pool (2.5.0)
+    declarative (0.0.20)
+    digest-crc (0.7.0)
+      rake (>= 12.0.0, < 14.0.0)
+    domain_name (0.6.20240107)
+    dotenv (2.8.1)
     drb (2.2.1)
+    emoji_regex (3.2.3)
     escape (0.0.4)
     ethon (0.16.0)
       ffi (>= 1.15.0)
+    excon (0.112.0)
+    faraday (1.10.4)
+      faraday-em_http (~> 1.0)
+      faraday-em_synchrony (~> 1.0)
+      faraday-excon (~> 1.1)
+      faraday-httpclient (~> 1.0)
+      faraday-multipart (~> 1.0)
+      faraday-net_http (~> 1.0)
+      faraday-net_http_persistent (~> 1.0)
+      faraday-patron (~> 1.0)
+      faraday-rack (~> 1.0)
+      faraday-retry (~> 1.0)
+      ruby2_keywords (>= 0.0.4)
+    faraday-cookie_jar (0.0.7)
+      faraday (>= 0.8.0)
+      http-cookie (~> 1.0.0)
+    faraday-em_http (1.0.0)
+    faraday-em_synchrony (1.0.0)
+    faraday-excon (1.1.0)
+    faraday-httpclient (1.0.1)
+    faraday-multipart (1.1.0)
+      multipart-post (~> 2.0)
+    faraday-net_http (1.0.2)
+    faraday-net_http_persistent (1.2.0)
+    faraday-patron (1.0.0)
+    faraday-rack (1.0.0)
+    faraday-retry (1.0.3)
+    faraday_middleware (1.2.1)
+      faraday (~> 1.0)
+    fastimage (2.4.0)
+    fastlane (2.227.0)
+      CFPropertyList (>= 2.3, < 4.0.0)
+      addressable (>= 2.8, < 3.0.0)
+      artifactory (~> 3.0)
+      aws-sdk-s3 (~> 1.0)
+      babosa (>= 1.0.3, < 2.0.0)
+      bundler (>= 1.12.0, < 3.0.0)
+      colored (~> 1.2)
+      commander (~> 4.6)
+      dotenv (>= 2.1.1, < 3.0.0)
+      emoji_regex (>= 0.1, < 4.0)
+      excon (>= 0.71.0, < 1.0.0)
+      faraday (~> 1.0)
+      faraday-cookie_jar (~> 0.0.6)
+      faraday_middleware (~> 1.0)
+      fastimage (>= 2.1.0, < 3.0.0)
+      fastlane-sirp (>= 1.0.0)
+      gh_inspector (>= 1.1.2, < 2.0.0)
+      google-apis-androidpublisher_v3 (~> 0.3)
+      google-apis-playcustomapp_v1 (~> 0.1)
+      google-cloud-env (>= 1.6.0, < 2.0.0)
+      google-cloud-storage (~> 1.31)
+      highline (~> 2.0)
+      http-cookie (~> 1.0.5)
+      json (< 3.0.0)
+      jwt (>= 2.1.0, < 3)
+      mini_magick (>= 4.9.4, < 5.0.0)
+      multipart-post (>= 2.0.0, < 3.0.0)
+      naturally (~> 2.2)
+      optparse (>= 0.1.1, < 1.0.0)
+      plist (>= 3.1.0, < 4.0.0)
+      rubyzip (>= 2.0.0, < 3.0.0)
+      security (= 0.1.5)
+      simctl (~> 1.6.3)
+      terminal-notifier (>= 2.0.0, < 3.0.0)
+      terminal-table (~> 3)
+      tty-screen (>= 0.6.3, < 1.0.0)
+      tty-spinner (>= 0.8.0, < 1.0.0)
+      word_wrap (~> 1.0.0)
+      xcodeproj (>= 1.13.0, < 2.0.0)
+      xcpretty (~> 0.4.0)
+      xcpretty-travis-formatter (>= 0.0.3, < 2.0.0)
+    fastlane-sirp (1.0.0)
+      sysrandom (~> 1.0)
     ffi (1.17.1)
     ffi (1.17.1-aarch64-linux-gnu)
     ffi (1.17.1-aarch64-linux-musl)
@@ -85,27 +187,107 @@ GEM
     fourflusher (2.3.1)
     fuzzy_match (2.0.4)
     gh_inspector (1.1.3)
+    google-apis-androidpublisher_v3 (0.54.0)
+      google-apis-core (>= 0.11.0, < 2.a)
+    google-apis-core (0.11.3)
+      addressable (~> 2.5, >= 2.5.1)
+      googleauth (>= 0.16.2, < 2.a)
+      httpclient (>= 2.8.1, < 3.a)
+      mini_mime (~> 1.0)
+      representable (~> 3.0)
+      retriable (>= 2.0, < 4.a)
+      rexml
+    google-apis-iamcredentials_v1 (0.17.0)
+      google-apis-core (>= 0.11.0, < 2.a)
+    google-apis-playcustomapp_v1 (0.13.0)
+      google-apis-core (>= 0.11.0, < 2.a)
+    google-apis-storage_v1 (0.31.0)
+      google-apis-core (>= 0.11.0, < 2.a)
+    google-cloud-core (1.8.0)
+      google-cloud-env (>= 1.0, < 3.a)
+      google-cloud-errors (~> 1.0)
+    google-cloud-env (1.6.0)
+      faraday (>= 0.17.3, < 3.0)
+    google-cloud-errors (1.5.0)
+    google-cloud-storage (1.47.0)
+      addressable (~> 2.8)
+      digest-crc (~> 0.4)
+      google-apis-iamcredentials_v1 (~> 0.1)
+      google-apis-storage_v1 (~> 0.31.0)
+      google-cloud-core (~> 1.6)
+      googleauth (>= 0.16.2, < 2.a)
+      mini_mime (~> 1.0)
+    googleauth (1.8.1)
+      faraday (>= 0.17.3, < 3.a)
+      jwt (>= 1.4, < 3.0)
+      multi_json (~> 1.11)
+      os (>= 0.9, < 2.0)
+      signet (>= 0.16, < 2.a)
+    highline (2.0.3)
+    http-cookie (1.0.8)
+      domain_name (~> 0.5)
     httpclient (2.9.0)
       mutex_m
     i18n (1.14.7)
       concurrent-ruby (~> 1.0)
+    jmespath (1.6.2)
     json (2.10.2)
+    jwt (2.10.1)
+      base64
     logger (1.6.6)
+    mini_magick (4.13.2)
+    mini_mime (1.1.5)
     minitest (5.25.5)
     molinillo (0.8.0)
+    multi_json (1.15.0)
+    multipart-post (2.4.1)
     mutex_m (0.3.0)
     nanaimo (0.4.0)
     nap (1.1.0)
+    naturally (2.2.1)
     netrc (0.11.0)
     nkf (0.2.0)
+    optparse (0.6.0)
+    os (1.1.4)
+    plist (3.7.2)
     public_suffix (4.0.7)
+    rake (13.2.1)
+    representable (3.2.0)
+      declarative (< 0.1.0)
+      trailblazer-option (>= 0.1.1, < 0.2.0)
+      uber (< 0.2.0)
+    retriable (3.1.2)
     rexml (3.4.1)
+    rouge (3.28.0)
     ruby-macho (2.5.1)
+    ruby2_keywords (0.0.5)
+    rubyzip (2.4.1)
     securerandom (0.4.1)
+    security (0.1.5)
+    signet (0.19.0)
+      addressable (~> 2.8)
+      faraday (>= 0.17.5, < 3.a)
+      jwt (>= 1.5, < 3.0)
+      multi_json (~> 1.10)
+    simctl (1.6.10)
+      CFPropertyList
+      naturally
+    sysrandom (1.0.5)
+    terminal-notifier (2.0.0)
+    terminal-table (3.0.2)
+      unicode-display_width (>= 1.1.1, < 3)
+    trailblazer-option (0.1.2)
+    tty-cursor (0.7.1)
+    tty-screen (0.8.2)
+    tty-spinner (0.9.3)
+      tty-cursor (~> 0.7)
     typhoeus (1.4.1)
       ethon (>= 0.9.0)
     tzinfo (2.0.6)
       concurrent-ruby (~> 1.0)
+    uber (0.1.0)
+    unicode-display_width (2.6.0)
+    word_wrap (1.0.0)
     xcodeproj (1.27.0)
       CFPropertyList (>= 2.3.3, < 4.0)
       atomos (~> 0.1.3)
@@ -113,6 +295,10 @@ GEM
       colored2 (~> 3.1)
       nanaimo (~> 0.4.0)
       rexml (>= 3.3.6, < 4.0)
+    xcpretty (0.4.0)
+      rouge (~> 3.28.0)
+    xcpretty-travis-formatter (1.0.1)
+      xcpretty (~> 0.2, >= 0.0.7)
 
 PLATFORMS
   aarch64-linux-gnu
@@ -129,6 +315,7 @@ PLATFORMS
 
 DEPENDENCIES
   cocoapods
+  fastlane
 
 BUNDLED WITH
    2.6.5

README.md

@@ -5,7 +5,8 @@ and expand to crowd-fund with time & money, then record and see the impact of co
 
 ## Roadmap
 
-See [ClickUp](https://sharing.clickup.com/9014278710/l/h/8cmnyhp-174/10573fec74e2ba0) for current priorities.
+See [project.task.yaml](project.task.yaml) for current priorities.
+(Numbers at the beginning of lines are estimated hours. See [taskyaml.org](https://taskyaml.org/) for details.)
 
 ## Setup & Building
 
@@ -15,198 +16,26 @@ Quick start:
 
 ```bash
 npm install
-npm run build:web:serve -- --test
+npm run dev
 ```
 
-To be able to make submissions: go to "profile" (bottom left), go to the bottom and expand "Show Advanced Settings", go to the bottom and to the "Test Page", and finally "Become User 0" to see all the functionality.
+See [BUILDING.md](BUILDING.md) for more details.
 
-See [BUILDING.md](BUILDING.md) for comprehensive build instructions for all platforms (Web, Electron, iOS, Android, Docker).
 
-## Development Database Clearing
 
-TimeSafari provides a simple script-based approach to clear the local database (not the claim server) for development purposes.
-
-## Logging Configuration
-
-TimeSafari supports configurable logging levels via the `VITE_LOG_LEVEL` environment variable. This allows developers to control console output verbosity without modifying code.
-
-### Quick Usage
-
-```bash
-# Show only errors
-VITE_LOG_LEVEL=error npm run dev
-
-# Show warnings and errors
-VITE_LOG_LEVEL=warn npm run dev
-
-# Show info, warnings, and errors (default)
-VITE_LOG_LEVEL=info npm run dev
-
-# Show all log levels including debug
-VITE_LOG_LEVEL=debug npm run dev
-```
-
-### Available Levels
-
-- **`error`**: Critical errors only
-- **`warn`**: Warnings and errors (default for production web)
-- **`info`**: Info, warnings, and errors (default for development/capacitor)
-- **`debug`**: All log levels including verbose debugging
-
-See [Logging Configuration Guide](doc/logging-configuration.md) for complete details.
-
-### Quick Usage
-```bash
-# Run the database clearing script
-./scripts/clear-database.sh
-
-# Then restart your development server
-npm run build:electron:dev  # For Electron
-npm run build:web:dev       # For Web
-```
-
-### What It Does
-
-#### **Electron (Desktop App)**
-- Automatically finds and clears the SQLite database files
-- Works on Linux, macOS, and Windows
-- Clears all data and forces fresh migrations on next startup
-
-#### **Web Browser**
-- Provides instructions for using custom browser data directories
-- Shows manual clearing via browser DevTools
-- Ensures reliable database clearing without browser complications
-
-### Safety Features
-- ✅ **Interactive Script**: Guides you through the process
-- ✅ **Platform Detection**: Automatically detects your OS
-- ✅ **Clear Instructions**: Step-by-step guidance for each platform
-- ✅ **Safe Paths**: Only clears TimeSafari-specific data
-
-### Manual Commands (if needed)
-
-#### **Electron Database Location**
-```bash
-# Linux
-rm -rf ~/.config/TimeSafari/*
-
-# macOS  
-rm -rf ~/Library/Application\ Support/TimeSafari/*
-
-# Windows
-rmdir /s /q %APPDATA%\TimeSafari
-```
-
-#### **Web Browser (Custom Data Directory)**
-```bash
-# Create isolated browser profile
-mkdir ~/timesafari-dev-data
-```
-
-## Domain Configuration
-
-TimeSafari uses a centralized domain configuration system to ensure consistent
-URL generation across all environments. This prevents localhost URLs from
-appearing in shared links during development.
-
-### Key Features
-- ✅ **Production URLs for Sharing**: All copy link buttons use production domain
-- ✅ **Environment-Specific Internal URLs**: Internal operations use appropriate
-  environment URLs
-- ✅ **Single Point of Control**: Change domain in one place for entire app
-- ✅ **Type-Safe Configuration**: Full TypeScript support
-
-### Quick Reference
-
-```typescript
-// For sharing functionality (environment-specific)
-import { APP_SERVER } from "@/constants/app";
-const shareLink = `${APP_SERVER}/deep-link/claim/123`;
-
-// For internal operations (environment-specific)
-import { APP_SERVER } from "@/constants/app";
-const apiUrl = `${APP_SERVER}/api/claim/123`;
-```
-
-### Documentation
-
-- [Constants and Configuration](src/constants/app.ts) - Core constants
 
 ## Tests
 
 See [TESTING.md](test-playwright/TESTING.md) for detailed test instructions.
 
-## Asset Management
 
-TimeSafari uses a standardized asset configuration system for consistent
-icon and splash screen generation across all platforms.
 
-### Asset Sources
 
-- **Single source of truth**: `resources/` directory (Capacitor default)
-- **Source files**: `icon.png`, `splash.png`, `splash_dark.png`
-- **Format**: PNG or SVG files for optimal quality
+## Icons
 
-### Asset Generation
+Application icons are in the `assets` directory, processed by the `capacitor-assets` command.
 
-- **Configuration**: `config/assets/capacitor-assets.config.json`
-- **Schema validation**: `config/assets/schema.json`
-- **Build-time generation**: Platform assets generated via `capacitor-assets`
-- **No VCS commits**: Generated assets are never committed to version control
-
-### Development Commands
-
-```bash
-# Generate/update asset configurations
-npm run assets:config
-
-# Validate asset configurations
-npm run assets:validate
-
-# Clean generated platform assets (local dev only)
-npm run assets:clean
-
-# Build with asset generation
-npm run build:native
-```
-
-### Environment Setup & Dependencies
-
-Before building the application, ensure your development environment is properly
-configured:
-
-```bash
-# Install all dependencies (required first time and after updates)
-npm install
-
-# Validate your development environment
-npm run check:dependencies
-
-# Check prerequisites for testing
-npm run test:prerequisites
-```
-
-**Common Issues & Solutions**:
-
-- **"tsx: command not found"**: Run `npm install` to install devDependencies
-- **"capacitor-assets: command not found"**: Ensure `@capacitor/assets` is installed
-- **Build failures**: Run `npm run check:dependencies` to diagnose environment issues
-
-**Required Versions**:
-- Node.js: 18+ (LTS recommended)
-- npm: 8+ (comes with Node.js)
-- Platform-specific tools: Android Studio, Xcode (for mobile builds)
-
-### Platform Support
-
-- **Android**: Adaptive icons with foreground/background, monochrome support
-- **iOS**: LaunchScreen storyboard preferred, splash assets when needed
-- **Web**: PWA icons generated during build to `dist/` (not committed)
-
-### Font Awesome Icons
-
-To add a Font Awesome icon, add to `fontawesome.ts` and reference with
-`font-awesome` element and `icon` attribute with the hyphenated name.
+To add a Font Awesome icon, add to main.ts and reference with `font-awesome` element and `icon` attribute with the hyphenated name.
 
 ## Other
 
@@ -237,25 +66,6 @@ Key principles:
 - Common interfaces are shared through `common.ts`
 - Type definitions are generated from Zod schemas where possible
 
-### Database Architecture
-
-The application uses a platform-agnostic database layer with Vue mixins for service access:
-
-* `src/services/PlatformService.ts` - Database interface definition
-* `src/services/PlatformServiceFactory.ts` - Platform-specific service factory
-* `src/services/AbsurdSqlDatabaseService.ts` - SQLite implementation
-* `src/utils/PlatformServiceMixin.ts` - Vue mixin for database access with caching
-* `src/db/` - Legacy Dexie database (migration in progress)
-
-**Development Guidelines**:
-
-- Always use `PlatformServiceMixin` for database operations in components
-- Test with PlatformServiceMixin for new features
-- Use migration tools for data transfer between systems
-- Leverage mixin's ultra-concise methods: `$db()`, `$exec()`, `$one()`, `$contacts()`, `$settings()`
-
-**Architecture Decision**: The project uses Vue mixins over Composition API composables for platform service access. See [Architecture Decisions](doc/architecture-decisions.md) for detailed rationale.
-
 ### Kudos
 
 Gifts make the world go 'round!

android/.gitignore

@@ -84,6 +84,13 @@ freeline.py
 freeline/
 freeline_project_description.json
 
+# fastlane
+fastlane/report.xml
+fastlane/Preview.html
+fastlane/screenshots
+fastlane/test_output
+fastlane/readme.md
+
 # Version control
 vcs.xml
 

android/app/build.gradle

@@ -31,8 +31,8 @@ android {
         applicationId "app.timesafari.app"
         minSdkVersion rootProject.ext.minSdkVersion
         targetSdkVersion rootProject.ext.targetSdkVersion
-        versionCode 40
-        versionName "1.0.7"
+        versionCode 25
+        versionName "0.5.0"
         testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
         aaptOptions {
              // Files and dirs to omit from the packaged assets dir, modified to accommodate modern web apps.
@@ -64,14 +64,6 @@ android {
             }
         }
     }
-    packagingOptions {
-        jniLibs {
-            pickFirsts += ['**/lib/x86_64/libbarhopper_v3.so', '**/lib/x86_64/libimage_processing_util_jni.so', '**/lib/x86_64/libsqlcipher.so']
-        }
-    }
-
-    // Configure for 16 KB page size compatibility
-
 
     // Enable bundle builds (without which it doesn't work right for bundleDebug vs bundleRelease)
     bundle {

android/app/src/main/AndroidManifest.xml

@@ -13,7 +13,6 @@
             android:exported="true"
             android:label="@string/title_activity_main"
             android:launchMode="singleTask"
-            android:screenOrientation="portrait"
             android:theme="@style/AppTheme.NoActionBarLaunch">
             <intent-filter>
                 <action android:name="android.intent.action.MAIN" />

android/app/src/main/assets/capacitor.config.json

@@ -2,6 +2,7 @@
 	"appId": "app.timesafari",
 	"appName": "TimeSafari",
 	"webDir": "dist",
+	"bundledWebRuntime": false,
 	"server": {
 		"cleartext": true
 	},
@@ -16,32 +17,18 @@
 				]
 			}
 		},
-		"SplashScreen": {
-			"launchShowDuration": 3000,
-			"launchAutoHide": true,
-			"backgroundColor": "#ffffff",
-			"androidSplashResourceName": "splash",
-			"androidScaleType": "CENTER_CROP",
-			"showSpinner": false,
-			"androidSpinnerStyle": "large",
-			"iosSpinnerStyle": "small",
-			"spinnerColor": "#999999",
-			"splashFullScreen": true,
-			"splashImmersive": true
-		},
-		"CapSQLite": {
+		"SQLite": {
 			"iosDatabaseLocation": "Library/CapacitorDatabase",
-			"iosIsEncryption": false,
+			"iosIsEncryption": true,
 			"iosBiometric": {
-				"biometricAuth": false,
+				"biometricAuth": true,
 				"biometricTitle": "Biometric login for TimeSafari"
 			},
-			"androidIsEncryption": false,
+			"androidIsEncryption": true,
 			"androidBiometric": {
-				"biometricAuth": false,
+				"biometricAuth": true,
 				"biometricTitle": "Biometric login for TimeSafari"
-			},
-			"electronIsEncryption": false
+			}
 		}
 	},
 	"ios": {
@@ -57,65 +44,13 @@
 		]
 	},
 	"android": {
-		"allowMixedContent": true,
+		"allowMixedContent": false,
 		"captureInput": true,
 		"webContentsDebuggingEnabled": false,
 		"allowNavigation": [
 			"*.timesafari.app",
 			"*.jsdelivr.net",
-			"api.endorser.ch",
-			"10.0.2.2:3000"
+			"api.endorser.ch"
 		]
-	},
-	"electron": {
-		"deepLinking": {
-			"schemes": [
-				"timesafari"
-			]
-		},
-		"buildOptions": {
-			"appId": "app.timesafari",
-			"productName": "TimeSafari",
-			"directories": {
-				"output": "dist-electron-packages"
-			},
-			"files": [
-				"dist/**/*",
-				"electron/**/*"
-			],
-			"mac": {
-				"category": "public.app-category.productivity",
-				"target": [
-					{
-						"target": "dmg",
-						"arch": [
-							"x64",
-							"arm64"
-						]
-					}
-				]
-			},
-			"win": {
-				"target": [
-					{
-						"target": "nsis",
-						"arch": [
-							"x64"
-						]
-					}
-				]
-			},
-			"linux": {
-				"target": [
-					{
-						"target": "AppImage",
-						"arch": [
-							"x64"
-						]
-					}
-				],
-				"category": "Utility"
-			}
-		}
 	}
 }

android/app/src/main/assets/public/img/icons/safari-pinned-tab-512x512.svg

@@ -0,0 +1,86 @@
+<?xml version="1.0" standalone="no"?>
+<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 20010904//EN"
+ "http://www.w3.org/TR/2001/REC-SVG-20010904/DTD/svg10.dtd">
+<svg version="1.0" xmlns="http://www.w3.org/2000/svg"
+ width="512.000000pt" height="512.000000pt" viewBox="0 0 512.000000 512.000000"
+ preserveAspectRatio="xMidYMid meet">
+
+<g transform="translate(0.000000,512.000000) scale(0.100000,-0.100000)"
+fill="#000000" stroke="none">
+<path d="M2480 4005 c-25 -7 -58 -20 -75 -29 -16 -9 -40 -16 -52 -16 -17 0
+-24 -7 -28 -27 -3 -16 -14 -45 -24 -65 -21 -41 -13 -55 18 -38 25 13 67 13 92
+-1 15 -8 35 -4 87 17 99 39 130 41 197 10 64 -29 77 -31 107 -15 20 11 20 11
+-3 35 -12 13 -30 24 -38 24 -24 1 -132 38 -148 51 -8 7 -11 20 -7 32 12 37
+-40 47 -126 22z"/>
+<path d="M1450 3775 c-7 -8 -18 -15 -24 -15 -7 0 -31 -14 -54 -32 -29 -22 -38
+-34 -29 -40 17 -11 77 -10 77 1 0 5 16 16 35 25 60 29 220 19 290 -18 17 -9
+33 -16 37 -16 4 0 31 -15 60 -34 108 -70 224 -215 282 -353 30 -71 53 -190 42
+-218 -10 -27 -23 -8 -52 75 -30 90 -88 188 -120 202 -13 6 -26 9 -29 6 -3 -2
+11 -51 30 -108 28 -83 35 -119 35 -179 0 -120 -22 -127 -54 -17 -11 37 -13 21
+-18 -154 -5 -180 -8 -200 -32 -264 -51 -132 -129 -245 -199 -288 -21 -12 -79
+-49 -129 -80 -161 -102 -294 -141 -473 -141 -228 0 -384 76 -535 259 -81 99
+-118 174 -154 312 -31 121 -35 273 -11 437 19 127 19 125 -4 125 -23 0 -51
+-34 -87 -104 -14 -28 -33 -64 -41 -81 -19 -34 -22 -253 -7 -445 9 -106 12
+-119 44 -170 19 -30 42 -67 50 -81 64 -113 85 -140 130 -169 28 -18 53 -44 61
+-62 8 -20 36 -45 83 -76 62 -39 80 -46 151 -54 44 -5 96 -13 115 -18 78 -20
+238 -31 282 -19 24 6 66 8 95 5 76 -9 169 24 319 114 32 19 80 56 106 82 27
+26 52 48 58 48 5 0 27 26 50 58 48 66 56 70 132 71 62 1 165 29 238 64 112 55
+177 121 239 245 37 76 39 113 10 267 -12 61 -23 131 -26 156 -5 46 -5 47 46
+87 92 73 182 70 263 -8 l51 -49 -6 -61 c-4 -34 -13 -85 -21 -113 -28 -103 -30
+-161 -4 -228 16 -44 32 -67 55 -83 18 -11 39 -37 47 -58 10 -23 37 -53 73 -81
+32 -25 69 -57 82 -71 14 -14 34 -26 47 -26 12 0 37 -7 56 -15 20 -8 66 -17
+104 -20 107 -10 110 -11 150 -71 50 -75 157 -177 197 -187 18 -5 53 -24 78
+-42 71 -51 176 -82 304 -89 61 -4 127 -12 147 -18 29 -9 45 -8 77 6 23 9 50
+16 60 16 31 0 163 46 216 76 28 15 75 46 105 69 30 23 69 49 85 58 17 8 46 31
+64 51 19 20 40 36 47 36 18 0 77 70 100 120 32 66 45 108 55 173 5 32 16 71
+24 87 43 84 43 376 0 549 -27 105 -43 127 -135 188 -30 21 -65 46 -77 57 -13
+11 -23 17 -23 14 0 -3 21 -46 47 -94 79 -151 85 -166 115 -263 25 -83 28 -110
+28 -226 0 -144 -17 -221 -75 -335 -39 -77 -208 -244 -304 -299 -451 -263 -975
+-67 -1138 426 -23 70 -26 95 -28 254 -1 108 -7 183 -14 196 -6 12 -11 31 -11
+43 0 32 31 122 52 149 10 13 18 28 18 34 0 5 25 40 56 78 60 73 172 170 219
+190 30 12 30 13 6 17 -15 2 -29 -2 -37 -12 -6 -9 -16 -16 -22 -16 -6 0 -23
+-11 -39 -24 -15 -12 -33 -25 -40 -27 -17 -6 -82 -60 -117 -97 -65 -70 -75 -82
+-107 -133 -23 -34 -35 -46 -37 -35 -3 16 20 87 44 134 6 12 9 34 6 48 -4 22
+-8 25 -31 19 -14 -3 -38 -15 -53 -26 -34 -24 -34 -21 -6 28 65 112 184 206
+291 227 15 3 39 9 55 12 l27 6 -24 9 c-90 35 -304 -66 -478 -225 -39 -36 -74
+-66 -77 -66 -22 0 18 82 72 148 19 23 32 46 28 49 -4 4 -26 13 -49 19 -73 21
+-161 54 -171 64 -6 6 -20 10 -32 10 -21 0 -21 -1 -8 -40 45 -130 8 -247 -93
+-299 -25 -13 -31 0 -14 29 15 22 1 33 -22 17 -56 -36 -117 -22 -117 28 0 13
+-16 47 -35 76 -22 34 -33 60 -29 73 4 16 -3 26 -26 39 -16 10 -30 21 -30 25 1
+18 54 64 87 76 l38 13 -33 5 c-30 4 -115 -18 -154 -42 -13 -7 -20 -5 -27 8 -9
+16 -12 16 -53 1 -160 -61 -258 -104 -258 -114 0 -7 10 -20 21 -31 103 -91 217
+-297 249 -449 28 -135 41 -237 35 -276 -14 -91 -48 -170 -97 -220 -44 -47 -68
+-60 -68 -40 0 6 4 12 8 15 5 3 24 35 42 72 l33 67 -6 141 c-4 103 -11 158 -26
+205 -12 35 -21 70 -21 77 0 7 -20 56 -45 108 -82 173 -227 322 -392 401 -67
+33 -90 39 -163 42 -108 5 -130 10 -130 28 0 20 -63 20 -80 0z"/>
+<path d="M3710 3765 c0 -20 8 -28 39 -41 22 -8 42 -22 45 -30 5 -14 42 -19 70
+-8 10 4 -7 21 -58 55 -41 27 -79 49 -85 49 -6 0 -11 -11 -11 -25z"/>
+<path d="M3173 3734 c-9 -25 10 -36 35 -18 12 8 22 19 22 25 0 16 -50 10 -57
+-7z"/>
+<path d="M1982 3728 c6 -16 36 -34 44 -26 3 4 4 14 1 23 -7 17 -51 21 -45 3z"/>
+<path d="M1540 3620 c0 -5 7 -10 16 -10 8 0 12 5 9 10 -3 6 -10 10 -16 10 -5
+0 -9 -4 -9 -10z"/>
+<path d="M4467 3624 c-4 -4 23 -27 60 -50 84 -56 99 -58 67 -9 -28 43 -107 79
+-127 59z"/>
+<path d="M655 3552 c-11 -2 -26 -9 -33 -14 -7 -6 -27 -18 -45 -27 -36 -18 -58
+-64 -39 -83 9 -9 25 1 70 43 53 48 78 78 70 84 -2 1 -12 -1 -23 -3z"/>
+<path d="M1015 3460 c-112 -24 -247 -98 -303 -165 -53 -65 -118 -214 -136
+-311 -20 -113 -20 -145 -1 -231 20 -88 49 -153 102 -230 79 -113 186 -182 331
+-214 108 -24 141 -24 247 1 130 30 202 72 316 181 102 100 153 227 152 384 0
+142 -58 293 -150 395 -60 67 -180 145 -261 171 -75 23 -232 34 -297 19z m340
+-214 c91 -43 174 -154 175 -234 0 -18 -9 -51 -21 -73 -19 -37 -19 -42 -5 -64
+35 -54 12 -121 -48 -142 -22 -7 -47 -19 -55 -27 -9 -8 -41 -27 -71 -42 -50
+-26 -64 -29 -155 -29 -111 0 -152 14 -206 68 -49 49 -63 85 -64 162 0 59 4 78
+28 118 31 52 96 105 141 114 23 5 33 17 56 68 46 103 121 130 225 81z"/>
+<path d="M3985 3464 c-44 -7 -154 -44 -200 -67 -55 -28 -138 -96 -162 -132
+-10 -16 -39 -75 -64 -130 l-44 -100 0 -160 0 -160 45 -90 c53 -108 152 -214
+245 -264 59 -31 215 -71 281 -71 53 0 206 40 255 67 98 53 203 161 247 253 53
+113 74 193 74 280 -1 304 -253 564 -557 575 -49 2 -103 1 -120 -1z m311 -220
+c129 -68 202 -209 160 -309 -15 -35 -15 -42 -1 -72 26 -55 -3 -118 -59 -129
+-19 -3 -43 -15 -53 -26 -26 -29 -99 -64 -165 -78 -45 -10 -69 -10 -120 -1 -74
+15 -113 37 -161 91 -110 120 -50 331 109 385 24 8 44 23 52 39 6 14 18 38 25
+53 33 72 127 93 213 47z"/>
+<path d="M487 3394 c-21 -12 -27 -21 -25 -40 2 -14 7 -26 12 -27 14 -3 48 48
+44 66 -3 14 -6 14 -31 1z"/>
+</g>
+</svg>

android/app/src/main/assets/public/models/lupine_plant/license.txt

@@ -0,0 +1,11 @@
+Model Information:
+* title:	Lupine Plant
+* source:	https://sketchfab.com/3d-models/lupine-plant-bf30f1110c174d4baedda0ed63778439
+* author:	rufusrockwell (https://sketchfab.com/rufusrockwell)
+
+Model License:
+* license type:	CC-BY-4.0 (http://creativecommons.org/licenses/by/4.0/)
+* requirements:	Author must be credited. Commercial use is allowed.
+
+If you use this 3D model in your project be sure to copy paste this credit wherever you share it:
+This work is based on "Lupine Plant" (https://sketchfab.com/3d-models/lupine-plant-bf30f1110c174d4baedda0ed63778439) by rufusrockwell (https://sketchfab.com/rufusrockwell) licensed under CC-BY-4.0 (http://creativecommons.org/licenses/by/4.0/)

android/app/src/main/assets/public/models/lupine_plant/scene.gltf

@@ -0,0 +1,229 @@
+{
+  "accessors": [
+    {
+      "bufferView": 2,
+      "componentType": 5126,
+      "count": 2759,
+      "max": [
+        41.3074951171875,
+        40.37548828125,
+        87.85917663574219
+      ],
+      "min": [
+        -35.245540618896484,
+        -36.895416259765625,
+        -0.9094290137290955
+      ],
+      "type": "VEC3"
+    },
+    {
+      "bufferView": 2,
+      "byteOffset": 33108,
+      "componentType": 5126,
+      "count": 2759,
+      "max": [
+        0.9999382495880127,
+        0.9986748695373535,
+        0.9985831379890442
+      ],
+      "min": [
+        -0.9998949766159058,
+        -0.9975876212120056,
+        -0.411094069480896
+      ],
+      "type": "VEC3"
+    },
+    {
+      "bufferView": 3,
+      "componentType": 5126,
+      "count": 2759,
+      "max": [
+        0.9987699389457703,
+        0.9998998045921326,
+        0.9577858448028564,
+        1.0
+      ],
+      "min": [
+        -0.9987726807594299,
+        -0.9990445971488953,
+        -0.999801516532898,
+        1.0
+      ],
+      "type": "VEC4"
+    },
+    {
+      "bufferView": 1,
+      "componentType": 5126,
+      "count": 2759,
+      "max": [
+        1.0061479806900024,
+        0.9993550181388855
+      ],
+      "min": [
+        0.00279300007969141,
+        0.0011620000004768372
+      ],
+      "type": "VEC2"
+    },
+    {
+      "bufferView": 0,
+      "componentType": 5125,
+      "count": 6378,
+      "type": "SCALAR"
+    }
+  ],
+  "asset": {
+    "extras": {
+      "author": "rufusrockwell (https://sketchfab.com/rufusrockwell)",
+      "license": "CC-BY-4.0 (http://creativecommons.org/licenses/by/4.0/)",
+      "source": "https://sketchfab.com/3d-models/lupine-plant-bf30f1110c174d4baedda0ed63778439",
+      "title": "Lupine Plant"
+    },
+    "generator": "Sketchfab-12.68.0",
+    "version": "2.0"
+  },
+  "bufferViews": [
+    {
+      "buffer": 0,
+      "byteLength": 25512,
+      "name": "floatBufferViews",
+      "target": 34963
+    },
+    {
+      "buffer": 0,
+      "byteLength": 22072,
+      "byteOffset": 25512,
+      "byteStride": 8,
+      "name": "floatBufferViews",
+      "target": 34962
+    },
+    {
+      "buffer": 0,
+      "byteLength": 66216,
+      "byteOffset": 47584,
+      "byteStride": 12,
+      "name": "floatBufferViews",
+      "target": 34962
+    },
+    {
+      "buffer": 0,
+      "byteLength": 44144,
+      "byteOffset": 113800,
+      "byteStride": 16,
+      "name": "floatBufferViews",
+      "target": 34962
+    }
+  ],
+  "buffers": [
+    {
+      "byteLength": 157944,
+      "uri": "scene.bin"
+    }
+  ],
+  "images": [
+    {
+      "uri": "textures/lambert2SG_baseColor.png"
+    },
+    {
+      "uri": "textures/lambert2SG_normal.png"
+    }
+  ],
+  "materials": [
+    {
+      "alphaCutoff": 0.2,
+      "alphaMode": "MASK",
+      "doubleSided": true,
+      "name": "lambert2SG",
+      "normalTexture": {
+        "index": 1
+      },
+      "pbrMetallicRoughness": {
+        "baseColorTexture": {
+          "index": 0
+        },
+        "metallicFactor": 0.0
+      }
+    }
+  ],
+  "meshes": [
+    {
+      "name": "Object_0",
+      "primitives": [
+        {
+          "attributes": {
+            "NORMAL": 1,
+            "POSITION": 0,
+            "TANGENT": 2,
+            "TEXCOORD_0": 3
+          },
+          "indices": 4,
+          "material": 0,
+          "mode": 4
+        }
+      ]
+    }
+  ],
+  "nodes": [
+    {
+      "children": [
+        1
+      ],
+      "matrix": [
+        1.0,
+        0.0,
+        0.0,
+        0.0,
+        0.0,
+        2.220446049250313e-16,
+        -1.0,
+        0.0,
+        0.0,
+        1.0,
+        2.220446049250313e-16,
+        0.0,
+        0.0,
+        0.0,
+        0.0,
+        1.0
+      ],
+      "name": "Sketchfab_model"
+    },
+    {
+      "children": [
+        2
+      ],
+      "name": "LupineSF.obj.cleaner.materialmerger.gles"
+    },
+    {
+      "mesh": 0,
+      "name": "Object_2"
+    }
+  ],
+  "samplers": [
+    {
+      "magFilter": 9729,
+      "minFilter": 9987,
+      "wrapS": 10497,
+      "wrapT": 10497
+    }
+  ],
+  "scene": 0,
+  "scenes": [
+    {
+      "name": "Sketchfab_Scene",
+      "nodes": [
+        0
+      ]
+    }
+  ],
+  "textures": [
+    {
+      "sampler": 0,
+      "source": 0
+    },
+    {
+      "sampler": 0,
+      "source": 1
+    }
+  ]
+}

android/app/src/main/assets/public/robots.txt

@@ -0,0 +1,2 @@
+User-agent: *
+Disallow:

android/app/src/main/res/drawable-v24/ic_launcher_foreground.xml

@@ -0,0 +1,34 @@
+<vector xmlns:android="http://schemas.android.com/apk/res/android"
+    xmlns:aapt="http://schemas.android.com/aapt"
+    android:width="108dp"
+    android:height="108dp"
+    android:viewportHeight="108"
+    android:viewportWidth="108">
+    <path
+        android:fillType="evenOdd"
+        android:pathData="M32,64C32,64 38.39,52.99 44.13,50.95C51.37,48.37 70.14,49.57 70.14,49.57L108.26,87.69L108,109.01L75.97,107.97L32,64Z"
+        android:strokeColor="#00000000"
+        android:strokeWidth="1">
+        <aapt:attr name="android:fillColor">
+            <gradient
+                android:endX="78.5885"
+                android:endY="90.9159"
+                android:startX="48.7653"
+                android:startY="61.0927"
+                android:type="linear">
+                <item
+                    android:color="#44000000"
+                    android:offset="0.0" />
+                <item
+                    android:color="#00000000"
+                    android:offset="1.0" />
+            </gradient>
+        </aapt:attr>
+    </path>
+    <path
+        android:fillColor="#FFFFFF"
+        android:fillType="nonZero"
+        android:pathData="M66.94,46.02L66.94,46.02C72.44,50.07 76,56.61 76,64L32,64C32,56.61 35.56,50.11 40.98,46.06L36.18,41.19C35.45,40.45 35.45,39.3 36.18,38.56C36.91,37.81 38.05,37.81 38.78,38.56L44.25,44.05C47.18,42.57 50.48,41.71 54,41.71C57.48,41.71 60.78,42.57 63.68,44.05L69.11,38.56C69.84,37.81 70.98,37.81 71.71,38.56C72.44,39.3 72.44,40.45 71.71,41.19L66.94,46.02ZM62.94,56.92C64.08,56.92 65,56.01 65,54.88C65,53.76 64.08,52.85 62.94,52.85C61.8,52.85 60.88,53.76 60.88,54.88C60.88,56.01 61.8,56.92 62.94,56.92ZM45.06,56.92C46.2,56.92 47.13,56.01 47.13,54.88C47.13,53.76 46.2,52.85 45.06,52.85C43.92,52.85 43,53.76 43,54.88C43,56.01 43.92,56.92 45.06,56.92Z"
+        android:strokeColor="#00000000"
+        android:strokeWidth="1" />
+</vector>

android/app/src/main/res/drawable/ic_launcher_background.xml

@@ -0,0 +1,170 @@
+<?xml version="1.0" encoding="utf-8"?>
+<vector xmlns:android="http://schemas.android.com/apk/res/android"
+    android:width="108dp"
+    android:height="108dp"
+    android:viewportHeight="108"
+    android:viewportWidth="108">
+    <path
+        android:fillColor="#26A69A"
+        android:pathData="M0,0h108v108h-108z" />
+    <path
+        android:fillColor="#00000000"
+        android:pathData="M9,0L9,108"
+        android:strokeColor="#33FFFFFF"
+        android:strokeWidth="0.8" />
+    <path
+        android:fillColor="#00000000"
+        android:pathData="M19,0L19,108"
+        android:strokeColor="#33FFFFFF"
+        android:strokeWidth="0.8" />
+    <path
+        android:fillColor="#00000000"
+        android:pathData="M29,0L29,108"
+        android:strokeColor="#33FFFFFF"
+        android:strokeWidth="0.8" />
+    <path
+        android:fillColor="#00000000"
+        android:pathData="M39,0L39,108"
+        android:strokeColor="#33FFFFFF"
+        android:strokeWidth="0.8" />
+    <path
+        android:fillColor="#00000000"
+        android:pathData="M49,0L49,108"
+        android:strokeColor="#33FFFFFF"
+        android:strokeWidth="0.8" />
+    <path
+        android:fillColor="#00000000"
+        android:pathData="M59,0L59,108"
+        android:strokeColor="#33FFFFFF"
+        android:strokeWidth="0.8" />
+    <path
+        android:fillColor="#00000000"
+        android:pathData="M69,0L69,108"
+        android:strokeColor="#33FFFFFF"
+        android:strokeWidth="0.8" />
+    <path
+        android:fillColor="#00000000"
+        android:pathData="M79,0L79,108"
+        android:strokeColor="#33FFFFFF"
+        android:strokeWidth="0.8" />
+    <path
+        android:fillColor="#00000000"
+        android:pathData="M89,0L89,108"
+        android:strokeColor="#33FFFFFF"
+        android:strokeWidth="0.8" />
+    <path
+        android:fillColor="#00000000"
+        android:pathData="M99,0L99,108"
+        android:strokeColor="#33FFFFFF"
+        android:strokeWidth="0.8" />
+    <path
+        android:fillColor="#00000000"
+        android:pathData="M0,9L108,9"
+        android:strokeColor="#33FFFFFF"
+        android:strokeWidth="0.8" />
+    <path
+        android:fillColor="#00000000"
+        android:pathData="M0,19L108,19"
+        android:strokeColor="#33FFFFFF"
+        android:strokeWidth="0.8" />
+    <path
+        android:fillColor="#00000000"
+        android:pathData="M0,29L108,29"
+        android:strokeColor="#33FFFFFF"
+        android:strokeWidth="0.8" />
+    <path
+        android:fillColor="#00000000"
+        android:pathData="M0,39L108,39"
+        android:strokeColor="#33FFFFFF"
+        android:strokeWidth="0.8" />
+    <path
+        android:fillColor="#00000000"
+        android:pathData="M0,49L108,49"
+        android:strokeColor="#33FFFFFF"
+        android:strokeWidth="0.8" />
+    <path
+        android:fillColor="#00000000"
+        android:pathData="M0,59L108,59"
+        android:strokeColor="#33FFFFFF"
+        android:strokeWidth="0.8" />
+    <path
+        android:fillColor="#00000000"
+        android:pathData="M0,69L108,69"
+        android:strokeColor="#33FFFFFF"
+        android:strokeWidth="0.8" />
+    <path
+        android:fillColor="#00000000"
+        android:pathData="M0,79L108,79"
+        android:strokeColor="#33FFFFFF"
+        android:strokeWidth="0.8" />
+    <path
+        android:fillColor="#00000000"
+        android:pathData="M0,89L108,89"
+        android:strokeColor="#33FFFFFF"
+        android:strokeWidth="0.8" />
+    <path
+        android:fillColor="#00000000"
+        android:pathData="M0,99L108,99"
+        android:strokeColor="#33FFFFFF"
+        android:strokeWidth="0.8" />
+    <path
+        android:fillColor="#00000000"
+        android:pathData="M19,29L89,29"
+        android:strokeColor="#33FFFFFF"
+        android:strokeWidth="0.8" />
+    <path
+        android:fillColor="#00000000"
+        android:pathData="M19,39L89,39"
+        android:strokeColor="#33FFFFFF"
+        android:strokeWidth="0.8" />
+    <path
+        android:fillColor="#00000000"
+        android:pathData="M19,49L89,49"
+        android:strokeColor="#33FFFFFF"
+        android:strokeWidth="0.8" />
+    <path
+        android:fillColor="#00000000"
+        android:pathData="M19,59L89,59"
+        android:strokeColor="#33FFFFFF"
+        android:strokeWidth="0.8" />
+    <path
+        android:fillColor="#00000000"
+        android:pathData="M19,69L89,69"
+        android:strokeColor="#33FFFFFF"
+        android:strokeWidth="0.8" />
+    <path
+        android:fillColor="#00000000"
+        android:pathData="M19,79L89,79"
+        android:strokeColor="#33FFFFFF"
+        android:strokeWidth="0.8" />
+    <path
+        android:fillColor="#00000000"
+        android:pathData="M29,19L29,89"
+        android:strokeColor="#33FFFFFF"
+        android:strokeWidth="0.8" />
+    <path
+        android:fillColor="#00000000"
+        android:pathData="M39,19L39,89"
+        android:strokeColor="#33FFFFFF"
+        android:strokeWidth="0.8" />
+    <path
+        android:fillColor="#00000000"
+        android:pathData="M49,19L49,89"
+        android:strokeColor="#33FFFFFF"
+        android:strokeWidth="0.8" />
+    <path
+        android:fillColor="#00000000"
+        android:pathData="M59,19L59,89"
+        android:strokeColor="#33FFFFFF"
+        android:strokeWidth="0.8" />
+    <path
+        android:fillColor="#00000000"
+        android:pathData="M69,19L69,89"
+        android:strokeColor="#33FFFFFF"
+        android:strokeWidth="0.8" />
+    <path
+        android:fillColor="#00000000"
+        android:pathData="M79,19L79,89"
+        android:strokeColor="#33FFFFFF"
+        android:strokeWidth="0.8" />
+</vector>

android/app/src/main/res/mipmap-anydpi-v26/ic_launcher.xml

@@ -0,0 +1,9 @@
+<?xml version="1.0" encoding="utf-8"?>
+<adaptive-icon xmlns:android="http://schemas.android.com/apk/res/android">
+    <background>
+        <inset android:drawable="@mipmap/ic_launcher_background" android:inset="16.7%" />
+    </background>
+    <foreground>
+        <inset android:drawable="@mipmap/ic_launcher_foreground" android:inset="16.7%" />
+    </foreground>
+</adaptive-icon>

android/app/src/main/res/mipmap-anydpi-v26/ic_launcher_round.xml

@@ -0,0 +1,9 @@
+<?xml version="1.0" encoding="utf-8"?>
+<adaptive-icon xmlns:android="http://schemas.android.com/apk/res/android">
+    <background>
+        <inset android:drawable="@mipmap/ic_launcher_background" android:inset="16.7%" />
+    </background>
+    <foreground>
+        <inset android:drawable="@mipmap/ic_launcher_foreground" android:inset="16.7%" />
+    </foreground>
+</adaptive-icon>

android/app/src/main/res/values/colors.xml

@@ -1,7 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<resources>
-    <color name="colorPrimary">#3F51B5</color>
-    <color name="colorPrimaryDark">#303F9F</color>
-    <color name="colorAccent">#FF4081</color>
-    <color name="ic_launcher_background">#FFFFFF</color>
-</resources>

android/app/src/main/res/values/ic_launcher_background.xml

@@ -0,0 +1,4 @@
+<?xml version="1.0" encoding="utf-8"?>
+<resources>
+    <color name="ic_launcher_background">#FFFFFF</color>
+</resources>

android/build.gradle

@@ -7,7 +7,7 @@ buildscript {
         mavenCentral()
     }
     dependencies {
-        classpath 'com.android.tools.build:gradle:8.12.0'
+        classpath 'com.android.tools.build:gradle:8.9.1'
         classpath 'com.google.gms:google-services:4.4.0'
 
         // NOTE: Do not place your application dependencies here; they belong

android/gradle.properties

@@ -20,4 +20,4 @@ org.gradle.jvmargs=-Xmx1536m
 # Android operating system, and which are packaged with your app's APK
 # https://developer.android.com/topic/libraries/support-library/androidx-rn
 android.useAndroidX=true
-android.suppressUnsupportedCompileSdk=36
+android.suppressUnsupportedCompileSdk=34

android/gradle/wrapper/gradle-wrapper.properties

@@ -1,6 +1,6 @@
 distributionBase=GRADLE_USER_HOME
 distributionPath=wrapper/dists
-distributionUrl=https\://services.gradle.org/distributions/gradle-8.13-all.zip
+distributionUrl=https\://services.gradle.org/distributions/gradle-8.11.1-all.zip
 networkTimeout=10000
 validateDistributionUrl=true
 zipStoreBase=GRADLE_USER_HOME

android/variables.gradle

@@ -1,7 +1,7 @@
 ext {
     minSdkVersion = 22
-    compileSdkVersion = 36
-    targetSdkVersion = 36
+    compileSdkVersion = 34
+    targetSdkVersion = 34
     androidxActivityVersion = '1.8.0'
     androidxAppCompatVersion = '1.6.1'
     androidxCoordinatorLayoutVersion = '1.2.0'

assets/README.md

@@ -0,0 +1,2 @@
+
+Application icons are here. They are processed for android & ios by the `capacitor-assets` command, as indicated in the BUILDING.md file.

capacitor-assets.config.json

@@ -1,32 +0,0 @@
-{
-  "icon": {
-    "android": {
-      "adaptive": {
-        "background": "#121212",
-        "foreground": "resources/icon.png",
-        "monochrome": "resources/icon.png"
-      },
-      "target": "android/app/src/main/res"
-    },
-    "ios": {
-      "padding": 0,
-      "target": "ios/App/App/Assets.xcassets/AppIcon.appiconset"
-    },
-    "source": "resources/icon.png",
-    "web": {
-      "target": "public/img/icons"
-    }
-  },
-  "splash": {
-    "android": {
-      "scale": "cover",
-      "target": "android/app/src/main/res"
-    },
-    "darkSource": "resources/splash_dark.png",
-    "ios": {
-      "target": "ios/App/App/Assets.xcassets",
-      "useStoryBoard": true
-    },
-    "source": "resources/splash.png"
-  }
-}

capacitor.config.json

@@ -2,6 +2,7 @@
 	"appId": "app.timesafari",
 	"appName": "TimeSafari",
 	"webDir": "dist",
+	"bundledWebRuntime": false,
 	"server": {
 		"cleartext": true
 	},
@@ -16,32 +17,18 @@
 				]
 			}
 		},
-		"SplashScreen": {
-			"launchShowDuration": 3000,
-			"launchAutoHide": true,
-			"backgroundColor": "#ffffff",
-			"androidSplashResourceName": "splash",
-			"androidScaleType": "CENTER_CROP",
-			"showSpinner": false,
-			"androidSpinnerStyle": "large",
-			"iosSpinnerStyle": "small",
-			"spinnerColor": "#999999",
-			"splashFullScreen": true,
-			"splashImmersive": true
-		},
-		"CapacitorSQLite": {
+		"SQLite": {
 			"iosDatabaseLocation": "Library/CapacitorDatabase",
-			"iosIsEncryption": false,
+			"iosIsEncryption": true,
 			"iosBiometric": {
-				"biometricAuth": false,
+				"biometricAuth": true,
 				"biometricTitle": "Biometric login for TimeSafari"
 			},
-			"androidIsEncryption": false,
+			"androidIsEncryption": true,
 			"androidBiometric": {
-				"biometricAuth": false,
+				"biometricAuth": true,
 				"biometricTitle": "Biometric login for TimeSafari"
-			},
-			"electronIsEncryption": false
+			}
 		}
 	},
 	"ios": {
@@ -57,56 +44,13 @@
 		]
 	},
 	"android": {
-		"allowMixedContent": true,
+		"allowMixedContent": false,
 		"captureInput": true,
 		"webContentsDebuggingEnabled": false,
 		"allowNavigation": [
 			"*.timesafari.app",
 			"*.jsdelivr.net",
-			"api.endorser.ch",
-			"10.0.2.2:3000"
+			"api.endorser.ch"
 		]
-	},
-	"electron": {
-		"deepLinking": {
-			"schemes": ["timesafari"]
-		},
-		"buildOptions": {
-			"appId": "app.timesafari",
-			"productName": "TimeSafari",
-			"directories": {
-				"output": "dist-electron-packages"
-			},
-			"files": [
-				"dist/**/*",
-				"electron/**/*"
-			],
-			"mac": {
-				"category": "public.app-category.productivity",
-				"target": [
-					{
-						"target": "dmg",
-						"arch": ["x64", "arm64"]
-					}
-				]
-			},
-			"win": {
-				"target": [
-					{
-						"target": "nsis",
-						"arch": ["x64"]
-					}
-				]
-			},
-			"linux": {
-				"target": [
-					{
-						"target": "AppImage",
-						"arch": ["x64"]
-					}
-				],
-				"category": "Utility"
-			}
-		}
 	}
 }

capacitor.config.ts

@@ -1,116 +0,0 @@
-import { CapacitorConfig } from '@capacitor/cli';
-
-const config: CapacitorConfig = {
-  appId: 'app.timesafari',
-  appName: 'TimeSafari',
-  webDir: 'dist',
-  server: {
-    cleartext: true
-  },
-  plugins: {
-    App: {
-      appUrlOpen: {
-        handlers: [
-          {
-            url: 'timesafari://*',
-            autoVerify: true
-          }
-        ]
-      }
-    },
-    SplashScreen: {
-      launchShowDuration: 3000,
-      launchAutoHide: true,
-      backgroundColor: '#ffffff',
-      androidSplashResourceName: 'splash',
-      androidScaleType: 'CENTER_CROP',
-      showSpinner: false,
-      androidSpinnerStyle: 'large',
-      iosSpinnerStyle: 'small',
-      spinnerColor: '#999999',
-      splashFullScreen: true,
-      splashImmersive: true
-    },
-    CapSQLite: {
-      iosDatabaseLocation: 'Library/CapacitorDatabase',
-      iosIsEncryption: false,
-      iosBiometric: {
-        biometricAuth: false,
-        biometricTitle: 'Biometric login for TimeSafari'
-      },
-      androidIsEncryption: false,
-      androidBiometric: {
-        biometricAuth: false,
-        biometricTitle: 'Biometric login for TimeSafari'
-      },
-      electronIsEncryption: false
-    }
-  },
-  ios: {
-    contentInset: 'never',
-    allowsLinkPreview: true,
-    scrollEnabled: true,
-    limitsNavigationsToAppBoundDomains: true,
-    backgroundColor: '#ffffff',
-    allowNavigation: [
-      '*.timesafari.app',
-      '*.jsdelivr.net',
-      'api.endorser.ch'
-    ]
-  },
-  android: {
-    allowMixedContent: true,
-    captureInput: true,
-    webContentsDebuggingEnabled: false,
-    allowNavigation: [
-      '*.timesafari.app',
-      '*.jsdelivr.net',
-      'api.endorser.ch',
-      '10.0.2.2:3000'
-    ]
-  },
-  electron: {
-    deepLinking: {
-      schemes: ['timesafari']
-    },
-    buildOptions: {
-      appId: 'app.timesafari',
-      productName: 'TimeSafari',
-      directories: {
-        output: 'dist-electron-packages'
-      },
-      files: [
-        'dist/**/*',
-        'electron/**/*'
-      ],
-      mac: {
-        category: 'public.app-category.productivity',
-        target: [
-          {
-            target: 'dmg',
-            arch: ['x64', 'arm64']
-          }
-        ]
-      },
-      win: {
-        target: [
-          {
-            target: 'nsis',
-            arch: ['x64']
-          }
-        ]
-      },
-      linux: {
-        target: [
-          {
-            target: 'AppImage',
-            arch: ['x64']
-          }
-        ],
-        category: 'Utility'
-      }
-    }
-  }
-};
-
-export default config;

config/assets/capacitor-assets.config.json

@@ -1,32 +0,0 @@
-{
-  "icon": {
-    "android": {
-      "adaptive": {
-        "background": "#121212",
-        "foreground": "resources/icon.png",
-        "monochrome": "resources/icon.png"
-      },
-      "target": "android/app/src/main/res"
-    },
-    "ios": {
-      "padding": 0,
-      "target": "ios/App/App/Assets.xcassets/AppIcon.appiconset"
-    },
-    "source": "resources/icon.png",
-    "web": {
-      "target": "public/img/icons"
-    }
-  },
-  "splash": {
-    "android": {
-      "scale": "cover",
-      "target": "android/app/src/main/res"
-    },
-    "darkSource": "resources/splash_dark.png",
-    "ios": {
-      "target": "ios/App/App/Assets.xcassets",
-      "useStoryBoard": true
-    },
-    "source": "resources/splash.png"
-  }
-}

config/assets/schema.json

@@ -1,119 +0,0 @@
-{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "title": "Capacitor Assets Configuration Schema",
-  "description": "Schema for validating capacitor-assets configuration files",
-  "type": "object",
-  "properties": {
-    "icon": {
-      "type": "object",
-      "properties": {
-        "source": { 
-          "type": "string", 
-          "pattern": "^resources/.*\\.(png|svg)$",
-          "description": "Source icon file path relative to project root"
-        },
-        "android": {
-          "type": "object",
-          "properties": {
-            "adaptive": {
-              "type": "object",
-              "properties": {
-                "foreground": { 
-                  "type": "string",
-                  "pattern": "^resources/.*\\.(png|svg)$",
-                  "description": "Foreground icon for Android adaptive icons"
-                },
-                "background": { 
-                  "type": ["string", "object"],
-                  "description": "Background color or image for adaptive icons"
-                },
-                "monochrome": { 
-                  "type": "string",
-                  "pattern": "^resources/.*\\.(png|svg)$",
-                  "description": "Monochrome icon for Android 13+"
-                }
-              },
-              "required": ["foreground", "background"]
-            },
-            "target": {
-              "type": "string",
-              "description": "Android target directory for generated icons"
-            }
-          }
-        },
-        "ios": {
-          "type": "object",
-          "properties": {
-            "padding": {
-              "type": "number",
-              "minimum": 0,
-              "maximum": 1,
-              "description": "Padding ratio for iOS icons"
-            },
-            "target": {
-              "type": "string",
-              "description": "iOS target directory for generated icons"
-            }
-          }
-        },
-        "web": {
-          "type": "object",
-          "properties": {
-            "target": {
-              "type": "string",
-              "description": "Web target directory for generated icons"
-            }
-          }
-        }
-      },
-      "required": ["source"],
-      "additionalProperties": false
-    },
-    "splash": {
-      "type": "object",
-      "properties": {
-        "source": { 
-          "type": "string",
-          "pattern": "^resources/.*\\.(png|svg)$",
-          "description": "Source splash screen file"
-        },
-        "darkSource": { 
-          "type": "string",
-          "pattern": "^resources/.*\\.(png|svg)$",
-          "description": "Dark mode splash screen file"
-        },
-        "android": {
-          "type": "object",
-          "properties": {
-            "scale": {
-              "type": "string",
-              "enum": ["cover", "contain", "fill"],
-              "description": "Android splash screen scaling mode"
-            },
-            "target": {
-              "type": "string",
-              "description": "Android target directory for splash screens"
-            }
-          }
-        },
-        "ios": {
-          "type": "object",
-          "properties": {
-            "useStoryBoard": {
-              "type": "boolean",
-              "description": "Use LaunchScreen storyboard instead of splash assets"
-            },
-            "target": {
-              "type": "string",
-              "description": "iOS target directory for splash screens"
-            }
-          }
-        }
-      },
-      "required": ["source"],
-      "additionalProperties": false
-    }
-  },
-  "required": ["icon", "splash"],
-  "additionalProperties": false
-}

doc/DEEP_LINKS.md

@@ -100,7 +100,6 @@ try {
 - `src/interfaces/deepLinks.ts`: Type definitions and validation schemas
 - `src/services/deepLinks.ts`: Deep link processing service
 - `src/main.capacitor.ts`: Capacitor integration
-- `src/views/DeepLinkRedirectView.vue`: Page to handle links to both mobile and web
 
 ## Type Safety Examples
 

doc/WORKER_ONLY_DATABASE_IMPLEMENTATION.md

@@ -1,381 +0,0 @@
-# Worker-Only Database Implementation for Web Platform
-
-## Overview
-
-This implementation fixes the double migration issue in the TimeSafari web platform by implementing worker-only database access, similar to the Capacitor platform architecture.
-
-## Problem Solved
-
-**Before:** Web platform had dual database contexts:
-
-- Worker thread: `registerSQLWorker.js` → `AbsurdSqlDatabaseService.initialize()` → migrations run
-- Main thread: `WebPlatformService.dbQuery()` → `databaseService.query()` → migrations run **AGAIN**
-
-**After:** Single database context:
-
-- Worker thread: Handles ALL database operations and initializes once
-- Main thread: Sends messages to worker, no direct database access
-
-## Architecture Changes
-
-### 1. Message-Based Communication
-
-```typescript
-// Main Thread (WebPlatformService)
-await this.sendWorkerMessage<QueryResult>({
-  type: "query",
-  sql: "SELECT * FROM users",
-  params: []
-});
-
-// Worker Thread (registerSQLWorker.js)
-onmessage = async (event) => {
-  const { id, type, sql, params } = event.data;
-  if (type === "query") {
-    const result = await databaseService.query(sql, params);
-    postMessage({ id, type: "success", data: { result } });
-  }
-};
-```
-
-### 2. Type-Safe Worker Messages
-
-```typescript
-// src/interfaces/worker-messages.ts
-export interface QueryRequest extends BaseWorkerMessage {
-  type: "query";
-  sql: string;
-  params?: unknown[];
-}
-
-export type WorkerRequest =
-  | QueryRequest
-  | ExecRequest
-  | GetOneRowRequest
-  | InitRequest
-  | PingRequest;
-```
-
-### 3. Circular Dependency Resolution
-
-#### 🔥 Critical Fix: Stack Overflow Prevention
-
-**Problem**: Circular module dependency caused infinite recursion:
-
-- `WebPlatformService` constructor → creates Worker
-- Worker loads `registerSQLWorker.js` → imports `databaseService`
-- Module resolution creates circular dependency → Stack Overflow
-
-**Solution**: Lazy Loading in Worker
-
-```javascript
-// Before (caused stack overflow)
-import databaseService from "./services/AbsurdSqlDatabaseService";
-
-// After (fixed)
-let databaseService = null;
-
-async function getDatabaseService() {
-  if (!databaseService) {
-    // Dynamic import prevents circular dependency
-    const { default: service } = await import("./services/AbsurdSqlDatabaseService");
-    databaseService = service;
-  }
-  return databaseService;
-}
-```
-
-**Key Changes for Stack Overflow Fix:**
-
-- ✅ Removed top-level import of database service
-- ✅ Added lazy loading with dynamic import
-- ✅ Updated all handlers to use `await getDatabaseService()`
-- ✅ Removed auto-initialization that triggered immediate loading
-- ✅ Database service only loads when first database operation occurs
-
-## Implementation Details
-
-### 1. WebPlatformService Changes
-
-- Removed direct database imports
-- Added worker message handling
-- Implemented timeout and error handling
-- All database methods now proxy to worker
-
-### 2. Worker Thread Changes
-
-- Added message-based operation handling
-- Implemented lazy loading for database service
-- Added proper error handling and response formatting
-- Fixed circular dependency with dynamic imports
-
-### 3. Main Thread Changes
-
-- Removed duplicate worker creation in `main.web.ts`
-- WebPlatformService now manages single worker instance
-- Added Safari compatibility with `initBackend()`
-
-## Files Modified
-
-1. **src/interfaces/worker-messages.ts** *(NEW)*
-   - Type definitions for worker communication
-   - Request and response message interfaces
-
-2. **src/registerSQLWorker.js** *(MAJOR REWRITE)*
-   - Message-based operation handling
-   - **Fixed circular dependency with lazy loading**
-   - Proper error handling and response formatting
-
-3. **src/services/platforms/WebPlatformService.ts** *(MAJOR REWRITE)*
-   - Worker-only database access
-   - Message sending and response handling
-   - Timeout and error management
-
-4. **src/main.web.ts** *(SIMPLIFIED)*
-   - Removed duplicate worker creation
-   - Simplified initialization flow
-
-5. **WORKER_ONLY_DATABASE_IMPLEMENTATION.md** *(NEW)*
-   - Complete documentation of changes
-
-## Benefits
-
-### ✅ Fixes Double Migration Issue
-
-- Database migrations now run only once in worker thread
-- No duplicate initialization between main thread and worker
-
-### ✅ Prevents Stack Overflow
-
-- Circular dependency resolved with lazy loading
-- Worker loads immediately without triggering database import
-- Database service loads on-demand when first operation occurs
-
-### ✅ Improved Performance
-
-- Single database connection
-- No redundant operations
-- Better resource utilization
-
-### ✅ Better Error Handling
-
-- Centralized error handling in worker
-- Type-safe message communication
-- Proper timeout handling
-
-### ✅ Consistent Architecture
-
-- Matches Capacitor platform pattern
-- Single-threaded database access
-- Clear separation of concerns
-
-## Testing Verification
-
-After implementation, you should see:
-
-1. **Worker Loading**:
-
-   ```text
-   [SQLWorker] Worker loaded, ready to receive messages
-   ```
-
-2. **Database Initialization** (only on first operation):
-
-   ```text
-   [SQLWorker] Starting database initialization...
-   [SQLWorker] Database initialization completed successfully
-   ```
-
-3. **No Stack Overflow**: Application starts without infinite recursion
-4. **Single Migration Run**: Database migrations execute only once
-5. **Functional Database**: All queries, inserts, and updates work correctly
-
-## Migration from Previous Implementation
-
-If upgrading from the dual-context implementation:
-
-1. **Remove Direct Database Imports**: No more `import databaseService` in main thread
-2. **Update Database Calls**: Use platform service methods instead of direct database calls
-3. **Handle Async Operations**: All database operations are now async message-based
-4. **Error Handling**: Update error handling to work with worker responses
-
-## Security Considerations
-
-- Worker thread isolates database operations
-- Message validation prevents malformed requests
-- Timeout handling prevents hanging operations
-- Type safety reduces runtime errors
-
-## Performance Notes
-
-- Initial worker creation has minimal overhead
-- Database operations have message passing overhead (negligible)
-- Single database connection is more efficient than dual connections
-- Lazy loading reduces startup time
-
-## Migration Execution Flow
-
-### Before (Problematic)
-
-```chart
-┌──────────────  ───┐    ┌─────────────────┐
-│   Main Thread     │    │  Worker Thread  │
-│                   │    │                 │
-│ WebPlatformService│    │registerSQLWorker│
-│        ↓          │    │        ↓        │
-│ databaseService   │    │ databaseService │
-│   (Instance A)    │    │   (Instance B)  │
-│        ↓          │    │        ↓        │
-│  [Run Migrations] │    │[Run Migrations] │ ← DUPLICATE!
-└───────────────  ──┘    └─────────────────┘
-```
-
-### After (Fixed)
-
-```text
-┌───────────────   ──┐    ┌─────────────────┐
-│   Main Thread      │    │  Worker Thread  │
-│                    │    │                 │
-│ WebPlatformService │───→│registerSQLWorker│
-│                    │    │        ↓        │
-│   [Send Messages]  │    │ databaseService │
-│                    │    │(Single Instance)│
-│                    │    │        ↓        │
-│                    │    │[Run Migrations] │ ← ONCE ONLY!
-└───────────────   ──┘    └─────────────────┘
-```
-
-## New Security Considerations
-
-### 1. **Message Validation**
-
-- All worker messages validated for required fields
-- Unknown message types rejected with errors
-- Proper error responses prevent information leakage
-
-### 2. **Timeout Protection**
-
-- 30-second timeout prevents hung operations
-- Automatic cleanup of pending messages
-- Worker health checks via ping/pong
-
-### 3. **Error Sanitization**
-
-- Error messages logged but not exposed raw to main thread
-- Stack traces included only in development
-- Graceful handling of worker failures
-
-## Testing Considerations
-
-### 1. **Unit Tests Needed**
-
-- Worker message handling
-- WebPlatformService worker communication
-- Error handling and timeouts
-- Migration execution (should run once only)
-
-### 2. **Integration Tests**
-
-- End-to-end database operations
-- Worker lifecycle management
-- Cross-browser compatibility (especially Safari)
-
-### 3. **Performance Tests**
-
-- Message passing overhead
-- Database operation throughput
-- Memory usage with worker communication
-
-## Browser Compatibility
-
-### 1. **Modern Browsers**
-
-- Chrome/Edge: Full SharedArrayBuffer support
-- Firefox: Full SharedArrayBuffer support (with headers)
-- Safari: Uses IndexedDB fallback via `initBackend()`
-
-### 2. **Required Headers**
-
-```text
-Cross-Origin-Opener-Policy: same-origin
-Cross-Origin-Embedder-Policy: require-corp
-```
-
-## Deployment Notes
-
-### 1. **Development**
-
-- Enhanced logging shows worker message flow
-- Clear separation between worker and main thread logs
-- Easy debugging via browser DevTools
-
-### 2. **Production**
-
-- Reduced logging overhead
-- Optimized message passing
-- Proper error reporting without sensitive data
-
-## Future Enhancements
-
-### 1. **Potential Optimizations**
-
-- Message batching for bulk operations
-- Connection pooling simulation
-- Persistent worker state management
-
-### 2. **Additional Features**
-
-- Database backup/restore via worker
-- Schema introspection commands
-- Performance monitoring hooks
-
-## Rollback Plan
-
-If issues arise, rollback involves:
-
-1. Restore original `WebPlatformService.ts`
-2. Restore original `registerSQLWorker.js`
-3. Restore original `main.web.ts`
-4. Remove `worker-messages.ts` interface
-
-## Commit Messages
-
-```bash
-git add src/interfaces/worker-messages.ts
-git commit -m "Add worker message interface for type-safe database communication
-
-- Define TypeScript interfaces for worker request/response messages
-- Include query, exec, getOneRow, init, and ping message types
-- Provide type safety for web platform worker messaging"
-
-git add src/registerSQLWorker.js
-git commit -m "Implement message-based worker for single-point database access
-
-- Replace simple auto-init with comprehensive message handler
-- Add support for query, exec, getOneRow, init, ping operations
-- Implement proper error handling and response management
-- Ensure single database initialization point to prevent double migrations"
-
-git add src/services/platforms/WebPlatformService.ts
-git commit -m "Migrate WebPlatformService to worker-only database access
-
-- Remove direct databaseService import to prevent dual context issue
-- Implement worker-based messaging for all database operations
-- Add worker lifecycle management with initialization tracking
-- Include message timeout and error handling for reliability
-- Add Safari compatibility with initBackend call"
-
-git add src/main.web.ts
-git commit -m "Remove duplicate worker creation from main.web.ts
-
-- Worker initialization now handled by WebPlatformService
-- Prevents duplicate worker creation and database contexts
-- Simplifies main thread initialization"
-
-git add WORKER_ONLY_DATABASE_IMPLEMENTATION.md
-git commit -m "Document worker-only database implementation
-
-- Comprehensive documentation of architecture changes
-- Explain problem solved and benefits achieved
-- Include security considerations and testing requirements"
-```

doc/architecture-decisions.md

@@ -1,125 +0,0 @@
-# Architecture Decisions
-
-This document records key architectural decisions made during the development of TimeSafari.
-
-## Platform Service Architecture: Mixins over Composables
-
-**Date:** July 2, 2025  
-**Status:** Accepted  
-**Context:** Need for consistent platform service access across Vue components
-
-### Decision
-
-**Use Vue mixins for platform service access instead of Vue 3 Composition API composables.**
-
-### Rationale
-
-#### Why Mixins Were Chosen
-
-1. **Existing Architecture Consistency**
-   - The entire codebase uses class-based components with `vue-facing-decorator`
-   - All components follow the established pattern of extending Vue class
-   - Mixins integrate seamlessly with the existing architecture
-
-2. **Performance Benefits**
-   - **Caching Layer**: `PlatformServiceMixin` provides smart TTL-based caching
-   - **Ultra-Concise Methods**: Short methods like `$db()`, `$exec()`, `$one()` reduce boilerplate
-   - **Settings Shortcuts**: `$saveSettings()`, `$saveMySettings()` eliminate 90% of update boilerplate
-   - **Memory Management**: WeakMap-based caching prevents memory leaks
-
-3. **Developer Experience**
-   - **Familiar Pattern**: Mixins are well-understood by the team
-   - **Type Safety**: Full TypeScript support with proper interfaces
-   - **Error Handling**: Centralized error handling across components
-   - **Code Reduction**: Reduces database code by up to 80%
-
-4. **Production Readiness**
-   - **Mature Implementation**: `PlatformServiceMixin` is actively used and tested
-   - **Comprehensive Features**: Includes transaction support, cache management, settings shortcuts
-   - **Security**: Proper input validation and error handling
-
-#### Why Composables Were Rejected
-
-1. **Architecture Mismatch**
-   - Would require rewriting all components to use Composition API
-   - Breaks consistency with existing class-based component pattern
-   - Requires significant refactoring effort
-
-2. **Limited Features**
-   - Basic platform service access without caching
-   - No settings management shortcuts
-   - No ultra-concise database methods
-   - Would require additional development to match mixin capabilities
-
-3. **Performance Considerations**
-   - No built-in caching layer
-   - Would require manual implementation of performance optimizations
-   - More verbose for common operations
-
-### Implementation
-
-#### Current Usage
-
-```typescript
-// Component implementation
-@Component({
-  mixins: [PlatformServiceMixin],
-})
-export default class HomeView extends Vue {
-  async mounted() {
-    // Ultra-concise cached settings loading
-    const settings = await this.$settings({
-      apiServer: "",
-      activeDid: "",
-      isRegistered: false,
-    });
-    
-    // Cached contacts loading
-    this.allContacts = await this.$contacts();
-    
-    // Settings update with automatic cache invalidation
-    await this.$saveMySettings({ isRegistered: true });
-  }
-}
-```
-
-#### Key Features
-
-- **Cached Database Operations**: `$contacts()`, `$settings()`, `$accountSettings()`
-- **Settings Shortcuts**: `$saveSettings()`, `$saveMySettings()`, `$saveUserSettings()`
-- **Ultra-Concise Methods**: `$db()`, `$exec()`, `$one()`, `$query()`, `$first()`
-- **Cache Management**: `$refreshSettings()`, `$clearAllCaches()`
-- **Transaction Support**: `$withTransaction()` with automatic rollback
-
-### Consequences
-
-#### Positive
-
-- **Consistent Architecture**: All components follow the same pattern
-- **High Performance**: Smart caching reduces database calls by 80%+
-- **Developer Productivity**: Ultra-concise methods reduce boilerplate by 90%
-- **Type Safety**: Full TypeScript support with proper interfaces
-- **Memory Safety**: WeakMap-based caching prevents memory leaks
-
-#### Negative
-
-- **Vue 2 Pattern**: Uses older mixin pattern instead of modern Composition API
-- **Tight Coupling**: Components are coupled to the mixin implementation
-- **Testing Complexity**: Mixins can make unit testing more complex
-
-### Future Considerations
-
-1. **Migration Path**: If Vue 4 or future versions deprecate mixins, we may need to migrate
-2. **Performance Monitoring**: Continue monitoring caching performance and adjust TTL values
-3. **Feature Expansion**: Add new ultra-concise methods as needed
-4. **Testing Strategy**: Develop comprehensive testing strategies for mixin-based components
-
-### Related Documentation
-
-- [PlatformServiceMixin Implementation](../src/utils/PlatformServiceMixin.ts)
-- [TimeSafari Cross-Platform Architecture Guide](./build-modernization-context.md)
-- [Database Migration Guide](./database-migration-guide.md)
-
----
-
-*This decision was made based on the current codebase architecture and team expertise. The mixin approach provides the best balance of performance, developer experience, and architectural consistency for the TimeSafari application.* 

doc/asset-migration-plan.md

@@ -1,214 +0,0 @@
-# TimeSafari Asset Configuration Migration Plan
-
-**Author**: Matthew Raymer  
-**Date**: 2025-08-14  
-**Status**: 🎯 **IMPLEMENTATION** - Ready for Execution
-
-## Overview
-
-This document outlines the migration from the current mixed asset management
-system to a standardized, single-source asset configuration approach using
-`capacitor-assets` as the standard generator.
-
-## Current State Analysis
-
-### Asset Sources (Duplicated)
-
-- **`assets/` directory**: Contains `icon.png`, `splash.png`, `splash_dark.png`
-- **`resources/` directory**: Contains identical files in platform-specific subdirectories
-- **Result**: Duplicate storage, confusion about source of truth
-
-### Asset Generation (Manual)
-
-- **Custom scripts**: `generate-icons.sh`, `generate-ios-assets.sh`, `generate-android-icons.sh`
-- **Bypass capacitor-assets**: Manual ImageMagick-based generation
-- **Inconsistent outputs**: Different generation methods for each platform
-
-### Configuration (Scattered)
-
-- **`capacitor-assets.config.json`**: Basic configuration at root
-- **Platform-specific configs**: Mixed in various build scripts
-- **No validation**: No schema or consistency checks
-
-## Target State
-
-### Single Source of Truth
-
-- **`resources/` directory**: Capacitor default location for source assets
-- **Eliminate duplication**: Remove `assets/` directory after migration
-- **Standardized paths**: All tools read from `resources/`
-
-### Standardized Generation
-
-- **`capacitor-assets`**: Single tool for all platform asset generation
-- **Build-time generation**: Assets generated during build, not committed
-- **Deterministic outputs**: Same inputs → same outputs every time
-
-### Centralized Configuration
-
-- **`config/assets/`**: All asset-related configuration files
-- **Schema validation**: JSON schema for configuration validation
-- **CI safeguards**: Automated validation and compliance checks
-
-## Migration Steps
-
-### Phase 1: Foundation Setup ✅
-
-- [x] Create `config/assets/` directory structure
-- [x] Create asset configuration schema (`schema.json`)
-- [x] Create enhanced capacitor-assets configuration
-- [x] Convert `capacitor.config.json` to `capacitor.config.ts`
-- [x] Pin Node.js version (`.nvmrc`, `.node-version`)
-- [x] Create dev-time asset configuration generator
-- [x] Create asset configuration validator
-- [x] Add npm scripts for asset management
-- [x] Update `.gitignore` with proper asset exclusions
-- [x] Create CI workflow for asset validation
-
-### Phase 2: Validation & Testing
-
-- [ ] Run `npm run assets:config` to generate new configuration
-- [ ] Run `npm run assets:validate` to verify configuration
-- [ ] Test `npm run build:native` workflow
-- [ ] Verify CI workflow passes all checks
-- [ ] Confirm no platform assets are committed to VCS
-
-### Phase 3: Cleanup & Removal
-
-- [ ] Remove `assets/` directory (after validation)
-- [ ] Remove manual asset generation scripts
-- [ ] Remove asset checking scripts
-- [ ] Update documentation references
-- [ ] Final validation of clean state
-
-## Implementation Details
-
-### File Structure
-
-```
-resources/                     # Image sources ONLY
-  icon.png
-  splash.png
-  splash_dark.png
-
-config/assets/                 # Versioned config & schema
-  capacitor-assets.config.json
-  schema.json
-
-scripts/
-  assets-config.js            # Dev-time config generator
-  assets-validator.js         # Schema validator
-```
-
-### Configuration Schema
-
-The schema enforces:
-- Source files must be in `resources/` directory
-- Required fields for icon and splash sections
-- Android adaptive icon support (foreground/background/monochrome)
-- iOS LaunchScreen preferences
-- Target directory validation
-
-### CI Safeguards
-
-- **Schema validation**: Configuration must comply with schema
-- **Source file validation**: All referenced files must exist
-- **Platform asset denial**: Reject commits with generated assets
-- **Clean tree enforcement**: Build must not modify committed configs
-
-## Testing Strategy
-
-### Local Validation
-
-```bash
-# Generate configuration
-npm run assets:config
-
-# Validate configuration
-npm run assets:validate
-
-# Test build workflow
-npm run build:native
-
-# Clean generated assets
-npm run assets:clean
-```
-
-### CI Validation
-
-- **Asset validation workflow**: Runs on asset-related changes
-- **Schema compliance**: Ensures configuration follows schema
-- **Source file existence**: Verifies all referenced files exist
-- **Platform asset detection**: Prevents committed generated assets
-- **Build tree verification**: Ensures clean tree after build
-
-## Risk Mitigation
-
-### Data Loss Prevention
-
-- **Backup branch**: Create backup before removing `assets/`
-- **Validation checks**: Multiple validation steps before removal
-- **Gradual migration**: Phase-by-phase approach with rollback capability
-
-### Build Continuity
-
-- **Per-platform scripts unchanged**: All existing build orchestration preserved
-- **Standard toolchain**: Uses capacitor-assets, not custom scripts
-- **Fallback support**: Manual scripts remain until migration complete
-
-### Configuration Consistency
-
-- **Schema enforcement**: JSON schema prevents invalid configurations
-- **CI validation**: Automated checks catch configuration issues
-- **Documentation updates**: Clear guidance for future changes
-
-## Success Criteria
-
-### Technical Requirements
-
-- [ ] Single source of truth in `resources/` directory
-- [ ] All platform assets generated via `capacitor-assets`
-- [ ] No manual asset generation scripts
-- [ ] Configuration validation passes all checks
-- [ ] CI workflow enforces asset policies
-
-### Quality Metrics
-
-- [ ] Zero duplicate asset sources
-- [ ] 100% configuration schema compliance
-- [ ] No platform assets committed to VCS
-- [ ] Clean build tree after asset generation
-- [ ] Deterministic asset outputs
-
-### User Experience
-
-- [ ] Clear asset management documentation
-- [ ] Simple development commands
-- [ ] Consistent asset generation across platforms
-- [ ] Reduced confusion about asset sources
-
-## Next Steps
-
-1. **Execute Phase 2**: Run validation and testing steps
-2. **Verify CI workflow**: Ensure all checks pass
-3. **Execute Phase 3**: Remove duplicate assets and scripts
-4. **Update documentation**: Finalize README and BUILDING.md
-5. **Team training**: Ensure all developers understand new workflow
-
-## Rollback Plan
-
-If issues arise during migration:
-
-1. **Restore backup branch**: `git checkout backup-before-asset-migration`
-2. **Revert configuration changes**: Remove new config files
-3. **Restore manual scripts**: Re-enable previous asset generation
-4. **Investigate issues**: Identify and resolve root causes
-5. **Plan revised migration**: Adjust approach based on lessons learned
-
----
-
-**Status**: Ready for Phase 2 execution  
-**Priority**: High  
-**Estimated Effort**: 2-3 hours  
-**Dependencies**: CI workflow validation  
-**Stakeholders**: Development team

doc/build-modernization-context.md

@@ -1,51 +0,0 @@
-# TimeSafari Build Modernization Context
-
-**Author:** Matthew Raymer
-
-## Motivation
-- Eliminate manual hacks and post-build scripts for Electron builds
-- Ensure maintainability, reproducibility, and security of build outputs
-- Unify build, test, and deployment scripts for developer experience and CI/CD
-
-## Key Technical Decisions
-- **Vite is the single source of truth for build output**
-  - All Electron build output (main process, preload, renderer HTML/CSS/JS) is managed by `vite.config.electron.mts`
-- **CSS injection for Electron is handled by a Vite plugin**
-  - No more manual HTML/CSS edits or post-build scripts
-- **Build scripts are unified and robust**
-  - Use `./scripts/build-electron.sh` for all Electron builds
-  - No more `fix-inject-css.js` or similar hacks
-- **Output structure is deterministic and ASAR-friendly**
-  - Main process: `dist-electron/main.js`
-  - Preload: `dist-electron/preload.js`
-  - Renderer assets: `dist-electron/www/` (HTML, CSS, JS)
-
-## Security & Maintenance Checklist
-- [x] All scripts and configs are committed and documented
-- [x] No manual file hacks remain
-- [x] All build output is deterministic and reproducible
-- [x] No sensitive data is exposed in the build process
-- [x] Documentation (`BUILDING.md`) is up to date
-
-## How to Build Electron
-1. Run:
-   ```bash
-   ./scripts/build-electron.sh
-   ```
-2. Output will be in `dist-electron/`:
-   - `main.js`, `preload.js` in root
-   - `www/` contains all renderer assets
-3. No manual post-processing is required
-
-## Customization
-- **Vite config:** All build output and asset handling is controlled in `vite.config.electron.mts`
-- **CSS/HTML injection:** Use Vite plugins (see `electron-css-injection` in the config) for further customization
-- **Build scripts:** All orchestration is in `scripts/` and documented in `BUILDING.md`
-
-## For Future Developers
-- Always use Vite plugins/config for build output changes
-- Never manually edit built files or inject assets post-build
-- Keep documentation and scripts in sync with the build process
-
----
-This file documents the context and rationale for the build modernization and should be included in the repository for onboarding and future reference. 

doc/circular-dependency-analysis.md

@@ -1,163 +0,0 @@
-# Circular Dependency Analysis
-
-## Overview
-
-This document analyzes the current state of circular dependencies in the TimeSafari codebase, particularly focusing on the migration from Dexie to SQLite and the PlatformServiceMixin implementation.
-
-## Current Circular Dependency Status
-
-### ✅ **EXCELLENT NEWS: All Circular Dependencies RESOLVED**
-
-The codebase currently has **no active circular dependencies** that are causing runtime or compilation errors. All circular dependency issues have been successfully resolved.
-
-### 🔍 **Resolved Dependency Patterns**
-
-#### 1. **Logger → PlatformServiceFactory → Logger** (RESOLVED)
-- **Status**: ✅ **RESOLVED**
-- **Previous Issue**: Logger imported `logToDb` from databaseUtil, which imported logger
-- **Solution**: Logger now uses direct database access via PlatformServiceFactory
-- **Implementation**: Self-contained `logToDatabase()` function in logger.ts
-
-#### 2. **PlatformServiceMixin → databaseUtil → logger → PlatformServiceMixin** (RESOLVED)
-- **Status**: ✅ **RESOLVED**
-- **Previous Issue**: PlatformServiceMixin imported `memoryLogs` from databaseUtil
-- **Solution**: Created self-contained `_memoryLogs` array in PlatformServiceMixin
-- **Implementation**: Self-contained memory logs implementation
-
-#### 3. **databaseUtil → logger → PlatformServiceFactory → databaseUtil** (RESOLVED)
-- **Status**: ✅ **RESOLVED**
-- **Previous Issue**: databaseUtil imported logger, which could create loops
-- **Solution**: Logger is now self-contained and doesn't import from databaseUtil
-
-#### 4. **Utility Files → databaseUtil → PlatformServiceMixin** (RESOLVED)
-- **Status**: ✅ **RESOLVED**
-- **Previous Issue**: `src/libs/util.ts` and `src/services/deepLinks.ts` imported from databaseUtil
-- **Solution**: Replaced with self-contained implementations and PlatformServiceFactory usage
-- **Implementation**: 
-  - Self-contained `parseJsonField()` and `mapQueryResultToValues()` functions
-  - Direct PlatformServiceFactory usage for database operations
-  - Console logging instead of databaseUtil logging functions
-
-## Detailed Dependency Analysis
-
-### ✅ **All Critical Dependencies Resolved**
-
-#### PlatformServiceMixin Independence
-- **Status**: ✅ **COMPLETE**
-- **Achievement**: PlatformServiceMixin has no external dependencies on databaseUtil
-- **Implementation**: Self-contained memory logs and utility functions
-- **Impact**: Enables complete migration of databaseUtil functions to PlatformServiceMixin
-
-#### Logger Independence
-- **Status**: ✅ **COMPLETE**
-- **Achievement**: Logger is completely self-contained
-- **Implementation**: Direct database access via PlatformServiceFactory
-- **Impact**: Eliminates all circular dependency risks
-
-#### Utility Files Independence
-- **Status**: ✅ **COMPLETE**
-- **Achievement**: All utility files no longer depend on databaseUtil
-- **Implementation**: Self-contained functions and direct platform service access
-- **Impact**: Enables complete databaseUtil migration
-
-### 🎯 **Migration Readiness Status**
-
-#### Files Ready for Migration (52 files)
-1. **Components** (15 files):
-   - `PhotoDialog.vue`
-   - `FeedFilters.vue`
-   - `UserNameDialog.vue`
-   - `ImageMethodDialog.vue`
-   - `OfferDialog.vue`
-   - `OnboardingDialog.vue`
-   - `PushNotificationPermission.vue`
-   - `GiftedPrompts.vue`
-   - `GiftedDialog.vue`
-   - `World/components/objects/landmarks.js`
-   - And 5 more...
-
-2. **Views** (30+ files):
-   - `IdentitySwitcherView.vue`
-   - `ContactEditView.vue`
-   - `ContactGiftingView.vue`
-   - `ImportAccountView.vue`
-   - `OnboardMeetingMembersView.vue`
-   - `RecentOffersToUserProjectsView.vue`
-   - `ClaimCertificateView.vue`
-   - `NewActivityView.vue`
-   - `HelpView.vue`
-   - `NewEditProjectView.vue`
-   - And 20+ more...
-
-3. **Services** (5 files):
-   - `deepLinks.ts` ✅ **MIGRATED**
-   - `endorserServer.ts`
-   - `libs/util.ts` ✅ **MIGRATED**
-   - `test/index.ts`
-
-### 🟢 **Healthy Dependencies**
-
-#### Logger Usage (80+ files)
-- **Status**: ✅ **HEALTHY**
-- **Pattern**: All files import logger from `@/utils/logger`
-- **Impact**: No circular dependencies, logger is self-contained
-- **Benefit**: Centralized logging with database integration
-
-## Resolution Strategy - COMPLETED
-
-### ✅ **Phase 1: Complete PlatformServiceMixin Independence (COMPLETE)**
-1. **Removed memoryLogs import** from PlatformServiceMixin ✅
-2. **Created self-contained memoryLogs** implementation ✅
-3. **Added missing utility methods** to PlatformServiceMixin ✅
-
-### ✅ **Phase 2: Utility Files Migration (COMPLETE)**
-1. **Migrated deepLinks.ts** - Replaced databaseUtil logging with console logging ✅
-2. **Migrated util.ts** - Replaced databaseUtil functions with self-contained implementations ✅
-3. **Updated all PlatformServiceFactory calls** to use async pattern ✅
-
-### 🎯 **Phase 3: File-by-File Migration (READY TO START)**
-1. **High-usage files first** (views, core components)
-2. **Replace databaseUtil imports** with PlatformServiceMixin
-3. **Update function calls** to use mixin methods
-
-### 🎯 **Phase 4: Cleanup (FUTURE)**
-1. **Remove unused databaseUtil functions**
-2. **Update TypeScript interfaces**
-3. **Remove databaseUtil imports** from all files
-
-## Current Status Summary
-
-### ✅ **Resolved Issues**
-1. **Logger circular dependency** - Fixed with self-contained implementation
-2. **PlatformServiceMixin circular dependency** - Fixed with self-contained memoryLogs
-3. **Utility files circular dependency** - Fixed with self-contained implementations
-4. **TypeScript compilation** - No circular dependency errors
-5. **Runtime stability** - No circular dependency crashes
-
-### 🎯 **Ready for Next Phase**
-1. **52 files** ready for databaseUtil migration
-2. **PlatformServiceMixin** fully independent and functional
-3. **Clear migration path** - Well-defined targets and strategy
-
-## Benefits of Current State
-
-### ✅ **Achieved**
-1. **No runtime circular dependencies** - Application runs without crashes
-2. **Self-contained logger** - No more logger/databaseUtil loops
-3. **PlatformServiceMixin ready** - All methods implemented and independent
-4. **Utility files independent** - No more databaseUtil dependencies
-5. **Clear migration path** - Well-defined targets and strategy
-
-### 🎯 **Expected After Migration**
-1. **Complete databaseUtil migration** - Single source of truth
-2. **Eliminated circular dependencies** - Clean architecture
-3. **Improved performance** - Caching and optimization
-4. **Better maintainability** - Centralized database operations
-
----
-
-**Author**: Matthew Raymer
-**Created**: 2025-07-05
-**Status**: ✅ **COMPLETE - All Circular Dependencies Resolved**
-**Last Updated**: 2025-01-06
-**Note**: PlatformServiceMixin circular dependency completely resolved. Ready for Phase 2: File-by-File Migration 

doc/component-communication-guide.md

@@ -1,314 +0,0 @@
-# Component Communication Guide
-
-## Overview
-
-This guide establishes our preferred patterns for component communication in Vue.js applications, with a focus on maintainability, type safety, and developer experience.
-
-## Core Principle: Function Props Over $emit
-
-**Preference**: Use function props for business logic and data operations, reserve $emit for DOM-like events.
-
-### Why Function Props?
-
-1. **Better TypeScript Support**: Full type checking of parameters and return values
-2. **Superior IDE Navigation**: Ctrl+click takes you directly to implementation
-3. **Explicit Contracts**: Clear declaration of what functions a component needs
-4. **Easier Testing**: Simple to mock and test in isolation
-5. **Flexibility**: Can pass any function, not just event handlers
-
-### When to Use $emit
-
-1. **DOM-like Events**: `@click`, `@input`, `@submit`, `@change`
-2. **Lifecycle Events**: `@mounted`, `@before-unmount`, `@updated`
-3. **Form Validation**: `@validation-error`, `@validation-success`
-4. **Event Bubbling**: When events need to bubble through multiple components
-5. **Vue DevTools Integration**: When you want events visible in DevTools timeline
-
-## Implementation Patterns
-
-### Function Props Pattern
-
-```typescript
-// Child Component
-@Component({
-  name: "MyComponent"
-})
-export default class MyComponent extends Vue {
-  @Prop({ required: true }) onSave!: (data: SaveData) => Promise<void>;
-  @Prop({ required: true }) onCancel!: () => void;
-  @Prop({ required: false }) onValidate?: (data: FormData) => boolean;
-
-  async handleSave() {
-    const data = this.collectFormData();
-    await this.onSave(data);
-  }
-
-  handleCancel() {
-    this.onCancel();
-  }
-}
-```
-
-```vue
-<!-- Parent Template -->
-<MyComponent
-  :on-save="handleSave"
-  :on-cancel="handleCancel"
-  :on-validate="validateForm"
-/>
-```
-
-### $emit Pattern (for DOM-like events)
-
-```typescript
-// Child Component
-@Component({
-  name: "FormComponent"
-})
-export default class FormComponent extends Vue {
-  @Emit("submit")
-  handleSubmit() {
-    return this.formData;
-  }
-
-  @Emit("input")
-  handleInput(value: string) {
-    return value;
-  }
-}
-```
-
-```vue
-<!-- Parent Template -->
-<FormComponent
-  @submit="handleFormSubmit"
-  @input="handleInputChange"
-/>
-```
-
-## Automatic Code Generation Guidelines
-
-### Component Template Generation
-
-When generating component templates, follow these patterns:
-
-#### Function Props Template
-```vue
-<template>
-  <div class="component-name">
-    <!-- Component content -->
-    <button @click="handleAction">
-      {{ buttonText }}
-    </button>
-  </div>
-</template>
-
-<script lang="ts">
-import { Component, Vue, Prop } from "vue-facing-decorator";
-
-@Component({
-  name: "ComponentName"
-})
-export default class ComponentName extends Vue {
-  @Prop({ required: true }) onAction!: () => void;
-  @Prop({ required: true }) buttonText!: string;
-  @Prop({ required: false }) disabled?: boolean;
-
-  handleAction() {
-    if (!this.disabled) {
-      this.onAction();
-    }
-  }
-}
-</script>
-```
-
-#### $emit Template (for DOM events)
-```vue
-<template>
-  <div class="component-name">
-    <!-- Component content -->
-    <button @click="handleClick">
-      {{ buttonText }}
-    </button>
-  </div>
-</template>
-
-<script lang="ts">
-import { Component, Vue, Prop, Emit } from "vue-facing-decorator";
-
-@Component({
-  name: "ComponentName"
-})
-export default class ComponentName extends Vue {
-  @Prop({ required: true }) buttonText!: string;
-  @Prop({ required: false }) disabled?: boolean;
-
-  @Emit("click")
-  handleClick() {
-    return { disabled: this.disabled };
-  }
-}
-</script>
-```
-
-### Code Generation Rules
-
-#### 1. Function Props for Business Logic
-- **Data operations**: Save, delete, update, validate
-- **Navigation**: Route changes, modal opening/closing
-- **State management**: Store actions, state updates
-- **API calls**: Data fetching, form submissions
-
-#### 2. $emit for User Interactions
-- **Click events**: Button clicks, link navigation
-- **Form events**: Input changes, form submissions
-- **Lifecycle events**: Component mounting, unmounting
-- **UI events**: Focus, blur, scroll, resize
-
-#### 3. Naming Conventions
-
-**Function Props:**
-```typescript
-// Action-oriented names
-onSave: (data: SaveData) => Promise<void>
-onDelete: (id: string) => Promise<void>
-onUpdate: (item: Item) => void
-onValidate: (data: FormData) => boolean
-onNavigate: (route: string) => void
-```
-
-**$emit Events:**
-```typescript
-// Event-oriented names
-@click: (event: MouseEvent) => void
-@input: (value: string) => void
-@submit: (data: FormData) => void
-@focus: (event: FocusEvent) => void
-@mounted: () => void
-```
-
-### TypeScript Integration
-
-#### Function Prop Types
-```typescript
-// Define reusable function types
-interface SaveHandler {
-  (data: SaveData): Promise<void>;
-}
-
-interface ValidationHandler {
-  (data: FormData): boolean;
-}
-
-// Use in components
-@Prop({ required: true }) onSave!: SaveHandler;
-@Prop({ required: true }) onValidate!: ValidationHandler;
-```
-
-#### Event Types
-```typescript
-// Define event payload types
-interface ClickEvent {
-  target: HTMLElement;
-  timestamp: number;
-}
-
-@Emit("click")
-handleClick(): ClickEvent {
-  return {
-    target: this.$el,
-    timestamp: Date.now()
-  };
-}
-```
-
-## Testing Guidelines
-
-### Function Props Testing
-```typescript
-// Easy to mock and test
-const mockOnSave = jest.fn();
-const wrapper = mount(MyComponent, {
-  propsData: {
-    onSave: mockOnSave
-  }
-});
-
-await wrapper.vm.handleSave();
-expect(mockOnSave).toHaveBeenCalledWith(expectedData);
-```
-
-### $emit Testing
-```typescript
-// Requires event simulation
-const wrapper = mount(MyComponent);
-await wrapper.find('button').trigger('click');
-expect(wrapper.emitted('click')).toBeTruthy();
-```
-
-## Migration Strategy
-
-### From $emit to Function Props
-
-1. **Identify business logic events** (not DOM events)
-2. **Add function props** to component interface
-3. **Update parent components** to pass functions
-4. **Remove $emit decorators** and event handlers
-5. **Update tests** to use function mocks
-
-### Example Migration
-
-**Before ($emit):**
-```typescript
-@Emit("save")
-handleSave() {
-  return this.formData;
-}
-```
-
-**After (Function Props):**
-```typescript
-@Prop({ required: true }) onSave!: (data: FormData) => void;
-
-handleSave() {
-  this.onSave(this.formData);
-}
-```
-
-## Best Practices Summary
-
-1. **Use function props** for business logic, data operations, and complex interactions
-2. **Use $emit** for DOM-like events, lifecycle events, and simple user interactions
-3. **Be consistent** within your codebase
-4. **Document your patterns** for team alignment
-5. **Consider TypeScript** when choosing between approaches
-6. **Test both patterns** appropriately
-
-## Code Generation Templates
-
-### Component Generator Input
-```typescript
-interface ComponentSpec {
-  name: string;
-  props: Array<{
-    name: string;
-    type: string;
-    required: boolean;
-    isFunction: boolean;
-  }>;
-  events: Array<{
-    name: string;
-    payloadType?: string;
-  }>;
-  template: string;
-}
-```
-
-### Generated Output
-```typescript
-// Generator should automatically choose function props vs $emit
-// based on the nature of the interaction (business logic vs DOM event)
-```
-
-This guide ensures consistent, maintainable component communication patterns across the application. 

doc/cors-disabled-for-universal-images.md

@@ -1,116 +0,0 @@
-# CORS Disabled for Universal Image Support
-
-## Decision Summary
-
-CORS headers have been **disabled** to support Time Safari's core mission: enabling users to share images from any domain without restrictions.
-
-## What Changed
-
-### ❌ Removed CORS Headers
-- `Cross-Origin-Opener-Policy: same-origin`
-- `Cross-Origin-Embedder-Policy: require-corp`
-
-### ✅ Results
-- Images from **any domain** now work in development and production
-- No proxy configuration needed
-- No whitelist of supported image hosts
-- True community-driven image sharing
-
-## Technical Tradeoffs
-
-### 🔻 Lost: SharedArrayBuffer Performance
-- **Before**: Fast SQLite operations via SharedArrayBuffer
-- **After**: Slightly slower IndexedDB fallback mode
-- **Impact**: Minimal for typical usage - absurd-sql automatically falls back
-
-### 🔺 Gained: Universal Image Support
-- **Before**: Only specific domains worked (TimeSafari, Flickr, Imgur, etc.)
-- **After**: Any image URL works immediately
-- **Impact**: Massive improvement for user experience
-
-## Architecture Impact
-
-### Database Operations
-```typescript
-// absurd-sql automatically detects SharedArrayBuffer availability
-if (typeof SharedArrayBuffer === "undefined") {
-  // Uses IndexedDB backend (current state)
-  console.log("Using IndexedDB fallback mode");
-} else {
-  // Uses SharedArrayBuffer (not available due to disabled CORS)
-  console.log("Using SharedArrayBuffer mode");
-}
-```
-
-### Image Loading
-```typescript
-// All images load directly now
-export function transformImageUrlForCors(imageUrl: string): string {
-  return imageUrl; // No transformation needed
-}
-```
-
-## Why This Was The Right Choice
-
-### Time Safari's Use Case
-- **Community platform** where users share content from anywhere
-- **User-generated content** includes images from arbitrary websites
-- **Flexibility** is more important than marginal performance gains
-
-### Alternative Would Require
-- Pre-configuring proxies for every possible image hosting service
-- Constantly updating proxy list as users find new sources
-- Poor user experience when images fail to load
-- Impossible to support the "any domain" requirement
-
-## Performance Comparison
-
-### Database Operations
-- **SharedArrayBuffer**: ~2x faster for large operations
-- **IndexedDB**: Still very fast for typical Time Safari usage
-- **Real Impact**: Negligible for typical user operations
-
-### Image Loading
-- **With CORS**: Many images failed to load in development
-- **Without CORS**: All images load immediately
-- **Real Impact**: Massive improvement in user experience
-
-## Browser Compatibility
-
-| Browser | SharedArrayBuffer | IndexedDB | Image Loading |
-|---------|------------------|-----------|---------------|
-| Chrome | ❌ (CORS disabled) | ✅ Works | ✅ Any domain |
-| Firefox | ❌ (CORS disabled) | ✅ Works | ✅ Any domain |
-| Safari | ❌ (CORS disabled) | ✅ Works | ✅ Any domain |
-| Edge | ❌ (CORS disabled) | ✅ Works | ✅ Any domain |
-
-## Migration Notes
-
-### For Developers
-- No code changes needed
-- `transformImageUrlForCors()` still exists but returns original URL
-- All existing image references work without modification
-
-### For Users
-- Images from any website now work immediately
-- No more "image failed to load" issues in development
-- Consistent behavior between development and production
-
-## Future Considerations
-
-### If Performance Becomes Critical
-1. **Selective CORS**: Enable only for specific operations
-2. **Service Worker**: Handle image proxying at service worker level
-3. **Build-time Processing**: Pre-process images during build
-4. **User Education**: Guide users toward optimized image hosting
-
-### Monitoring
-- Track database operation performance
-- Monitor for any user-reported slowness
-- Consider re-enabling SharedArrayBuffer if usage patterns change
-
-## Conclusion
-
-This change prioritizes **user experience** and **community functionality** over marginal performance gains. The database still works efficiently via IndexedDB, while images now work universally without configuration.
-
-For a community platform like Time Safari, the ability to share images from any domain is fundamental to the user experience and mission. 

doc/cors-image-loading-solution.md

@@ -1,240 +0,0 @@
-# CORS Image Loading Solution
-
-## Overview
-
-This document describes the implementation of a comprehensive image loading solution that works in a cross-origin isolated environment (required for SharedArrayBuffer support) while accepting images from any domain.
-
-## Problem Statement
-
-When using SharedArrayBuffer (required for absurd-sql), browsers enforce a cross-origin isolated environment with these headers:
-- `Cross-Origin-Opener-Policy: same-origin`
-- `Cross-Origin-Embedder-Policy: require-corp`
-
-This isolation prevents loading external resources (including images) unless they have proper CORS headers, which most image hosting services don't provide.
-
-## Solution Architecture
-
-### 1. Multi-Tier Proxy System
-
-The solution uses a multi-tier approach to handle images from various sources:
-
-#### Tier 1: Specific Domain Proxies (Development Only)
-- **TimeSafari Images**: `/image-proxy/` → `https://image.timesafari.app/`
-- **Flickr Images**: `/flickr-proxy/` → `https://live.staticflickr.com/`
-- **Imgur Images**: `/imgur-proxy/` → `https://i.imgur.com/`
-- **GitHub Raw**: `/github-proxy/` → `https://raw.githubusercontent.com/`
-- **Unsplash**: `/unsplash-proxy/` → `https://images.unsplash.com/`
-
-#### Tier 2: Universal CORS Proxy (Development Only)
-- **Any External Domain**: Uses `https://api.allorigins.win/raw?url=` for arbitrary domains
-
-#### Tier 3: Direct Loading (Production)
-- **Production Mode**: All images load directly without proxying
-
-### 2. Smart URL Transformation
-
-The `transformImageUrlForCors` function automatically:
-- Detects the image source domain
-- Routes through appropriate proxy in development
-- Preserves original URLs in production
-- Handles edge cases (data URLs, relative paths, etc.)
-
-## Implementation Details
-
-### Configuration Files
-
-#### `vite.config.common.mts`
-```typescript
-server: {
-  headers: {
-    // Required for SharedArrayBuffer support
-    'Cross-Origin-Opener-Policy': 'same-origin',
-    'Cross-Origin-Embedder-Policy': 'require-corp'
-  },
-  proxy: {
-    // Specific domain proxies with CORS headers
-    '/image-proxy': { /* TimeSafari images */ },
-    '/flickr-proxy': { /* Flickr images */ },
-    '/imgur-proxy': { /* Imgur images */ },
-    '/github-proxy': { /* GitHub raw images */ },
-    '/unsplash-proxy': { /* Unsplash images */ }
-  }
-}
-```
-
-#### `src/libs/util.ts`
-```typescript
-export function transformImageUrlForCors(imageUrl: string): string {
-  // Development mode: Transform URLs to use proxies
-  // Production mode: Return original URLs
-  
-  // Handle specific domains with dedicated proxies
-  // Fall back to universal CORS proxy for arbitrary domains
-}
-```
-
-### Usage in Components
-
-All image loading in components uses the transformation function:
-
-```typescript
-// In Vue components
-import { transformImageUrlForCors } from "../libs/util";
-
-// Transform image URL before using
-const imageUrl = transformImageUrlForCors(originalImageUrl);
-```
-
-```html
-<!-- In templates -->
-<img :src="transformImageUrlForCors(imageUrl)" alt="Description" />
-```
-
-## Benefits
-
-### ✅ SharedArrayBuffer Support
-- Maintains cross-origin isolation required for SharedArrayBuffer
-- Enables fast SQLite database operations via absurd-sql
-- Provides better performance than IndexedDB fallback
-
-### ✅ Universal Image Support
-- Handles images from any domain
-- No need to pre-configure every possible image source
-- Graceful fallback for unknown domains
-
-### ✅ Development/Production Flexibility
-- Proxy system only active in development
-- Production uses direct URLs for maximum performance
-- No proxy server required in production
-
-### ✅ Automatic Detection
-- Smart URL transformation based on domain patterns
-- Preserves relative URLs and data URLs
-- Handles edge cases gracefully
-
-## Testing
-
-### Automated Testing
-Run the test suite to verify URL transformation:
-
-```typescript
-import { testCorsImageTransformation } from './libs/test-cors-images';
-
-// Console output shows transformation results
-testCorsImageTransformation();
-```
-
-### Visual Testing
-Create test image elements to verify loading:
-
-```typescript
-import { createTestImageElements } from './libs/test-cors-images';
-
-// Creates visual test panel in browser
-createTestImageElements();
-```
-
-### Manual Testing
-1. Start development server: `npm run dev`
-2. Open browser console to see transformation logs
-3. Check Network tab for proxy requests
-4. Verify images load correctly from various domains
-
-## Security Considerations
-
-### Development Environment
-- CORS proxies are only used in development
-- External proxy services (allorigins.win) are used for testing
-- No sensitive data is exposed through proxies
-
-### Production Environment
-- All images load directly without proxying
-- No dependency on external proxy services
-- Original security model maintained
-
-### Privacy
-- Image URLs are not logged or stored by proxy services
-- Proxy requests are only made during development
-- No tracking or analytics in proxy chain
-
-## Performance Impact
-
-### Development
-- Slight latency from proxy requests
-- Additional network hops for external domains
-- More verbose logging for debugging
-
-### Production
-- No performance impact
-- Direct image loading as before
-- No proxy overhead
-
-## Troubleshooting
-
-### Common Issues
-
-#### Images Not Loading in Development
-1. Check console for proxy errors
-2. Verify CORS headers are set
-3. Test with different image URLs
-4. Check network connectivity to proxy services
-
-#### SharedArrayBuffer Not Available
-1. Verify CORS headers are set in server configuration
-2. Check that site is served over HTTPS (or localhost)
-3. Ensure browser supports SharedArrayBuffer
-
-#### Proxy Service Unavailable
-1. Check if allorigins.win is accessible
-2. Consider using alternative CORS proxy services
-3. Temporarily disable CORS headers for testing
-
-### Debug Commands
-
-```bash
-# Check if SharedArrayBuffer is available
-console.log(typeof SharedArrayBuffer !== 'undefined');
-
-# Test URL transformation
-import { transformImageUrlForCors } from './libs/util';
-console.log(transformImageUrlForCors('https://example.com/image.jpg'));
-
-# Run comprehensive tests
-import { testCorsImageTransformation } from './libs/test-cors-images';
-testCorsImageTransformation();
-```
-
-## Migration Guide
-
-### From Previous Implementation
-1. CORS headers are now required for SharedArrayBuffer
-2. Image URLs automatically transformed in development
-3. No changes needed to existing image loading code
-4. Test thoroughly in both development and production
-
-### Adding New Image Sources
-1. Add specific proxy for frequently used domains
-2. Update `transformImageUrlForCors` function
-3. Add CORS headers to proxy configuration
-4. Test with sample images
-
-## Future Enhancements
-
-### Possible Improvements
-1. **Local Proxy Server**: Run dedicated proxy server for development
-2. **Caching**: Cache proxy responses for better performance
-3. **Fallback Chain**: Multiple proxy services for reliability
-4. **Image Optimization**: Compress/resize images through proxy
-5. **Analytics**: Track image loading success/failure rates
-
-### Alternative Approaches
-1. **Service Worker**: Intercept image requests at service worker level
-2. **Build-time Processing**: Pre-process images during build
-3. **CDN Integration**: Use CDN with proper CORS headers
-4. **Local Storage**: Cache images in browser storage
-
-## Conclusion
-
-This solution provides a robust, scalable approach to image loading in a cross-origin isolated environment while maintaining the benefits of SharedArrayBuffer support. The multi-tier proxy system ensures compatibility with any image source while optimizing for performance and security.
-
-For questions or issues, refer to the troubleshooting section or consult the development team. 

doc/database-migration-guide.md

@@ -1,304 +0,0 @@
-# Database Migration Guide
-
-## Overview
-
-The Database Migration feature allows you to compare and migrate data between Dexie (IndexedDB) and SQLite databases in the TimeSafari application. This is particularly useful during the transition from the old Dexie-based storage system to the new SQLite-based system.
-
-**⚠️ UPDATE**: The migration is now controlled through the **PlatformServiceMixin** rather than a `USE_DEXIE_DB` constant. This provides a cleaner, more maintainable approach to database access control.
-
-## Features
-
-### 1. Database Comparison
-
-- Compare data between Dexie and SQLite databases
-- View detailed differences in contacts and settings
-- Identify added, modified, and missing records
-- Export comparison results for analysis
-
-### 2. Data Migration
-
-- Migrate contacts from Dexie to SQLite
-- Migrate settings from Dexie to SQLite
-- Option to overwrite existing records or skip them
-- Comprehensive error handling and reporting
-
-### 3. User Interface
-
-- Modern, responsive UI built with Tailwind CSS
-- Real-time loading states and progress indicators
-- Clear success and error messaging
-- Export functionality for comparison data
-
-## Prerequisites
-
-### Enable Dexie Database Access
-
-Before using the migration features, you must ensure the Dexie database is accessible for migration purposes. The migration tools will automatically handle database access through the PlatformServiceMixin.
-
-**Note**: The migration tools are designed to work with both databases simultaneously during the migration process.
-
-## Accessing the Migration Interface
-
-1. Navigate to the **Account** page in the TimeSafari app
-2. Scroll down to find the **Database Migration** link
-3. Click the link to open the migration interface
-
-## Using the Migration Interface
-
-### Step 1: Compare Databases
-
-1. Click the **"Compare Databases"** button
-2. The system will retrieve data from both Dexie and SQLite databases
-3. Review the comparison results showing:
-   - Summary counts for each database
-   - Detailed differences (added, modified, missing records)
-   - Specific records that need attention
-
-### Step 2: Review Differences
-
-The comparison results are displayed in several sections:
-
-#### Summary Cards
-
-- **Dexie Contacts**: Number of contacts in Dexie database
-- **SQLite Contacts**: Number of contacts in SQLite database
-- **Dexie Settings**: Number of settings in Dexie database
-- **SQLite Settings**: Number of settings in SQLite database
-
-#### Contact Differences
-
-- **Added**: Contacts in Dexie but not in SQLite
-- **Modified**: Contacts that differ between databases
-- **Missing**: Contacts in SQLite but not in Dexie
-
-#### Settings Differences
-
-- **Added**: Settings in Dexie but not in SQLite
-- **Modified**: Settings that differ between databases
-- **Missing**: Settings in SQLite but not in Dexie
-
-### Step 3: Configure Migration Options
-
-Before migrating data, configure the migration options:
-
-- **Overwrite existing records**: When enabled, existing records in SQLite will be updated with data from Dexie. When disabled, existing records will be skipped.
-
-### Step 4: Migrate Data
-
-#### Migrate Contacts
-
-1. Click the **"Migrate Contacts"** button
-2. The system will transfer contacts from Dexie to SQLite
-3. Review the migration results showing:
-   - Number of contacts successfully migrated
-   - Any warnings or errors encountered
-
-#### Migrate Settings
-
-1. Click the **"Migrate Settings"** button
-2. The system will transfer settings from Dexie to SQLite
-3. Review the migration results showing:
-   - Number of settings successfully migrated
-   - Any warnings or errors encountered
-
-### Step 5: Export Comparison (Optional)
-
-1. Click the **"Export Comparison"** button
-2. A JSON file will be downloaded containing the complete comparison data
-3. This file can be used for analysis or backup purposes
-
-## Migration Process Details
-
-### Contact Migration
-
-The contact migration process:
-
-1. **Retrieves** all contacts from Dexie database
-2. **Checks** for existing contacts in SQLite by DID
-3. **Inserts** new contacts or **updates** existing ones (if overwrite is enabled)
-4. **Handles** complex fields like `contactMethods` (JSON arrays)
-5. **Reports** success/failure for each contact
-
-### Settings Migration
-
-The settings migration process:
-
-1. **Retrieves** all settings from Dexie database
-2. **Focuses** on key user-facing settings:
-   - `firstName`
-   - `isRegistered`
-   - `profileImageUrl`
-   - `showShortcutBvc`
-   - `searchBoxes`
-3. **Preserves** other settings in SQLite
-4. **Reports** success/failure for each setting
-
-## Error Handling
-
-### Common Issues
-
-#### Database Connection Issues
-
-**Error**: "Failed to retrieve Dexie contacts"
-**Solution**: Check that the Dexie database is properly initialized and accessible
-
-#### SQLite Query Errors
-
-**Error**: "Failed to retrieve SQLite contacts"
-**Solution**: Verify that the SQLite database is properly set up and the platform service is working
-
-#### Migration Failures
-
-**Error**: "Migration failed: [specific error]"
-**Solution**: Review the error details and check data integrity in both databases
-
-### Error Recovery
-
-1. **Review** the error messages carefully
-2. **Check** the browser console for additional details
-3. **Verify** database connectivity and permissions
-4. **Retry** the operation if appropriate
-5. **Export** comparison data for manual review if needed
-
-## Best Practices
-
-### Before Migration
-
-1. **Backup** your data if possible
-2. **Test** the migration on a small dataset first
-3. **Verify** that both databases are accessible
-4. **Review** the comparison results before migrating
-
-### During Migration
-
-1. **Don't** interrupt the migration process
-2. **Monitor** the progress and error messages
-3. **Note** any warnings or skipped records
-4. **Export** comparison data for reference
-
-### After Migration
-
-1. **Verify** that data was migrated correctly
-2. **Test** the application functionality
-3. **Use PlatformServiceMixin** for all new database operations
-4. **Clean up** any temporary files or exports
-
-## Technical Details
-
-### Database Schema
-
-The migration handles the following data structures:
-
-#### Contacts Table
-
-```typescript
-interface Contact {
-  did: string;                    // Decentralized Identifier
-  name: string;                   // Contact name
-  contactMethods: ContactMethod[]; // Array of contact methods
-  nextPubKeyHashB64: string;      // Next public key hash
-  notes: string;                  // Contact notes
-  profileImageUrl: string;        // Profile image URL
-  publicKeyBase64: string;        // Public key in base64
-  seesMe: boolean;                // Visibility flag
-  registered: boolean;            // Registration status
-}
-```
-
-#### Settings Table
-
-```typescript
-interface Settings {
-  id: number;                     // Settings ID
-  accountDid: string;             // Account DID
-  activeDid: string;              // Active DID
-  firstName: string;              // User's first name
-  isRegistered: boolean;          // Registration status
-  profileImageUrl: string;        // Profile image URL
-  showShortcutBvc: boolean;       // UI preference
-  searchBoxes: any[];             // Search configuration
-  // ... other fields
-}
-```
-
-### Migration Logic
-
-The migration service uses sophisticated comparison logic:
-
-1. **Primary Key Matching**: Uses DID for contacts, ID for settings
-2. **Deep Comparison**: Compares all fields including complex objects
-3. **JSON Handling**: Properly handles JSON fields like `contactMethods` and `searchBoxes`
-4. **Conflict Resolution**: Provides options for handling existing records
-
-### Performance Considerations
-
-- **Batch Processing**: Processes records one by one for reliability
-- **Error Isolation**: Individual record failures don't stop the entire migration
-- **Memory Management**: Handles large datasets efficiently
-- **Progress Reporting**: Provides real-time feedback during migration
-
-## Troubleshooting
-
-### Migration Stuck
-
-If the migration appears to be stuck:
-
-1. **Check** the browser console for errors
-2. **Refresh** the page and try again
-3. **Verify** database connectivity
-4. **Check** for large datasets that might take time
-
-### Incomplete Migration
-
-If migration doesn't complete:
-
-1. **Review** error messages
-2. **Check** data integrity in both databases
-3. **Export** comparison data for manual review
-4. **Consider** migrating in smaller batches
-
-### Data Inconsistencies
-
-If you notice data inconsistencies:
-
-1. **Export** comparison data
-2. **Review** the differences carefully
-3. **Manually** verify critical records
-4. **Consider** selective migration of specific records
-
-## Support
-
-For issues with the Database Migration feature:
-
-1. **Check** this documentation first
-2. **Review** the browser console for error details
-3. **Export** comparison data for analysis
-4. **Contact** the development team with specific error details
-
-## Security Considerations
-
-- **Data Privacy**: Migration data is processed locally and not sent to external servers
-- **Access Control**: Only users with access to the account can perform migration
-- **Data Integrity**: Migration preserves data integrity and handles conflicts gracefully
-- **Audit Trail**: Export functionality provides an audit trail of migration operations
-
-## PlatformServiceMixin Integration
-
-After migration, all database operations should use the PlatformServiceMixin:
-
-```typescript
-// Use mixin methods for database access
-const contacts = await this.$contacts();
-const settings = await this.$settings();
-const result = await this.$db("SELECT * FROM contacts WHERE did = ?", [accountDid]);
-```
-
-This provides:
-- **Caching**: Automatic caching for performance
-- **Error Handling**: Consistent error handling
-- **Type Safety**: Enhanced TypeScript integration
-- **Code Reduction**: Up to 80% reduction in boilerplate
-
----
-
-**Note**: This migration tool is designed for the transition period between database systems. Once migration is complete and verified, the Dexie database should be disabled to avoid confusion and potential data conflicts. All new development should use the PlatformServiceMixin for database operations.