feat(git-hooks): implement conditional Husky activation system

- Implements conditional activation logic in husky.sh helper script
- Updates pre-commit hook to run linting only when enabled
- Updates commit-msg hook to validate messages only when enabled
- Adds .husky-enabled to .gitignore for user-specific activation
- Creates user activation instructions in .husky/README.md
- Provides graceful fallback when hooks are disabled

Activation: Environment variable, local file, or global config
Hooks: Pre-commit (linting) and commit-msg (validation)
Behavior: Optional activation with helpful instructions when disabled

.cursor/rules/adr_template.mdc

@@ -0,0 +1,65 @@
+# 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

@@ -0,0 +1,352 @@
+---
+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

@@ -0,0 +1,181 @@
+# 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

@@ -1,287 +0,0 @@
----
-description: 
-globs: 
-alwaysApply: true
----
-# TimeSafari Cross-Platform Architecture Guide
-
-## 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
-
-### 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.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.web.mts      # Web/PWA build
-```
-
-## 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
-└── 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),
-      // PWA is automatically enabled for web platforms via build configuration
-      __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"
-```
-
-## 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/architecture/README.md

@@ -0,0 +1,75 @@
+# Architecture Rules Directory
+
+**Author**: Matthew Raymer
+**Date**: 2025-08-20
+**Status**: 🎯 **ACTIVE** - Architecture protection guidelines
+
+## Overview
+
+This directory contains MDC (Model Directive Configuration) rules that protect
+critical architectural components of the TimeSafari project. These rules ensure
+that changes to system architecture follow proper review, testing, and
+documentation procedures.
+
+## Available Rules
+
+### Build Architecture Guard (`build_architecture_guard.mdc`)
+
+Protects the multi-platform build system including:
+
+- Vite configuration files
+- Build scripts and automation
+- Platform-specific configurations (iOS, Android, Electron, Web)
+- Docker and deployment infrastructure
+- CI/CD pipeline components
+
+**When to use**: Any time you're modifying build scripts, configuration files,
+or deployment processes.
+
+**Authorization levels**:
+
+- **Level 1**: Minor changes (review required)
+- **Level 2**: Moderate changes (testing required)
+- **Level 3**: Major changes (ADR required)
+
+## Usage Guidelines
+
+### For Developers
+
+1. **Check the rule**: Before making architectural changes, review the relevant
+   rule
+2. **Follow the process**: Use the appropriate authorization level
+3. **Complete validation**: Run through the required checklist
+4. **Update documentation**: Keep BUILDING.md and related docs current
+
+### For Reviewers
+
+1. **Verify authorization**: Ensure changes match the required level
+2. **Check testing**: Confirm appropriate testing has been completed
+3. **Validate documentation**: Ensure BUILDING.md reflects changes
+4. **Assess risk**: Consider impact on other platforms and systems
+
+## Integration with Other Rules
+
+- **Version Control**: Works with `workflow/version_control.mdc`
+- **Research & Diagnostic**: Supports `research_diagnostic.mdc` for
+  investigations
+- **Software Development**: Aligns with development best practices
+- **Markdown Automation**: Integrates with `docs/markdown-automation.mdc` for
+  consistent documentation formatting
+
+## Emergency Procedures
+
+If architectural changes cause system failures:
+
+1. **Immediate rollback** to last known working state
+2. **Document the failure** with full error details
+3. **Investigate root cause** using diagnostic workflows
+4. **Update procedures** to prevent future failures
+
+---
+
+**Status**: Active architecture protection
+**Priority**: Critical
+**Maintainer**: Development team
+**Next Review**: 2025-09-20

.cursor/rules/architecture/build_architecture_guard.mdc

@@ -0,0 +1,295 @@
+---
+description: Guards against unauthorized changes to the TimeSafari building
+  architecture
+alwaysApply: false
+---
+
+# Build Architecture Guard Directive
+
+**Author**: Matthew Raymer
+**Date**: 2025-08-20
+**Status**: 🎯 **ACTIVE** - Build system protection guidelines
+
+## Purpose
+
+Protect the TimeSafari building architecture from unauthorized changes that
+could break the multi-platform build pipeline, deployment processes, or
+development workflow. This directive ensures all build system modifications
+follow proper review, testing, and documentation procedures.
+
+## Protected Architecture Components
+
+### Core Build Infrastructure
+
+- **Vite Configuration Files**: `vite.config.*.mts` files
+- **Build Scripts**: All scripts in `scripts/` directory
+- **Package Scripts**: `package.json` build-related scripts
+- **Platform Configs**: `capacitor.config.ts`, `electron/`, `android/`,
+  `ios/`
+- **Docker Configuration**: `Dockerfile`, `docker-compose.yml`
+- **Environment Files**: `.env.*`, `.nvmrc`, `.node-version`
+
+### Critical Build Dependencies
+
+- **Build Tools**: Vite, Capacitor, Electron, Android SDK, Xcode
+- **Asset Management**: `capacitor-assets.config.json`, asset scripts
+- **Testing Infrastructure**: Playwright, Jest, mobile test scripts
+- **CI/CD Pipeline**: GitHub Actions, build validation scripts
+- **Service Worker Assembly**: `sw_scripts/`, `sw_combine.js`, WASM copy steps
+
+## Change Authorization Requirements
+
+### Level 1: Minor Changes (Requires Review)
+
+- Documentation updates to `BUILDING.md`
+- Non-breaking script improvements
+- Test additions or improvements
+- Asset configuration updates
+
+**Process**: Code review + basic testing
+
+### Level 2: Moderate Changes (Requires Testing)
+
+- New build script additions
+- Environment variable changes
+- Dependency version updates
+- Platform-specific optimizations
+
+**Process**: Code review + platform testing + documentation update
+
+### Level 3: Major Changes (Requires ADR)
+
+- Build system architecture changes
+- New platform support
+- Breaking changes to build scripts
+- Major dependency migrations
+
+**Process**: ADR creation + comprehensive testing + team review
+
+## Prohibited Actions
+
+### ❌ Never Allow Without ADR
+
+- **Delete or rename** core build scripts
+- **Modify** `package.json` build script names
+- **Change** Vite configuration structure
+- **Remove** platform-specific build targets
+- **Alter** Docker build process
+- **Modify** CI/CD pipeline without testing
+
+### ❌ Never Allow Without Testing
+
+- **Update** build dependencies
+- **Change** environment configurations
+- **Modify** asset generation scripts
+- **Alter** test infrastructure
+- **Update** platform SDK versions
+
+## Required Validation Checklist
+
+### Before Any Build System Change
+
+- [ ] **Impact Assessment**: Which platforms are affected?
+- [ ] **Testing Plan**: How will this be tested across platforms?
+- [ ] **Rollback Plan**: How can this be reverted if it breaks?
+- [ ] **Documentation**: Will `BUILDING.md` need updates?
+- [ ] **Dependencies**: Are all required tools available?
+
+### After Build System Change
+
+- [ ] **Web Platform**: Does `npm run build:web:dev` work?
+- [ ] **Mobile Platforms**: Do iOS/Android builds succeed?
+- [ ] **Desktop Platform**: Does Electron build and run?
+- [ ] **Tests Pass**: Do all build-related tests pass?
+- [ ] **Documentation Updated**: Is `BUILDING.md` current?
+
+## Specific Test Commands (Minimum Required)
+
+### Web Platform
+
+- **Development**: `npm run build:web:dev` - serve and load app
+- **Production**: `npm run build:web:prod` - verify SW and WASM present
+
+### Mobile Platforms
+
+- **Android**: `npm run build:android:test` or `:prod` - confirm assets copied
+- **iOS**: `npm run build:ios:test` or `:prod` - verify build succeeds
+
+### Desktop Platform
+
+- **Electron**: `npm run build:electron:dev` and packaging for target OS
+- **Verify**: Single-instance behavior and app boot
+
+### Auto-run (if affected)
+
+- **Test Mode**: `npm run auto-run:test` and platform variants
+- **Production Mode**: `npm run auto-run:prod` and platform variants
+
+### Clean and Rebuild
+
+- Run relevant `clean:*` scripts and ensure re-build works
+
+## Emergency Procedures
+
+### Build System Broken
+
+1. **Immediate**: Revert to last known working commit
+2. **Investigation**: Create issue with full error details
+3. **Testing**: Verify all platforms work after revert
+4. **Documentation**: Update `BUILDING.md` with failure notes
+
+### Platform-Specific Failure
+
+1. **Isolate**: Identify which platform is affected
+2. **Test Others**: Verify other platforms still work
+3. **Rollback**: Revert platform-specific changes
+4. **Investigation**: Debug in isolated environment
+
+## Integration Points
+
+### With Version Control
+
+- **Branch Protection**: Require reviews for build script changes
+- **Commit Messages**: Must reference ADR for major changes
+- **Testing**: All build changes must pass CI/CD pipeline
+
+### With Documentation
+
+- **BUILDING.md**: Must be updated for any script changes
+- **README.md**: Must reflect new build requirements
+- **CHANGELOG.md**: Must document breaking build changes
+
+### With Testing
+
+- **Pre-commit**: Run basic build validation
+- **CI/CD**: Full platform build testing
+- **Manual Testing**: Human verification of critical paths
+
+## Risk Matrix & Required Validation
+
+### Environment Handling
+
+- **Trigger**: Change to `.env.*` loading / variable names
+- **Validation**: Prove `dev/test/prod` builds; show environment echo in logs
+
+### Script Flow
+
+- **Trigger**: Reorder steps (prebuild → build → package), new flags
+- **Validation**: Dry-run + normal run, show exit codes & timing
+
+### Platform Packaging
+
+- **Trigger**: Electron NSIS/DMG/AppImage, Android/iOS bundle
+- **Validation**: Produce installer/artifact and open it; verify single-instance,
+  icons, signing
+
+### Service Worker / WASM
+
+- **Trigger**: `sw_combine.js`, WASM copy path
+- **Validation**: Verify combined SW exists and is injected; page loads offline;
+  WASM present
+
+### Docker
+
+- **Trigger**: New base image, build args
+- **Validation**: Build image locally; run container; list produced `/dist`
+
+### Signing/Notarization
+
+- **Trigger**: Cert path/profiles
+- **Validation**: Show signing logs + verify on target OS
+
+## PR Template (Paste into Description)
+
+- [ ] **Level**: L1 / L2 / L3 + justification
+- [ ] **Files & platforms touched**:
+- [ ] **Risk triggers & mitigations**:
+- [ ] **Commands run (paste logs)**:
+- [ ] **Artifacts (names + sha256)**:
+- [ ] **Docs updated (sections/links)**:
+- [ ] **Rollback steps verified**:
+- [ ] **CI**: Jobs passing and artifacts uploaded
+
+## Rollback Playbook
+
+### Immediate Rollback
+
+1. `git revert` or `git reset --hard <prev>`; restore prior `scripts/` or config
+   files
+2. Rebuild affected targets; verify old behavior returns
+3. Post-mortem notes → update this guard and `BUILDING.md` if gaps found
+
+### Rollback Verification
+
+- **Web**: `npm run build:web:dev` and `npm run build:web:prod`
+- **Mobile**: `npm run build:android:test` and `npm run build:ios:test`
+- **Desktop**: `npm run build:electron:dev` and packaging commands
+- **Clean**: Run relevant `clean:*` scripts and verify re-build works
+
+## ADR Trigger List
+
+Raise an ADR when you propose any of:
+
+- **New build stage** or reorder of canonical stages
+- **Replacement of packager** / packaging format
+- **New environment model** or secure secret handling scheme
+- **New service worker assembly** strategy or cache policy
+- **New Docker base** or multi-stage pipeline
+- **Relocation of build outputs** or directory conventions
+
+**ADR must include**: motivation, alternatives, risks, validation plan, rollback,
+  doc diffs.
+
+## Competence Hooks
+
+### Why This Works
+
+- **Prevents Build Failures**: Catches issues before they reach production
+- **Maintains Consistency**: Ensures all platforms build identically
+- **Reduces Debugging Time**: Prevents build system regressions
+
+### Common Pitfalls
+
+- **Silent Failures**: Changes that work on one platform but break others
+- **Dependency Conflicts**: Updates that create version incompatibilities
+- **Documentation Drift**: Build scripts that don't match documentation
+
+### Next Skill Unlock
+
+- Learn to test build changes across all platforms simultaneously
+
+### Teach-back
+
+- "What three platforms must I test before committing a build script change?"
+
+## Collaboration Hooks
+
+### Team Review Requirements
+
+- **Platform Owners**: iOS, Android, Electron, Web specialists
+- **DevOps**: CI/CD pipeline maintainers
+- **QA**: Testing infrastructure owners
+
+### Discussion Prompts
+
+- "Which platforms will be affected by this build change?"
+- "How can we test this change without breaking existing builds?"
+- "What's our rollback plan if this change fails?"
+
+## Self-Check (Before Allowing Changes)
+
+- [ ] **Authorization Level**: Is this change appropriate for the level?
+- [ ] **Testing Plan**: Is there a comprehensive testing strategy?
+- [ ] **Documentation**: Will BUILDING.md be updated?
+- [ ] **Rollback**: Is there a safe rollback mechanism?
+- [ ] **Team Review**: Have appropriate stakeholders been consulted?
+- [ ] **CI/CD**: Will this pass the build pipeline?
+
+---
+
+**Status**: Active build system protection
+**Priority**: Critical
+**Estimated Effort**: Ongoing vigilance
+**Dependencies**: All build system components
+**Stakeholders**: Development team, DevOps, Platform owners
+**Next Review**: 2025-09-20

.cursor/rules/asset_configuration.mdc

@@ -0,0 +1,61 @@
+---
+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

@@ -0,0 +1,154 @@
+---
+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/database/absurd-sql.mdc

@@ -1,14 +1,23 @@
 ---
-description: 
-globs: 
-alwaysApply: true
+globs: **/db/databaseUtil.ts, **/interfaces/absurd-sql.d.ts, **/src/registerSQLWorker.js, **/
+services/AbsurdSqlDatabaseService.ts
+alwaysApply: false
 ---
 # 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
@@ -21,36 +30,45 @@ 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
    ```
@@ -61,17 +79,20 @@ 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
@@ -79,18 +100,21 @@ 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
@@ -99,6 +123,7 @@ PRAGMA page_size=8192;  -- Optional, but recommended
 ## Common Patterns
 
 ### Worker Initialization
+
 ```javascript
 // Main thread
 import { initBackend } from 'absurd-sql/dist/indexeddb-main-thread';
@@ -110,6 +135,7 @@ function init() {
 ```
 
 ### Database Setup
+
 ```javascript
 // Worker thread
 import initSqlJs from '@jlongster/sql.js';
@@ -131,6 +157,7 @@ async function setupDatabase() {
 ## Troubleshooting
 
 ### Common Issues
+
 1. SharedArrayBuffer not available
    - Check COOP/COEP headers
    - Verify browser support
@@ -147,7 +174,20 @@ 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/) 
+- [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/)

.cursor/rules/database/legacy_dexie.mdc

@@ -0,0 +1,8 @@
+---
+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,7 +1,6 @@
 ---
-description: rules used while developing
-globs: 
-alwaysApply: true
+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

.cursor/rules/development/type_safety_guide.mdc

@@ -0,0 +1,139 @@
+---
+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/markdown-automation.mdc

@@ -0,0 +1,79 @@
+---
+alwaysApply: true
+---
+
+# Markdown Automation System
+
+**Author**: Matthew Raymer
+**Date**: 2025-08-20
+**Status**: 🎯 **ACTIVE** - Markdown formatting automation
+
+## Overview
+
+The Markdown Automation System ensures your markdown formatting standards are
+followed **during content generation** by AI agents, not just applied after the
+fact.
+
+## AI-First Approach
+
+### **Primary Method**: AI Agent Compliance
+
+- **AI agents follow markdown rules** while generating content
+- **No post-generation fixes needed** - content is compliant from creation
+- **Consistent formatting** across all generated documentation
+
+### **Secondary Method**: Automated Validation
+
+- **Pre-commit hooks** catch any remaining issues
+- **GitHub Actions** validate formatting before merge
+- **Manual tools** for bulk fixes when needed
+
+## How It Works
+
+### 1. **AI Agent Compliance** (Primary)
+
+- **When**: Every time AI generates markdown content
+- **What**: AI follows markdown rules during generation
+- **Result**: Content is properly formatted from creation
+
+### 2. **Pre-commit Hooks** (Backup)
+
+- **When**: Every time you commit
+- **What**: Catches any remaining formatting issues
+- **Result**: Clean, properly formatted markdown files
+
+### 3. **GitHub Actions** (Pre-merge)
+
+- **When**: Every pull request
+- **What**: Validates markdown formatting across all files
+- **Result**: Blocks merge if formatting issues exist
+
+## AI Agent Rules Integration
+
+The AI agent follows markdown rules defined in `.cursor/rules/docs/markdown.mdc`:
+
+- **alwaysApply: true** - Rules are enforced during generation
+- **Line Length**: AI never generates lines > 80 characters
+- **Blank Lines**: AI adds proper spacing around all elements
+- **Structure**: AI uses established templates and patterns
+
+## Available Commands
+
+### NPM Scripts
+
+- **`npm run markdown:setup`** - Install the automation system
+- **`npm run markdown:fix`** - Fix formatting in all markdown files
+- **`npm run markdown:check`** - Validate formatting without fixing
+
+## Benefits
+
+- **No more manual fixes** - AI generates compliant content from start
+- **Consistent style** - All files follow same standards
+- **Faster development** - No need to fix formatting manually
+
+---
+
+**Status**: Active automation system
+**Priority**: High
+**Maintainer**: Development team
+**Next Review**: 2025-09-20

.cursor/rules/docs/markdown.mdc

@@ -1,5 +1,5 @@
 ---
-globs: *.md
+globs: ["*.md", "*.mdc"]
 alwaysApply: false
 ---
 # Cursor Markdown Ruleset for TimeSafari Documentation
@@ -10,6 +10,36 @@ This ruleset enforces consistent markdown formatting standards across all projec
 documentation, ensuring readability, maintainability, and compliance with
 markdownlint best practices.
 
+**⚠️ CRITICAL FOR AI AGENTS**: These rules must be followed DURING content
+generation, not applied after the fact. Always generate markdown that complies
+with these standards from the start.
+
+## AI Generation Guidelines
+
+### **MANDATORY**: Follow These Rules While Writing
+
+When generating markdown content, you MUST:
+
+1. **Line Length**: Never exceed 80 characters per line
+2. **Blank Lines**: Always add blank lines around headings, lists, and code
+   blocks
+3. **Structure**: Use proper heading hierarchy and document templates
+4. **Formatting**: Apply consistent formatting patterns immediately
+
+### **DO NOT**: Generate content that violates these rules
+
+- ❌ Generate long lines that need breaking
+- ❌ Create content without proper blank line spacing
+- ❌ Use inconsistent formatting patterns
+- ❌ Assume post-processing will fix violations
+
+### **DO**: Generate compliant content from the start
+
+- ✅ Write within 80-character limits
+- ✅ Add blank lines around all structural elements
+- ✅ Use established templates and patterns
+- ✅ Apply formatting standards immediately
+
 ## General Formatting Standards
 
 ### Line Length
@@ -326,6 +356,10 @@ Description of current situation or problem.
   ### Authentication
   ### Authorization
 
+  ## Features        ❌ (Duplicate heading)
+  ### Security
+  ### Performance
+  ```
   ## Features        ❌ (Duplicate heading)
   ### Security
   ### Performance

.cursor/rules/features/camera-implementation.mdc

@@ -1,13 +1,13 @@
 ---
-description: 
-globs: 
+description: when dealing with cameras in the application
 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/harbor_pilot_universal.mdc

@@ -0,0 +1,207 @@
+---
+alwaysApply: true
+inherits: base_context.mdc
+---
+```json
+{
+  "coaching_level": "standard",
+  "socratic_max_questions": 2,
+  "verbosity": "concise",
+  "timebox_minutes": 10,
+  "format_enforcement": "strict"
+}
+```
+
+# Harbor Pilot — Universal Directive for Human-Facing Technical Guides
+
+**Author**: System/Shared  
+**Date**: 2025-08-21 (UTC)  
+**Status**: 🚢 ACTIVE — General ruleset extending *Base Context — Human Competence First*
+
+> **Alignment with Base Context**
+> - **Purpose fit**: Prioritizes human competence and collaboration while delivering reproducible artifacts.  
+> - **Output Contract**: This directive **adds universal constraints** for any technical topic while **inheriting** the Base Context contract sections.  
+> - **Toggles honored**: Uses the same toggle semantics; defaults above can be overridden by the caller.
+
+---
+
+## Objective
+Produce a **developer-grade, reproducible guide** for any technical topic that onboards a competent practitioner **without meta narration** and **with evidence-backed steps**.
+
+## Scope & Constraints
+- **One Markdown document** as the deliverable.
+- Use **absolute dates** in **UTC** (e.g., `2025-08-21T14:22Z`) — avoid “today/yesterday”.
+- Include at least **one diagram** (Mermaid preferred). Choose the most fitting type:
+  - `sequenceDiagram` (protocols/flows), `flowchart`, `stateDiagram`, `gantt` (timelines), or `classDiagram` (schemas).
+- Provide runnable examples where applicable:
+  - **APIs**: `curl` + one client library (e.g., `httpx` for Python).
+  - **CLIs**: literal command blocks and expected output snippets.
+  - **Code**: minimal, self-contained samples (language appropriate).
+- Cite **evidence** for *Works/Doesn’t* items (timestamps, filenames, line numbers, IDs/status codes, or logs).
+- If something is unknown, output `TODO:<missing>` — **never invent**.
+
+## Required Sections (extends Base Output Contract)
+Follow this exact order **after** the Base Contract’s **Objective → Result → Use/Run** headers:
+
+1. **Context & Scope**
+   - Problem statement, audience, in/out-of-scope bullets.
+2. **Artifacts & Links**
+   - Repos/PRs, design docs, datasets/HARs/pcaps, scripts/tools, dashboards.
+3. **Environment & Preconditions**
+   - OS/runtime, versions/build IDs, services/endpoints/URLs, credentials/auth mode (describe acquisition, do not expose secrets).
+4. **Architecture / Process Overview**
+   - Short prose + **one diagram** selected from the list above.
+5. **Interfaces & Contracts (choose one)**
+   - **API-based**: Endpoint table (*Step, Method, Path/URL, Auth, Key Headers/Params, Sample Req/Resp ref*).
+   - **Data/Files**: I/O contract table (*Source, Format, Schema/Columns, Size, Validation rules*).
+   - **Systems/Hardware**: Interfaces table (*Port/Bus, Protocol, Voltage/Timing, Constraints*).
+6. **Repro: End-to-End Procedure**
+   - Minimal copy-paste steps with code/commands and **expected outputs**.
+7. **What Works (with Evidence)**
+   - Each item: **Time (UTC)** • **Artifact/Req IDs** • **Status/Result** • **Where to verify**.
+8. **What Doesn’t (Evidence & Hypotheses)**
+   - Each failure: locus (file/endpoint/module), evidence snippet; short hypothesis and **next probe**.
+9. **Risks, Limits, Assumptions**
+   - SLOs/limits, rate/size caps, security boundaries (CORS/CSRF/ACLs), retries/backoff/idempotency patterns.
+10. **Next Steps (Owner • Exit Criteria • Target Date)**
+    - Actionable, assigned, and time-bound.
+11. **References**
+    - Canonical docs, specs, tickets, prior analyses.
+
+> **Competence Hooks (per Base Context; keep lightweight):**
+> - *Why this works* (≤3 bullets) — core invariants or guarantees.  
+> - *Common pitfalls* (≤3 bullets) — the traps we saw in evidence.  
+> - *Next skill unlock* (1 line) — the next capability to implement/learn.  
+> - *Teach-back* (1 line) — prompt the reader to restate the flow/architecture.
+
+> **Collaboration Hooks (per Base Context):**
+> - Name reviewers for **Interfaces & Contracts** and the **diagram**.  
+> - Short **sign-off checklist** before merging/publishing the guide.
+
+## Do / Don’t (Base-aligned)
+- **Do** quantify progress only against a defined scope with acceptance criteria.
+- **Do** include minimal sample payloads/headers or I/O schemas; redact sensitive values.
+- **Do** keep commentary lean; if timeboxed, move depth to **Deferred for depth**.
+- **Don’t** use marketing language or meta narration (“Perfect!”, “tool called”, “new chat”).  
+- **Don’t** include IDE-specific chatter or internal rules unrelated to the task.
+
+## Validation Checklist (self-check before returning)
+- [ ] All Required Sections present and ordered.  
+- [ ] Diagram compiles (basic Mermaid syntax) and fits the problem.  
+- [ ] If API-based, **Auth** and **Key Headers/Params** are listed for each endpoint.  
+- [ ] Repro section includes commands/code **and expected outputs**.  
+- [ ] Every Works/Doesn’t item has **UTC timestamp**, **status/result**, and **verifiable evidence**.  
+- [ ] Next Steps include **Owner**, **Exit Criteria**, **Target Date**.  
+- [ ] Unknowns are `TODO:<missing>` — no fabrication.  
+- [ ] Base **Output Contract** sections satisfied (Objective/Result/Use/Run/Competence/Collaboration/Assumptions/References).
+
+## Universal Template (fill-in)
+```markdown
+# <Title> — Working Notes (As of YYYY-MM-DDTHH:MMZ)
+
+## Objective
+<one line>
+
+## Result
+<link to the produced guide file or say “this document”>
+
+## Use/Run
+<how to apply/test and where to run samples>
+
+## Context & Scope
+- Audience: <role(s)>
+- In scope: <bullets>
+- Out of scope: <bullets>
+
+## Artifacts & Links
+- Repo/PR: <link>
+- Data/Logs: <paths or links>
+- Scripts/Tools: <paths>
+- Dashboards: <links>
+
+## Environment & Preconditions
+- OS/Runtime: <details>
+- Versions/Builds: <list>
+- Services/Endpoints: <list>
+- Auth mode: <Bearer/Session/Keys + how acquired>
+
+## Architecture / Process Overview
+<short prose>
+```mermaid
+<one suitable diagram: sequenceDiagram | flowchart | stateDiagram | gantt | classDiagram>
+```
+
+## Interfaces & Contracts
+### If API-based
+| Step | Method | Path/URL | Auth | Key Headers/Params | Sample |
+|---|---|---|---|---|---|
+| <…> | <…> | <…> | <…> | <…> | below |
+
+### If Data/Files
+| Source | Format | Schema/Columns | Size | Validation |
+|---|---|---|---|---|
+| <…> | <…> | <…> | <…> | <…> |
+
+### If Systems/Hardware
+| Interface | Protocol | Timing/Voltage | Constraints | Notes |
+|---|---|---|---|---|
+| <…> | <…> | <…> | <…> | <…> |
+
+## Repro: End-to-End Procedure
+```bash
+# commands / curl examples (redacted where necessary)
+```
+```python
+# minimal client library example (language appropriate)
+```
+> Expected output: <snippet/checks>
+
+## What Works (Evidence)
+- ✅ <short statement>  
+  - **Time**: <YYYY-MM-DDTHH:MMZ>  
+  - **Evidence**: file/line/log or request id/status  
+  - **Verify at**: <where>
+
+## What Doesn’t (Evidence & Hypotheses)
+- ❌ <short failure> at `<component/endpoint/file>`  
+  - **Time**: <YYYY-MM-DDTHH:MMZ>  
+  - **Evidence**: <snippet/id/status>  
+  - **Hypothesis**: <short>  
+  - **Next probe**: <short>
+
+## Risks, Limits, Assumptions
+<bullets: limits, security boundaries, retries/backoff, idempotency, SLOs>
+
+## Next Steps
+| Owner | Task | Exit Criteria | Target Date (UTC) |
+|---|---|---|---|
+| <name> | <action> | <measurable outcome> | <YYYY-MM-DD> |
+
+## References
+<links/titles>
+
+## Competence Hooks
+- *Why this works*: <≤3 bullets>
+- *Common pitfalls*: <≤3 bullets>
+- *Next skill unlock*: <1 line>
+- *Teach-back*: <1 line>
+
+## Collaboration Hooks
+- Reviewers: <names/roles>
+- Sign-off checklist: <≤5 checks>
+
+## Assumptions & Limits
+<bullets>
+
+## Deferred for depth
+<park deeper material here to respect timeboxing>
+```
+
+---
+
+**Notes for Implementers:**  
+- Respect Base *Do-Not* (no filler, no invented facts, no censorship).  
+- Prefer clarity over completeness when timeboxed; capture unknowns explicitly.
+- Apply historical comment management rules (see `.cursor/rules/historical_comment_management.mdc`)
+- Apply realistic time estimation rules (see `.cursor/rules/realistic_time_estimation.mdc`)
+- Apply Playwright test investigation rules (see `.cursor/rules/playwright_test_investigation.mdc`)

.cursor/rules/historical_comment_management.mdc

@@ -0,0 +1,236 @@
+---
+description: when comments are generated by the model
+alwaysApply: false
+---
+# Historical Comment Management — Harbor Pilot Directive
+
+> **Agent role**: When encountering historical comments about removed methods, deprecated patterns, or architectural changes, apply these guidelines to maintain code clarity and developer guidance.
+
+## 🎯 Purpose
+
+Historical comments should either be **removed entirely** or **transformed into actionable guidance** for future developers. Avoid keeping comments that merely state what was removed without explaining why or what to do instead.
+
+## 📋 Decision Framework
+
+### Remove Historical Comments When:
+- **Obsolete Information**: Comment describes functionality that no longer exists
+- **No Action Required**: Comment doesn't help future developers make decisions
+- **Outdated Context**: Comment refers to old patterns that are no longer relevant
+- **Self-Evident**: The current code clearly shows the current approach
+
+### Transform Historical Comments When:
+- **Architectural Context**: The change represents a significant pattern shift
+- **Migration Guidance**: Future developers might need to understand the evolution
+- **Decision Rationale**: The "why" behind the change is still relevant
+- **Alternative Approaches**: The comment can guide future implementation choices
+
+## 🔄 Transformation Patterns
+
+### 1. From Removal Notice to Migration Note
+```typescript
+// ❌ REMOVE THIS
+// turnOffNotifyingFlags method removed - notification state is now managed by NotificationSection component
+
+// ✅ TRANSFORM TO THIS
+// Note: Notification state management has been migrated to NotificationSection component
+// which handles its own lifecycle and persistence via PlatformServiceMixin
+```
+
+### 2. From Deprecation Notice to Implementation Guide
+```typescript
+// ❌ REMOVE THIS
+// This will be handled by the NewComponent now
+// No need to call oldMethod() as it's no longer needed
+
+// ✅ TRANSFORM TO THIS
+// Note: This functionality has been migrated to NewComponent
+// which provides better separation of concerns and testability
+```
+
+### 3. From Historical Note to Architectural Context
+```typescript
+// ❌ REMOVE THIS
+// Old approach: used direct database calls
+// New approach: uses service layer
+
+// ✅ TRANSFORM TO THIS
+// Note: Database access has been abstracted through service layer
+// for better testability and platform independence
+```
+
+## 🚫 Anti-Patterns to Remove
+
+- Comments that only state what was removed
+- Comments that don't explain the current approach
+- Comments that reference non-existent methods
+- Comments that are self-evident from the code
+- Comments that don't help future decision-making
+
+## ✅ Best Practices
+
+### When Keeping Historical Context:
+1. **Explain the "Why"**: Why was the change made?
+2. **Describe the "What"**: What is the current approach?
+3. **Provide Context**: When might this information be useful?
+4. **Use Actionable Language**: Guide future decisions, not just document history
+
+### When Removing Historical Context:
+1. **Verify Obsoleteness**: Ensure the information is truly outdated
+2. **Check for Dependencies**: Ensure no other code references the old approach
+3. **Update Related Docs**: If removing from code, consider adding to documentation
+4. **Preserve in Git History**: The change is preserved in version control
+
+## 🔍 Implementation Checklist
+
+- [ ] Identify historical comments about removed/deprecated functionality
+- [ ] Determine if comment provides actionable guidance
+- [ ] Transform useful comments into migration notes or architectural context
+- [ ] Remove comments that are purely historical without guidance value
+- [ ] Ensure remaining comments explain current approach and rationale
+- [ ] Update related documentation if significant context is removed
+
+## 📚 Examples
+
+### Good Historical Comment (Keep & Transform)
+```typescript
+// Note: Database access has been migrated from direct IndexedDB calls to PlatformServiceMixin
+// This provides better platform abstraction and consistent error handling across web/mobile/desktop
+// When adding new database operations, use this.$getContact(), this.$saveSettings(), etc.
+```
+
+### Bad Historical Comment (Remove)
+```typescript
+// Old method getContactFromDB() removed - now handled by PlatformServiceMixin
+// No need to call the old method anymore
+```
+
+## 🎯 Integration with Harbor Pilot
+
+This rule works in conjunction with:
+- **Component Creation Ideals**: Maintains architectural consistency
+- **Migration Patterns**: Documents evolution of patterns
+- **Code Review Guidelines**: Ensures comments provide value
+
+## 📝 Version History
+
+### v1.0.0 (2025-08-21)
+- Initial creation based on notification system cleanup
+- Established decision framework for historical comment management
+- Added transformation patterns and anti-patterns
+- Integrated with existing Harbor Pilot architecture rules
+# Historical Comment Management — Harbor Pilot Directive
+
+> **Agent role**: When encountering historical comments about removed methods, deprecated patterns, or architectural changes, apply these guidelines to maintain code clarity and developer guidance.
+
+## 🎯 Purpose
+
+Historical comments should either be **removed entirely** or **transformed into actionable guidance** for future developers. Avoid keeping comments that merely state what was removed without explaining why or what to do instead.
+
+## 📋 Decision Framework
+
+### Remove Historical Comments When:
+- **Obsolete Information**: Comment describes functionality that no longer exists
+- **No Action Required**: Comment doesn't help future developers make decisions
+- **Outdated Context**: Comment refers to old patterns that are no longer relevant
+- **Self-Evident**: The current code clearly shows the current approach
+
+### Transform Historical Comments When:
+- **Architectural Context**: The change represents a significant pattern shift
+- **Migration Guidance**: Future developers might need to understand the evolution
+- **Decision Rationale**: The "why" behind the change is still relevant
+- **Alternative Approaches**: The comment can guide future implementation choices
+
+## 🔄 Transformation Patterns
+
+### 1. From Removal Notice to Migration Note
+```typescript
+// ❌ REMOVE THIS
+// turnOffNotifyingFlags method removed - notification state is now managed by NotificationSection component
+
+// ✅ TRANSFORM TO THIS
+// Note: Notification state management has been migrated to NotificationSection component
+// which handles its own lifecycle and persistence via PlatformServiceMixin
+```
+
+### 2. From Deprecation Notice to Implementation Guide
+```typescript
+// ❌ REMOVE THIS
+// This will be handled by the NewComponent now
+// No need to call oldMethod() as it's no longer needed
+
+// ✅ TRANSFORM TO THIS
+// Note: This functionality has been migrated to NewComponent
+// which provides better separation of concerns and testability
+```
+
+### 3. From Historical Note to Architectural Context
+```typescript
+// ❌ REMOVE THIS
+// Old approach: used direct database calls
+// New approach: uses service layer
+
+// ✅ TRANSFORM TO THIS
+// Note: Database access has been abstracted through service layer
+// for better testability and platform independence
+```
+
+## 🚫 Anti-Patterns to Remove
+
+- Comments that only state what was removed
+- Comments that don't explain the current approach
+- Comments that reference non-existent methods
+- Comments that are self-evident from the code
+- Comments that don't help future decision-making
+
+## ✅ Best Practices
+
+### When Keeping Historical Context:
+1. **Explain the "Why"**: Why was the change made?
+2. **Describe the "What"**: What is the current approach?
+3. **Provide Context**: When might this information be useful?
+4. **Use Actionable Language**: Guide future decisions, not just document history
+
+### When Removing Historical Context:
+1. **Verify Obsoleteness**: Ensure the information is truly outdated
+2. **Check for Dependencies**: Ensure no other code references the old approach
+3. **Update Related Docs**: If removing from code, consider adding to documentation
+4. **Preserve in Git History**: The change is preserved in version control
+
+## 🔍 Implementation Checklist
+
+- [ ] Identify historical comments about removed/deprecated functionality
+- [ ] Determine if comment provides actionable guidance
+- [ ] Transform useful comments into migration notes or architectural context
+- [ ] Remove comments that are purely historical without guidance value
+- [ ] Ensure remaining comments explain current approach and rationale
+- [ ] Update related documentation if significant context is removed
+
+## 📚 Examples
+
+### Good Historical Comment (Keep & Transform)
+```typescript
+// Note: Database access has been migrated from direct IndexedDB calls to PlatformServiceMixin
+// This provides better platform abstraction and consistent error handling across web/mobile/desktop
+// When adding new database operations, use this.$getContact(), this.$saveSettings(), etc.
+```
+
+### Bad Historical Comment (Remove)
+```typescript
+// Old method getContactFromDB() removed - now handled by PlatformServiceMixin
+// No need to call the old method anymore
+```
+
+## 🎯 Integration with Harbor Pilot
+
+This rule works in conjunction with:
+- **Component Creation Ideals**: Maintains architectural consistency
+- **Migration Patterns**: Documents evolution of patterns
+- **Code Review Guidelines**: Ensures comments provide value
+
+## 📝 Version History
+
+### v1.0.0 (2025-08-21)
+- Initial creation based on notification system cleanup
+- Established decision framework for historical comment management
+- Added transformation patterns and anti-patterns
+- Integrated with existing Harbor Pilot architecture rules

.cursor/rules/investigation_report_example.mdc

@@ -0,0 +1,117 @@
+# 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/legacy_dexie.mdc

@@ -1,6 +0,0 @@
----
-description: 
-globs: 
-alwaysApply: true
----
-All references in the codebase to Dexie apply only to migration from IndexedDb to Sqlite and will be deprecated in future versions.

.cursor/rules/logging_standards.mdc

@@ -0,0 +1,222 @@
+# 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/playwright-test-investigation.mdc

@@ -0,0 +1,356 @@
+---
+description: when working with playwright tests either generating them or using them to test code
+alwaysApply: false
+---
+# Playwright Test Investigation — Harbor Pilot Directive
+
+**Author**: Matthew Raymer  
+**Date**: 2025-08-21T14:22Z  
+**Status**: 🎯 **ACTIVE** - Playwright test debugging guidelines
+
+## Objective
+Provide systematic approach for investigating Playwright test failures with focus on UI element conflicts, timing issues, and selector ambiguity.
+
+## Context & Scope
+- **Audience**: Developers debugging Playwright test failures
+- **In scope**: Test failure analysis, selector conflicts, UI state investigation, timing issues
+- **Out of scope**: Test writing best practices, CI/CD configuration
+
+## Artifacts & Links
+- Test results: `test-results/` directory
+- Error context: `error-context.md` files with page snapshots
+- Trace files: `trace.zip` files for failed tests
+- HTML reports: Interactive test reports with screenshots
+
+## Environment & Preconditions
+- OS/Runtime: Linux/Windows/macOS with Node.js
+- Versions: Playwright test framework, browser drivers
+- Services: Local test server (localhost:8080), test data setup
+- Auth mode: None required for test investigation
+
+## Architecture / Process Overview
+Playwright test investigation follows a systematic diagnostic workflow that leverages built-in debugging tools and error context analysis.
+
+```mermaid
+flowchart TD
+    A[Test Failure] --> B[Check Error Context]
+    B --> C[Analyze Page Snapshot]
+    C --> D[Identify UI Conflicts]
+    D --> E[Check Trace Files]
+    E --> F[Verify Selector Uniqueness]
+    F --> G[Test Selector Fixes]
+    G --> H[Document Root Cause]
+    
+    B --> I[Check Test Results Directory]
+    I --> J[Locate Failed Test Results]
+    J --> K[Extract Error Details]
+    
+    D --> L[Multiple Alerts?]
+    L --> M[Button Text Conflicts?]
+    M --> N[Timing Issues?]
+    
+    E --> O[Use Trace Viewer]
+    O --> P[Analyze Action Sequence]
+    P --> Q[Identify Failure Point]
+```
+
+## Interfaces & Contracts
+
+### Test Results Structure
+| Component | Format | Content | Validation |
+|---|---|---|---|
+| Error Context | Markdown | Page snapshot in YAML | Verify DOM state matches test expectations |
+| Trace Files | ZIP archive | Detailed execution trace | Use `npx playwright show-trace` |
+| HTML Reports | Interactive HTML | Screenshots, traces, logs | Check browser for full report |
+| JSON Results | JSON | Machine-readable results | Parse for automated analysis |
+
+### Investigation Commands
+| Step | Command | Expected Output | Notes |
+|---|---|---|---|
+| Locate failed tests | `find test-results -name "*test-name*"` | Test result directories | Use exact test name patterns |
+| Check error context | `cat test-results/*/error-context.md` | Page snapshots | Look for UI state conflicts |
+| View traces | `npx playwright show-trace trace.zip` | Interactive trace viewer | Analyze exact failure sequence |
+
+## Repro: End-to-End Investigation Procedure
+
+### 1. Locate Failed Test Results
+```bash
+# Find all results for a specific test
+find test-results -name "*test-name*" -type d
+
+# Check for error context files
+find test-results -name "error-context.md" | head -5
+```
+
+### 2. Analyze Error Context
+```bash
+# Read error context for specific test
+cat test-results/test-name-test-description-browser/error-context.md
+
+# Look for UI conflicts in page snapshot
+grep -A 10 -B 5 "button.*Yes\|button.*No" test-results/*/error-context.md
+```
+
+### 3. Check Trace Files
+```bash
+# List available trace files
+find test-results -name "*.zip" | grep trace
+
+# View trace in browser
+npx playwright show-trace test-results/test-name/trace.zip
+```
+
+### 4. Investigate Selector Issues
+```typescript
+// Check for multiple elements with same text
+await page.locator('button:has-text("Yes")').count(); // Should be 1
+
+// Use more specific selectors
+await page.locator('div[role="alert"]:has-text("Register") button:has-text("Yes")').click();
+```
+
+## What Works (Evidence)
+- ✅ **Error context files** provide page snapshots showing exact DOM state at failure  
+  - **Time**: 2025-08-21T14:22Z  
+  - **Evidence**: `test-results/60-new-activity-New-offers-for-another-user-chromium/error-context.md` shows both alerts visible  
+  - **Verify at**: Error context files in test results directory
+
+- ✅ **Trace files** capture detailed execution sequence for failed tests  
+  - **Time**: 2025-08-21T14:22Z  
+  - **Evidence**: `trace.zip` files available for all failed tests  
+  - **Verify at**: Use `npx playwright show-trace <filename>`
+
+- ✅ **Page snapshots** reveal UI conflicts like multiple alerts with duplicate button text  
+  - **Time**: 2025-08-21T14:22Z  
+  - **Evidence**: YAML snapshots show registration + export alerts simultaneously  
+  - **Verify at**: Error context markdown files
+
+## What Doesn't (Evidence & Hypotheses)
+- ❌ **Generic selectors** fail with multiple similar elements at `test-playwright/testUtils.ts:161`  
+  - **Time**: 2025-08-21T14:22Z  
+  - **Evidence**: `button:has-text("Yes")` matches both "Yes" and "Yes, Export Data"  
+  - **Hypothesis**: Selector ambiguity due to multiple alerts with conflicting button text  
+  - **Next probe**: Use more specific selectors or dismiss alerts sequentially
+
+- ❌ **Timing-dependent tests** fail due to alert stacking at `src/views/ContactsView.vue:860,1283`  
+  - **Time**: 2025-08-21T14:22Z  
+  - **Evidence**: Both alerts use identical 1000ms delays, ensuring simultaneous display  
+  - **Hypothesis**: Race condition between alert displays creates UI conflicts  
+  - **Next probe**: Implement alert queuing or prevent overlapping alerts
+
+## Risks, Limits, Assumptions
+- **Trace file size**: Large trace files may impact storage and analysis time
+- **Browser compatibility**: Trace viewer requires specific browser support
+- **Test isolation**: Shared state between tests may affect investigation results
+- **Timing sensitivity**: Tests may pass/fail based on system performance
+
+## Next Steps
+| Owner | Task | Exit Criteria | Target Date (UTC) |
+|---|---|---|---|
+| Development Team | Fix test selectors for multiple alerts | All tests pass consistently | 2025-08-22 |
+| Development Team | Implement alert queuing system | No overlapping alerts with conflicting buttons | 2025-08-25 |
+| Development Team | Add test IDs to alert buttons | Unique selectors for all UI elements | 2025-08-28 |
+
+## References
+- [Playwright Trace Viewer Documentation](https://playwright.dev/docs/trace-viewer)
+- [Playwright Test Results](https://playwright.dev/docs/test-reporters)
+- [Test Investigation Workflow](./research_diagnostic.mdc)
+
+## Competence Hooks
+- **Why this works**: Systematic investigation leverages Playwright's built-in debugging tools to identify root causes
+- **Common pitfalls**: Generic selectors fail with multiple similar elements; timing issues create race conditions; alert stacking causes UI conflicts
+- **Next skill unlock**: Implement unique test IDs and handle alert dismissal order in test flows
+- **Teach-back**: "How would you investigate a Playwright test failure using error context, trace files, and page snapshots?"
+
+## Collaboration Hooks
+- **Reviewers**: QA team, test automation engineers
+- **Sign-off checklist**: Error context analyzed, trace files reviewed, root cause identified, fix implemented and tested
+
+## Assumptions & Limits
+- Test results directory structure follows Playwright conventions
+- Trace files are enabled in configuration (`trace: "retain-on-failure"`)
+- Error context files contain valid YAML page snapshots
+- Browser environment supports trace viewer functionality
+
+---
+
+**Status**: Active investigation directive  
+**Priority**: High  
+**Maintainer**: Development team  
+**Next Review**: 2025-09-21
+# Playwright Test Investigation — Harbor Pilot Directive
+
+**Author**: Matthew Raymer  
+**Date**: 2025-08-21T14:22Z  
+**Status**: 🎯 **ACTIVE** - Playwright test debugging guidelines
+
+## Objective
+Provide systematic approach for investigating Playwright test failures with focus on UI element conflicts, timing issues, and selector ambiguity.
+
+## Context & Scope
+- **Audience**: Developers debugging Playwright test failures
+- **In scope**: Test failure analysis, selector conflicts, UI state investigation, timing issues
+- **Out of scope**: Test writing best practices, CI/CD configuration
+
+## Artifacts & Links
+- Test results: `test-results/` directory
+- Error context: `error-context.md` files with page snapshots
+- Trace files: `trace.zip` files for failed tests
+- HTML reports: Interactive test reports with screenshots
+
+## Environment & Preconditions
+- OS/Runtime: Linux/Windows/macOS with Node.js
+- Versions: Playwright test framework, browser drivers
+- Services: Local test server (localhost:8080), test data setup
+- Auth mode: None required for test investigation
+
+## Architecture / Process Overview
+Playwright test investigation follows a systematic diagnostic workflow that leverages built-in debugging tools and error context analysis.
+
+```mermaid
+flowchart TD
+    A[Test Failure] --> B[Check Error Context]
+    B --> C[Analyze Page Snapshot]
+    C --> D[Identify UI Conflicts]
+    D --> E[Check Trace Files]
+    E --> F[Verify Selector Uniqueness]
+    F --> G[Test Selector Fixes]
+    G --> H[Document Root Cause]
+    
+    B --> I[Check Test Results Directory]
+    I --> J[Locate Failed Test Results]
+    J --> K[Extract Error Details]
+    
+    D --> L[Multiple Alerts?]
+    L --> M[Button Text Conflicts?]
+    M --> N[Timing Issues?]
+    
+    E --> O[Use Trace Viewer]
+    O --> P[Analyze Action Sequence]
+    P --> Q[Identify Failure Point]
+```
+
+## Interfaces & Contracts
+
+### Test Results Structure
+| Component | Format | Content | Validation |
+|---|---|---|---|
+| Error Context | Markdown | Page snapshot in YAML | Verify DOM state matches test expectations |
+| Trace Files | ZIP archive | Detailed execution trace | Use `npx playwright show-trace` |
+| HTML Reports | Interactive HTML | Screenshots, traces, logs | Check browser for full report |
+| JSON Results | JSON | Machine-readable results | Parse for automated analysis |
+
+### Investigation Commands
+| Step | Command | Expected Output | Notes |
+|---|---|---|---|
+| Locate failed tests | `find test-results -name "*test-name*"` | Test result directories | Use exact test name patterns |
+| Check error context | `cat test-results/*/error-context.md` | Page snapshots | Look for UI state conflicts |
+| View traces | `npx playwright show-trace trace.zip` | Interactive trace viewer | Analyze exact failure sequence |
+
+## Repro: End-to-End Investigation Procedure
+
+### 1. Locate Failed Test Results
+```bash
+# Find all results for a specific test
+find test-results -name "*test-name*" -type d
+
+# Check for error context files
+find test-results -name "error-context.md" | head -5
+```
+
+### 2. Analyze Error Context
+```bash
+# Read error context for specific test
+cat test-results/test-name-test-description-browser/error-context.md
+
+# Look for UI conflicts in page snapshot
+grep -A 10 -B 5 "button.*Yes\|button.*No" test-results/*/error-context.md
+```
+
+### 3. Check Trace Files
+```bash
+# List available trace files
+find test-results -name "*.zip" | grep trace
+
+# View trace in browser
+npx playwright show-trace test-results/test-name/trace.zip
+```
+
+### 4. Investigate Selector Issues
+```typescript
+// Check for multiple elements with same text
+await page.locator('button:has-text("Yes")').count(); // Should be 1
+
+// Use more specific selectors
+await page.locator('div[role="alert"]:has-text("Register") button:has-text("Yes")').click();
+```
+
+## What Works (Evidence)
+- ✅ **Error context files** provide page snapshots showing exact DOM state at failure  
+  - **Time**: 2025-08-21T14:22Z  
+  - **Evidence**: `test-results/60-new-activity-New-offers-for-another-user-chromium/error-context.md` shows both alerts visible  
+  - **Verify at**: Error context files in test results directory
+
+- ✅ **Trace files** capture detailed execution sequence for failed tests  
+  - **Time**: 2025-08-21T14:22Z  
+  - **Evidence**: `trace.zip` files available for all failed tests  
+  - **Verify at**: Use `npx playwright show-trace <filename>`
+
+- ✅ **Page snapshots** reveal UI conflicts like multiple alerts with duplicate button text  
+  - **Time**: 2025-08-21T14:22Z  
+  - **Evidence**: YAML snapshots show registration + export alerts simultaneously  
+  - **Verify at**: Error context markdown files
+
+## What Doesn't (Evidence & Hypotheses)
+- ❌ **Generic selectors** fail with multiple similar elements at `test-playwright/testUtils.ts:161`  
+  - **Time**: 2025-08-21T14:22Z  
+  - **Evidence**: `button:has-text("Yes")` matches both "Yes" and "Yes, Export Data"  
+  - **Hypothesis**: Selector ambiguity due to multiple alerts with conflicting button text  
+  - **Next probe**: Use more specific selectors or dismiss alerts sequentially
+
+- ❌ **Timing-dependent tests** fail due to alert stacking at `src/views/ContactsView.vue:860,1283`  
+  - **Time**: 2025-08-21T14:22Z  
+  - **Evidence**: Both alerts use identical 1000ms delays, ensuring simultaneous display  
+  - **Hypothesis**: Race condition between alert displays creates UI conflicts  
+  - **Next probe**: Implement alert queuing or prevent overlapping alerts
+
+## Risks, Limits, Assumptions
+- **Trace file size**: Large trace files may impact storage and analysis time
+- **Browser compatibility**: Trace viewer requires specific browser support
+- **Test isolation**: Shared state between tests may affect investigation results
+- **Timing sensitivity**: Tests may pass/fail based on system performance
+
+## Next Steps
+| Owner | Task | Exit Criteria | Target Date (UTC) |
+|---|---|---|---|
+| Development Team | Fix test selectors for multiple alerts | All tests pass consistently | 2025-08-22 |
+| Development Team | Implement alert queuing system | No overlapping alerts with conflicting buttons | 2025-08-25 |
+| Development Team | Add test IDs to alert buttons | Unique selectors for all UI elements | 2025-08-28 |
+
+## References
+- [Playwright Trace Viewer Documentation](https://playwright.dev/docs/trace-viewer)
+- [Playwright Test Results](https://playwright.dev/docs/test-reporters)
+- [Test Investigation Workflow](./research_diagnostic.mdc)
+
+## Competence Hooks
+- **Why this works**: Systematic investigation leverages Playwright's built-in debugging tools to identify root causes
+- **Common pitfalls**: Generic selectors fail with multiple similar elements; timing issues create race conditions; alert stacking causes UI conflicts
+- **Next skill unlock**: Implement unique test IDs and handle alert dismissal order in test flows
+- **Teach-back**: "How would you investigate a Playwright test failure using error context, trace files, and page snapshots?"
+
+## Collaboration Hooks
+- **Reviewers**: QA team, test automation engineers
+- **Sign-off checklist**: Error context analyzed, trace files reviewed, root cause identified, fix implemented and tested
+
+## Assumptions & Limits
+- Test results directory structure follows Playwright conventions
+- Trace files are enabled in configuration (`trace: "retain-on-failure"`)
+- Error context files contain valid YAML page snapshots
+- Browser environment supports trace viewer functionality
+
+---
+
+**Status**: Active investigation directive  
+**Priority**: High  
+**Maintainer**: Development team  
+**Next Review**: 2025-09-21

.cursor/rules/realistic_time_estimation.mdc

@@ -0,0 +1,348 @@
+---
+description: when generating text that has project task work estimates
+alwaysApply: false
+---
+# No Time Estimates — Harbor Pilot Directive
+
+> **Agent role**: **DO NOT MAKE TIME ESTIMATES**. Instead, use phases, milestones, and complexity levels. Time estimates are consistently wrong and create unrealistic expectations.
+
+## 🎯 Purpose
+
+Development time estimates are consistently wrong and create unrealistic expectations. This rule ensures we focus on phases, milestones, and complexity rather than trying to predict specific timeframes.
+
+## 🚨 Critical Rule
+
+**DO NOT MAKE TIME ESTIMATES**
+- **Never provide specific time estimates** - they are always wrong
+- **Use phases and milestones** instead of days/weeks
+- **Focus on complexity and dependencies** rather than time
+- **Set expectations based on progress, not deadlines**
+
+## 📊 Planning Framework (Not Time Estimates)
+
+### **Complexity Categories**
+- **Simple**: Text changes, styling updates, minor bug fixes
+- **Medium**: New features, refactoring, component updates
+- **Complex**: Architecture changes, integrations, cross-platform work
+- **Unknown**: New technologies, APIs, or approaches
+
+### **Platform Complexity**
+- **Single platform**: Web-only or mobile-only changes
+- **Two platforms**: Web + mobile or web + desktop
+- **Three platforms**: Web + mobile + desktop
+- **Cross-platform consistency**: Ensuring behavior matches across all platforms
+
+### **Testing Complexity**
+- **Basic**: Unit tests for new functionality
+- **Comprehensive**: Integration tests, cross-platform testing
+- **User acceptance**: User testing, feedback integration
+
+## 🔍 Planning Process (No Time Estimates)
+
+### **Step 1: Break Down the Work**
+- Identify all subtasks and dependencies
+- Group related work into logical phases
+- Identify critical path and blockers
+
+### **Step 2: Define Phases and Milestones**
+- **Phase 1**: Foundation work (basic fixes, core functionality)
+- **Phase 2**: Enhancement work (new features, integrations)
+- **Phase 3**: Polish work (testing, user experience, edge cases)
+
+### **Step 3: Identify Dependencies**
+- **Technical dependencies**: What must be built first
+- **Platform dependencies**: What works on which platforms
+- **Testing dependencies**: What can be tested when
+
+### **Step 4: Set Progress Milestones**
+- **Milestone 1**: Basic functionality working
+- **Milestone 2**: All platforms supported
+- **Milestone 3**: Fully tested and polished
+
+## 📋 Planning Checklist (No Time Estimates)
+
+- [ ] Work broken down into logical phases
+- [ ] Dependencies identified and mapped
+- [ ] Milestones defined with clear criteria
+- [ ] Complexity levels assigned to each phase
+- [ ] Platform requirements identified
+- [ ] Testing strategy planned
+- [ ] Risk factors identified
+- [ ] Success criteria defined
+
+## 🎯 Example Planning (No Time Estimates)
+
+### **Example 1: Simple Feature**
+```
+Phase 1: Core implementation
+- Basic functionality
+- Single platform support
+- Unit tests
+
+Phase 2: Platform expansion
+- Multi-platform support
+- Integration tests
+
+Phase 3: Polish
+- User testing
+- Edge case handling
+```
+
+### **Example 2: Complex Cross-Platform Feature**
+```
+Phase 1: Foundation
+- Architecture design
+- Core service implementation
+- Basic web platform support
+
+Phase 2: Platform Integration
+- Mobile platform support
+- Desktop platform support
+- Cross-platform consistency
+
+Phase 3: Testing & Polish
+- Comprehensive testing
+- Error handling
+- User experience refinement
+```
+
+## 🚫 Anti-Patterns to Avoid
+
+- **"This should take X days"** - Red flag for time estimation
+- **"Just a few hours"** - Ignores complexity and testing
+- **"Similar to X"** - Without considering differences
+- **"Quick fix"** - Nothing is ever quick in software
+- **"No testing needed"** - Testing always takes effort
+
+## ✅ Best Practices
+
+### **When Planning:**
+1. **Break down everything** - no work is too small to plan
+2. **Consider all platforms** - web, mobile, desktop differences
+3. **Include testing strategy** - unit, integration, and user testing
+4. **Account for unknowns** - there are always surprises
+5. **Focus on dependencies** - what blocks what
+
+### **When Presenting Plans:**
+1. **Show the phases** - explain the logical progression
+2. **Highlight dependencies** - what could block progress
+3. **Define milestones** - clear success criteria
+4. **Identify risks** - what could go wrong
+5. **Suggest alternatives** - ways to reduce scope or complexity
+
+## 🔄 Continuous Improvement
+
+### **Track Progress**
+- Record planned vs. actual phases completed
+- Identify what took longer than expected
+- Learn from complexity misjudgments
+- Adjust planning process based on experience
+
+### **Learn from Experience**
+- **Underestimated complexity**: Increase complexity categories
+- **Missed dependencies**: Improve dependency mapping
+- **Platform surprises**: Better platform research upfront
+
+## 🎯 Integration with Harbor Pilot
+
+This rule works in conjunction with:
+- **Project Planning**: Focuses on phases and milestones
+- **Resource Allocation**: Based on complexity, not time
+- **Risk Management**: Identifies blockers and dependencies
+- **Stakeholder Communication**: Sets progress-based expectations
+
+## 📝 Version History
+
+### v2.0.0 (2025-08-21)
+- **Major Change**: Completely removed time estimation approach
+- **New Focus**: Phases, milestones, and complexity-based planning
+- **Eliminated**: All time multipliers, estimates, and calculations
+- **Added**: Dependency mapping and progress milestone framework
+
+### v1.0.0 (2025-08-21)
+- Initial creation based on user feedback about estimation accuracy
+- ~~Established realistic estimation multipliers and process~~
+- ~~Added comprehensive estimation checklist and examples~~
+- Integrated with Harbor Pilot planning and risk management
+
+---
+
+## 🚨 Remember
+
+**DO NOT MAKE TIME ESTIMATES. Use phases, milestones, and complexity instead. Focus on progress, not deadlines.**
+
+## 🚨 Remember
+
+**Your first estimate is wrong. Your second estimate is probably still wrong. Focus on progress, not deadlines.**
+# No Time Estimates — Harbor Pilot Directive
+
+> **Agent role**: **DO NOT MAKE TIME ESTIMATES**. Instead, use phases, milestones, and complexity levels. Time estimates are consistently wrong and create unrealistic expectations.
+
+## 🎯 Purpose
+
+Development time estimates are consistently wrong and create unrealistic expectations. This rule ensures we focus on phases, milestones, and complexity rather than trying to predict specific timeframes.
+
+## 🚨 Critical Rule
+
+**DO NOT MAKE TIME ESTIMATES**
+- **Never provide specific time estimates** - they are always wrong
+- **Use phases and milestones** instead of days/weeks
+- **Focus on complexity and dependencies** rather than time
+- **Set expectations based on progress, not deadlines**
+
+## 📊 Planning Framework (Not Time Estimates)
+
+### **Complexity Categories**
+- **Simple**: Text changes, styling updates, minor bug fixes
+- **Medium**: New features, refactoring, component updates
+- **Complex**: Architecture changes, integrations, cross-platform work
+- **Unknown**: New technologies, APIs, or approaches
+
+### **Platform Complexity**
+- **Single platform**: Web-only or mobile-only changes
+- **Two platforms**: Web + mobile or web + desktop
+- **Three platforms**: Web + mobile + desktop
+- **Cross-platform consistency**: Ensuring behavior matches across all platforms
+
+### **Testing Complexity**
+- **Basic**: Unit tests for new functionality
+- **Comprehensive**: Integration tests, cross-platform testing
+- **User acceptance**: User testing, feedback integration
+
+## 🔍 Planning Process (No Time Estimates)
+
+### **Step 1: Break Down the Work**
+- Identify all subtasks and dependencies
+- Group related work into logical phases
+- Identify critical path and blockers
+
+### **Step 2: Define Phases and Milestones**
+- **Phase 1**: Foundation work (basic fixes, core functionality)
+- **Phase 2**: Enhancement work (new features, integrations)
+- **Phase 3**: Polish work (testing, user experience, edge cases)
+
+### **Step 3: Identify Dependencies**
+- **Technical dependencies**: What must be built first
+- **Platform dependencies**: What works on which platforms
+- **Testing dependencies**: What can be tested when
+
+### **Step 4: Set Progress Milestones**
+- **Milestone 1**: Basic functionality working
+- **Milestone 2**: All platforms supported
+- **Milestone 3**: Fully tested and polished
+
+## 📋 Planning Checklist (No Time Estimates)
+
+- [ ] Work broken down into logical phases
+- [ ] Dependencies identified and mapped
+- [ ] Milestones defined with clear criteria
+- [ ] Complexity levels assigned to each phase
+- [ ] Platform requirements identified
+- [ ] Testing strategy planned
+- [ ] Risk factors identified
+- [ ] Success criteria defined
+
+## 🎯 Example Planning (No Time Estimates)
+
+### **Example 1: Simple Feature**
+```
+Phase 1: Core implementation
+- Basic functionality
+- Single platform support
+- Unit tests
+
+Phase 2: Platform expansion
+- Multi-platform support
+- Integration tests
+
+Phase 3: Polish
+- User testing
+- Edge case handling
+```
+
+### **Example 2: Complex Cross-Platform Feature**
+```
+Phase 1: Foundation
+- Architecture design
+- Core service implementation
+- Basic web platform support
+
+Phase 2: Platform Integration
+- Mobile platform support
+- Desktop platform support
+- Cross-platform consistency
+
+Phase 3: Testing & Polish
+- Comprehensive testing
+- Error handling
+- User experience refinement
+```
+
+## 🚫 Anti-Patterns to Avoid
+
+- **"This should take X days"** - Red flag for time estimation
+- **"Just a few hours"** - Ignores complexity and testing
+- **"Similar to X"** - Without considering differences
+- **"Quick fix"** - Nothing is ever quick in software
+- **"No testing needed"** - Testing always takes effort
+
+## ✅ Best Practices
+
+### **When Planning:**
+1. **Break down everything** - no work is too small to plan
+2. **Consider all platforms** - web, mobile, desktop differences
+3. **Include testing strategy** - unit, integration, and user testing
+4. **Account for unknowns** - there are always surprises
+5. **Focus on dependencies** - what blocks what
+
+### **When Presenting Plans:**
+1. **Show the phases** - explain the logical progression
+2. **Highlight dependencies** - what could block progress
+3. **Define milestones** - clear success criteria
+4. **Identify risks** - what could go wrong
+5. **Suggest alternatives** - ways to reduce scope or complexity
+
+## 🔄 Continuous Improvement
+
+### **Track Progress**
+- Record planned vs. actual phases completed
+- Identify what took longer than expected
+- Learn from complexity misjudgments
+- Adjust planning process based on experience
+
+### **Learn from Experience**
+- **Underestimated complexity**: Increase complexity categories
+- **Missed dependencies**: Improve dependency mapping
+- **Platform surprises**: Better platform research upfront
+
+## 🎯 Integration with Harbor Pilot
+
+This rule works in conjunction with:
+- **Project Planning**: Focuses on phases and milestones
+- **Resource Allocation**: Based on complexity, not time
+- **Risk Management**: Identifies blockers and dependencies
+- **Stakeholder Communication**: Sets progress-based expectations
+
+## 📝 Version History
+
+### v2.0.0 (2025-08-21)
+- **Major Change**: Completely removed time estimation approach
+- **New Focus**: Phases, milestones, and complexity-based planning
+- **Eliminated**: All time multipliers, estimates, and calculations
+- **Added**: Dependency mapping and progress milestone framework
+
+### v1.0.0 (2025-08-21)
+- Initial creation based on user feedback about estimation accuracy
+- ~~Established realistic estimation multipliers and process~~
+- ~~Added comprehensive estimation checklist and examples~~
+- Integrated with Harbor Pilot planning and risk management
+
+---
+
+## 🚨 Remember
+
+**DO NOT MAKE TIME ESTIMATES. Use phases, milestones, and complexity instead. Focus on progress, not deadlines.**
+
+## 🚨 Remember
+
+**Your first estimate is wrong. Your second estimate is probably still wrong. Focus on progress, not deadlines.**

.cursor/rules/research_diagnostic.mdc

@@ -0,0 +1,174 @@
+---
+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

@@ -0,0 +1,225 @@
+
+# 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

@@ -0,0 +1,329 @@
+---
+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

@@ -1,316 +0,0 @@
----
-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
-  - F.I.R.S.T. (for Unit Tests)
-    F – Fast
-    I – Independent
-    R – Repeatable
-    S – Self-validating
-    T – Timely
-
-### 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

.cursor/rules/unit_testing_mocks.mdc

@@ -0,0 +1,714 @@
+```json
+{
+  "coaching_level": "standard",
+  "socratic_max_questions": 2,
+  "verbosity": "normal",
+  "timebox_minutes": null,
+  "format_enforcement": "strict"
+}
+```
+
+# Unit Testing & Mocks — Universal Development Guide
+
+**Author**: Matthew Raymer
+**Date**: 2025-08-21T09:40Z
+**Status**: 🎯 **ACTIVE** - Comprehensive testing standards
+
+## Overview
+
+This guide establishes **unified unit testing and mocking standards** for Vue 
+and React projects, ensuring consistent, maintainable test patterns using 
+Vitest, JSDOM, and component testing utilities. All tests follow F.I.R.S.T. 
+principles with comprehensive mock implementations.
+
+## Scope and Goals
+
+**Scope**: Applies to all unit tests, mock implementations, and testing 
+infrastructure in any project workspace.
+
+**Goal**: One consistent testing approach with comprehensive mock coverage, 
+100% test coverage for simple components, and maintainable test patterns.
+
+## Non‑Negotiables (DO THIS)
+
+- **MUST** use Vitest + JSDOM for unit testing; **DO NOT** use Jest or other 
+  frameworks
+- **MUST** implement comprehensive mock levels (Simple, Standard, Complex) for 
+  all components
+- **MUST** achieve 100% line coverage for simple components (<100 lines)
+- **MUST** follow F.I.R.S.T. principles: Fast, Independent, Repeatable, 
+  Self-validating, Timely
+- **MUST** use centralized test utilities from `src/test/utils/`
+
+## Testing Infrastructure
+
+### **Core Technologies**
+
+- **Vitest**: Fast unit testing framework with Vue/React support
+- **JSDOM**: Browser-like environment for Node.js testing
+- **@vue/test-utils**: Vue component testing utilities
+- **TypeScript**: Full type safety for tests and mocks
+
+### **Configuration Files**
+
+- `vitest.config.ts` - Vitest configuration with JSDOM environment
+- `src/test/setup.ts` - Global test configuration and mocks
+- `src/test/utils/` - Centralized testing utilities
+
+### **Global Mocks**
+
+```typescript
+// Required browser API mocks
+ResizeObserver, IntersectionObserver, localStorage, sessionStorage,
+matchMedia, console methods (reduced noise)
+```
+
+## Mock Implementation Standards
+
+### **Mock Architecture Levels**
+
+#### **1. Simple Mock (Basic Testing)**
+
+```typescript
+// Minimal interface compliance
+class ComponentSimpleMock {
+  // Essential props and methods only
+  // Basic computed properties
+  // No complex behavior
+}
+```
+
+#### **2. Standard Mock (Integration Testing)**
+
+```typescript
+// Full interface compliance
+class ComponentStandardMock {
+  // All props, methods, computed properties
+  // Realistic behavior simulation
+  // Helper methods for test scenarios
+}
+```
+
+#### **3. Complex Mock (Advanced Testing)**
+
+```typescript
+// Enhanced testing capabilities
+class ComponentComplexMock extends ComponentStandardMock {
+  // Mock event listeners
+  // Performance testing hooks
+  // Error scenario simulation
+  // Accessibility testing support
+}
+```
+
+### **Mock Component Structure**
+
+Each mock component provides:
+
+- Same interface as original component
+- Simplified behavior for testing
+- Helper methods for test scenarios
+- Computed properties for state validation
+
+### **Enhanced Mock Architecture Validation** ✅ **NEW**
+
+The three-tier mock architecture (Simple/Standard/Complex) has been successfully 
+validated through real-world implementation:
+
+#### **Tier 1: Simple Mock**
+
+```typescript
+class ComponentSimpleMock {
+  // Basic interface compliance
+  // Minimal implementation for simple tests
+  // Fast execution for high-volume testing
+}
+```
+
+#### **Tier 2: Standard Mock**
+
+```typescript
+class ComponentStandardMock {
+  // Full interface implementation
+  // Realistic behavior simulation
+  // Helper methods for common scenarios
+}
+```
+
+#### **Tier 3: Complex Mock**
+
+```typescript
+class ComponentComplexMock {
+  // Enhanced testing capabilities
+  // Validation and error simulation
+  // Advanced state management
+  // Performance testing support
+}
+```
+
+#### **Factory Function Pattern**
+
+```typescript
+// Specialized factory functions for common use cases
+export const createComponentMock = () =>
+  new ComponentStandardMock({ type: 'default' })
+
+export const createSpecializedMock = () =>
+  new ComponentComplexMock({
+    options: { filter: 'active', sort: 'name' }
+  })
+```
+
+### **Mock Usage Examples**
+
+```typescript
+export default class ComponentMock {
+  // Props simulation
+  props: ComponentProps
+
+  // Computed properties
+  get computedProp(): boolean {
+    return this.props.condition
+  }
+
+  // Mock methods
+  mockMethod(): void {
+    // Simulate behavior
+  }
+
+  // Helper methods
+  getCssClasses(): string[] {
+    return ['base-class', 'conditional-class']
+  }
+}
+```
+
+## Test Patterns
+
+### **Component Testing Template**
+
+```typescript
+import { mount } from '@vue/test-utils'
+import { createComponentWrapper } from '@/test/utils/componentTestUtils'
+
+describe('ComponentName', () => {
+  let wrapper: VueWrapper<any>
+
+  const mountComponent = (props = {}) => {
+    return mount(ComponentName, {
+      props: { ...defaultProps, ...props }
+    })
+  }
+
+  beforeEach(() => {
+    wrapper = mountComponent()
+  })
+
+  afterEach(() => {
+    wrapper?.unmount()
+  })
+
+  describe('Component Rendering', () => {
+    it('should render correctly', () => {
+      expect(wrapper.exists()).toBe(true)
+    })
+  })
+})
+```
+
+### **Mock Integration Testing**
+
+```typescript
+import ComponentMock from '@/test/__mocks__/Component.mock'
+
+it('should work with mock component', () => {
+  const mock = new ComponentMock()
+  expect(mock.shouldShow).toBe(true)
+})
+```
+
+### **Event Testing**
+
+```typescript
+it('should emit event when triggered', async () => {
+  await wrapper.find('button').trigger('click')
+  expect(wrapper.emitted('event-name')).toBeTruthy()
+})
+```
+
+### **Prop Validation**
+
+```typescript
+it('should accept all required props', () => {
+  wrapper = mountComponent()
+  expect(wrapper.vm.propName).toBeDefined()
+})
+```
+
+## Test Categories
+
+### **Required Coverage Areas**
+
+1. **Component Rendering** - Existence, structure, conditional rendering
+2. **Component Styling** - CSS classes, responsive design, framework 
+   integration
+3. **Component Props** - Required/optional prop handling, type validation
+4. **User Interactions** - Click events, form inputs, keyboard navigation
+5. **Component Methods** - Method existence, functionality, return values
+6. **Edge Cases** - Empty/null props, rapid interactions, state changes
+7. **Error Handling** - Invalid props, malformed data, graceful degradation
+8. **Accessibility** - Semantic HTML, ARIA attributes, keyboard navigation
+9. **Performance** - Render time, memory leaks, rapid re-renders
+10. **Integration** - Parent-child interaction, dependency injection
+
+### **Error Handling Testing**
+
+```typescript
+const invalidPropCombinations = [
+  null, undefined, 'invalid', 0, -1, {}, [],
+  () => {}, NaN, Infinity
+]
+
+invalidPropCombinations.forEach(invalidProp => {
+  it(`should handle invalid prop: ${invalidProp}`, () => {
+    wrapper = mountComponent({ prop: invalidProp })
+    expect(wrapper.exists()).toBe(true)
+    // Verify graceful handling
+  })
+})
+```
+
+## Centralized Test Utilities
+
+### **Component Testing Utilities**
+
+```typescript
+import {
+  createComponentWrapper,
+  createTestDataFactory,
+  testLifecycleEvents,
+  testComputedProperties,
+  testWatchers,
+  testPerformance,
+  testAccessibility,
+  testErrorHandling
+} from '@/test/utils/componentTestUtils'
+
+// Component wrapper factory
+const wrapperFactory = createComponentWrapper(
+  Component,
+  defaultProps,
+  globalOptions
+)
+
+// Test data factory
+const createTestProps = createTestDataFactory({
+  prop1: 'default',
+  prop2: true
+})
+```
+
+### **Test Data Factories**
+
+```typescript
+import {
+  createMockContact,
+  createMockProject,
+  createMockUser
+} from '@/test/factories/contactFactory'
+
+const testContact = createMockContact({
+  id: 'test-1',
+  name: 'Test User'
+})
+```
+
+## Coverage Standards
+
+### **Coverage Standards by Component Complexity**
+
+| Component Complexity | Line Coverage | Branch Coverage | Function Coverage |
+|---------------------|---------------|-----------------|-------------------|
+| **Simple (<100 lines)** | 100% | 100% | 100% |
+| **Medium (100-300 lines)** | 95% | 90% | 100% |
+| **Complex (300+ lines)** | 90% | 85% | 100% |
+
+### **Current Coverage Status**
+
+- **Simple Components**: Ready for implementation
+- **Medium Components**: Ready for expansion
+- **Complex Components**: Ready for expansion
+- **Overall Coverage**: Varies by project implementation
+
+### **Test Infrastructure Requirements**
+
+- **Test Framework**: Vitest + JSDOM recommended
+- **Component Testing**: Vue Test Utils integration
+- **Mock Architecture**: Three-tier system (Simple/Standard/Complex)
+- **Test Categories**: 10 comprehensive categories
+- **Coverage Goals**: 100% for simple components, 90%+ for complex
+
+## Testing Philosophy
+
+### **Defensive Programming Validation**
+
+- **Real-world edge case protection** against invalid API responses
+- **System stability assurance** preventing cascading failures
+- **Production readiness** ensuring graceful error handling
+
+### **Comprehensive Error Scenarios**
+
+- **Invalid input testing** with 10+ different invalid prop combinations
+- **Malformed data testing** with various corrupted data structures
+- **Extreme value testing** with boundary conditions and edge cases
+- **Concurrent error testing** with rapid state changes
+
+### **Benefits Beyond Coverage**
+
+1. **Defensive Programming Validation** - Components handle unexpected data 
+   gracefully
+2. **Real-World Resilience** - Tested against actual failure scenarios
+3. **Developer Confidence** - Safe to refactor and extend components
+4. **Production Stability** - Reduced support tickets and user complaints
+
+## Advanced Testing Patterns
+
+### **Performance Testing** ✅ **NEW**
+
+- Render time benchmarks
+- Memory leak detection
+- Rapid re-render efficiency
+- Component cleanup validation
+
+#### **Advanced Performance Testing Patterns**
+
+```typescript
+// Memory leak detection
+it('should not cause memory leaks during prop changes', async () => {
+  const initialMemory = (performance as any).memory?.usedJSHeapSize || 0
+
+  for (let i = 0; i < 100; i++) {
+    await wrapper.setProps({
+      queryParams: { iteration: i.toString() }
+    })
+  }
+
+  const finalMemory = (performance as any).memory?.usedJSHeapSize || 0
+  const memoryIncrease = finalMemory - initialMemory
+
+  // Memory increase should be reasonable (less than 10MB)
+  expect(memoryIncrease).toBeLessThan(10 * 1024 * 1024)
+})
+
+// Rapid re-render efficiency
+it('should handle rapid re-renders efficiently', async () => {
+  const start = performance.now()
+
+  for (let i = 0; i < 50; i++) {
+    await wrapper.setProps({
+      entityType: i % 2 === 0 ? 'type1' : 'type2',
+      queryParams: { index: i.toString() }
+    })
+  }
+
+  const end = performance.now()
+  expect(end - start).toBeLessThan(500) // 500ms threshold for 50 updates
+})
+```
+
+### **Snapshot Testing** ✅ **NEW**
+
+- DOM structure validation
+- CSS class regression detection
+- Accessibility attribute consistency
+- Visual structure verification
+
+#### **Snapshot Testing Implementation**
+
+```typescript
+describe('Snapshot Testing', () => {
+  it('should maintain consistent DOM structure', () => {
+    expect(wrapper.html()).toMatchSnapshot()
+  })
+
+  it('should maintain consistent structure with different props', () => {
+    wrapper = mountComponent({ type: 'alternative' })
+    expect(wrapper.html()).toMatchSnapshot()
+  })
+
+  it('should maintain consistent structure with query params', () => {
+    wrapper = mountComponent({
+      queryParams: { filter: 'active', sort: 'name' }
+    })
+    expect(wrapper.html()).toMatchSnapshot()
+  })
+})
+```
+
+### **Mock Integration Testing** ✅ **NEW**
+
+- Mock component validation
+- Factory function testing
+- Mock behavior verification
+- Integration with testing utilities
+
+#### **Mock Integration Testing Patterns**
+
+```typescript
+describe('Mock Integration Testing', () => {
+  it('should work with simple mock', () => {
+    const mock = new ComponentSimpleMock()
+    expect(mock.navigationRoute).toEqual({
+      name: 'default',
+      query: {}
+    })
+  })
+
+  it('should work with standard mock', () => {
+    const mock = new ComponentStandardMock({
+      type: 'special',
+      name: 'test'
+    })
+    expect(mock.getType()).toBe('special')
+    expect(mock.getName()).toBe('test')
+  })
+
+  it('should work with complex mock', () => {
+    const mock = new ComponentComplexMock({
+      type: 'advanced',
+      options: { filter: 'active' }
+    })
+
+    expect(mock.isValidState()).toBe(true)
+    expect(mock.getValidationErrors()).toEqual([])
+  })
+
+  it('should work with factory functions', () => {
+    const defaultMock = createComponentMock()
+    const specializedMock = createSpecializedMock()
+
+    expect(defaultMock.getType()).toBe('default')
+    expect(specializedMock.getOptions()).toHaveProperty('filter')
+  })
+})
+```
+
+## Project Implementation Tracking
+
+### **Setting Up Project-Specific Tracking**
+
+Each project should maintain its own tracking file to monitor testing progress 
+and coverage metrics. This keeps the universal MDC clean while providing a 
+template for project implementation.
+
+#### **Recommended Project Tracking Structure**
+
+```tree
+src/test/
+├── README.md                       # Testing documentation
+├── PROJECT_COVERAGE_TRACKING.md    # Project-specific progress tracking
+├── __mocks__/                      # Mock implementations
+├── utils/                          # Test utilities
+└── [test files]
+```
+
+#### **Project Tracking File Template**
+
+Create a `PROJECT_COVERAGE_TRACKING.md` file with:
+
+- **Current Coverage Status**: Component-by-component breakdown
+- **Implementation Progress**: Phase completion status
+- **Test Infrastructure Status**: Framework setup and metrics
+- **Next Steps**: Immediate priorities and long-term goals
+- **Lessons Learned**: Project-specific insights and best practices
+
+#### **Example Project Tracking Sections**
+
+```markdown
+# [Project Name] Testing Coverage Tracking
+
+## Current Coverage Status
+- Simple Components: X/Y at 100% coverage
+- Medium Components: X/Y ready for expansion
+- Complex Components: X/Y planned
+
+## Implementation Progress
+- Phase 1: Simple Components ✅ COMPLETE
+- Phase 2: Medium Components 🔄 IN PROGRESS
+- Phase 3: Complex Components 🔄 PLANNED
+
+## Test Infrastructure Status
+- Total Tests: X tests passing
+- Test Files: X files
+- Mock Files: X implementations
+- Overall Coverage: X% (focused on simple components)
+```
+
+### **Integration with Universal MDC**
+
+- **MDC provides**: Testing patterns, mock architecture, best practices
+- **Project tracking provides**: Implementation status, coverage metrics, 
+  progress
+- **Separation ensures**: MDC remains reusable, project data stays local
+- **Template approach**: Other projects can copy and adapt the structure
+
+### **Benefits of This Approach**
+
+1. **Universal Reusability**: MDC works for any project
+2. **Project Visibility**: Clear tracking of implementation progress
+3. **Template Reuse**: Easy to set up tracking in new projects
+4. **Clean Separation**: No project data polluting universal guidance
+5. **Scalability**: Multiple projects can use the same MDC
+
+## Best Practices
+
+### **Test Organization**
+
+1. **Group related tests** using `describe` blocks
+2. **Use descriptive test names** that explain the scenario
+3. **Keep tests focused** on one specific behavior
+4. **Use helper functions** for common setup
+
+### **Mock Design**
+
+1. **Maintain interface compatibility** with original components
+2. **Provide helper methods** for common test scenarios
+3. **Include computed properties** for state validation
+4. **Document mock behavior** clearly
+
+### **Coverage Goals**
+
+1. **100% line coverage** for simple components
+2. **100% branch coverage** for conditional logic
+3. **100% function coverage** for all methods
+4. **Edge case coverage** for error scenarios
+
+### **Lessons Learned from Implementation** ✅ **NEW**
+
+#### **1. Performance Testing Best Practices**
+
+- **Memory leak detection**: Use `performance.memory.usedJSHeapSize` for 
+  memory profiling
+- **Render time benchmarking**: Set realistic thresholds (100ms for single 
+  render, 500ms for 50 updates)
+- **Rapid re-render testing**: Test with 50+ prop changes to ensure 
+  stability
+
+#### **2. Snapshot Testing Implementation**
+
+- **DOM structure validation**: Use `toMatchSnapshot()` for consistent 
+  structure verification
+- **Prop variation testing**: Test snapshots with different prop combinations
+- **Regression prevention**: Snapshots catch unexpected DOM changes
+
+#### **3. Mock Integration Validation**
+
+- **Mock self-testing**: Test that mocks work correctly with testing 
+  utilities
+- **Factory function testing**: Validate specialized factory functions
+- **Mock behavior verification**: Ensure mocks simulate real component 
+  behavior
+
+#### **4. Edge Case Coverage**
+
+- **Null/undefined handling**: Test with `null as any` and `undefined` 
+  props
+- **Extreme values**: Test with very long strings and large numbers
+- **Rapid changes**: Test with rapid prop changes to ensure stability
+
+#### **5. Accessibility Testing**
+
+- **Semantic structure**: Verify proper HTML elements and hierarchy
+- **Component attributes**: Check component-specific attributes
+- **Text content**: Validate text content and trimming
+
+## Future Improvements
+
+### **Implemented Enhancements**
+
+1. ✅ **Error handling** - Component error states and exception handling
+2. ✅ **Performance testing** - Render time benchmarks and memory leak 
+   detection
+3. ✅ **Integration testing** - Parent-child component interaction and 
+   dependency injection
+4. ✅ **Snapshot testing** - DOM structure validation and CSS class 
+   regression detection
+5. ✅ **Accessibility compliance** - ARIA attributes and semantic structure 
+   validation
+
+### **Future Enhancements**
+
+1. **Visual regression testing** - Automated UI consistency checks
+2. **Cross-browser compatibility** testing
+3. **Service layer integration** testing
+4. **End-to-end component** testing
+5. **Advanced performance** profiling
+
+### **Coverage Expansion**
+
+1. **Medium complexity components** (100-300 lines)
+2. **Complex components** (300+ lines)
+3. **Service layer testing**
+4. **Utility function testing**
+5. **API integration testing**
+
+## Troubleshooting
+
+### **Common Issues**
+
+1. **Import errors**: Check path aliases in `vitest.config.ts`
+2. **Mock not found**: Verify mock file exists and exports correctly
+3. **Test failures**: Check for timing issues with async operations
+4. **Coverage gaps**: Add tests for uncovered code paths
+
+### **Debug Tips**
+
+1. **Use `console.log`** in tests for debugging
+2. **Check test output** for detailed error messages
+3. **Verify component props** are being passed correctly
+4. **Test one assertion at a time** to isolate issues
+
+---
+
+**Status**: Active testing standards
+**Priority**: High
+**Estimated Effort**: Ongoing reference
+**Dependencies**: Vitest, JSDOM, Vue Test Utils
+**Stakeholders**: Development team, QA team
+
+## Competence Hooks
+
+- *Why this works*: Three-tier mock architecture provides flexibility, 
+  comprehensive test categories ensure thorough coverage, performance testing 
+  catches real-world issues early
+- *Common pitfalls*: Not testing mocks themselves, missing edge case 
+  coverage, ignoring performance implications
+- *Next skill unlock*: Implement medium complexity component testing with 
+  established patterns
+- *Teach-back*: Explain how the three-tier mock architecture supports 
+  different testing needs
+
+## Collaboration Hooks
+
+- **Reviewers**: Testing team, component developers, architecture team
+- **Sign-off checklist**: All simple components at 100% coverage, mock 
+  utilities documented, test patterns established, coverage expansion plan 
+  approved
+
+## Assumptions & Limits
+
+- Assumes Vue/React component architecture
+- Requires Vitest + JSDOM testing environment
+- Mock complexity scales with component complexity
+- Performance testing requires browser-like environment
+
+## References
+
+- [Vitest Documentation](https://vitest.dev/)
+- [Vue Test Utils](https://test-utils.vuejs.org/)
+- [JSDOM](https://github.com/jsdom/jsdom)
+- [Testing Best Practices](https://testing-library.com/docs/guiding-principles)
+
+- **Sign-off checklist**: All simple components at 100% coverage, mock
+  utilities documented, test patterns established, coverage expansion plan
+  approved

.cursor/rules/version_control.mdc

@@ -1,122 +0,0 @@
----
-alwaysApply: true
----
-# Directive: Peaceful Co-Existence with Developers
-
-## 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.
-
----
-
-# 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

.cursor/rules/workflow/version_control.mdc

@@ -0,0 +1,335 @@
+---
+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

@@ -140,7 +140,7 @@ docker-compose*
 .dockerignore
 
 # CI/CD files
-.github
+
 .gitlab-ci.yml
 .travis.yml
 .circleci

.env.test

@@ -7,7 +7,7 @@ VITE_LOG_LEVEL=info
 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": "warn",
+    "@typescript-eslint/no-explicit-any": "error",
     "@typescript-eslint/explicit-function-return-type": "off",
     "@typescript-eslint/no-unnecessary-type-constraint": "off",
     "@typescript-eslint/no-unused-vars": ["error", { "argsIgnorePattern": "^_" }]

.github/workflows/playwright.yml

@@ -1,27 +0,0 @@
-name: Playwright Tests
-on:
-  push:
-    branches: [ main, master ]
-  pull_request:
-    branches: [ main, master ]
-jobs:
-  test:
-    timeout-minutes: 60
-    runs-on: ubuntu-latest
-    steps:
-    - uses: actions/checkout@v4
-    - uses: actions/setup-node@v4
-      with:
-        node-version: lts/*
-    - name: Install dependencies
-      run: npm ci
-    - name: Install Playwright Browsers
-      run: npx playwright install --with-deps
-    - name: Run Playwright tests
-      run: npx playwright test
-    - uses: actions/upload-artifact@v4
-      if: always()
-      with:
-        name: playwright-report
-        path: playwright-report/
-        retention-days: 30

.gitignore

@@ -56,6 +56,10 @@ icons
 
 *.log
 
+# Build outputs
+dist/
+build/
+
 # Generated Android assets and resources (should be generated during build)
 android/app/src/main/assets/public/
 
@@ -64,6 +68,14 @@ 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
@@ -128,4 +140,6 @@ electron/out/
 # Gradle cache files
 android/.gradle/file-system.probe
 android/.gradle/caches/
-coverage
+
+coverage/
+.husky-enabled

.husky/README.md

@@ -0,0 +1,37 @@
+# Husky Git Hooks - Optional Activation
+
+## How to Enable Husky Locally
+
+### Option 1: Environment Variable (Session Only)
+```bash
+export HUSKY_ENABLED=1
+```
+
+### Option 2: Local File (Persistent)
+```bash
+touch .husky-enabled
+```
+
+### Option 3: Global Configuration
+```bash
+git config --global husky.enabled true
+```
+
+## Available Hooks
+
+- **pre-commit**: Runs `npm run lint-fix` before commits
+- **commit-msg**: Validates commit message format
+
+## Disable Hooks
+
+```bash
+unset HUSKY_ENABLED
+rm .husky-enabled
+```
+
+## Why This Approach?
+
+- Hooks are committed to git for consistency
+- Hooks don't run unless explicitly enabled
+- Each developer can choose to use them
+- No automatic activation on other systems

.husky/_/husky.sh

@@ -0,0 +1,48 @@
+#!/usr/bin/env sh
+#
+# Husky Helper Script - Conditional Activation
+# This file is sourced by all Husky hooks
+#
+if [ -z "$husky_skip_init" ]; then
+  # Check if Husky is enabled for this user
+  if [ "$HUSKY_ENABLED" != "1" ] && [ ! -f .husky-enabled ]; then
+    echo "Husky is not enabled. To enable:"
+    echo "  export HUSKY_ENABLED=1"
+    echo "  or create .husky-enabled file"
+    exit 0
+  fi
+
+  debug () {
+    if [ "$HUSKY_DEBUG" = "1" ]; then
+      echo "husky (debug) - $1"
+    fi
+  }
+
+  readonly hook_name="$(basename -- "$0")"
+  debug "starting $hook_name..."
+
+  if [ "$HUSKY" = "0" ]; then
+    debug "HUSKY env variable is set to 0, skipping hook"
+    exit 0
+  fi
+
+  if [ -f ~/.huskyrc ]; then
+    debug "sourcing ~/.huskyrc"
+    . ~/.huskyrc
+  fi
+
+  readonly husky_skip_init=1
+  export husky_skip_init
+  sh -e "$0" "$@"
+  exitCode="$?"
+
+  if [ $exitCode != 0 ]; then
+    echo "husky - $hook_name hook exited with code $exitCode (error)"
+  fi
+
+  if [ $exitCode = 127 ]; then
+    echo "husky - command not found in PATH=$PATH"
+  fi
+
+  exit $exitCode
+fi

.husky/commit-msg

@@ -0,0 +1,11 @@
+#!/usr/bin/env sh
+. "$(dirname -- "$0")/_/husky.sh"
+
+# Only run if Husky is enabled
+if [ "$HUSKY_ENABLED" = "1" ] || [ -f .husky-enabled ]; then
+  echo "Running commit-msg hooks..."
+  npx commitlint --edit "$1"
+else
+  echo "Husky commit-msg hook skipped (not enabled)"
+  exit 0
+fi

.husky/pre-commit

@@ -0,0 +1,11 @@
+#!/usr/bin/env sh
+. "$(dirname -- "$0")/_/husky.sh"
+
+# Only run if Husky is enabled
+if [ "$HUSKY_ENABLED" = "1" ] || [ -f .husky-enabled ]; then
+  echo "Running pre-commit hooks..."
+  npm run lint-fix
+else
+  echo "Husky pre-commit hook skipped (not enabled)"
+  exit 0
+fi

.husky/pre-push

@@ -0,0 +1,27 @@
+#!/usr/bin/env bash
+#
+# Husky Pre-push Hook  
+# Runs Build Architecture Guard to check commits being pushed
+#
+. "$(dirname -- "$0")/_/husky.sh"
+
+echo "🔍 Running Build Architecture Guard (pre-push)..."
+
+# Get the remote branch we're pushing to
+REMOTE_BRANCH="origin/$(git rev-parse --abbrev-ref HEAD)"
+
+# Check if remote branch exists
+if git show-ref --verify --quiet "refs/remotes/$REMOTE_BRANCH"; then
+    RANGE="$REMOTE_BRANCH...HEAD"
+else
+    # If remote branch doesn't exist, check last commit
+    RANGE="HEAD~1..HEAD"
+fi
+
+bash ./scripts/build-arch-guard.sh --range "$RANGE" || {
+    echo
+    echo "💡 To bypass this check for emergency pushes, use:"
+    echo "   git push --no-verify"
+    echo
+    exit 1
+}

.node-version

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

.nvmrc

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

CHANGELOG.md

@@ -5,72 +5,89 @@ 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.3] - 2025.07.12
-### Changed
-- Photo is pinned to profile mode
+## [1.0.7] - 2025.08.18
+
 ### Fixed
-- Deep link URLs (and other prod settings)
-- Error in BVC begin view
+
+- 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]
+
 ### Fixed
+
 - Cameras everywhere
+
 ### Changed
+
 - IndexedDB -> SQLite
 
-
 ## [0.4.5] - 2025.02.23
-### Added
-- Total amounts of gives on project page
-### Changed in DB or environment
-- Requires Endorser.ch version 4.2.6+
 
+### Added
+
+- Total amounts of gives on project page
+
+### Changed in DB or environment
+
+- Requires Endorser.ch version 4.2.6+
 
 ## [0.4.4] - 2025.02.17
 

README-BUILD-GUARD.md

@@ -0,0 +1,290 @@
+# Build Architecture Guard - Husky Implementation
+
+## Overview
+
+The Build Architecture Guard protects your build system by enforcing
+documentation requirements through **Git hooks**. When you modify
+build-critical files, the system automatically blocks commits/pushes
+until you update `BUILDING.md`.
+
+## 🎯 **Why Husky-Only?**
+
+**Advantages:**
+
+- ✅ **Immediate feedback** - Hooks run before commit/push
+- ✅ **Works everywhere** - No server-side CI/CD required
+- ✅ **Simple setup** - One tool, one configuration
+- ✅ **Fast execution** - No network delays or server queues
+- ✅ **Offline support** - Works without internet connection
+
+**Trade-offs:**
+
+- ⚠️ **Can be bypassed** - `git commit --no-verify` or `git push --no-verify`
+- ⚠️ **Developer discipline** - Relies on team following the rules
+
+## 🏗️ **Architecture**
+
+```bash
+Developer Workflow:
+1. Modify build files (scripts/, vite.config.*, etc.)
+2. Try to commit → Husky pre-commit hook runs
+3. Guard script checks if BUILDING.md was updated
+4. ✅ Commit succeeds if docs updated
+5. ❌ Commit blocked if docs missing
+```
+
+## 🚀 **Quick Start**
+
+### 1. Install Dependencies
+
+```bash
+npm install
+npm run prepare  # Sets up Husky hooks
+```
+
+### 2. Test the System
+
+```bash
+# Modify a build file without updating BUILDING.md
+echo "# test" >> scripts/test.sh
+
+# Try to commit (should be blocked)
+git add scripts/test.sh
+git commit -m "test: add build script"
+# ❌ Hook blocks commit with helpful message
+```
+
+### 3. Fix and Retry
+
+```bash
+# Update BUILDING.md with your changes
+echo "## New Build Script" >> BUILDING.md
+echo "Added test.sh for testing purposes" >> BUILDING.md
+
+# Now commit should succeed
+git add BUILDING.md
+git commit -m "feat: add test build script with docs"
+# ✅ Commit succeeds
+```
+
+## 🔧 **How It Works**
+
+### Pre-commit Hook (`.husky/pre-commit`)
+
+- **When**: Every `git commit`
+- **What**: Runs `./scripts/build-arch-guard.sh --staged`
+- **Result**: Blocks commit if build files changed without BUILDING.md update
+
+### Pre-push Hook (`.husky/pre-push`)
+
+- **When**: Every `git push`
+- **What**: Runs `./scripts/build-arch-guard.sh --range`
+- **Result**: Blocks push if commits contain undocumented build changes
+
+### Guard Script (`scripts/build-arch-guard.sh`)
+
+- **Detects**: Changes to build-sensitive file patterns
+- **Validates**: BUILDING.md was updated alongside changes
+- **Reports**: Clear error messages with guidance
+
+## 📁 **Protected File Patterns**
+
+The guard script monitors these paths for changes:
+
+```text
+Build Configuration:
+├── vite.config.*          # Vite configuration
+├── capacitor.config.ts    # Capacitor configuration
+├── package.json           # Package configuration
+├── package-lock.json      # Lock files
+├── yarn.lock
+└── pnpm-lock.yaml
+
+Build Scripts:
+├── scripts/**             # All build and automation scripts
+├── electron/**            # Electron build files
+├── android/**             # Android build configuration
+├── ios/**                 # iOS build configuration
+├── sw_scripts/**          # Service worker scripts
+└── sw_combine.js          # Service worker combination
+
+Deployment:
+├── Dockerfile             # Docker configuration
+└── docker/**              # Docker services
+```
+
+## 🎭 **Usage Scenarios**
+
+### Scenario 1: Adding a New Build Script
+
+```bash
+# ❌ This will be blocked
+echo '#!/bin/bash' > scripts/new-build.sh
+git add scripts/new-build.sh
+git commit -m "feat: add new build script"
+# Hook blocks: "Build-sensitive files changed but BUILDING.md not updated"
+
+# ✅ This will succeed
+echo '#!/bin/bash' > scripts/new-build.sh
+echo '## New Build Script' >> BUILDING.md
+echo 'Added new-build.sh for feature X' >> BUILDING.md
+git add scripts/new-build.sh BUILDING.md
+git commit -m "feat: add new build script with docs"
+# ✅ Commit succeeds
+```
+
+### Scenario 2: Updating Vite Configuration
+
+```bash
+# ❌ This will be blocked
+echo 'export default { newOption: true }' >> vite.config.ts
+git add vite.config.ts
+git commit -m "config: add new vite option"
+# Hook blocks: "Build-sensitive files changed but BUILDING.md not updated"
+
+# ✅ This will succeed
+echo 'export default { newOption: true }' >> vite.config.ts
+echo '### New Vite Option' >> BUILDING.md
+echo 'Added newOption for improved performance' >> BUILDING.md
+git add vite.config.ts BUILDING.md
+git commit -m "config: add new vite option with docs"
+# ✅ Commit succeeds
+```
+
+## 🚨 **Emergency Bypass**
+
+**⚠️ Use sparingly and only for emergencies:**
+
+```bash
+# Skip pre-commit hook
+git commit -m "emergency: critical fix" --no-verify
+
+# Skip pre-push hook  
+git push --no-verify
+
+# Remember to update BUILDING.md later!
+```
+
+## 🔍 **Troubleshooting**
+
+### Hooks Not Running
+
+```bash
+# Reinstall hooks
+npm run prepare
+
+# Check hook files exist and are executable
+ls -la .husky/
+chmod +x .husky/*
+
+# Verify Git hooks path
+git config core.hooksPath
+# Should show: .husky
+```
+
+### Guard Script Issues
+
+```bash
+# Test guard script manually
+./scripts/build-arch-guard.sh --help
+
+# Check script permissions
+chmod +x scripts/build-arch-guard.sh
+
+# Test with specific files
+./scripts/build-arch-guard.sh --staged
+```
+
+### False Positives
+
+```bash
+# If guard blocks legitimate changes, check:
+# 1. Are you modifying a protected file pattern?
+# 2. Did you update BUILDING.md?
+# 3. Is BUILDING.md staged for commit?
+
+# View what the guard sees
+git diff --name-only --cached
+```
+
+## 📋 **Best Practices**
+
+### For Developers
+
+1. **Update BUILDING.md first** - Document changes before implementing
+2. **Test locally** - Run `./scripts/build-arch-guard.sh --staged` before committing
+3. **Use descriptive commits** - Include context about build changes
+4. **Don't bypass lightly** - Only use `--no-verify` for true emergencies
+
+### For Teams
+
+1. **Document the system** - Ensure everyone understands the guard
+2. **Review BUILDING.md updates** - Verify documentation quality
+3. **Monitor bypass usage** - Track when hooks are skipped
+4. **Regular audits** - Check that BUILDING.md stays current
+
+### For Maintainers
+
+1. **Update protected patterns** - Modify `scripts/build-arch-guard.sh` as needed
+2. **Monitor effectiveness** - Track how often the guard catches issues
+3. **Team training** - Help developers understand the system
+4. **Continuous improvement** - Refine patterns and error messages
+
+## 🔄 **Customization**
+
+### Adding New Protected Paths
+
+Edit `scripts/build-arch-guard.sh`:
+
+```bash
+SENSITIVE=(
+  # ... existing patterns ...
+  "new-pattern/**"        # Add your new pattern
+  "*.config.js"           # Add file extensions
+)
+```
+
+### Modifying Error Messages
+
+Edit the guard script to customize:
+
+- Error message content
+- File pattern matching
+- Documentation requirements
+- Bypass instructions
+
+### Adding New Validation Rules
+
+Extend the guard script to check for:
+
+- Specific file content patterns
+- Required documentation sections
+- Commit message formats
+- Branch naming conventions
+
+## 📚 **Integration with PR Template**
+
+The `pull_request_template.md` works with this system by:
+
+- **Guiding developers** through required documentation
+- **Ensuring consistency** across all build changes
+- **Providing checklist** for comprehensive updates
+- **Supporting L1/L2/L3** change classification
+
+## 🎯 **Success Metrics**
+
+Track the effectiveness of your Build Architecture Guard:
+
+- **Hook execution rate** - How often hooks run successfully
+- **Bypass frequency** - How often `--no-verify` is used
+- **Documentation quality** - BUILDING.md stays current
+- **Build failures** - Fewer issues from undocumented changes
+- **Team adoption** - Developers follow the process
+
+---
+
+**Status**: Active protection system
+**Architecture**: Client-side Git hooks only
+**Dependencies**: Husky, Git, Bash
+**Maintainer**: Development team
+**Related**: `pull_request_template.md`, `scripts/build-arch-guard.sh`

README-PR-TEMPLATE.md

@@ -0,0 +1,82 @@
+# Pull Request Template
+
+## Location
+
+The Build Architecture Guard PR template is located at:
+
+- **`pull_request_template.md`** (root directory)
+
+## Usage
+
+When creating a pull request in Gitea, this template will automatically populate the PR description with the required checklist.
+
+## Template Features
+
+### Change Level Classification
+
+- **L1**: Minor changes, documentation updates
+- **L2**: Moderate changes, new features, environment changes
+- **L3**: Major changes, architecture changes, new platforms
+
+### Required Fields for All Levels
+
+- Change level selection
+- Scope and impact description
+- Commands executed and their output
+- Documentation updates (BUILDING.md)
+- Rollback verification steps
+
+### Additional Requirements for L3
+
+- **ADR link**: Must provide URL to Architectural Decision Record
+- **Artifacts with SHA256**: Must list artifacts with cryptographic hashes
+
+## Integration
+
+This template works with:
+
+- **Gitea Actions**: `.gitea/workflows/build-guard.yml`
+- **Client-side hooks**: `.husky/` pre-commit and pre-push hooks
+- **Guard script**: `scripts/build-arch-guard.sh`
+
+## Example Usage
+
+```markdown
+### Change Level
+- [x] Level: **L2**
+
+**Why:** Adding new build script for Docker deployment
+
+### Scope & Impact
+- [x] Files & platforms touched: scripts/build-docker.sh,
+  BUILDING.md
+- [x] Risk triggers: Docker build process changes
+- [x] Mitigations/validation done: Tested on local Docker environment
+
+### Commands Run
+- [x] Web: `npm run build:web:docker` ✅
+- [x] Docker: `docker build -t test-image .` ✅
+
+### Artifacts
+- [x] Names + **sha256** of artifacts/installers:
+
+Artifacts:
+```text
+test-image.tar  a1b2c3d4e5f6...
+```
+
+### Docs
+- [x] **BUILDING.md** updated (sections): Docker deployment
+- [x] Troubleshooting updated: Added Docker troubleshooting section
+
+### Rollback
+- [x] Verified steps to restore previous behavior:
+  1. `git revert HEAD`
+  2. `docker rmi test-image`
+  3. Restore previous BUILDING.md
+```
+
+---
+
+**Note**: This template is enforced by the Build Architecture Guard
+system. Complete all required fields to ensure your PR can be merged.

README.md

@@ -1,204 +1,118 @@
-# TimeSafari.app - Crowd-Funder for Time - PWA
+# Time Safari Application
 
-[Time Safari](https://timesafari.org/) allows people to ease into collaboration: start with expressions of gratitude
-and expand to crowd-fund with time & money, then record and see the impact of contributions.
+**Author**: Matthew Raymer
+**Version**: 1.0.8-beta
+**Description**: Time Safari Application
 
-## Roadmap
+## 🛡️ Build Architecture Guard
 
-See [ClickUp](https://sharing.clickup.com/9014278710/l/h/8cmnyhp-174/10573fec74e2ba0) for current priorities.
+This project uses **Husky Git hooks** to protect the build system
+architecture. When you modify build-critical files, the system
+automatically blocks commits until you update `BUILDING.md`.
 
-## Setup & Building
+### Quick Setup
 
-Quick start:
+```bash
+npm run guard:setup  # Install and activate the guard
+```
 
-* For setup, we recommend [pkgx](https://pkgx.dev), which installs what you need (either automatically or with the `dev` command). Core dependencies are typescript & npm; when building for other platforms, you'll need other things such as those in the pkgx.yaml & BUILDING.md files.
+### How It Works
+
+- **Pre-commit**: Blocks commits if build files changed without
+  BUILDING.md updates
+- **Pre-push**: Blocks pushes if commits contain undocumented build
+  changes
+- **Protected paths**: `scripts/`, `vite.config.*`, `electron/`,
+  `android/`, `ios/`, etc.
+
+### Usage
+
+```bash
+# Test the guard manually
+npm run guard:test
+
+# Emergency bypass (use sparingly)
+git commit --no-verify
+git push --no-verify
+```
+
+**📚 Full documentation**: See `README-BUILD-GUARD.md`
+
+## 🚀 Quick Start
+
+### Prerequisites
+
+- Node.js 18+
+- npm, yarn, or pnpm
+- Git
+
+### Installation
 
 ```bash
 npm install
-npm run build:web:serve -- --test
+npm run guard:setup  # Sets up Build Architecture Guard
 ```
 
-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 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
+### Development
 
 ```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
+npm run build:web:dev    # Build web version
+npm run build:ios:test   # Build iOS test version
+npm run build:android:test # Build Android test version
+npm run build:electron:dev # Build Electron dev version
 ```
 
-### Available Levels
+### Testing
 
-- **`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
+npm run test:web         # Run web tests
+npm run test:mobile      # Run mobile tests
+npm run test:all         # Run all tests
 ```
 
-### What It Does
+## 📁 Project Structure
 
-#### **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
+```text
+timesafari/
+├── 📁 src/              # Source code
+├── 📁 scripts/          # Build and automation scripts
+├── 📁 electron/         # Electron configuration
+├── 📁 android/          # Android configuration  
+├── 📁 ios/              # iOS configuration
+├── 📁 .husky/           # Git hooks (Build Architecture Guard)
+├── 📄 BUILDING.md       # Build system documentation
+├── 📄 pull_request_template.md # PR template
+└── 📄 README-BUILD-GUARD.md # Guard system documentation
 ```
 
-#### **Web Browser (Custom Data Directory)**
-```bash
-# Create isolated browser profile
-mkdir ~/timesafari-dev-data
-```
+## 🔧 Build System
 
-## Domain Configuration
+This project supports multiple platforms:
 
-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.
+- **Web**: Vite-based build with service worker support
+- **Mobile**: Capacitor-based iOS and Android builds
+- **Desktop**: Electron-based cross-platform desktop app
+- **Docker**: Containerized deployment options
 
-### 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
+## 📚 Documentation
 
-### Quick Reference
+- **`BUILDING.md`** - Complete build system guide
+- **`README-BUILD-GUARD.md`** - Build Architecture Guard documentation
+- **`pull_request_template.md`** - PR template for build changes
 
-```typescript
-// For sharing functionality (environment-specific)
-import { APP_SERVER } from "@/constants/app";
-const shareLink = `${APP_SERVER}/deep-link/claim/123`;
+## 🤝 Contributing
 
-// For internal operations (environment-specific)
-import { APP_SERVER } from "@/constants/app";
-const apiUrl = `${APP_SERVER}/api/claim/123`;
-```
+1. **Follow the Build Architecture Guard** - Update BUILDING.md when modifying build files
+2. **Use the PR template** - Complete the checklist for build-related changes
+3. **Test your changes** - Ensure builds work on affected platforms
+4. **Document updates** - Keep BUILDING.md current and accurate
 
-### Documentation
+## 📄 License
 
-- [Constants and Configuration](src/constants/app.ts) - Core constants
+[Add your license information here]
 
-## Tests
+---
 
-See [TESTING.md](test-playwright/TESTING.md) for detailed test instructions.
-
-## Icons
-
-Application icons are in the `assets` directory, processed by the `capacitor-assets` command.
-
-To add a Font Awesome icon, add to fontawesome.ts and reference with `font-awesome` element and `icon` attribute with the hyphenated name.
-
-## Other
-
-### Reference Material
-
-* Notifications can be type of `toast` (self-dismiss), `info`, `success`, `warning`, and `danger`.
-  They are done via [notiwind](https://www.npmjs.com/package/notiwind) and set up in App.vue.
-
-* [Customize Vue configuration](https://cli.vuejs.org/config/).
-
-* If you are deploying in a subdirectory, add it to `publicPath` in vue.config.js, eg: `publicPath: "/app/time-tracker/",`
-
-### Code Organization
-
-The project uses a centralized approach to type definitions and interfaces:
-
-* `src/interfaces/` - Contains all TypeScript interfaces and type definitions
-  * `deepLinks.ts` - Deep linking type system and Zod validation schemas
-  * `give.ts` - Give-related interfaces and type definitions
-  * `claims.ts` - Claim-related interfaces and verifiable credentials
-  * `common.ts` - Shared interfaces and utility types
-  * Other domain-specific interface files
-
-Key principles:
-- All interfaces and types are defined in the interfaces folder
-- Zod schemas are used for runtime validation and type generation
-- Domain-specific interfaces are separated into their own files
-- 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!
-
-* [WebStorm by JetBrains](https://www.jetbrains.com/webstorm/) for the free open-source license
-* [Máximo Fernández](https://medium.com/@maxfarenas) for the 3D [code](https://github.com/maxfer03/vue-three-ns) and [explanatory post](https://medium.com/nicasource/building-an-interactive-web-portfolio-with-vue-three-js-part-three-implementing-three-js-452cb375ef80)
-* [Many tools & libraries](https://gitea.anomalistdesign.com/trent_larson/crowd-funder-for-time-pwa/src/branch/master/package.json#L10) such as Nodejs.org, IntelliJ Idea, Veramo.io, Vuejs.org, threejs.org
-* [Bush 3D model](https://sketchfab.com/3d-models/lupine-plant-bf30f1110c174d4baedda0ed63778439)
-* [Forest floor image](https://www.goodfreephotos.com/albums/textures/leafy-autumn-forest-floor.jpg)
-* Time Safari logo assisted by [DALL-E in ChatGPT](https://chat.openai.com/g/g-2fkFE8rbu-dall-e)
-* [DiceBear](https://www.dicebear.com/licenses/) and [Avataaars](https://www.dicebear.com/styles/avataaars/#details) for human-looking identicons
-* Some gratitude prompts thanks to [Develop Good Habits](https://www.developgoodhabits.com/gratitude-journal-prompts/)
+**Note**: The Build Architecture Guard is active and will block
+commits/pushes that modify build files without proper documentation
+updates. See `README-BUILD-GUARD.md` for complete details.

TASK_storage.md

@@ -1,7 +1,6 @@
 
 # What to do about storage for native apps?
 
-
 ## Problem
 
 We can't trust iOS IndexedDB to persist. I want to start delivering an app to people now, in preparation for presentations mid-June: Rotary on June 12 and Porcfest on June 17.
@@ -14,7 +13,6 @@ We can't trust iOS IndexedDB to persist. I want to start delivering an app to pe
 
 Also, with sensitive data, the accounts info should be encrypted.
 
-
 # Options
 
 * There is a community [SQLite plugin for Capacitor](https://github.com/capacitor-community/sqlite) with encryption by [SQLCipher](https://github.com/sqlcipher/sqlcipher).
@@ -29,16 +27,12 @@ Also, with sensitive data, the accounts info should be encrypted.
 
 * Not an option yet: Dexie may support SQLite in [a future version](https://dexie.org/roadmap/dexie5.0).
 
-
-
 # Current Plan
 
 * Implement SQLite for Capacitor & web, with encryption. That will allow us to test quickly and keep the same interface for native & web, but we don't deal with migrations for current web users.
 
 * After that is delivered, write a migration for current web users from IndexedDB to SQLite.
 
-
-
 # Current method calls
 
 ... which is not 100% complete because the AI that generated thus claimed no usage of 'temp' DB.
@@ -80,5 +74,3 @@ Logs operations:
 db.logs.get(todayKey) - Gets logs for a specific day
 db.logs.update(todayKey, { message: fullMessage }) - Updates logs
 db.logs.clear() - Clears all logs
-
-

TODO.md

@@ -0,0 +1,184 @@
+# Test Improvements TODO
+
+## ImageViewer Mock Units - Completed ✅
+- [x] Create comprehensive mock units for ImageViewer component
+- [x] Implement 4 mock levels (Simple, Standard, Complex, Integration)
+- [x] Fix template structure issues (Teleport/Transition complexity)
+- [x] Resolve event simulation problems (SupportedEventInterface errors)
+- [x] Fix platform detection logic (mobile vs desktop)
+- [x] Implement analytics tracking in integration mock
+- [x] Achieve 38/39 tests passing (97% success rate)
+
+## Immediate Test Improvements Needed 🔧
+
+### 1. Fix Remaining ImageViewer Test
+- [ ] **Fix mobile share button test** - Vue reactivity issue with computed properties
+  - [ ] Investigate Vue 3 reactivity system for computed properties
+  - [ ] Try different approaches: `nextTick()`, `flushPromises()`, or reactive refs
+  - [ ] Consider using `shallowRef()` for userAgent to force reactivity
+
+### 2. Event Simulation Improvements
+- [ ] **Create global event simulation utilities**
+  - [ ] Build `triggerEvent()` helper that works with Vue Test Utils
+  - [ ] Handle `SupportedEventInterface` errors consistently
+  - [ ] Create fallback methods for problematic event types
+- [ ] **Improve test environment setup**
+  - [ ] Configure proper DOM environment for event simulation
+  - [ ] Mock browser APIs more comprehensively
+  - [ ] Add global test utilities for common patterns
+
+### 3. Mock Architecture Enhancements
+- [ ] **Create reusable mock patterns**
+  - [ ] Extract common mock utilities (`createMockUserAgent`, etc.)
+  - [ ] Build mock factory patterns for other components
+  - [ ] Create mock validation helpers
+- [ ] **Improve mock documentation**
+  - [ ] Add JSDoc comments to all mock functions
+  - [ ] Create usage examples for each mock level
+  - [ ] Document mock limitations and workarounds
+
+## Component-Specific Test Improvements 🧪
+
+### 4. Expand Mock Units to Other Components
+- [ ] **QR Scanner Component**
+  - [ ] Create mock for `WebInlineQRScanner`
+  - [ ] Mock camera permissions and device detection
+  - [ ] Test platform-specific behavior (web vs mobile)
+- [ ] **Platform Service Components**
+  - [ ] Mock `CapacitorPlatformService`
+  - [ ] Mock `WebPlatformService`
+  - [ ] Mock `ElectronPlatformService`
+- [ ] **Database Components**
+  - [ ] Mock `AbsurdSqlDatabaseService`
+  - [ ] Test migration scenarios
+  - [ ] Mock IndexedDB operations
+
+### 5. Integration Test Improvements
+- [ ] **Cross-component communication**
+  - [ ] Test ImageViewer + QR Scanner integration
+  - [ ] Test platform service + component interactions
+  - [ ] Mock complex user workflows
+- [ ] **End-to-end scenarios**
+  - [ ] Complete user journeys (scan → view → share)
+  - [ ] Error recovery flows
+  - [ ] Performance testing scenarios
+
+## Test Infrastructure Improvements 🏗️
+
+### 6. Test Environment Setup
+- [ ] **Improve Vitest configuration**
+  - [ ] Add proper DOM environment setup
+  - [ ] Configure global mocks for browser APIs
+  - [ ] Add test utilities for common patterns
+- [ ] **Create test helpers**
+  - [ ] `createComponentWrapper()` utility
+  - [ ] `mockPlatformService()` helper
+  - [ ] `simulateUserInteraction()` utilities
+
+### 7. Performance Testing
+- [ ] **Add performance benchmarks**
+  - [ ] Component render time testing
+  - [ ] Memory usage monitoring
+  - [ ] Image loading performance tests
+- [ ] **Load testing scenarios**
+  - [ ] Multiple ImageViewer instances
+  - [ ] Large image handling
+  - [ ] Concurrent operations
+
+## Quality Assurance Improvements 📊
+
+### 8. Test Coverage Enhancement
+- [ ] **Add missing test scenarios**
+  - [ ] Edge cases for image formats
+  - [ ] Network error handling
+  - [ ] Accessibility compliance tests
+- [ ] **Mutation testing**
+  - [ ] Verify test quality with mutation testing
+  - [ ] Ensure tests catch actual bugs
+  - [ ] Improve test reliability
+
+### 9. Test Documentation
+- [ ] **Create test guidelines**
+  - [ ] Best practices for Vue component testing
+  - [ ] Mock unit design patterns
+  - [ ] Troubleshooting common test issues
+- [ ] **Add test examples**
+  - [ ] Example test files for each component type
+  - [ ] Integration test examples
+  - [ ] Performance test examples
+
+## Advanced Testing Features 🚀
+
+### 10. Visual Regression Testing
+- [ ] **Add visual testing**
+  - [ ] Screenshot comparison for ImageViewer
+  - [ ] Visual diff testing for UI changes
+  - [ ] Cross-platform visual consistency
+- [ ] **Accessibility testing**
+  - [ ] Automated accessibility checks
+  - [ ] Screen reader compatibility tests
+  - [ ] Keyboard navigation testing
+
+### 11. Contract Testing
+- [ ] **API contract testing**
+  - [ ] Test component prop contracts
+  - [ ] Event emission contracts
+  - [ ] Service interface contracts
+- [ ] **Mock contract validation**
+  - [ ] Ensure mocks match real component behavior
+  - [ ] Validate mock completeness
+  - [ ] Test mock accuracy
+
+## Priority Levels 📋
+
+### High Priority (Next Sprint)
+1. Fix mobile share button test
+2. Create global event simulation utilities
+3. Expand mock units to QR Scanner component
+4. Improve test environment setup
+
+### Medium Priority (Next Month)
+1. Create reusable mock patterns
+2. Add performance testing
+3. Improve test documentation
+4. Add visual regression testing
+
+### Low Priority (Future)
+1. Advanced integration testing
+2. Contract testing
+3. Mutation testing
+4. Cross-platform visual testing
+
+## Success Metrics 📈
+
+### Current Status
+- ✅ **97% test pass rate** (38/39 tests)
+- ✅ **4 mock levels** implemented
+- ✅ **Comprehensive coverage** of ImageViewer functionality
+- ✅ **Behavior-focused testing** approach working
+
+### Target Metrics
+- [ ] **100% test pass rate** (fix remaining test)
+- [ ] **10+ components** with mock units
+- [ ] **< 100ms** average test execution time
+- [ ] **90%+ code coverage** for critical components
+- [ ] **Zero flaky tests** in CI/CD pipeline
+
+## Notes 📝
+
+### Lessons Learned
+- Vue 3 reactivity can be tricky with computed properties in tests
+- Direct method calls work better than `trigger()` for complex events
+- Mock levels provide excellent flexibility for different testing needs
+- Behavior-focused testing is more maintainable than implementation-focused
+
+### Technical Debt
+- Some TypeScript linter errors in mock files (non-blocking)
+- Event simulation needs better abstraction
+- Test environment could be more robust
+- Mock documentation could be more comprehensive
+
+---
+
+*Last updated: 2025-01-07*
+*Status: Active development* 

android/app/build.gradle

@@ -31,8 +31,8 @@ android {
         applicationId "app.timesafari.app"
         minSdkVersion rootProject.ext.minSdkVersion
         targetSdkVersion rootProject.ext.targetSdkVersion
-        versionCode 39
-        versionName "1.0.6"
+        versionCode 40
+        versionName "1.0.7"
         testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
         aaptOptions {
              // Files and dirs to omit from the packaged assets dir, modified to accommodate modern web apps.

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

@@ -29,7 +29,7 @@
 			"splashFullScreen": true,
 			"splashImmersive": true
 		},
-		"CapacitorSQLite": {
+		"CapSQLite": {
 			"iosDatabaseLocation": "Library/CapacitorDatabase",
 			"iosIsEncryption": false,
 			"iosBiometric": {

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

@@ -0,0 +1,7 @@
+<?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/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.12.1'
         classpath 'com.google.gms:google-services:4.4.0'
 
         // NOTE: Do not place your application dependencies here; they belong

assets/README.md

@@ -1,2 +0,0 @@
-
-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,36 +1,32 @@
 {
   "icon": {
-    "ios": {
-      "source": "resources/ios/icon/icon.png",
-      "target": "ios/App/App/Assets.xcassets/AppIcon.appiconset"
-    },
     "android": {
-      "source": "resources/android/icon/icon.png",
+      "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": {
-      "source": "resources/web/icon/icon.png",
       "target": "public/img/icons"
     }
   },
   "splash": {
-    "ios": {
-      "source": "resources/ios/splash/splash.png",
-      "target": "ios/App/App/Assets.xcassets/Splash.imageset"
-    },
     "android": {
-      "source": "resources/android/splash/splash.png",
+      "scale": "cover",
       "target": "android/app/src/main/res"
-    }
-  },
-  "splashDark": {
-    "ios": {
-      "source": "resources/ios/splash/splash_dark.png",
-      "target": "ios/App/App/Assets.xcassets/SplashDark.imageset"
     },
-    "android": {
-      "source": "resources/android/splash/splash_dark.png",
-      "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.ts

@@ -0,0 +1,116 @@
+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

@@ -0,0 +1,32 @@
+{
+  "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

@@ -0,0 +1,119 @@
+{
+  "$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

@@ -47,6 +47,7 @@ type ClaimParams = z.infer<typeof claimSchema>;
 ### Type Safety Layers
 
 1. **Schema Definition**
+
    ```typescript
    // src/interfaces/deepLinks.ts
    export const deepLinkSchemas = {
@@ -59,6 +60,7 @@ type ClaimParams = z.infer<typeof claimSchema>;
    ```
 
 2. **Type Generation**
+
    ```typescript
    // Types are automatically generated from schemas
    export type DeepLinkParams = {
@@ -67,6 +69,7 @@ type ClaimParams = z.infer<typeof claimSchema>;
    ```
 
 3. **Runtime Validation**
+
    ```typescript
    // In DeepLinkHandler
    const result = deepLinkSchemas.claim.safeParse(params);

doc/README.md

@@ -6,7 +6,7 @@ This uses Pandoc and BasicTex (LaTeX) Installed through Homebrew.
 
 ### Set Up
 
-```bash 
+```bash
 brew install pandoc
 
 brew install basictex
@@ -54,7 +54,7 @@ sudo tlmgr install sourceserifpro
 
 The following guide was adapted to this project except that we install with Brew and have a few more packages.
 
-Guide: https://daniel.feldroy.com/posts/setting-up-latex-on-mac-os-x
+Guide: <https://daniel.feldroy.com/posts/setting-up-latex-on-mac-os-x>
 
 ### Usage
 
@@ -71,6 +71,7 @@ open usage-guide.pdf
 ```
 
 Or use this one-liner
+
 ```bash
 pandoc usage-guide.md -o usage-guide.pdf && open usage-guide.pdf
 ```

doc/architecture-decisions.md

@@ -122,4 +122,4 @@ export default class HomeView extends Vue {
 
 ---
 
-*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.* 
+*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

@@ -0,0 +1,215 @@
+# 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

@@ -3,11 +3,13 @@
 **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**
@@ -21,6 +23,7 @@
   - 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
@@ -28,24 +31,29 @@
 - [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. 
+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

@@ -13,27 +13,31 @@ The codebase currently has **no active circular dependencies** that are causing
 ### 🔍 **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**: 
+- **Implementation**:
   - Self-contained `parseJsonField()` and `mapQueryResultToValues()` functions
   - Direct PlatformServiceFactory usage for database operations
   - Console logging instead of databaseUtil logging functions
@@ -43,18 +47,21 @@ The codebase currently has **no active circular dependencies** that are causing
 ### ✅ **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
@@ -63,6 +70,7 @@ The codebase currently has **no active circular dependencies** that are causing
 ### 🎯 **Migration Readiness Status**
 
 #### Files Ready for Migration (52 files)
+
 1. **Components** (15 files):
    - `PhotoDialog.vue`
    - `FeedFilters.vue`
@@ -98,6 +106,7 @@ The codebase currently has **no active circular dependencies** that are causing
 ### 🟢 **Healthy Dependencies**
 
 #### Logger Usage (80+ files)
+
 - **Status**: ✅ **HEALTHY**
 - **Pattern**: All files import logger from `@/utils/logger`
 - **Impact**: No circular dependencies, logger is self-contained
@@ -106,21 +115,25 @@ The codebase currently has **no active circular dependencies** that are causing
 ## 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
@@ -128,6 +141,7 @@ The codebase currently has **no active circular dependencies** that are causing
 ## 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
@@ -135,6 +149,7 @@ The codebase currently has **no active circular dependencies** that are causing
 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
@@ -142,6 +157,7 @@ The codebase currently has **no active circular dependencies** that are causing
 ## 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
@@ -149,6 +165,7 @@ The codebase currently has **no active circular dependencies** that are causing
 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
@@ -160,4 +177,4 @@ The codebase currently has **no active circular dependencies** that are causing
 **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 
+**Note**: PlatformServiceMixin circular dependency completely resolved. Ready for Phase 2: File-by-File Migration

doc/component-communication-guide.md

@@ -93,6 +93,7 @@ export default class FormComponent extends Vue {
 When generating component templates, follow these patterns:
 
 #### Function Props Template
+
 ```vue
 <template>
   <div class="component-name">
@@ -124,6 +125,7 @@ export default class ComponentName extends Vue {
 ```
 
 #### $emit Template (for DOM events)
+
 ```vue
 <template>
   <div class="component-name">
@@ -155,12 +157,14 @@ export default class ComponentName extends Vue {
 ### 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
@@ -169,6 +173,7 @@ export default class ComponentName extends Vue {
 #### 3. Naming Conventions
 
 **Function Props:**
+
 ```typescript
 // Action-oriented names
 onSave: (data: SaveData) => Promise<void>
@@ -179,6 +184,7 @@ onNavigate: (route: string) => void
 ```
 
 **$emit Events:**
+
 ```typescript
 // Event-oriented names
 @click: (event: MouseEvent) => void
@@ -191,6 +197,7 @@ onNavigate: (route: string) => void
 ### TypeScript Integration
 
 #### Function Prop Types
+
 ```typescript
 // Define reusable function types
 interface SaveHandler {
@@ -207,6 +214,7 @@ interface ValidationHandler {
 ```
 
 #### Event Types
+
 ```typescript
 // Define event payload types
 interface ClickEvent {
@@ -226,6 +234,7 @@ handleClick(): ClickEvent {
 ## Testing Guidelines
 
 ### Function Props Testing
+
 ```typescript
 // Easy to mock and test
 const mockOnSave = jest.fn();
@@ -240,6 +249,7 @@ expect(mockOnSave).toHaveBeenCalledWith(expectedData);
 ```
 
 ### $emit Testing
+
 ```typescript
 // Requires event simulation
 const wrapper = mount(MyComponent);
@@ -260,6 +270,7 @@ expect(wrapper.emitted('click')).toBeTruthy();
 ### Example Migration
 
 **Before ($emit):**
+
 ```typescript
 @Emit("save")
 handleSave() {
@@ -268,6 +279,7 @@ handleSave() {
 ```
 
 **After (Function Props):**
+
 ```typescript
 @Prop({ required: true }) onSave!: (data: FormData) => void;
 
@@ -288,6 +300,7 @@ handleSave() {
 ## Code Generation Templates
 
 ### Component Generator Input
+
 ```typescript
 interface ComponentSpec {
   name: string;
@@ -306,9 +319,10 @@ interface ComponentSpec {
 ```
 
 ### 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. 
+This guide ensures consistent, maintainable component communication patterns across the application.

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

@@ -7,10 +7,12 @@ CORS headers have been **disabled** to support Time Safari's core mission: enabl
 ## 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
@@ -19,11 +21,13 @@ CORS headers have been **disabled** to support Time Safari's core mission: enabl
 ## 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
@@ -31,6 +35,7 @@ CORS headers have been **disabled** to support Time Safari's core mission: enabl
 ## Architecture Impact
 
 ### Database Operations
+
 ```typescript
 // absurd-sql automatically detects SharedArrayBuffer availability
 if (typeof SharedArrayBuffer === "undefined") {
@@ -43,6 +48,7 @@ if (typeof SharedArrayBuffer === "undefined") {
 ```
 
 ### Image Loading
+
 ```typescript
 // All images load directly now
 export function transformImageUrlForCors(imageUrl: string): string {
@@ -53,11 +59,13 @@ export function transformImageUrlForCors(imageUrl: string): string {
 ## 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
@@ -66,11 +74,13 @@ export function transformImageUrlForCors(imageUrl: string): string {
 ## 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
@@ -87,11 +97,13 @@ export function transformImageUrlForCors(imageUrl: string): string {
 ## 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
@@ -99,12 +111,14 @@ export function transformImageUrlForCors(imageUrl: string): string {
 ## 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
@@ -113,4 +127,4 @@ export function transformImageUrlForCors(imageUrl: string): string {
 
 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. 
+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

@@ -7,6 +7,7 @@ This document describes the implementation of a comprehensive image loading solu
 ## 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`
 
@@ -19,6 +20,7 @@ This isolation prevents loading external resources (including images) unless the
 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/`
@@ -26,14 +28,17 @@ The solution uses a multi-tier approach to handle images from various sources:
 - **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
@@ -44,6 +49,7 @@ The `transformImageUrlForCors` function automatically:
 ### Configuration Files
 
 #### `vite.config.common.mts`
+
 ```typescript
 server: {
   headers: {
@@ -63,6 +69,7 @@ server: {
 ```
 
 #### `src/libs/util.ts`
+
 ```typescript
 export function transformImageUrlForCors(imageUrl: string): string {
   // Development mode: Transform URLs to use proxies
@@ -93,21 +100,25 @@ const imageUrl = transformImageUrlForCors(originalImageUrl);
 ## 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
@@ -115,6 +126,7 @@ const imageUrl = transformImageUrlForCors(originalImageUrl);
 ## Testing
 
 ### Automated Testing
+
 Run the test suite to verify URL transformation:
 
 ```typescript
@@ -125,6 +137,7 @@ testCorsImageTransformation();
 ```
 
 ### Visual Testing
+
 Create test image elements to verify loading:
 
 ```typescript
@@ -135,6 +148,7 @@ 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
@@ -143,16 +157,19 @@ createTestImageElements();
 ## 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
@@ -160,11 +177,13 @@ createTestImageElements();
 ## 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
@@ -174,17 +193,20 @@ createTestImageElements();
 ### 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
@@ -207,12 +229,14 @@ 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
@@ -221,6 +245,7 @@ testCorsImageTransformation();
 ## 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
@@ -228,6 +253,7 @@ testCorsImageTransformation();
 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
@@ -237,4 +263,4 @@ testCorsImageTransformation();
 
 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. 
+For questions or issues, refer to the troubleshooting section or consult the development team.

doc/database-migration-guide.md

@@ -294,6 +294,7 @@ const result = await this.$db("SELECT * FROM contacts WHERE did = ?", [accountDi
 ```
 
 This provides:
+
 - **Caching**: Automatic caching for performance
 - **Error Handling**: Consistent error handling
 - **Type Safety**: Enhanced TypeScript integration

doc/debug-hook-guide.md

@@ -0,0 +1,187 @@
+# TimeSafari Debug Hook Guide
+
+**Complete Guide for Team Members**
+
+**Date**: 2025-01-27  
+**Author**: Matthew Raymer  
+**Status**: ✅ **ACTIVE** - Ready for production use
+
+## 🎯 Overview
+
+A pre-commit hook that automatically detects and prevents debug code from reaching protected branches (master, main, production, release, stable). This ensures production code remains clean while allowing free development on feature branches.
+
+## 🚀 Quick Installation
+
+**From within the TimeSafari repository:**
+
+```bash
+./scripts/install-debug-hook.sh
+```
+
+This automatically installs, updates, and verifies the hook in your current
+repository. **Note**: Hooks are not automatically installed - you must run this
+script deliberately to enable debug code checking.
+
+## 🔧 Manual Installation
+
+**Copy files manually:**
+
+```bash
+cp scripts/git-hooks/pre-commit /path/to/your/repo/.git/hooks/
+cp scripts/git-hooks/debug-checker.config /path/to/your/repo/.git/hooks/
+chmod +x /path/to/your/repo/.git/hooks/pre-commit
+```
+
+## 📋 What Gets Installed
+
+- **`pre-commit`** - Main hook script (executable)
+- **`debug-checker.config`** - Configuration file
+- **`README.md`** - Documentation and troubleshooting
+
+**Note**: Hooks are stored in `scripts/git-hooks/` and must be deliberately
+installed by each developer. They are not automatically active.
+
+## 🎯 How It Works
+
+1. **Deliberate Installation**: Hooks must be explicitly installed by each
+   developer
+2. **Branch Detection**: Only runs on protected branches
+3. **File Filtering**: Automatically skips tests, scripts, and documentation
+4. **Pattern Matching**: Detects debug code using regex patterns
+5. **Commit Prevention**: Blocks commits containing debug code
+
+## 🔒 Installation Philosophy
+
+**Why deliberate installation?**
+
+- **Developer choice**: Each developer decides whether to use the hook
+- **No forced behavior**: Hooks don't interfere with existing workflows
+- **Local control**: Hooks are installed locally, not globally
+- **Easy removal**: Can be uninstalled at any time
+- **Team flexibility**: Some developers may prefer different tools
+
+## 🌿 Branch Behavior
+
+- **Protected branches** (master, main, production, release, stable): Hook runs automatically
+- **Feature branches**: Hook is skipped, allowing free development with debug code
+
+## 🔍 Debug Patterns Detected
+
+- **Console statements**: `console.log`, `console.debug`, `console.error`
+- **Template debug**: `Debug:`, `debug:` in Vue templates
+- **Debug constants**: `DEBUG_`, `debug_` variables
+- **HTML debug**: `<!-- debug` comments
+- **Debug attributes**: `debug="true"` attributes
+- **Vue debug**: `v-if="debug"`, `v-show="debug"`
+- **Debug TODOs**: `TODO debug`, `FIXME debug`
+
+## 📁 Files Automatically Skipped
+
+- Test files: `*.test.js`, `*.spec.ts`, `*.test.vue`
+- Scripts: `scripts/` directory
+- Test directories: `test-*` directories
+- Documentation: `docs/`, `*.md`, `*.txt`
+- Config files: `*.json`, `*.yml`, `*.yaml`
+- IDE files: `.cursor/` directory
+
+## ✅ Verification
+
+**After installation, verify it's working:**
+
+```bash
+# Check if files exist
+ls -la .git/hooks/pre-commit
+ls -la .git/hooks/debug-checker.config
+
+# Test the hook manually
+.git/hooks/pre-commit
+
+# Test with actual commit
+echo "console.log('test')" > test.vue
+git add test.vue
+git commit -m "test"  # Should be blocked
+```
+
+## 📊 Example Output
+
+```
+❌ Debug code detected in staged files!
+   Branch: master
+   Files checked: 1
+   Errors found: 3
+
+   🚨 AccountViewView.vue: Found debug pattern 'console\.'
+   🚨 AccountViewView.vue: Found debug pattern 'Debug:'
+   🚨 AccountViewView.vue: Found debug pattern 'DEBUG_'
+
+💡 Please remove debug code before committing to master
+```
+
+## ⚙️ Configuration
+
+Edit `.git/hooks/debug-checker.config` to customize:
+
+- **Protected branches**: Add/remove branches as needed
+- **Debug patterns**: Customize what gets detected
+- **Skip patterns**: Adjust file filtering rules
+
+## 🚨 Emergency Bypass
+
+If you absolutely need to commit debug code to a protected branch:
+
+```bash
+git commit --no-verify -m "emergency: debug code needed"
+```
+
+⚠️ **Warning**: This bypasses all pre-commit hooks. Use sparingly.
+
+## 🔄 Updates
+
+When the hook is updated in the main repository:
+
+```bash
+./scripts/install-debug-hook.sh
+```
+
+## 🚨 Troubleshooting
+
+| Issue | Solution |
+|-------|----------|
+| Hook not running | Check if on protected branch, verify permissions |
+| Permission denied | Run `chmod +x .git/hooks/pre-commit` |
+| Files not found | Ensure you're copying from TimeSafari repo |
+| False positives | Edit `debug-checker.config` to customize patterns |
+
+## 🧪 Testing
+
+A test script is available at `scripts/test-debug-hook.sh` to verify the hook works correctly.
+
+## 💡 Best Practices
+
+1. **Use feature branches** for development with debug code
+2. **Use proper logging** instead of console statements (`logger.info`, `logger.debug`)
+3. **Test thoroughly** before merging to protected branches
+4. **Review commits** to ensure no debug code slips through
+5. **Keep hooks updated** across all repositories
+
+## 📚 Additional Resources
+
+- **Hook documentation**: `scripts/git-hooks/README.md`
+- **Configuration**: `scripts/git-hooks/debug-checker.config`
+- **Test script**: `scripts/test-debug-hook.sh`
+- **Installation script**: `scripts/install-debug-hook.sh`
+
+## 🎯 Team Workflow
+
+**Recommended setup:**
+
+1. **Repository setup**: Include hook files in `.githooks/` directory
+2. **Team onboarding**: Run installation script in each repo
+3. **Updates**: Re-run installation script when hooks are updated
+4. **Documentation**: Keep this guide updated
+
+---
+
+**Status**: Active and enforced  
+**Last Updated**: 2025-01-27  
+**Maintainer**: Matthew Raymer

doc/electron-cleanup-summary.md

@@ -7,18 +7,22 @@ This document summarizes the comprehensive cleanup and improvements made to the
 ## Key Issues Resolved
 
 ### 1. Platform Detection Problems
+
 - **Before**: `PlatformServiceFactory` only supported "capacitor" and "web" platforms
 - **After**: Added proper "electron" platform support with dedicated `ElectronPlatformService`
 
 ### 2. Build Configuration Confusion
+
 - **Before**: Electron builds used `VITE_PLATFORM=capacitor`, causing confusion
 - **After**: Electron builds now properly use `VITE_PLATFORM=electron`
 
 ### 3. Missing Platform Service Methods
+
 - **Before**: Platform services lacked proper `isElectron()`, `isCapacitor()`, `isWeb()` methods
 - **After**: All platform services implement complete interface with proper detection
 
 ### 4. Inconsistent Build Scripts
+
 - **Before**: Mixed platform settings in build scripts
 - **After**: Clean, consistent electron-specific build process
 
@@ -215,11 +219,13 @@ if (capabilities.hasFileDownload) {
 ## File Structure Changes
 
 ### New Files
+
 - `vite.config.electron.mts` - Electron-specific Vite configuration
 - `src/main.electron.ts` - Electron main entry point
 - `doc/electron-cleanup-summary.md` - This documentation
 
 ### Modified Files
+
 - `src/services/PlatformServiceFactory.ts` - Added electron platform support
 - `src/services/PlatformService.ts` - Added platform detection methods
 - `src/services/platforms/CapacitorPlatformService.ts` - Added missing interface methods
@@ -301,4 +307,4 @@ For developers working with the previous implementation:
 - [ ] Implement desktop-specific UI components
 - [ ] Add Electron auto-updater integration
 - [ ] Create platform-specific testing utilities
-- [ ] Add desktop notification system integration 
+- [ ] Add desktop notification system integration

doc/electron-console-cleanup.md

@@ -7,18 +7,22 @@ This document summarizes the comprehensive changes made to reduce excessive cons
 ## Issues Addressed
 
 ### 1. Excessive Database Logging (Major Issue - 90% Reduction)
+
 **Problem:** Every database operation was logging detailed parameter information, creating hundreds of lines of console output.
 
 **Solution:** Modified `src/services/platforms/CapacitorPlatformService.ts`:
+
 - Changed `logger.warn` to `logger.debug` for routine SQL operations
-- Reduced migration logging verbosity 
+- Reduced migration logging verbosity
 - Made database integrity checks use debug-level logging
 - Kept error and completion messages at appropriate log levels
 
 ### 2. Enhanced Logger Configuration
+
 **Problem:** No platform-specific logging controls, causing noise in Electron.
 
 **Solution:** Updated `src/utils/logger.ts`:
+
 - Added platform detection for Electron vs Web
 - Suppressed debug and verbose logs for Electron
 - Filtered out routine database operations from database logging
@@ -26,28 +30,35 @@ This document summarizes the comprehensive changes made to reduce excessive cons
 - Added intelligent filtering for CapacitorPlatformService messages
 
 ### 3. API Configuration Issues (Major Fix)
+
 **Problem:** Electron was trying to use local development endpoints (localhost:3000) from saved user settings, which don't exist in desktop environment, causing:
+
 - 400 status errors from missing local development servers
 - JSON parsing errors (HTML error pages instead of JSON responses)
 
-**Solution:** 
+**Solution:**
+
 - Updated `src/constants/app.ts` to provide Electron-specific API endpoints
 - **Critical Fix:** Modified `src/db/databaseUtil.ts` in `retrieveSettingsForActiveAccount()` to force Electron to use production API endpoints regardless of saved user settings
 - This ensures Electron never uses localhost development servers that users might have saved
 
 ### 4. SharedArrayBuffer Logging Noise
+
 **Problem:** Web-specific SharedArrayBuffer detection was running in Electron, creating unnecessary debug output.
 
 **Solution:** Modified `src/main.web.ts`:
+
 - Made SharedArrayBuffer logging conditional on web platform only
 - Converted console.log statements to logger.debug
 - Only show in development mode for web platform
 - Reduced platform detection noise
 
 ### 5. Missing Source Maps Warnings
+
 **Problem:** Electron DevTools was complaining about missing source maps for external dependencies.
 
 **Solution:** Updated `vite.config.electron.mts`:
+
 - Disabled source maps for Electron builds (`sourcemap: false`)
 - Added build configuration to suppress external dependency warnings
 - Prevents DevTools from looking for non-existent source map files
@@ -87,14 +98,16 @@ This document summarizes the comprehensive changes made to reduce excessive cons
 
 ## Impact
 
-### Before Cleanup:
+### Before Cleanup
+
 - 500+ lines of console output per minute
 - Detailed SQL parameter logging for every operation
 - API connection errors every few seconds (400 status, JSON parsing errors)
 - SharedArrayBuffer warnings on every startup
 - DevTools source map warnings
 
-### After Cleanup:
+### After Cleanup
+
 - **~95% reduction** in console output
 - Only errors and important status messages visible
 - **No API connection errors** - Electron uses proper production endpoints
@@ -106,6 +119,7 @@ This document summarizes the comprehensive changes made to reduce excessive cons
 ## Technical Details
 
 ### API Configuration Fix
+
 The most critical fix was in `src/db/databaseUtil.ts` where we added:
 
 ```typescript
@@ -122,6 +136,7 @@ if (process.env.VITE_PLATFORM === "electron") {
 This ensures that even if users have localhost development endpoints saved in their settings, Electron will override them with production endpoints.
 
 ### Logger Enhancement
+
 Enhanced the logger with platform-specific behavior:
 
 ```typescript
@@ -135,6 +150,7 @@ if (!isElectron || !message.includes("[CapacitorPlatformService]")) {
 ## Testing
 
 The changes were tested with:
+
 - `npm run lint-fix` - 0 errors, warnings only (pre-existing)
 - Electron development environment
 - Web platform (unchanged functionality)
@@ -150,6 +166,7 @@ The changes were tested with:
 ## Backward Compatibility
 
 All changes maintain backward compatibility:
+
 - Web platform logging unchanged
 - Capacitor platform logging unchanged  
 - Error handling preserved
@@ -185,4 +202,4 @@ Tests: lint passes, Web/Capacitor functionality preserved
 1. **Test the fixes** - Run `npm run electron:dev` to verify console noise is eliminated
 2. **Monitor for remaining issues** - Check for any other console noise sources
 3. **Performance monitoring** - Verify the reduced logging doesn't impact functionality
-4. **Documentation updates** - Update any development guides that reference the old logging behavior 
+4. **Documentation updates** - Update any development guides that reference the old logging behavior

doc/error-diagnostics-log.md

@@ -5,9 +5,10 @@ This file tracks console errors observed during development for future investiga
 ## 2025-07-07 08:56 UTC - ProjectsView.vue Migration Session
 
 ### Migration Context
+
 - **Current Work**: Completed ProjectsView.vue Triple Migration Pattern
 - **Migration Status**: 21 complete, 4 appropriately incomplete components
-- **Recent Changes**: 
+- **Recent Changes**:
   - ProjectsView.vue: databaseUtil → PlatformServiceMixin
   - Added notification constants and literal string extraction
   - Template logic streamlining with computed properties
@@ -15,42 +16,50 @@ This file tracks console errors observed during development for future investiga
 ### Observed Errors
 
 #### 1. HomeView.vue API Rate Limit Errors
+
 ```
 GET https://api.endorser.ch/api/report/rateLimits 400 (Bad Request)
 Source: endorserServer.ts:1494, HomeView.vue:593, HomeView.vue:742
 ```
 
-**Analysis**: 
+**Analysis**:
+
 - API server returning 400 for rate limit checks
 - Occurs during identity initialization and registration status checks
 - **Migration Impact**: None - HomeView.vue was migrated and tested earlier
 - **Likely Cause**: Server-side authentication or API configuration issue
 
 **Action Items**:
+
 - [ ] Check endorser.ch API documentation for rate limit endpoint changes
 - [ ] Verify authentication headers being sent correctly
 - [ ] Consider fallback handling for rate limit API failures
 
 #### 2. ProjectViewView.vue Project Not Found Error
+
 ```
 GET https://api.endorser.ch/api/claim/byHandle/...01JY2Q5D90E8P267ABB963S71D 404 (Not Found)
 Source: ProjectViewView.vue:830 loadProject() method
 ```
 
 **Analysis**:
+
 - Attempting to load project ID: `01JY2Q5D90E8P267ABB963S71D`
 - **Migration Impact**: None - error handling working correctly
 - **Likely Cause**: User navigated to non-existent project or stale link
 
 **Action Items**:
+
 - [ ] Consider adding better user messaging for missing projects
 - [ ] Investigate if project IDs are being generated/stored correctly
 - [ ] Add breadcrumb or "return to projects" option on 404s
 
 #### 3. Axios Request Stack Traces
+
 Multiple stack traces showing Vue router navigation and component mounting cycles.
 
 **Analysis**:
+
 - Normal Vue.js lifecycle and routing behavior
 - No obvious memory leaks or infinite loops
 - **Migration Impact**: None - expected framework behavior
@@ -58,26 +67,30 @@ Multiple stack traces showing Vue router navigation and component mounting cycle
 ### System Health Indicators
 
 #### ✅ Working Correctly
+
 - Database migrations: `Migration process complete! Summary: 0 applied, 2 skipped`
 - Platform service factory initialization: `Creating singleton instance for platform: development`
 - SQL worker loading: `Worker loaded, ready to receive messages`
 - Database connection: `Opened!`
 
 #### 🔄 For Investigation
+
 - API authentication/authorization with endorser.ch
 - Project ID validation and error handling
 - Rate limiting strategy
 
 ### Migration Validation
+
 - **ProjectsView.vue**: Appropriately incomplete (3 helpers + 1 complex modal)
 - **Error Handling**: Migrated components showing proper error handling
 - **No Migration-Related Errors**: All errors appear to be infrastructure/data issues
 
 ### Next Steps
+
 1. Continue migration slog with next component
 2. Monitor these same error patterns in future sessions
 3. Address API/server issues in separate debugging session
 
 ---
 *Log Entry by: Migration Assistant*  
-*Session: ProjectsView.vue Triple Migration Pattern* 
+*Session: ProjectsView.vue Triple Migration Pattern*

doc/husky-conditional-activation.md

@@ -0,0 +1,381 @@
+# Husky Conditional Activation System
+
+**Author**: Matthew Raymer
+**Date**: 2025-08-21T09:40Z
+**Status**: 🎯 **ACTIVE** - Git hooks with optional activation
+
+## Overview
+
+This document describes the **conditional Husky activation system** implemented
+in the TimeSafari project. The system provides standardized git hooks that are
+committed to version control but only activate when explicitly enabled by
+individual developers.
+
+## Problem Statement
+
+Traditional Husky implementations face several challenges:
+
+1. **Automatic activation** on all systems can be disruptive
+2. **Different environments** may have different requirements
+3. **Team preferences** vary regarding git hook enforcement
+4. **CI/CD systems** may not need or want git hooks
+5. **New developers** may be surprised by unexpected hook behavior
+
+## Solution: Conditional Activation
+
+The conditional activation system solves these problems by:
+
+- **Committing hooks to git** for consistency and version control
+- **Making hooks optional** by default
+- **Providing multiple activation methods** for flexibility
+- **Ensuring hooks exit gracefully** when disabled
+- **Maintaining team standards** without forcing compliance
+
+## System Architecture
+
+### **Core Components**
+
+```
+.husky/
+├── _/husky.sh              # Conditional activation logic
+├── pre-commit              # Pre-commit hook (linting)
+├── commit-msg              # Commit message validation
+└── README.md               # User activation instructions
+```
+
+### **Activation Methods**
+
+#### **Method 1: Environment Variable (Session Only)**
+
+```bash
+export HUSKY_ENABLED=1
+```
+
+- **Scope**: Current terminal session only
+- **Use case**: Temporary activation for testing
+- **Reset**: `unset HUSKY_ENABLED`
+
+#### **Method 2: Local File (Persistent)**
+
+```bash
+touch .husky-enabled
+```
+
+- **Scope**: Current repository, persistent
+- **Use case**: Long-term activation for development
+- **Reset**: `rm .husky-enabled`
+
+#### **Method 3: Global Git Configuration**
+
+```bash
+git config --global husky.enabled true
+```
+
+- **Scope**: All repositories for current user
+- **Use case**: Developer preference across projects
+- **Reset**: `git config --global --unset husky.enabled`
+
+## Implementation Details
+
+### **Conditional Activation Logic**
+
+The core logic in `.husky/_/husky.sh`:
+
+```bash
+# Check if Husky is enabled for this user
+if [ "$HUSKY_ENABLED" != "1" ] && [ ! -f .husky-enabled ]; then
+  echo "Husky is not enabled. To enable:"
+  echo "  export HUSKY_ENABLED=1"
+  echo "  or create .husky-enabled file"
+  exit 0  # Graceful exit, not an error
+fi
+```
+
+### **Hook Behavior**
+
+When **disabled**:
+
+- Hooks display helpful activation instructions
+- Exit with code 0 (success, not error)
+- No git operations are blocked
+- No performance impact
+
+When **enabled**:
+
+- Hooks run normally with full functionality
+- Standard Husky behavior applies
+- Git operations may be blocked if hooks fail
+
+## Available Hooks
+
+### **Pre-commit Hook**
+
+**File**: `.husky/pre-commit`
+**Purpose**: Code quality enforcement before commits
+**Action**: Runs `npm run lint-fix`
+**When**: Before each commit
+**Failure**: Prevents commit if linting fails
+
+**Activation Check**:
+
+```bash
+if [ "$HUSKY_ENABLED" = "1" ] || [ -f .husky-enabled ]; then
+  echo "Running pre-commit hooks..."
+  npm run lint-fix
+else
+  echo "Husky pre-commit hook skipped (not enabled)"
+  exit 0
+fi
+```
+
+### **Commit-msg Hook**
+
+**File**: `.husky/commit-msg`
+**Purpose**: Commit message format validation
+**Action**: Runs `npx commitlint --edit "$1"`
+**When**: After commit message is written
+**Failure**: Prevents commit if message format is invalid
+
+**Activation Check**:
+
+```bash
+if [ "$HUSKY_ENABLED" = "1" ] || [ -f .husky-enabled ]; then
+  echo "Running commit-msg hooks..."
+  npx commitlint --edit "$1"
+else
+  echo "Husky commit-msg hook skipped (not enabled)"
+  exit 0
+fi
+```
+
+## User Workflows
+
+### **New Developer Setup**
+
+1. **Clone repository**
+
+   ```bash
+   git clone <repository-url>
+   cd <repository-name>
+   ```
+
+2. **Hooks are present but inactive**
+   - Pre-commit and commit-msg hooks exist
+   - No automatic activation
+   - Git operations work normally
+
+3. **Optional: Enable hooks**
+
+   ```bash
+   # For current session only
+   export HUSKY_ENABLED=1
+
+   # For persistent activation
+   touch .husky-enabled
+   ```
+
+### **Daily Development**
+
+#### **With Hooks Disabled**
+
+```bash
+git add .
+git commit -m "feat: add new feature"
+# Hooks are skipped, commit proceeds normally
+```
+
+#### **With Hooks Enabled**
+
+```bash
+git add .
+git commit -m "feat: add new feature"
+# Pre-commit hook runs linting
+# Commit-msg hook validates message format
+# Commit only proceeds if all hooks pass
+```
+
+### **Troubleshooting**
+
+#### **Hooks Not Running**
+
+```bash
+# Check if hooks are enabled
+echo $HUSKY_ENABLED
+ls -la .husky-enabled
+
+# Enable hooks
+export HUSKY_ENABLED=1
+# or
+touch .husky-enabled
+```
+
+#### **Hooks Running Unexpectedly**
+
+```bash
+# Disable hooks
+unset HUSKY_ENABLED
+rm -f .husky-enabled
+
+# Check global configuration
+git config --global --get husky.enabled
+```
+
+## Configuration Files
+
+### **`.gitignore` Entry**
+
+```gitignore
+# Husky activation file (user-specific)
+.husky-enabled
+```
+
+This ensures that:
+
+- Hooks are committed to git (team standard)
+- Activation files are not committed (user preference)
+- Each developer can control their own activation
+
+### **Package.json Dependencies**
+
+```json
+{
+  "devDependencies": {
+    "husky": "^9.0.11",
+    "@commitlint/cli": "^18.6.1",
+    "@commitlint/config-conventional": "^18.6.2"
+  }
+}
+```
+
+## Benefits
+
+### **For Development Teams**
+
+1. **Consistency**: All developers have the same hook configuration
+2. **Flexibility**: Individual developers can choose activation
+3. **Standards**: Team coding standards are enforced when enabled
+4. **Version Control**: Hook configuration is tracked and versioned
+5. **Onboarding**: New developers get standardized setup
+
+### **For Individual Developers**
+
+1. **Choice**: Control over when hooks are active
+2. **Performance**: No unnecessary hook execution when disabled
+3. **Learning**: Gradual adoption of git hook practices
+4. **Debugging**: Easy to disable hooks for troubleshooting
+5. **Environment**: Works across different development environments
+
+### **For CI/CD Systems**
+
+1. **No Interference**: Hooks don't run in automated environments
+2. **Consistency**: Same hook logic available if needed
+3. **Flexibility**: Can enable hooks in specific CI scenarios
+4. **Reliability**: No unexpected hook failures in automation
+
+## Best Practices
+
+### **Team Adoption**
+
+1. **Start with disabled hooks** for new team members
+2. **Encourage gradual adoption** of hook activation
+3. **Document hook benefits** and usage patterns
+4. **Provide training** on hook configuration
+5. **Support troubleshooting** when hooks cause issues
+
+### **Hook Development**
+
+1. **Keep hooks lightweight** and fast
+2. **Provide clear error messages** when hooks fail
+3. **Include helpful activation instructions** in disabled state
+4. **Test hooks in both enabled and disabled states**
+5. **Document hook requirements** and dependencies
+
+### **Configuration Management**
+
+1. **Commit hook files** to version control
+2. **Ignore activation files** in .gitignore
+3. **Document activation methods** clearly
+4. **Provide examples** for common use cases
+5. **Maintain backward compatibility** when updating hooks
+
+## Troubleshooting Guide
+
+### **Common Issues**
+
+#### **Hooks Running When Not Expected**
+
+```bash
+# Check all activation methods
+echo "Environment variable: $HUSKY_ENABLED"
+echo "Local file exists: $([ -f .husky-enabled ] && echo "yes" || echo "no")"
+echo "Global config: $(git config --global --get husky.enabled)"
+```
+
+#### **Hooks Not Running When Expected**
+
+```bash
+# Verify hook files exist and are executable
+ls -la .husky/
+chmod +x .husky/pre-commit
+chmod +x .husky/commit-msg
+```
+
+#### **Permission Denied Errors**
+
+```bash
+# Fix file permissions
+chmod +x .husky/_/husky.sh
+chmod +x .husky/pre-commit
+chmod +x .husky/commit-msg
+```
+
+### **Debug Mode**
+
+Enable debug output to troubleshoot hook issues:
+
+```bash
+export HUSKY_DEBUG=1
+export HUSKY_ENABLED=1
+git commit -m "test: debug commit"
+```
+
+## Future Enhancements
+
+### **Planned Improvements**
+
+1. **Hook Configuration File**: YAML/JSON configuration for hook behavior
+2. **Selective Hook Activation**: Enable/disable specific hooks individually
+3. **Hook Performance Metrics**: Track execution time and success rates
+4. **Integration with IDEs**: IDE-specific activation methods
+5. **Remote Configuration**: Team-wide hook settings via configuration
+
+### **Extension Points**
+
+1. **Custom Hook Scripts**: Easy addition of project-specific hooks
+2. **Hook Templates**: Reusable hook patterns for common tasks
+3. **Conditional Logic**: Complex activation rules based on context
+4. **Notification System**: Hook status reporting and alerts
+5. **Analytics**: Hook usage and effectiveness tracking
+
+## Conclusion
+
+The conditional Husky activation system provides an elegant solution to the
+challenges  of git hook management in team environments. By committing
+standardized hooks while making activation optional, it balances consistency
+with flexibility, enabling teams to maintain coding standards without forcing compliance.
+
+This approach supports gradual adoption, respects individual preferences, and
+provides a solid foundation for git hook practices that can evolve with team needs
+and project requirements.
+
+---
+
+**Related Documents**:
+
+- [Git Hooks Best Practices](./git-hooks-best-practices.md)
+- [Code Quality Standards](./code-quality-standards.md)
+- [Development Workflow](./development-workflow.md)
+
+**Maintainer**: Development Team
+**Review Schedule**: Quarterly
+**Next Review**: 2025-11-21

doc/image-hosting-guide.md

@@ -25,6 +25,7 @@
 ## Why This Happens
 
 In development mode, we enable SharedArrayBuffer for fast SQLite operations, which requires:
+
 - `Cross-Origin-Opener-Policy: same-origin`
 - `Cross-Origin-Embedder-Policy: require-corp`
 
@@ -35,6 +36,7 @@ These headers create a **cross-origin isolated environment** that blocks resourc
 ### 1. Use Supported Image Hosting Services
 
 **Recommended services that work well:**
+
 - **Imgur**: Free, no registration required, direct links
 - **GitHub**: If you have images in repositories
 - **Unsplash**: For stock photos
@@ -45,6 +47,7 @@ These headers create a **cross-origin isolated environment** that blocks resourc
 If you frequently use images from a specific domain, add a proxy:
 
 #### Step 1: Add Proxy to `vite.config.common.mts`
+
 ```typescript
 '/yourservice-proxy': {
   target: 'https://yourservice.com',
@@ -63,6 +66,7 @@ If you frequently use images from a specific domain, add a proxy:
 ```
 
 #### Step 2: Update Transform Function in `src/libs/util.ts`
+
 ```typescript
 // Transform YourService URLs to use proxy
 if (imageUrl.startsWith("https://yourservice.com/")) {
@@ -74,6 +78,7 @@ if (imageUrl.startsWith("https://yourservice.com/")) {
 ### 3. Use Alternative Image Sources
 
 For frequently failing domains, consider:
+
 - Upload images to Imgur or GitHub
 - Use a CDN with proper CORS headers
 - Host images on your own domain with CORS enabled
@@ -81,11 +86,13 @@ For frequently failing domains, consider:
 ## Development vs Production
 
 ### Development Mode
+
 - Images from supported services work through proxies
 - Unsupported images may fail to load
 - Console warnings show which images have issues
 
 ### Production Mode
+
 - All images load directly without proxies
 - No CORS restrictions in production
 - Better performance without proxy overhead
@@ -93,6 +100,7 @@ For frequently failing domains, consider:
 ## Testing Image Sources
 
 ### Check if an Image Source Works
+
 ```bash
 # Test in browser console:
 fetch('https://example.com/image.jpg', { mode: 'cors' })
@@ -101,6 +109,7 @@ fetch('https://example.com/image.jpg', { mode: 'cors' })
 ```
 
 ### Visual Testing
+
 ```typescript
 import { createTestImageElements } from './libs/test-cors-images';
 createTestImageElements(); // Creates visual test panel
@@ -109,30 +118,36 @@ createTestImageElements(); // Creates visual test panel
 ## Common Error Messages
 
 ### `ERR_BLOCKED_BY_RESPONSE.NotSameOriginAfterDefaultedToSameOriginByCoep`
+
 **Cause**: Image source doesn't send required CORS headers
 **Solution**: Use a supported image hosting service or add a proxy
 
 ### `ERR_NETWORK` or `ERR_INTERNET_DISCONNECTED`
+
 **Cause**: Proxy service is unavailable
 **Solution**: Check internet connection or use alternative image source
 
 ### Images Load in Production but Not Development
+
 **Cause**: Normal behavior - development has stricter CORS requirements
 **Solution**: Use supported image sources for development testing
 
 ## Best Practices
 
 ### For New Projects
+
 1. Use supported image hosting services from the start
 2. Upload user images to Imgur or similar service
 3. Host critical images on your own domain with CORS enabled
 
 ### For Existing Projects
+
 1. Identify frequently used image domains in console warnings
 2. Add proxies for the most common domains
 3. Gradually migrate to supported image hosting services
 
 ### For User-Generated Content
+
 1. Provide upload functionality to supported services
 2. Validate image URLs against supported domains
 3. Show helpful error messages for unsupported sources
@@ -140,17 +155,20 @@ createTestImageElements(); // Creates visual test panel
 ## Troubleshooting
 
 ### Image Not Loading?
+
 1. Check browser console for error messages
 2. Verify the domain is in the supported list
 3. Test if the image loads in production mode
 4. Consider adding a proxy for that domain
 
 ### Proxy Not Working?
+
 1. Check if the target service allows proxying
 2. Verify CORS headers are being set correctly
 3. Test with a simpler image URL from the same domain
 
 ### Performance Issues?
+
 1. Proxies add latency in development only
 2. Production uses direct image loading
 3. Consider using a local image cache for development
@@ -158,6 +176,7 @@ createTestImageElements(); // Creates visual test panel
 ## Quick Fixes
 
 ### For Immediate Issues
+
 ```typescript
 // Temporary fallback: disable CORS headers for testing
 // In vite.config.common.mts, comment out:
@@ -166,9 +185,11 @@ createTestImageElements(); // Creates visual test panel
 //   'Cross-Origin-Embedder-Policy': 'require-corp'
 // },
 ```
+
 **Note**: This disables SharedArrayBuffer performance benefits.
 
 ### For Long-term Solution
+
 - Use supported image hosting services
 - Add proxies for frequently used domains
 - Migrate critical images to your own CORS-enabled CDN
@@ -177,4 +198,4 @@ createTestImageElements(); // Creates visual test panel
 
 The cross-origin isolated environment is necessary for SharedArrayBuffer performance but requires careful image source management. Use the supported services, add proxies for common domains, and accept that some external images may not work in development mode.
 
-This is a development-only limitation - production deployments work with any image source. 
+This is a development-only limitation - production deployments work with any image source.

doc/logging-configuration.md

@@ -101,6 +101,7 @@ Database logging continues to work regardless of console log level settings. All
 ### No Logs Appearing
 
 Check your `VITE_LOG_LEVEL` setting:
+
 ```bash
 echo $VITE_LOG_LEVEL
 ```
@@ -108,6 +109,7 @@ echo $VITE_LOG_LEVEL
 ### Too Many Logs
 
 Reduce verbosity by setting a lower log level:
+
 ```bash
 VITE_LOG_LEVEL=warn
 ```

doc/migration-fence-definition.md

@@ -9,6 +9,7 @@ This document defines the **migration fence** - the boundary between the legacy
 ## Current Migration Status
 
 ### ✅ Completed Components
+
 - **SQLite Database Service**: Fully implemented with absurd-sql
 - **Platform Service Layer**: Unified database interface across platforms
 - **PlatformServiceMixin**: Centralized database access with caching and utilities
@@ -17,12 +18,14 @@ This document defines the **migration fence** - the boundary between the legacy
 - **Data Export/Import**: Backup and restore functionality
 
 ### 🔄 Active Migration Components
+
 - **Settings Migration**: Core user settings transferred
 - **Account Migration**: Identity and key management
 - **Contact Migration**: User contact data (via import interface)
 - **DatabaseUtil Migration**: Moving functions to PlatformServiceMixin
 
 ### ❌ Legacy Components (Fence Boundary)
+
 - **Dexie Database**: Legacy IndexedDB storage (disabled by default)
 - **Dexie-Specific Code**: Direct database access patterns
 - **Legacy Migration Paths**: Old data transfer methods
@@ -45,6 +48,7 @@ export const PlatformServiceMixin = {
 ```
 
 **Fence Rule**: All database operations must use:
+
 - `this.$db()` for read operations
 - `this.$exec()` for write operations
 - `this.$settings()` for settings access
@@ -64,6 +68,7 @@ export class PlatformServiceFactory {
 ```
 
 **Fence Rule**: All database operations must use:
+
 - `PlatformService.dbQuery()` for read operations
 - `PlatformService.dbExec()` for write operations
 - No direct `db.` or `accountsDBPromise` access in application code
@@ -71,6 +76,7 @@ export class PlatformServiceFactory {
 ### 3. Data Access Patterns
 
 #### ✅ Allowed (Inside Fence)
+
 ```typescript
 // Use PlatformServiceMixin for all database operations
 const contacts = await this.$contacts();
@@ -79,6 +85,7 @@ const result = await this.$db("SELECT * FROM contacts WHERE did = ?", [accountDi
 ```
 
 #### ❌ Forbidden (Outside Fence)
+
 ```typescript
 // Direct Dexie access (legacy pattern)
 const contacts = await db.contacts.where('did').equals(accountDid).toArray();
@@ -98,6 +105,7 @@ export async function compareDatabases(): Promise<DataComparison> {
 ```
 
 **Fence Rule**: Migration tools are the exclusive interface between:
+
 - Legacy Dexie database
 - New SQLite database
 - Data comparison and transfer operations
@@ -107,11 +115,13 @@ export async function compareDatabases(): Promise<DataComparison> {
 ### 1. Code Development Rules
 
 #### New Feature Development
+
 - **Always** use `PlatformServiceMixin` for database operations
 - **Never** import or reference Dexie directly
 - **Always** use mixin methods like `this.$settings()`, `this.$contacts()`
 
 #### Legacy Code Maintenance
+
 - **Only** modify Dexie code for migration purposes
 - **Always** add migration tests for schema changes
 - **Never** add new Dexie-specific features
@@ -119,11 +129,13 @@ export async function compareDatabases(): Promise<DataComparison> {
 ### 2. Data Integrity Rules
 
 #### Migration Safety
+
 - **Always** create backups before migration
 - **Always** verify data integrity after migration
 - **Never** delete legacy data until verified
 
 #### Rollback Strategy
+
 - **Always** maintain ability to rollback to Dexie
 - **Always** preserve migration logs
 - **Never** assume migration is irreversible
@@ -131,6 +143,7 @@ export async function compareDatabases(): Promise<DataComparison> {
 ### 3. Testing Requirements
 
 #### Migration Testing
+
 ```typescript
 // Required test pattern for migration
 describe('Database Migration', () => {
@@ -144,6 +157,7 @@ describe('Database Migration', () => {
 ```
 
 #### Application Testing
+
 ```typescript
 // Required test pattern for application features
 describe('Feature with Database', () => {
@@ -159,6 +173,7 @@ describe('Feature with Database', () => {
 ### 1. Static Analysis
 
 #### ESLint Rules
+
 ```json
 {
   "rules": {
@@ -178,6 +193,7 @@ describe('Feature with Database', () => {
 ```
 
 #### TypeScript Rules
+
 ```json
 {
   "compilerOptions": {
@@ -190,6 +206,7 @@ describe('Feature with Database', () => {
 ### 2. Runtime Checks
 
 #### Development Mode Validation
+
 ```typescript
 // Development-only fence validation
 if (import.meta.env.DEV) {
@@ -198,6 +215,7 @@ if (import.meta.env.DEV) {
 ```
 
 #### Production Safety
+
 ```typescript
 // Production fence enforcement
 if (import.meta.env.PROD) {
@@ -209,6 +227,7 @@ if (import.meta.env.PROD) {
 ## Migration Status Checklist
 
 ### ✅ Completed
+
 - [x] PlatformServiceMixin implementation
 - [x] SQLite database service
 - [x] Migration tools
@@ -217,11 +236,13 @@ if (import.meta.env.PROD) {
 - [x] ActiveDid migration
 
 ### 🔄 In Progress
+
 - [ ] Contact migration
 - [ ] DatabaseUtil to PlatformServiceMixin migration
 - [ ] File-by-file migration
 
 ### ❌ Not Started
+
 - [ ] Legacy Dexie removal
 - [ ] Final cleanup and validation
 
@@ -240,4 +261,4 @@ if (import.meta.env.PROD) {
 **Created**: 2025-07-05
 **Status**: Active Migration Phase
 **Last Updated**: 2025-07-05
-**Note**: Migration fence now implemented through PlatformServiceMixin instead of USE_DEXIE_DB constant 
+**Note**: Migration fence now implemented through PlatformServiceMixin instead of USE_DEXIE_DB constant

doc/migration-progress-tracker.md

@@ -3,6 +3,7 @@
 ## Per-File Migration Workflow (MANDATORY)
 
 For each file migrated:
+
 1. **First**, migrate to PlatformServiceMixin (replace all databaseUtil usage, etc.).
 2. **Immediately after**, standardize notify helper usage (property + created() pattern) and fix any related linter/type errors.
 
@@ -25,22 +26,26 @@ This document tracks the progress of the 2-day sprint to complete PlatformServic
 ## ✅ **DAY 1: PlatformServiceMixin Completion (COMPLETE)**
 
 ### **Phase 1: Remove Circular Dependency (COMPLETE)**
+
 **Status**: ✅ **COMPLETE**
 **Issue**: PlatformServiceMixin imports `memoryLogs` from databaseUtil
 **Solution**: Create self-contained memoryLogs implementation
 
-#### **Tasks**:
+#### **Tasks**
+
 - [x] **Step 1.1**: Remove `memoryLogs` import from PlatformServiceMixin.ts ✅
 - [x] **Step 1.2**: Add self-contained `_memoryLogs` array to PlatformServiceMixin ✅
 - [x] **Step 1.3**: Add `$appendToMemoryLogs()` method to PlatformServiceMixin ✅
 - [x] **Step 1.4**: Update logger.ts to use self-contained memoryLogs ✅
 - [x] **Step 1.5**: Test memoryLogs functionality ✅
 
-#### **Files Modified**:
+#### **Files Modified**
+
 - `src/utils/PlatformServiceMixin.ts` ✅
 - `src/utils/logger.ts` ✅
 
-#### **Validation**:
+#### **Validation**
+
 - [x] No circular dependency errors ✅
 - [x] memoryLogs functionality works correctly ✅
 - [x] Linting passes ✅
@@ -48,20 +53,24 @@ This document tracks the progress of the 2-day sprint to complete PlatformServic
 ---
 
 ### **Phase 2: Add Missing Utility Functions (COMPLETE)**
+
 **Status**: ✅ **COMPLETE**
 **Missing Functions**: `generateInsertStatement`, `generateUpdateStatement`
 
-#### **Tasks**:
+#### **Tasks**
+
 - [x] **Step 2.1**: Add `_generateInsertStatement()` private method to PlatformServiceMixin ✅
 - [x] **Step 2.2**: Add `_generateUpdateStatement()` private method to PlatformServiceMixin ✅
 - [x] **Step 2.3**: Add `$generateInsertStatement()` public wrapper method ✅
 - [x] **Step 2.4**: Add `$generateUpdateStatement()` public wrapper method ✅
 - [x] **Step 2.5**: Test both utility functions ✅
 
-#### **Files Modified**:
+#### **Files Modified**
+
 - `src/utils/PlatformServiceMixin.ts` ✅
 
-#### **Validation**:
+#### **Validation**
+
 - [x] Both functions generate correct SQL ✅
 - [x] Parameter handling works correctly ✅
 - [x] Type safety maintained ✅
@@ -69,18 +78,22 @@ This document tracks the progress of the 2-day sprint to complete PlatformServic
 ---
 
 ### **Phase 3: Update Type Definitions (COMPLETE)**
+
 **Status**: ✅ **COMPLETE**
 **Goal**: Add new methods to TypeScript interfaces
 
-#### **Tasks**:
+#### **Tasks**
+
 - [x] **Step 3.1**: Add new methods to `IPlatformServiceMixin` interface ✅
 - [x] **Step 3.2**: Add new methods to `ComponentCustomProperties` interface ✅
 - [x] **Step 3.3**: Verify TypeScript compilation ✅
 
-#### **Files Modified**:
+#### **Files Modified**
+
 - `src/utils/PlatformServiceMixin.ts` (interface definitions) ✅
 
-#### **Validation**:
+#### **Validation**
+
 - [x] TypeScript compilation passes ✅
 - [x] All new methods properly typed ✅
 - [x] No type errors in existing code ✅
@@ -88,17 +101,20 @@ This document tracks the progress of the 2-day sprint to complete PlatformServic
 ---
 
 ### **Phase 4: Testing & Validation (COMPLETE)**
+
 **Status**: ✅ **COMPLETE**
 **Goal**: Ensure PlatformServiceMixin is fully functional
 
-#### **Tasks**:
+#### **Tasks**
+
 - [x] **Step 4.1**: Create test component to verify all methods ✅
 - [x] **Step 4.2**: Run comprehensive linting ✅
 - [x] **Step 4.3**: Run TypeScript type checking ✅
 - [x] **Step 4.4**: Test caching functionality ✅
 - [x] **Step 4.5**: Test database operations ✅
 
-#### **Validation**:
+#### **Validation**
+
 - [x] All tests pass ✅
 - [x] No linting errors ✅
 - [x] No TypeScript errors ✅
@@ -108,10 +124,12 @@ This document tracks the progress of the 2-day sprint to complete PlatformServic
 ---
 
 ### **Phase 5: Utility Files Migration (COMPLETE)**
+
 **Status**: ✅ **COMPLETE**
 **Goal**: Remove all remaining databaseUtil imports from utility files
 
-#### **Tasks**:
+#### **Tasks**
+
 - [x] **Step 5.1**: Migrate `src/services/deepLinks.ts` ✅
   - Replaced `logConsoleAndDb` with `console.error`
   - Removed databaseUtil import
@@ -121,7 +139,8 @@ This document tracks the progress of the 2-day sprint to complete PlatformServic
   - Updated all async calls to use proper async pattern
 - [x] **Step 5.3**: Verify no remaining databaseUtil imports ✅
 
-#### **Validation**:
+#### **Validation**
+
 - [x] No databaseUtil imports in any TypeScript files ✅
 - [x] No databaseUtil imports in any Vue files ✅
 - [x] All functions work correctly ✅
@@ -131,13 +150,16 @@ This document tracks the progress of the 2-day sprint to complete PlatformServic
 ## 🎯 **DAY 2: Migrate All 52 Files (READY TO START)**
 
 ### **Migration Strategy**
+
 **Priority Order**:
+
 1. **Views** (25 files) - User-facing components
 2. **Components** (15 files) - Reusable UI components  
 3. **Services** (8 files) - Business logic
 4. **Utils** (4 files) - Utility functions
 
 ### **Migration Pattern for Each File**
+
 ```typescript
 // 1. Add PlatformServiceMixin
 import { PlatformServiceMixin } from "@/utils/PlatformServiceMixin";
@@ -155,6 +177,7 @@ export default class ComponentName extends Vue {
 ```
 
 ### **Common Replacements**
+
 - `generateInsertStatement` → `this.$generateInsertStatement`
 - `generateUpdateStatement` → `this.$generateUpdateStatement`
 - `parseJsonField` → `this._parseJsonField`
@@ -168,6 +191,7 @@ export default class ComponentName extends Vue {
 ## 📋 **File Migration Checklist**
 
 ### **Views (25 files) - Priority 1**
+
 **Progress**: 6/25 (24%)
 
 - [ ] QuickActionBvcEndView.vue
@@ -209,6 +233,7 @@ export default class ComponentName extends Vue {
 - [ ] UserProfileView.vue
 
 ### **Components (15 files) - Priority 2**
+
 **Progress**: 9/15 (60%)
 
 - [x] UserNameDialog.vue ✅ **MIGRATED**
@@ -233,6 +258,7 @@ export default class ComponentName extends Vue {
 - [x] IconRenderer.vue ✅ MIGRATED & HUMAN TESTED 2024-12-19 (0 min, no migration needed - already compliant)
 
 ### **Services (8 files) - Priority 3**
+
 **Progress**: 2/8 (25%)
 
 - [x] api.ts ✅ MIGRATED 2024-12-19 (0 min, no migration needed - already compliant)
@@ -241,6 +267,7 @@ export default class ComponentName extends Vue {
 - [ ] deepLinks.ts
 
 ### **Utils (4 files) - Priority 4**
+
 **Progress**: 1/4 (25%)
 
 - [ ] LogCollector.ts
@@ -253,6 +280,7 @@ export default class ComponentName extends Vue {
 ## 🛠️ **Migration Tools**
 
 ### **Migration Helper Script**
+
 ```bash
 # Track progress
 ./scripts/migration-helper.sh progress
@@ -277,6 +305,7 @@ export default class ComponentName extends Vue {
 ```
 
 ### **Validation Commands**
+
 ```bash
 # Check for remaining databaseUtil imports
 find src -name "*.vue" -o -name "*.ts" | xargs grep -l "import.*databaseUtil"
@@ -296,12 +325,14 @@ find src -name "*.vue" -o -name "*.ts" | xargs grep -l "import.*databaseUtil" |
 ## 📊 **Progress Tracking**
 
 ### **Day 1 Progress**
+
 - [ ] Phase 1: Circular dependency resolved
 - [ ] Phase 2: Utility functions added
 - [ ] Phase 3: Type definitions updated
 - [ ] Phase 4: Testing completed
 
 ### **Day 2 Progress**
+
 - [ ] Views migrated (0/25)
 - [ ] Components migrated (0/15)
 - [ ] Services migrated (0/8)
@@ -309,6 +340,7 @@ find src -name "*.vue" -o -name "*.ts" | xargs grep -l "import.*databaseUtil" |
 - [ ] Validation completed
 
 ### **Overall Progress**
+
 - **Total files to migrate**: 52
 - **Files migrated**: 3
 - **Progress**: 6%
@@ -318,6 +350,7 @@ find src -name "*.vue" -o -name "*.ts" | xargs grep -l "import.*databaseUtil" |
 ## 🎯 **Success Criteria**
 
 ### **Day 1 Success Criteria**
+
 - [ ] PlatformServiceMixin has no circular dependencies
 - [ ] All utility functions implemented and tested
 - [ ] Type definitions complete and accurate
@@ -325,6 +358,7 @@ find src -name "*.vue" -o -name "*.ts" | xargs grep -l "import.*databaseUtil" |
 - [ ] TypeScript compilation passes
 
 ### **Day 2 Success Criteria**
+
 - [ ] 0 files importing databaseUtil
 - [ ] All 52 files migrated to PlatformServiceMixin
 - [ ] No runtime errors in migrated components
@@ -332,6 +366,7 @@ find src -name "*.vue" -o -name "*.ts" | xargs grep -l "import.*databaseUtil" |
 - [ ] Performance maintained or improved
 
 ### **Overall Success Criteria**
+
 - [ ] Complete elimination of databaseUtil dependency
 - [ ] PlatformServiceMixin is the single source of truth for database operations
 - [ ] Migration fence is fully implemented
@@ -354,14 +389,17 @@ find src -name "*.vue" -o -name "*.ts" | xargs grep -l "import.*databaseUtil" |
 ## 📝 **Notes & Issues**
 
 ### **Current Issues**
+
 - None identified yet
 
 ### **Decisions Made**
+
 - PlatformServiceMixin approach chosen over USE_DEXIE_DB constant
 - Self-contained utility functions preferred over imports
 - Priority order: Views → Components → Services → Utils
 
 ### **Lessons Learned**
+
 - To be filled as migration progresses
 
 ---
@@ -369,6 +407,7 @@ find src -name "*.vue" -o -name "*.ts" | xargs grep -l "import.*databaseUtil" |
 ## 🔄 **Daily Updates**
 
 ### **Day 1 Updates**
+
 - [ ] Start time: _____
 - [ ] Phase 1 completion: _____
 - [ ] Phase 2 completion: _____
@@ -377,6 +416,7 @@ find src -name "*.vue" -o -name "*.ts" | xargs grep -l "import.*databaseUtil" |
 - [ ] End time: _____
 
 ### **Day 2 Updates**
+
 - [ ] Start time: _____
 - [ ] Views migration completion: _____
 - [ ] Components migration completion: _____
@@ -390,16 +430,19 @@ find src -name "*.vue" -o -name "*.ts" | xargs grep -l "import.*databaseUtil" |
 ## 🆘 **Contingency Plans**
 
 ### **If Day 1 Takes Longer**
+
 - Focus on core functionality first
 - Defer advanced utility functions to Day 2
 - Prioritize circular dependency resolution
 
 ### **If Day 2 Takes Longer**
+
 - Focus on high-impact views first
 - Batch similar components together
 - Use automated scripts for common patterns
 
 ### **If Issues Arise**
+
 - Document specific problems in Notes section
 - Create targeted fixes
 - Maintain backward compatibility during transition
@@ -421,4 +464,4 @@ These practices ensure maintainability, consistency, and type safety for all not
 ---
 
 **Last Updated**: $(date)
-**Next Review**: After each phase completion 
+**Next Review**: After each phase completion

doc/migration-quick-reference.md

@@ -63,6 +63,7 @@ export default class ComponentName extends Vue {
 ## ✅ **Validation Checklist**
 
 After each file migration:
+
 - [ ] No databaseUtil imports
 - [ ] PlatformServiceMixin added
 - [ ] Method calls updated
@@ -91,4 +92,4 @@ npm run lint && npx tsc --noEmit
 ---
 
 **Last Updated**: $(date)
-**Full Documentation**: `doc/migration-progress-tracker.md` 
+**Full Documentation**: `doc/migration-progress-tracker.md`

doc/migration-readiness-summary.md

@@ -11,11 +11,14 @@
 ## 🎯 **Migration Overview**
 
 ### **Goal**
+
 Complete the TimeSafari database migration from Dexie to SQLite by:
+
 1. **Day 1**: Finish PlatformServiceMixin implementation (4-6 hours)
 2. **Day 2**: Migrate all 52 files to PlatformServiceMixin (6-8 hours)
 
 ### **Current Status**
+
 - ✅ **PlatformServiceMixin**: 95% complete (1,301 lines)
 - ✅ **Migration Tools**: Ready and tested
 - ✅ **Documentation**: Complete and cross-machine accessible
@@ -27,22 +30,30 @@ Complete the TimeSafari database migration from Dexie to SQLite by:
 ## 📊 **File Breakdown**
 
 ### **Views (42 files) - Priority 1**
+
 User-facing components that need immediate attention:
+
 - 25 files from original list
 - 17 additional files identified by migration helper
 
 ### **Components (9 files) - Priority 2**
+
 Reusable UI components:
+
 - FeedFilters.vue, GiftedDialog.vue, GiftedPrompts.vue
 - ImageMethodDialog.vue, OfferDialog.vue, OnboardingDialog.vue
 - PhotoDialog.vue, PushNotificationPermission.vue, UserNameDialog.vue
 
 ### **Services (1 file) - Priority 3**
+
 Business logic:
+
 - deepLinks.ts
 
 ### **Utils (3 files) - Priority 4**
+
 Utility functions:
+
 - util.ts, test/index.ts, PlatformServiceMixin.ts (circular dependency fix)
 
 ---
@@ -50,17 +61,21 @@ Utility functions:
 ## 🛠️ **Available Tools**
 
 ### **Migration Helper Script**
+
 ```bash
 ./scripts/migration-helper.sh [command]
 ```
+
 **Commands**: progress, files, patterns, template, validate, next, all
 
 ### **Progress Tracking**
+
 - **Main Tracker**: `doc/migration-progress-tracker.md`
 - **Quick Reference**: `doc/migration-quick-reference.md`
 - **Completion Plan**: `doc/platformservicemixin-completion-plan.md`
 
 ### **Validation Commands**
+
 ```bash
 # Check progress
 ./scripts/migration-helper.sh progress
@@ -77,6 +92,7 @@ find src -name "*.vue" -o -name "*.ts" | xargs grep -l "import.*databaseUtil" |
 ## 🔄 **Migration Pattern**
 
 ### **Standard Template**
+
 ```typescript
 // 1. Add import
 import { PlatformServiceMixin } from "@/utils/PlatformServiceMixin";
@@ -94,6 +110,7 @@ export default class ComponentName extends Vue {
 ```
 
 ### **Common Replacements**
+
 | Old | New |
 |-----|-----|
 | `generateInsertStatement` | `this.$generateInsertStatement` |
@@ -109,19 +126,23 @@ export default class ComponentName extends Vue {
 ## 🎯 **Day 1 Plan: PlatformServiceMixin Completion**
 
 ### **Phase 1: Remove Circular Dependency (30 min)**
+
 - Remove `memoryLogs` import from PlatformServiceMixin
 - Add self-contained memoryLogs implementation
 - Update logger.ts
 
 ### **Phase 2: Add Missing Functions (1 hour)**
+
 - Add `generateInsertStatement` and `generateUpdateStatement`
 - Test both utility functions
 
 ### **Phase 3: Update Types (30 min)**
+
 - Add new methods to TypeScript interfaces
 - Verify compilation
 
 ### **Phase 4: Testing (1 hour)**
+
 - Comprehensive testing and validation
 - Ensure no circular dependencies
 
@@ -130,17 +151,20 @@ export default class ComponentName extends Vue {
 ## 🎯 **Day 2 Plan: File Migration**
 
 ### **Strategy**
+
 1. **Views First** (42 files) - High impact, user-facing
 2. **Components** (9 files) - Reusable UI elements
 3. **Services** (1 file) - Business logic
 4. **Utils** (3 files) - Utility functions
 
 ### **Batch Processing**
+
 - Process similar files together
 - Use automated scripts for common patterns
 - Validate after each batch
 
 ### **Success Criteria**
+
 - 0 files importing databaseUtil
 - All tests passing
 - No runtime errors
@@ -151,12 +175,14 @@ export default class ComponentName extends Vue {
 ## 🚀 **Expected Benefits**
 
 ### **Immediate Benefits**
+
 - **80% reduction** in database boilerplate code
 - **Eliminated circular dependencies**
 - **Centralized caching** for performance
 - **Type-safe** database operations
 
 ### **Long-term Benefits**
+
 - **Simplified testing** with mockable mixin
 - **Consistent error handling** across components
 - **Ready for SQLite-only mode**
@@ -167,18 +193,21 @@ export default class ComponentName extends Vue {
 ## 📋 **Pre-Migration Checklist**
 
 ### **Environment Ready**
+
 - [x] Migration helper script tested and working
 - [x] Progress tracking system operational
 - [x] Documentation complete and accessible
 - [x] Validation commands working
 
 ### **Tools Available**
+
 - [x] Automated progress tracking
 - [x] Migration pattern templates
 - [x] Validation scripts
 - [x] Cross-machine documentation
 
 ### **Knowledge Base**
+
 - [x] Common replacement patterns documented
 - [x] Migration templates ready
 - [x] Troubleshooting guides available
@@ -191,12 +220,14 @@ export default class ComponentName extends Vue {
 **All systems are ready for the 2-day migration sprint.**
 
 ### **Next Steps**
+
 1. **Start Day 1**: Complete PlatformServiceMixin
 2. **Use tracking tools**: Monitor progress with helper script
 3. **Follow documentation**: Use provided templates and patterns
 4. **Validate frequently**: Run checks after each phase
 
 ### **Success Metrics**
+
 - **Day 1**: PlatformServiceMixin 100% complete, no circular dependencies
 - **Day 2**: 0 files importing databaseUtil, all tests passing
 - **Overall**: Ready for Phase 3 cleanup and optimization
@@ -210,4 +241,4 @@ export default class ComponentName extends Vue {
 ---
 
 **Last Updated**: $(date)
-**Next Review**: After Day 1 completion 
+**Next Review**: After Day 1 completion

doc/migration-roadmap-next-steps.md

@@ -7,6 +7,7 @@ This document outlines the immediate next steps for completing the TimeSafari da
 ## Current Status Summary
 
 ### ✅ **Completed Achievements**
+
 1. **Circular Dependencies Resolved** - No active circular dependencies blocking development
 2. **PlatformServiceMixin Implemented** - Core functionality with caching and utilities
 3. **Migration Tools Ready** - Data comparison and transfer utilities functional
@@ -14,6 +15,7 @@ This document outlines the immediate next steps for completing the TimeSafari da
 5. **Documentation Updated** - All docs reflect current PlatformServiceMixin approach
 
 ### 🔄 **Current Phase: Phase 2 - Active Migration**
+
 - **DatabaseUtil Migration**: 52 files still importing databaseUtil
 - **Contact Migration**: Framework ready, implementation in progress
 - **File-by-File Migration**: Ready to begin systematic migration
@@ -23,6 +25,7 @@ This document outlines the immediate next steps for completing the TimeSafari da
 ### 🔴 **Priority 1: Complete PlatformServiceMixin Independence**
 
 #### **Step 1.1: Remove memoryLogs Dependency**
+
 ```typescript
 // Current: PlatformServiceMixin imports from databaseUtil
 import { memoryLogs } from "@/db/databaseUtil";
@@ -32,12 +35,15 @@ const memoryLogs: string[] = [];
 ```
 
 **Files to modify**:
+
 - `src/utils/PlatformServiceMixin.ts` - Remove import, add self-contained implementation
 
 **Estimated time**: 30 minutes
 
 #### **Step 1.2: Add Missing Utility Methods**
+
 Add these methods to PlatformServiceMixin:
+
 - `$parseJson()` - Self-contained JSON parsing
 - `$generateInsertStatement()` - SQL generation
 - `$generateUpdateStatement()` - SQL generation
@@ -48,6 +54,7 @@ Add these methods to PlatformServiceMixin:
 ### 🟡 **Priority 2: Start File-by-File Migration**
 
 #### **Step 2.1: Migrate Critical Files First**
+
 Based on the migration plan, start with these high-priority files:
 
 1. **`src/App.vue`** - Main application (highest impact)
@@ -57,6 +64,7 @@ Based on the migration plan, start with these high-priority files:
 5. **`src/services/deepLinks.ts`** - Service layer
 
 **Migration pattern for each file**:
+
 ```typescript
 // 1. Remove databaseUtil import
 // Remove: import * as databaseUtil from "../db/databaseUtil";
@@ -82,7 +90,9 @@ Based on the migration plan, start with these high-priority files:
 ### 🟡 **Priority 3: Systematic File Migration**
 
 #### **Step 3.1: Migrate High-Usage Components (15 files)**
+
 Target components with databaseUtil imports:
+
 - `PhotoDialog.vue`
 - `FeedFilters.vue`
 - `UserNameDialog.vue`
@@ -97,7 +107,9 @@ Target components with databaseUtil imports:
 **Estimated time**: 15-30 hours
 
 #### **Step 3.2: Migrate High-Usage Views (20 files)**
+
 Target views with databaseUtil imports:
+
 - `IdentitySwitcherView.vue`
 - `ContactEditView.vue`
 - `ContactGiftingView.vue`
@@ -113,6 +125,7 @@ Target views with databaseUtil imports:
 **Estimated time**: 20-40 hours
 
 #### **Step 3.3: Migrate Remaining Files (27 files)**
+
 Complete migration of all remaining files with databaseUtil imports.
 
 **Estimated time**: 27-54 hours
@@ -120,6 +133,7 @@ Complete migration of all remaining files with databaseUtil imports.
 ### 🟢 **Priority 4: Contact Migration Completion**
 
 #### **Step 4.1: Complete Contact Migration Framework**
+
 - Implement contact import/export functionality
 - Add contact validation and error handling
 - Test contact migration with real data
@@ -127,6 +141,7 @@ Complete migration of all remaining files with databaseUtil imports.
 **Estimated time**: 4-8 hours
 
 #### **Step 4.2: User Testing and Validation**
+
 - Test migration with various data scenarios
 - Validate data integrity after migration
 - Performance testing with large datasets
@@ -138,7 +153,9 @@ Complete migration of all remaining files with databaseUtil imports.
 ### 🔵 **Priority 5: Cleanup and Optimization**
 
 #### **Step 5.1: Remove Unused databaseUtil Functions**
+
 After all files are migrated:
+
 - Remove unused functions from databaseUtil.ts
 - Update TypeScript interfaces
 - Clean up legacy code
@@ -146,6 +163,7 @@ After all files are migrated:
 **Estimated time**: 4-8 hours
 
 #### **Step 5.2: Performance Optimization**
+
 - Optimize PlatformServiceMixin caching
 - Add performance monitoring
 - Implement database query optimization
@@ -153,6 +171,7 @@ After all files are migrated:
 **Estimated time**: 8-16 hours
 
 #### **Step 5.3: Legacy Dexie Removal**
+
 - Remove Dexie dependencies
 - Clean up migration tools
 - Update build configurations
@@ -162,6 +181,7 @@ After all files are migrated:
 ## Migration Commands and Tools
 
 ### **Automated Migration Script**
+
 Create a script to help with bulk migrations:
 
 ```bash
@@ -193,6 +213,7 @@ echo "Please review and test the changes"
 ```
 
 ### **Migration Testing Commands**
+
 ```bash
 # Test individual file migration
 npm run test -- --grep "ComponentName"
@@ -213,18 +234,21 @@ npx tsc --noEmit
 ## Risk Mitigation
 
 ### **Incremental Migration Strategy**
+
 1. **One file at a time** - Minimize risk of breaking changes
 2. **Comprehensive testing** - Test each migration thoroughly
 3. **Rollback capability** - Keep databaseUtil.ts until migration complete
 4. **Documentation updates** - Update docs as methods are migrated
 
 ### **Testing Strategy**
+
 1. **Unit tests** - Test individual component functionality
 2. **Integration tests** - Test database operations
 3. **End-to-end tests** - Test complete user workflows
 4. **Performance tests** - Ensure no performance regression
 
 ### **Rollback Plan**
+
 1. **Git branches** - Each migration in separate branch
 2. **Backup files** - Keep original files until migration verified
 3. **Feature flags** - Ability to switch back to databaseUtil if needed
@@ -233,18 +257,21 @@ npx tsc --noEmit
 ## Success Metrics
 
 ### **Short-Term (This Week)**
+
 - [ ] PlatformServiceMixin completely independent
 - [ ] 5 critical files migrated
 - [ ] No new circular dependencies
 - [ ] All tests passing
 
 ### **Medium-Term (Next 2 Weeks)**
+
 - [ ] 35+ files migrated (70% completion)
 - [ ] Contact migration framework complete
 - [ ] Performance maintained or improved
 - [ ] User testing completed
 
 ### **Long-Term (Next Month)**
+
 - [ ] All 52 files migrated (100% completion)
 - [ ] databaseUtil.ts removed or minimal
 - [ ] Legacy Dexie code removed
@@ -253,12 +280,14 @@ npx tsc --noEmit
 ## Resource Requirements
 
 ### **Development Time**
+
 - **Immediate (This Week)**: 8-12 hours
 - **Medium-Term (Next 2 Weeks)**: 35-70 hours
 - **Long-Term (Next Month)**: 16-32 hours
 - **Total Estimated**: 59-114 hours
 
 ### **Testing Time**
+
 - **Unit Testing**: 20-30 hours
 - **Integration Testing**: 10-15 hours
 - **User Testing**: 8-12 hours
@@ -266,6 +295,7 @@ npx tsc --noEmit
 - **Total Testing**: 43-65 hours
 
 ### **Total Project Time**
+
 - **Development**: 59-114 hours
 - **Testing**: 43-65 hours
 - **Documentation**: 5-10 hours
@@ -274,6 +304,7 @@ npx tsc --noEmit
 ## Conclusion
 
 The migration is well-positioned for completion with:
+
 - ✅ **No blocking circular dependencies**
 - ✅ **PlatformServiceMixin mostly complete**
 - ✅ **Clear migration path defined**
@@ -287,4 +318,4 @@ The next steps focus on systematic file-by-file migration with proper testing an
 **Created**: 2025-07-05
 **Status**: Active Planning
 **Last Updated**: 2025-07-05
-**Note**: This roadmap is based on current codebase analysis and documented progress 
+**Note**: This roadmap is based on current codebase analysis and documented progress

doc/migration-security-checklist.md

@@ -352,4 +352,4 @@ This security audit checklist ensures that the database migration maintains the
 
 **Reviewed By**: _______________
 
-**Approved By**: _______________ 
+**Approved By**: _______________

doc/migration-to-wa-sqlite.md

@@ -29,12 +29,15 @@ This document outlines the migration process from Dexie.js to absurd-sql for the
 ## Migration Architecture
 
 ### Migration Fence
+
 The migration fence is now defined by the **PlatformServiceMixin** in `src/utils/PlatformServiceMixin.ts`:
+
 - **PlatformServiceMixin**: Centralized database access with caching and utilities
 - **Migration Tools**: Exclusive interface between legacy and new databases
 - **Service Layer**: All database operations go through PlatformService
 
 ### Migration Order
+
 The migration follows a specific order to maintain data integrity:
 
 1. **Accounts** (foundational - contains DIDs)
@@ -45,9 +48,11 @@ The migration follows a specific order to maintain data integrity:
 ## ActiveDid Migration ⭐ **NEW FEATURE**
 
 ### Problem Solved
+
 Previously, the `activeDid` setting was not migrated from Dexie to SQLite, causing users to lose their active identity after migration.
 
 ### Solution Implemented
+
 The migration now includes a dedicated step for migrating the `activeDid`:
 
 1. **Detection**: Identifies the `activeDid` from Dexie master settings
@@ -58,6 +63,7 @@ The migration now includes a dedicated step for migrating the `activeDid`:
 ### Implementation Details
 
 #### New Function: `migrateActiveDid()`
+
 ```typescript
 export async function migrateActiveDid(): Promise<MigrationResult> {
   // 1. Get Dexie settings to find the activeDid
@@ -76,13 +82,17 @@ export async function migrateActiveDid(): Promise<MigrationResult> {
    ```
 
 #### Enhanced `migrateSettings()` Function
+
 The settings migration now includes activeDid handling:
+
 - Extracts `activeDid` from Dexie master settings
 - Validates account existence in SQLite
 - Updates SQLite master settings with the `activeDid`
 
 #### Updated `migrateAll()` Function
+
 The complete migration now includes a dedicated step for activeDid:
+
 ```typescript
 // Step 3: Migrate ActiveDid (depends on accounts and settings)
 logger.info("[MigrationService] Step 3: Migrating activeDid...");
@@ -90,6 +100,7 @@ const activeDidResult = await migrateActiveDid();
 ```
 
 ### Benefits
+
 - ✅ **User Identity Preservation**: Users maintain their active identity
 - ✅ **Seamless Experience**: No need to manually select identity after migration
 - ✅ **Data Consistency**: Ensures all identity-related settings are preserved
@@ -98,17 +109,20 @@ const activeDidResult = await migrateActiveDid();
 ## Migration Process
 
 ### Phase 1: Preparation ✅
+
 - [x] PlatformServiceMixin implementation
 - [x] Implement data comparison tools
 - [x] Create migration service structure
 
 ### Phase 2: Core Migration ✅
+
 - [x] Account migration with `importFromMnemonic`
 - [x] Settings migration (excluding activeDid)
 - [x] **ActiveDid migration** ⭐ **COMPLETED**
 - [x] Contact migration framework
 
 ### Phase 3: Validation and Cleanup 🔄
+
 - [ ] Comprehensive data validation
 - [ ] Performance testing
 - [ ] User acceptance testing
@@ -117,6 +131,7 @@ const activeDidResult = await migrateActiveDid();
 ## Usage
 
 ### Manual Migration
+
 ```typescript
 import { migrateAll, migrateActiveDid } from '../services/indexedDBMigrationService';
 
@@ -128,6 +143,7 @@ const activeDidResult = await migrateActiveDid();
 ```
 
 ### Migration Verification
+
 ```typescript
 import { compareDatabases } from '../services/indexedDBMigrationService';
 
@@ -136,7 +152,9 @@ console.log('Migration differences:', comparison.differences);
 ```
 
 ### PlatformServiceMixin Integration
+
 After migration, use the mixin for all database operations:
+
 ```typescript
 // Use mixin methods for database access
 const contacts = await this.$contacts();
@@ -147,11 +165,13 @@ const result = await this.$db("SELECT * FROM contacts WHERE did = ?", [accountDi
 ## Error Handling
 
 ### ActiveDid Migration Errors
+
 - **Missing Account**: If the `activeDid` from Dexie doesn't exist in SQLite accounts
 - **Database Errors**: Connection or query failures
 - **Settings Update Failures**: Issues updating SQLite master settings
 
 ### Recovery Strategies
+
 1. **Automatic Recovery**: Migration continues even if activeDid migration fails
 2. **Manual Recovery**: Users can manually select their identity after migration
 3. **Fallback**: System creates new identity if none exists
@@ -159,11 +179,13 @@ const result = await this.$db("SELECT * FROM contacts WHERE did = ?", [accountDi
 ## Security Considerations
 
 ### Data Protection
+
 - All sensitive data (mnemonics, private keys) are encrypted
 - Migration preserves encryption standards
 - No plaintext data exposure during migration
 
 ### Identity Verification
+
 - ActiveDid migration validates account existence
 - Prevents setting non-existent identities as active
 - Maintains cryptographic integrity
@@ -171,6 +193,7 @@ const result = await this.$db("SELECT * FROM contacts WHERE did = ?", [accountDi
 ## Testing
 
 ### Migration Testing
+
 ```bash
 # Run migration
 npm run migrate
@@ -180,6 +203,7 @@ npm run test:migration
 ```
 
 ### ActiveDid Testing
+
    ```typescript
 // Test activeDid migration specifically
 const result = await migrateActiveDid();
@@ -188,6 +212,7 @@ expect(result.warnings).toContain('Successfully migrated activeDid');
 ```
 
 ### PlatformServiceMixin Testing
+
 ```typescript
 // Test mixin integration
 describe('PlatformServiceMixin', () => {
@@ -224,6 +249,7 @@ describe('PlatformServiceMixin', () => {
    - Verify caching and error handling work correctly
 
 ### Debugging
+
 ```typescript
 // Debug migration process
 import { logger } from '../utils/logger';
@@ -245,6 +271,7 @@ logger.debug('[Migration] Migration completed:', result);
 ## Migration Status Checklist
 
 ### ✅ Completed
+
 - [x] PlatformServiceMixin implementation
 - [x] SQLite database service
 - [x] Migration tools
@@ -253,11 +280,13 @@ logger.debug('[Migration] Migration completed:', result);
 - [x] ActiveDid migration
 
 ### 🔄 In Progress
+
 - [ ] Contact migration
 - [ ] DatabaseUtil to PlatformServiceMixin migration
 - [ ] File-by-file migration
 
 ### ❌ Not Started
+
 - [ ] Legacy Dexie removal
 - [ ] Final cleanup and validation
 
@@ -267,4 +296,4 @@ logger.debug('[Migration] Migration completed:', result);
 **Created**: 2025-07-05
 **Status**: Active Migration Phase
 **Last Updated**: 2025-07-05
-**Note**: Migration fence now implemented through PlatformServiceMixin instead of USE_DEXIE_DB constant 
+**Note**: Migration fence now implemented through PlatformServiceMixin instead of USE_DEXIE_DB constant

doc/platformservicemixin-completion-plan.md

@@ -7,6 +7,7 @@ This document outlines the complete plan to finish PlatformServiceMixin implemen
 ## Current Status
 
 ### ✅ **PlatformServiceMixin - 95% Complete**
+
 - **Core functionality**: ✅ Implemented
 - **Caching system**: ✅ Implemented  
 - **Database methods**: ✅ Implemented
@@ -14,6 +15,7 @@ This document outlines the complete plan to finish PlatformServiceMixin implemen
 - **Type definitions**: ✅ Implemented
 
 ### ⚠️ **Remaining Issues**
+
 1. **Single circular dependency**: `memoryLogs` import from databaseUtil
 2. **Missing utility functions**: `generateInsertStatement`, `generateUpdateStatement`
 3. **52 files** still importing databaseUtil
@@ -25,6 +27,7 @@ This document outlines the complete plan to finish PlatformServiceMixin implemen
 ### **Phase 1: Remove Circular Dependency (30 minutes)**
 
 #### **Step 1.1: Create Self-Contained memoryLogs**
+
 ```typescript
 // In PlatformServiceMixin.ts - Replace line 50:
 // Remove: import { memoryLogs } from "@/db/databaseUtil";
@@ -48,6 +51,7 @@ $appendToMemoryLogs(message: string): void {
 ```
 
 #### **Step 1.2: Update logger.ts**
+
 ```typescript
 // In logger.ts - Replace memoryLogs usage:
 // Remove: import { memoryLogs } from "@/db/databaseUtil";
@@ -70,6 +74,7 @@ export function getMemoryLogs(): string[] {
 ### **Phase 2: Add Missing Utility Functions (1 hour)**
 
 #### **Step 2.1: Add generateInsertStatement to PlatformServiceMixin**
+
 ```typescript
 // Add to PlatformServiceMixin methods:
 _generateInsertStatement(
@@ -95,6 +100,7 @@ _generateInsertStatement(
 ```
 
 #### **Step 2.2: Add generateUpdateStatement to PlatformServiceMixin**
+
 ```typescript
 // Add to PlatformServiceMixin methods:
 _generateUpdateStatement(
@@ -129,6 +135,7 @@ _generateUpdateStatement(
 ```
 
 #### **Step 2.3: Add Public Wrapper Methods**
+
 ```typescript
 // Add to PlatformServiceMixin methods:
 $generateInsertStatement(
@@ -151,6 +158,7 @@ $generateUpdateStatement(
 ### **Phase 3: Update Type Definitions (30 minutes)**
 
 #### **Step 3.1: Update IPlatformServiceMixin Interface**
+
 ```typescript
 // Add to IPlatformServiceMixin interface:
 $generateInsertStatement(
@@ -167,6 +175,7 @@ $appendToMemoryLogs(message: string): void;
 ```
 
 #### **Step 3.2: Update ComponentCustomProperties**
+
 ```typescript
 // Add to ComponentCustomProperties interface:
 $generateInsertStatement(
@@ -185,12 +194,14 @@ $appendToMemoryLogs(message: string): void;
 ### **Phase 4: Test PlatformServiceMixin (1 hour)**
 
 #### **Step 4.1: Create Test Component**
+
 ```typescript
 // Create test file: src/test/PlatformServiceMixin.test.ts
 // Test all methods including new utility functions
 ```
 
 #### **Step 4.2: Run Linting and Type Checking**
+
 ```bash
 npm run lint
 npx tsc --noEmit
@@ -203,6 +214,7 @@ npx tsc --noEmit
 ### **Migration Strategy**
 
 #### **Priority Order:**
+
 1. **Views** (25 files) - User-facing components
 2. **Components** (15 files) - Reusable UI components  
 3. **Services** (8 files) - Business logic
@@ -211,6 +223,7 @@ npx tsc --noEmit
 #### **Migration Pattern for Each File:**
 
 **Step 1: Add PlatformServiceMixin**
+
 ```typescript
 // Add to component imports:
 import { PlatformServiceMixin } from "@/utils/PlatformServiceMixin";
@@ -223,6 +236,7 @@ export default class ComponentName extends Vue {
 ```
 
 **Step 2: Replace databaseUtil Imports**
+
 ```typescript
 // Remove:
 import { 
@@ -244,6 +258,7 @@ import {
 ```
 
 **Step 3: Update Method Calls**
+
 ```typescript
 // Before:
 const { sql, params } = generateInsertStatement(contact, 'contacts');
@@ -255,6 +270,7 @@ const { sql, params } = this.$generateInsertStatement(contact, 'contacts');
 ### **File Migration Checklist**
 
 #### **Views (25 files) - Priority 1**
+
 - [ ] QuickActionBvcEndView.vue
 - [ ] ProjectsView.vue
 - [ ] ClaimReportCertificateView.vue
@@ -278,6 +294,7 @@ const { sql, params } = this.$generateInsertStatement(contact, 'contacts');
 - [ ] [5 more view files]
 
 #### **Components (15 files) - Priority 2**
+
 - [ ] ActivityListItem.vue
 - [ ] AmountInput.vue
 - [ ] ChoiceButtonDialog.vue
@@ -295,18 +312,21 @@ const { sql, params } = this.$generateInsertStatement(contact, 'contacts');
 - [ ] IconRenderer.vue
 
 #### **Services (8 files) - Priority 3**
+
 - [ ] api.ts
 - [ ] endorserServer.ts
 - [ ] partnerServer.ts
 - [ ] [5 more service files]
 
 #### **Utils (4 files) - Priority 4**
+
 - [ ] LogCollector.ts
 - [ ] [3 more util files]
 
 ### **Migration Tools**
 
 #### **Automated Script for Common Patterns**
+
 ```bash
 #!/bin/bash
 # migration-helper.sh
@@ -326,6 +346,7 @@ echo "logConsoleAndDb → this.\$logAndConsole"
 ```
 
 #### **Validation Script**
+
 ```bash
 #!/bin/bash
 # validate-migration.sh
@@ -350,6 +371,7 @@ echo "Migration validation complete!"
 ## 🎯 **Success Criteria**
 
 ### **Day 1 Success Criteria:**
+
 - [ ] PlatformServiceMixin has no circular dependencies
 - [ ] All utility functions implemented and tested
 - [ ] Type definitions complete and accurate
@@ -357,6 +379,7 @@ echo "Migration validation complete!"
 - [ ] TypeScript compilation passes
 
 ### **Day 2 Success Criteria:**
+
 - [ ] 0 files importing databaseUtil
 - [ ] All 52 files migrated to PlatformServiceMixin
 - [ ] No runtime errors in migrated components
@@ -364,6 +387,7 @@ echo "Migration validation complete!"
 - [ ] Performance maintained or improved
 
 ### **Overall Success Criteria:**
+
 - [ ] Complete elimination of databaseUtil dependency
 - [ ] PlatformServiceMixin is the single source of truth for database operations
 - [ ] Migration fence is fully implemented
@@ -386,12 +410,14 @@ echo "Migration validation complete!"
 ## 📋 **Daily Progress Tracking**
 
 ### **Day 1 Progress:**
+
 - [ ] Phase 1: Circular dependency resolved
 - [ ] Phase 2: Utility functions added
 - [ ] Phase 3: Type definitions updated
 - [ ] Phase 4: Testing completed
 
 ### **Day 2 Progress:**
+
 - [ ] Views migrated (0/25)
 - [ ] Components migrated (0/15)
 - [ ] Services migrated (0/8)
@@ -403,16 +429,19 @@ echo "Migration validation complete!"
 ## 🆘 **Contingency Plans**
 
 ### **If Day 1 Takes Longer:**
+
 - Focus on core functionality first
 - Defer advanced utility functions to Day 2
 - Prioritize circular dependency resolution
 
 ### **If Day 2 Takes Longer:**
+
 - Focus on high-impact views first
 - Batch similar components together
 - Use automated scripts for common patterns
 
 ### **If Issues Arise:**
+
 - Document specific problems
 - Create targeted fixes
-- Maintain backward compatibility during transition 
+- Maintain backward compatibility during transition

doc/qr-code-implementation-guide.md

@@ -7,6 +7,7 @@ This document describes the QR code scanning and generation implementation in th
 ## Architecture
 
 ### Directory Structure
+
 ```
 src/
 ├── services/
@@ -74,6 +75,7 @@ interface QRScannerOptions {
 ### Platform-Specific Implementations
 
 #### Mobile (Capacitor)
+
 - Uses `@capacitor-mlkit/barcode-scanning`
 - Native camera access through platform APIs
 - Optimized for mobile performance
@@ -82,6 +84,7 @@ interface QRScannerOptions {
 - Back camera preferred for scanning
 
 Configuration:
+
 ```typescript
 // capacitor.config.ts
 const config: CapacitorConfig = {
@@ -105,6 +108,7 @@ const config: CapacitorConfig = {
 ```
 
 #### Web
+
 - Uses browser's MediaDevices API
 - Vue.js components for UI
 - EventEmitter for stream management
@@ -116,6 +120,7 @@ const config: CapacitorConfig = {
 ### View Components
 
 #### ContactQRScanView
+
 - Dedicated view for scanning QR codes
 - Full-screen camera interface
 - Simple UI focused on scanning
@@ -123,6 +128,7 @@ const config: CapacitorConfig = {
 - Streamlined scanning experience
 
 #### ContactQRScanShowView
+
 - Combined view for QR code display and scanning
 - Shows user's own QR code
 - Handles user registration status
@@ -160,6 +166,7 @@ const config: CapacitorConfig = {
 ## Build Configuration
 
 ### Common Vite Configuration
+
 ```typescript
 // vite.config.common.mts
 export async function createBuildConfig(mode: string) {
@@ -183,6 +190,7 @@ export async function createBuildConfig(mode: string) {
 ```
 
 ### Platform-Specific Builds
+
 ```json
 {
   "scripts": {
@@ -196,6 +204,7 @@ export async function createBuildConfig(mode: string) {
 ## Error Handling
 
 ### Common Error Scenarios
+
 1. No camera found
 2. Permission denied
 3. Camera in use by another application
@@ -207,6 +216,7 @@ export async function createBuildConfig(mode: string) {
 9. Network connectivity issues
 
 ### Error Response
+
 - User-friendly error messages
 - Troubleshooting tips
 - Clear instructions for resolution
@@ -215,6 +225,7 @@ export async function createBuildConfig(mode: string) {
 ## Security Considerations
 
 ### QR Code Security
+
 - Encryption of contact data
 - Timestamp validation
 - Version checking
@@ -222,6 +233,7 @@ export async function createBuildConfig(mode: string) {
 - Rate limiting for scans
 
 ### Data Protection
+
 - Secure transmission of contact data
 - Validation of QR code authenticity
 - Prevention of duplicate scans
@@ -231,6 +243,7 @@ export async function createBuildConfig(mode: string) {
 ## Best Practices
 
 ### Camera Access
+
 1. Always check for camera availability
 2. Request permissions explicitly
 3. Handle all error conditions
@@ -238,6 +251,7 @@ export async function createBuildConfig(mode: string) {
 5. Implement proper cleanup
 
 ### Performance
+
 1. Optimize camera resolution
 2. Implement proper resource cleanup
 3. Handle camera switching efficiently
@@ -245,6 +259,7 @@ export async function createBuildConfig(mode: string) {
 5. Battery usage optimization
 
 ### User Experience
+
 1. Clear visual feedback
 2. Camera preview
 3. Scanning status indicators
@@ -257,6 +272,7 @@ export async function createBuildConfig(mode: string) {
 ## Testing
 
 ### Test Scenarios
+
 1. Permission handling
 2. Camera switching
 3. Error conditions
@@ -267,6 +283,7 @@ export async function createBuildConfig(mode: string) {
 8. Security validation
 
 ### Test Environment
+
 - Multiple browsers
 - iOS and Android devices
 - Various network conditions
@@ -275,6 +292,7 @@ export async function createBuildConfig(mode: string) {
 ## Dependencies
 
 ### Key Packages
+
 - `@capacitor-mlkit/barcode-scanning`
 - `qrcode-stream`
 - `vue-qrcode-reader`
@@ -283,12 +301,14 @@ export async function createBuildConfig(mode: string) {
 ## Maintenance
 
 ### Regular Updates
+
 - Keep dependencies updated
 - Monitor platform changes
 - Update documentation
 - Review security patches
 
 ### Performance Monitoring
+
 - Track memory usage
 - Monitor camera performance
 - Check error rates
@@ -436,6 +456,7 @@ The camera switching implementation includes comprehensive error handling:
    - Camera switch timeout
 
 2. **Error Response**
+
    ```typescript
    private async handleCameraSwitch(deviceId: string): Promise<void> {
      try {
@@ -460,6 +481,7 @@ The camera switching implementation includes comprehensive error handling:
 The camera system maintains several states:
 
 1. **Camera States**
+
    ```typescript
    type CameraState =
      | "initializing"  // Camera is being initialized
@@ -529,6 +551,7 @@ The camera system maintains several states:
 #### MLKit Barcode Scanner Configuration
 
 1. **Plugin Setup**
+
    ```typescript
    // capacitor.config.ts
    const config: CapacitorConfig = {
@@ -552,6 +575,7 @@ The camera system maintains several states:
    ```
 
 2. **Camera Management**
+
    ```typescript
    // CapacitorQRScanner.ts
    export class CapacitorQRScanner implements QRScannerService {
@@ -603,6 +627,7 @@ The camera system maintains several states:
    ```
 
 3. **Camera State Management**
+
    ```typescript
    // CapacitorQRScanner.ts
    private async handleCameraState(): Promise<void> {
@@ -645,6 +670,7 @@ The camera system maintains several states:
    ```
 
 4. **Error Handling**
+
    ```typescript
    // CapacitorQRScanner.ts
    private async handleCameraError(error: Error): Promise<void> {
@@ -737,6 +763,7 @@ The camera system maintains several states:
 #### Performance Optimization
 
 1. **Battery Usage**
+
    ```typescript
    // CapacitorQRScanner.ts
    private optimizeBatteryUsage(): void {
@@ -759,6 +786,7 @@ The camera system maintains several states:
    ```
 
 2. **Memory Management**
+
    ```typescript
    // CapacitorQRScanner.ts
    private async cleanupResources(): Promise<void> {
@@ -802,4 +830,4 @@ The camera system maintains several states:
    - Camera switching speed
    - QR code detection speed
    - App responsiveness
-   - Background/foreground transitions
+   - Background/foreground transitions

doc/secure-storage-implementation.md

@@ -111,6 +111,7 @@ export class AbsurdSqlDatabaseService implements PlatformService {
 ```
 
 Key features:
+
 - Uses absurd-sql for SQLite in the browser
 - Implements operation queuing for thread safety
 - Handles initialization and connection management
@@ -143,6 +144,7 @@ async function getAccount(did: string): Promise<Account | undefined> {
 When converting from Dexie.js to SQL-based implementation, follow these patterns:
 
 1. **Database Access Pattern**
+
    ```typescript
    // Before (Dexie)
    const result = await db.table.where("field").equals(value).first();
@@ -161,6 +163,7 @@ When converting from Dexie.js to SQL-based implementation, follow these patterns
    ```
 
 2. **Update Operations**
+
    ```typescript
    // Before (Dexie)
    await db.table.where("id").equals(id).modify(changes);
@@ -184,6 +187,7 @@ When converting from Dexie.js to SQL-based implementation, follow these patterns
    ```
 
 3. **Insert Operations**
+
    ```typescript
    // Before (Dexie)
    await db.table.add(item);
@@ -202,6 +206,7 @@ When converting from Dexie.js to SQL-based implementation, follow these patterns
    ```
 
 4. **Delete Operations**
+
    ```typescript
    // Before (Dexie)
    await db.table.where("id").equals(id).delete();
@@ -216,6 +221,7 @@ When converting from Dexie.js to SQL-based implementation, follow these patterns
    ```
 
 5. **Result Processing**
+
    ```typescript
    // Before (Dexie)
    const items = await db.table.toArray();
@@ -247,6 +253,7 @@ await databaseUtil.logConsoleAndDb(message, showInConsole);
 ```
 
 Key Considerations:
+
 - Always use `databaseUtil.mapQueryResultToValues()` to process SQL query results
 - Use utility methods from `db/index.ts` when available instead of direct SQL
 - Keep Dexie fallbacks wrapped in migration period checks
@@ -254,6 +261,7 @@ Key Considerations:
 - For updates/inserts/deletes, execute both SQL and Dexie operations during migration period
 
 Example Migration:
+
 ```typescript
 // Before (Dexie)
 export async function updateSettings(settings: Settings): Promise<void> {
@@ -274,6 +282,7 @@ export async function updateSettings(settings: Settings): Promise<void> {
 ```
 
 Remember to:
+
 - Create database access code to use the platform service, putting it in front of the Dexie version
 - Instead of removing Dexie-specific code, keep it.
 
@@ -330,4 +339,4 @@ it's during migration then use that result instead of the SQL code's result.
 4. **Documentation**
    - Add API documentation
    - Create migration guides
-   - Document security measures
+   - Document security measures

doc/sharebufferarray_spectre_security.md

@@ -4,11 +4,13 @@
 ## 1. Introduction to SharedArrayBuffer
 
 ### Overview
+
 - `SharedArrayBuffer` is a JavaScript object that enables **shared memory** access between the main thread and Web Workers.
 - Unlike `ArrayBuffer`, the memory is **not copied** between threads—allowing **true parallelism**.
 - Paired with `Atomics`, it allows low-level memory synchronization (e.g., locks, waits).
 
 ### Example Use
+
 ```js
 const sab = new SharedArrayBuffer(1024);
 const sharedArray = new Uint8Array(sab);
@@ -18,6 +20,7 @@ sharedArray[0] = 42;
 ## 2. Browser Security Requirements
 
 ### Security Headers Required to Use SharedArrayBuffer
+
 Modern browsers **restrict access** to `SharedArrayBuffer` due to Spectre-class vulnerabilities.
 
 The following **HTTP headers must be set** to enable it:
@@ -28,23 +31,28 @@ Cross-Origin-Embedder-Policy: require-corp
 ```
 
 ### HTTPS Requirement
+
 - Must be served over **HTTPS** (except `localhost` for dev).
 - These headers enforce **cross-origin isolation**.
 
 ### Role of CORS
+
 - CORS **alone is not sufficient**.
 - However, embedded resources (like scripts and iframes) must still include proper CORS headers if they are to be loaded in a cross-origin isolated context.
 
 ## 3. Spectre Vulnerability
 
 ### What is Spectre?
+
 - A class of **side-channel attacks** exploiting **speculative execution** in CPUs.
 - Allows an attacker to read arbitrary memory from the same address space.
 
 ### Affected Architectures
+
 - Intel, AMD, ARM — essentially **all modern processors**.
 
 ### Why It's Still a Concern
+
 - It's a **hardware flaw**, not just a software bug.
 - Can't be fully fixed in software without performance penalties.
 - New Spectre **variants** (e.g., v2, RSB, BranchScope) continue to emerge.
@@ -52,16 +60,19 @@ Cross-Origin-Embedder-Policy: require-corp
 ## 4. Mitigations and Current Limitations
 
 ### Browser Mitigations
+
 - **Restricted precision** for `performance.now()`.
 - **Disabled or gated** access to `SharedArrayBuffer`.
 - **Reduced or removed** fine-grained timers.
 
 ### OS/Hardware Mitigations
+
 - **Kernel Page Table Isolation (KPTI)**
 - **Microcode updates**
 - **Retpoline** compiler mitigations
 
 ### Developer Responsibilities
+
 - Avoid sharing sensitive data across threads unless necessary.
 - Use **constant-time cryptographic functions**.
 - Assume timing attacks are **still possible**.
@@ -70,10 +81,12 @@ Cross-Origin-Embedder-Policy: require-corp
 ## 5. Practical Development Notes
 
 ### Using SharedArrayBuffer Safely
+
 - Ensure the site is **cross-origin isolated**:
   - Serve all resources with appropriate **CORS policies** (`Cross-Origin-Resource-Policy`, `Access-Control-Allow-Origin`)
   - Set the required **COOP/COEP headers**
 - Validate support using:
+
 ```js
 if (window.crossOriginIsolated) {
     // Safe to use SharedArrayBuffer
@@ -81,6 +94,7 @@ if (window.crossOriginIsolated) {
 ```
 
 ### Testing and Fallback
+
 - Provide fallbacks to `ArrayBuffer` if isolation is not available.
 - Document use cases clearly (e.g., high-performance WebAssembly applications or real-time audio/video processing).
 

doc/storage-implementation-checklist.md

@@ -3,6 +3,7 @@
 ## Core Services
 
 ### 1. Storage Service Layer
+
 - [x] Create base `PlatformService` interface
   - [x] Define common methods for all platforms
   - [x] Add platform-specific method signatures
@@ -25,6 +26,7 @@
     - [ ] File system access
 
 ### 2. Migration Services
+
 - [x] Implement basic migration support
   - [x] Dual-storage pattern (SQLite + Dexie)
   - [x] Basic data verification
@@ -37,6 +39,7 @@
   - [ ] Manual triggers
 
 ### 3. Security Layer
+
 - [x] Basic data integrity
 - [ ] Implement `EncryptionService` (planned)
   - [ ] Key management
@@ -50,14 +53,17 @@
 ## Platform-Specific Implementation
 
 ### Web Platform
+
 - [x] Setup absurd-sql
   - [x] Install dependencies
+
     ```json
     {
       "@jlongster/sql.js": "^1.8.0",
       "absurd-sql": "^1.8.0"
     }
     ```
+
   - [x] Configure VFS with IndexedDB backend
   - [x] Setup worker threads
   - [x] Implement operation queuing
@@ -83,6 +89,7 @@
   - [x] Implement atomic operations
 
 ### iOS Platform (Planned)
+
 - [ ] Setup SQLCipher
   - [ ] Install pod dependencies
   - [ ] Configure encryption
@@ -96,6 +103,7 @@
   - [ ] Setup app groups
 
 ### Android Platform (Planned)
+
 - [ ] Setup SQLCipher
   - [ ] Add Gradle dependencies
   - [ ] Configure encryption
@@ -109,6 +117,7 @@
   - [ ] Setup file provider
 
 ### Electron Platform (Planned)
+
 - [ ] Setup Node SQLite
   - [ ] Install dependencies
   - [ ] Configure IPC
@@ -124,6 +133,7 @@
 ## Data Models and Types
 
 ### 1. Database Schema
+
 - [x] Define tables
 
   ```sql
@@ -166,6 +176,7 @@
 ### 2. Type Definitions
 
 - [x] Create interfaces
+
   ```typescript
   interface Account {
     did: string;
@@ -197,6 +208,7 @@
 ## UI Components
 
 ### 1. Migration UI (Planned)
+
 - [ ] Create components
   - [ ] `MigrationProgress.vue`
   - [ ] `MigrationError.vue`
@@ -204,6 +216,7 @@
   - [ ] `MigrationStatus.vue`
 
 ### 2. Settings UI (Planned)
+
 - [ ] Update components
   - [ ] Add storage settings
   - [ ] Add migration controls
@@ -211,6 +224,7 @@
   - [ ] Add security settings
 
 ### 3. Error Handling UI (Planned)
+
 - [ ] Create components
   - [ ] `StorageError.vue`
   - [ ] `QuotaExceeded.vue`
@@ -220,6 +234,7 @@
 ## Testing
 
 ### 1. Unit Tests
+
 - [x] Basic service tests
   - [x] Platform service tests
   - [x] Database operation tests
@@ -227,6 +242,7 @@
   - [ ] Platform detection tests (planned)
 
 ### 2. Integration Tests (Planned)
+
 - [ ] Test migrations
   - [ ] Web platform tests
   - [ ] iOS platform tests
@@ -234,6 +250,7 @@
   - [ ] Electron platform tests
 
 ### 3. E2E Tests (Planned)
+
 - [ ] Test workflows
   - [ ] Account management
   - [ ] Settings management
@@ -243,12 +260,14 @@
 ## Documentation
 
 ### 1. Technical Documentation
+
 - [x] Update architecture docs
 - [x] Add API documentation
 - [ ] Create migration guides (planned)
 - [ ] Document security measures (planned)
 
 ### 2. User Documentation (Planned)
+
 - [ ] Update user guides
 - [ ] Add troubleshooting guides
 - [ ] Create FAQ
@@ -257,12 +276,14 @@
 ## Deployment
 
 ### 1. Build Process
+
 - [x] Update build scripts
 - [x] Add platform-specific builds
 - [ ] Configure CI/CD (planned)
 - [ ] Setup automated testing (planned)
 
 ### 2. Release Process (Planned)
+
 - [ ] Create release checklist
 - [ ] Add version management
 - [ ] Setup rollback procedures
@@ -271,12 +292,14 @@
 ## Monitoring and Analytics (Planned)
 
 ### 1. Error Tracking
+
 - [ ] Setup error logging
 - [ ] Add performance monitoring
 - [ ] Configure alerts
 - [ ] Create dashboards
 
 ### 2. Usage Analytics
+
 - [ ] Add storage metrics
 - [ ] Track migration success
 - [ ] Monitor performance
@@ -285,12 +308,14 @@
 ## Security Audit (Planned)
 
 ### 1. Code Review
+
 - [ ] Review encryption
 - [ ] Check access controls
 - [ ] Verify data handling
 - [ ] Audit dependencies
 
 ### 2. Penetration Testing
+
 - [ ] Test data access
 - [ ] Verify encryption
 - [ ] Check authentication
@@ -299,6 +324,7 @@
 ## Success Criteria
 
 ### 1. Performance
+
 - [x] Query response time < 100ms
 - [x] Operation queuing for thread safety
 - [x] Proper initialization handling
@@ -307,6 +333,7 @@
 - [ ] Memory usage < 50MB (planned)
 
 ### 2. Reliability
+
 - [x] Basic data integrity
 - [x] Operation queuing
 - [ ] Automatic recovery (planned)
@@ -315,6 +342,7 @@
 - [ ] Data consistency (planned)
 
 ### 3. Security
+
 - [x] Basic data integrity
 - [ ] AES-256 encryption (planned)
 - [ ] Secure key storage (planned)
@@ -322,8 +350,9 @@
 - [ ] Audit logging (planned)
 
 ### 4. User Experience
+
 - [x] Basic database operations
 - [ ] Smooth migration (planned)
 - [ ] Clear error messages (planned)
 - [ ] Progress indicators (planned)
-- [ ] Recovery options (planned) 
+- [ ] Recovery options (planned)

doc/usage-guide.md

@@ -53,10 +53,9 @@ header-includes:
 
 \clearpage
 
-
 # Purpose of Document
 
-Both end-users and development team members need to know how to use TimeSafari. 
+Both end-users and development team members need to know how to use TimeSafari.
 This document serves to show how to use every feature of the TimeSafari platform.
 
 Sections of this document are geared specifically for software developers and quality assurance
@@ -64,7 +63,7 @@ team members.
 
 Companion videos will also describe end-to-end workflows for the end-user.
 
-# TimeSafari 
+# TimeSafari
 
 ## Overview
 
@@ -90,49 +89,51 @@ development environment. This section will guide you through the process.
 ## Prerequisites
 
 1. Have the following installed on your local machine:
-  - Node.js and NPM
-  - A web browser. For this guide, we will use Google Chrome.
-  - Git
-  - A code editor
+
+- Node.js and NPM
+- A web browser. For this guide, we will use Google Chrome.
+- Git
+- A code editor
 
 2. Create an API key on Infura. This is necessary for the Endorser API to connect to the Ethereum
-   blockchain. 
-  - You can create an account on Infura [here](https://infura.io/).\
+   blockchain.
+
+- You can create an account on Infura [here](https://infura.io/).\
     Click "CREATE NEW API KEY" and label the key. Then click "API Keys" in the top menu bar to
     be taken back to the list of keys.
-    
-    Click "VIEW STATS" on the key you want to use.   
-    
+
+    Click "VIEW STATS" on the key you want to use.
+
     ![](images/01_infura-api-keys.png){ width=550px }
   
-  - Go to the key detail page. Then click "MANAGE API KEY".
+- Go to the key detail page. Then click "MANAGE API KEY".
   
     ![](images/02-infura-key-detail.png){ width=550px }
   
-  - Click the copy and paste button next to the string of alphanumeric characters.\
+- Click the copy and paste button next to the string of alphanumeric characters.\
     This is your API, also known as your project ID.
   
     ![](images/03-infura-api-key-id.png){width=550px }
   
-  - Save this for later during the Endorser API setup. This will go in your `INFURA_PROJECT_ID` 
+- Save this for later during the Endorser API setup. This will go in your `INFURA_PROJECT_ID`
     environment variable.
-    
 
 ## Setup steps
 
-### 1. Clone the following repositories from their respective Git hosts:
-  - [TimeSafari Frontend](https://gitea.anomalistdesign.com/trent_larson/crowd-funder-for-time-pwa)\
+### 1. Clone the following repositories from their respective Git hosts
+
+- [TimeSafari Frontend](https://gitea.anomalistdesign.com/trent_larson/crowd-funder-for-time-pwa)\
     This is a Progressive Web App (PWA) built with VueJS and TypeScript.
     Note that the clone command here is different from the one you would use for GitHub.
-    
+
 ```bash
 git clone git clone \
   ssh://git@gitea.anomalistdesign.com:222/trent_larson/crowd-funder-for-time-pwa.git
 ```
   
-  - [TimeSafari Backend - Endorser API](https://github.com/trentlarson/endorser-ch)\
+- [TimeSafari Backend - Endorser API](https://github.com/trentlarson/endorser-ch)\
     This is a NodeJS service providing the backend for TimeSafari.
-    
+
     ```bash
     git clone git@github.com:trentlarson/endorser-ch.git
     ```
@@ -148,7 +149,7 @@ below to generate sample data. Then copy the test database, rename it to `-dev`
 `cp ../endorser-ch-test-local.sqlite3 ../endorser-ch-dev.sqlite3` \
 and rerun `npm run dev` to give yourself user #0 and others from the ETHR_CRED_DATA in [the endorser.ch test util file](https://github.com/trentlarson/endorser-ch/blob/master/test/util.js#L90)
 
-#### Alternative 2 - boostrap single seed user 
+#### Alternative 2 - boostrap single seed user
 
 In this method you will end up with two accounts in the database, one for the first boostrap user,
 and the second as the primary user you will use during testing. The first user will invite the
@@ -157,26 +158,30 @@ second user to the app.
 1. Install dependencies and environment variables.\
    In endorser-ch install dependencies and set up environment variables to allow starting it up in
    development mode.
+
    ```bash
    cd endorser-ch
    npm clean install  # or npm ci
    cp .env.local .env
    ```
+
    Edit the .env file's INFURA_PROJECT_ID with the value you saved earlier in the
    prerequisites.\
    Then create the SQLite database by running `npm run flyway migrate` with environment variables
    set correctly to select the default SQLite development user as follows.
+
    ```bash
    export NODE_ENV=dev 
    export DBUSER=sa 
    export DBPASS=sasa 
    npm run flyway migrate
-   ``` 
-   The first run of flyway migrate may take some time to complete because the entire Flyway 
+   ```
+
+   The first run of flyway migrate may take some time to complete because the entire Flyway
    distribution must be downloaded prior to executing migrations.
-    
+
    Successful output looks similar to the following:
-    
+
 ```
 Database: jdbc:sqlite:../endorser-ch-dev.sqlite3 (SQLite 3.41)
 Schema history table "main"."flyway_schema_history" does not exist yet
@@ -202,23 +207,23 @@ A Flyway report has been generated here: /Users/kbull/code/timesafari/endorser-c
 2. Generate the first user in TimeSafari PWA and bootstrap that user in Endorser's database.\
    As TimeSafari is an invite-only platform the first user must be manually bootstrapped since
    no other users exist to be able to invite the first user. This first user must be added manually
-   to the SQLite database used by Endorser. In this setup you generate the first user from the PWA. 
-   
-   This user is automatically generated on first usage of the TimeSafari PWA. Bootstrapping that 
+   to the SQLite database used by Endorser. In this setup you generate the first user from the PWA.
+
+   This user is automatically generated on first usage of the TimeSafari PWA. Bootstrapping that
    user is required so that this first user can register other users.
    - Change directories into `crowd-funder-for-time-pwa`
-     
+
      ```bash
      cd ..
      cd crowd-funder-for-time-pwa 
      ```
-   
+
    - Ensure the `.env.development` file exists and has the following values:
-   
+
      ```env
      VITE_DEFAULT_ENDORSER_API_SERVER=http://127.0.0.1:3000
      ```
-   
+
    - Install dependencies and run in dev mode. For now don't worry about configuring the app. All we
      need is to generate the first root user and this happens automatically on app startup.
   
@@ -230,45 +235,45 @@ A Flyway report has been generated here: /Users/kbull/code/timesafari/endorser-c
    - Open the app in a browser and go to the developer tools. It is recommended to use a completely
      separate browser profile so you do not clear out your existing user account. We will be
      completely resetting the PWA app state prior to generating the first user.
-   
+
      In the Developer Tools go to the Application tab.
-     
-     ![](images/04-pwa-chrome-devtools.png){width=350px} 
-   
+
+     ![](images/04-pwa-chrome-devtools.png){width=350px}
+
      Click the "Clear site data" button and then refresh the page.
-   
+
    - Click the account button in the bottom right corner of the page.
-   
+
      ![](images/05-pwa-account-button.png){width=150px}
-   
+
    - This will take you to the account page titled "Your Identity" on which you can see your DID,
      a `did:ethr` DID in this case.
-   
+
      ![](images/06-pwa-account-page.png){width=350px}
-   
+
    - Copy the DID by selecting it and copying it to the clipboard or by clicking the copy and paste
      button as shown in the image.
-   
+
      ![](images/07-pwa-did-copied.png){width=200px}
-    
+
      In our case this DID is:\
      `did:ethr:0xe4B783c74c8B0e229524e44d0cD898D272E02CD6`
-   
-  - Add that DID to the following echoed SQL statement where it says `YOUR_DID`
+
+- Add that DID to the following echoed SQL statement where it says `YOUR_DID`
   
     ```bash
     echo "INSERT INTO registration (did, maxClaims, maxRegs, epoch) 
     VALUES ('YOUR_DID', 100, 10000, 1719348718092);"
     | sqlite3 ./endorser-ch-dev.sqlite3
     ```
-    
+
     and run this command in the parent directory just above the `endorser-ch` directory.
-    
-    It needs to be the parent directory of your `endorser-ch` repository because when 
+
+    It needs to be the parent directory of your `endorser-ch` repository because when
     `endorser-ch` creates the SQLite database it depends on it creates it in the parent directory
     of `endorser-ch`.
-    
-  - You can verify with an SQL browser tool that your record has been added to the `registration`
+
+- You can verify with an SQL browser tool that your record has been added to the `registration`
     table.
   
     ![](images/08-endorser-sqlite-row-added.png){width=350px}
@@ -285,14 +290,14 @@ A Flyway report has been generated here: /Users/kbull/code/timesafari/endorser-c
 4. Create the second user by opening up a separate browser profile or incognito session, opening the
    TimeSafari PWA at `http://localhost:8080`. You will see the yellow banner stating "Someone must
    register you before you can give or offer."
-   
+
    ![](images/09-pwa-second-profile-first-open.png){width=350px}
-   
+
    - If you want to ensure you have a fresh user account then open the developer tools, clear the
-     Application data as before, and then refresh the page. This will generate a new user in the 
+     Application data as before, and then refresh the page. This will generate a new user in the
      browser's IndexedDB database.
 5. Go to the second users' account page to copy the DID.
-    
+
     ![](images/10-pwa-second-user-did.png){width=350px}
 
 6. Copy the DID and put it in the text bar on the "Your Contacts" page for the first account

docker/README.md

@@ -155,6 +155,7 @@ VITE_PASSKEYS_ENABLED=true
 ## Build Modes
 
 ### Development Mode
+
 - **Target**: `development`
 - **Features**: Hot reloading, development server
 - **Port**: 5173
@@ -168,6 +169,7 @@ docker build --target development -t timesafari:dev .
 ```
 
 ### Staging Mode
+
 - **Target**: `staging`
 - **Features**: Production build with relaxed caching
 - **Port**: 8080 (mapped from 80)
@@ -181,6 +183,7 @@ docker build --build-arg BUILD_MODE=staging -t timesafari:staging .
 ```
 
 ### Production Mode
+
 - **Target**: `production`
 - **Features**: Optimized production build
 - **Port**: 80
@@ -194,6 +197,7 @@ docker build -t timesafari:latest .
 ```
 
 ### Custom Mode
+
 - **Target**: Configurable via `BUILD_TARGET`
 - **Features**: Fully configurable
 - **Port**: Configurable via `CUSTOM_PORT`
@@ -250,6 +254,7 @@ docker-compose up staging
 ## Security Features
 
 ### Built-in Security
+
 - **Non-root user execution**: All containers run as non-root users
 - **Security headers**: XSS protection, content type options, frame options
 - **Rate limiting**: API request rate limiting
@@ -257,6 +262,7 @@ docker-compose up staging
 - **Minimal attack surface**: Alpine Linux base images
 
 ### Security Headers
+
 - `X-Frame-Options: SAMEORIGIN`
 - `X-Content-Type-Options: nosniff`
 - `X-XSS-Protection: 1; mode=block`
@@ -266,17 +272,20 @@ docker-compose up staging
 ## Performance Optimizations
 
 ### Caching Strategy
+
 - **Static assets**: 1 year cache with immutable flag (production)
 - **HTML files**: 1 hour cache (production) / no cache (staging)
 - **Service worker**: No cache
 - **Manifest**: 1 day cache (production) / 1 hour cache (staging)
 
 ### Compression
+
 - **Gzip compression**: Enabled for text-based files
 - **Compression level**: 6 (balanced)
 - **Minimum size**: 1024 bytes
 
 ### Nginx Optimizations
+
 - **Sendfile**: Enabled for efficient file serving
 - **TCP optimizations**: nopush and nodelay enabled
 - **Keepalive**: 65 second timeout
@@ -285,19 +294,23 @@ docker-compose up staging
 ## Health Checks
 
 ### Built-in Health Checks
+
 All services include health checks that:
+
 - Check every 30 seconds
 - Timeout after 10 seconds
 - Retry 3 times before marking unhealthy
 - Start checking after 40 seconds
 
 ### Health Check Endpoints
+
 - **Production/Staging**: `http://localhost/health`
 - **Development**: `http://localhost:5173`
 
 ## SSL/HTTPS Setup
 
 ### SSL Certificates
+
 For SSL deployment, create an `ssl` directory with certificates:
 
 ```bash
@@ -308,6 +321,7 @@ cp your-key.pem ssl/
 ```
 
 ### SSL Configuration
+
 Use the `production-ssl` service in docker-compose:
 
 ```bash
@@ -317,10 +331,12 @@ docker-compose up production-ssl
 ## Monitoring and Logging
 
 ### Log Locations
+
 - **Access logs**: `/var/log/nginx/access.log`
 - **Error logs**: `/var/log/nginx/error.log`
 
 ### Log Format
+
 ```
 $remote_addr - $remote_user [$time_local] "$request" 
 $status $body_bytes_sent "$http_referer" 
@@ -328,6 +344,7 @@ $status $body_bytes_sent "$http_referer"
 ```
 
 ### Log Levels
+
 - **Production**: `warn` level
 - **Staging**: `debug` level
 - **Development**: Full logging
@@ -337,6 +354,7 @@ $status $body_bytes_sent "$http_referer"
 ### Common Issues
 
 #### Build Failures
+
 ```bash
 # Check build logs
 docker build -t timesafari:latest . 2>&1 | tee build.log
@@ -349,6 +367,7 @@ docker run --rm timesafari:latest npm list --depth=0
 ```
 
 #### Container Won't Start
+
 ```bash
 # Check container logs
 docker logs <container_id>
@@ -361,6 +380,7 @@ netstat -tulpn | grep :80
 ```
 
 #### Environment Variables Not Set
+
 ```bash
 # Check environment in container
 docker exec <container_id> env | grep VITE_
@@ -373,6 +393,7 @@ cat .env.production
 ```
 
 #### Performance Issues
+
 ```bash
 # Check container resources
 docker stats <container_id>
@@ -387,6 +408,7 @@ docker exec <container_id> tail -f /var/log/nginx/access.log
 ### Debug Commands
 
 #### Container Debugging
+
 ```bash
 # Enter running container
 docker exec -it <container_id> /bin/sh
@@ -399,6 +421,7 @@ docker exec <container_id> ls -la /usr/share/nginx/html
 ```
 
 #### Network Debugging
+
 ```bash
 # Check container network
 docker network inspect bridge
@@ -413,6 +436,7 @@ docker exec <container_id> nslookup google.com
 ## Production Deployment
 
 ### Recommended Production Setup
+
 1. **Use specific version tags**: `timesafari:1.0.0`
 2. **Implement health checks**: Already included
 3. **Configure proper logging**: Use external log aggregation
@@ -420,6 +444,7 @@ docker exec <container_id> nslookup google.com
 5. **Use Docker secrets**: For sensitive data
 
 ### Production Commands
+
 ```bash
 # Build with specific version
 docker build -t timesafari:1.0.0 .
@@ -442,6 +467,7 @@ docker run -d --name timesafari -p 80:80 --restart unless-stopped --env-file .en
 ## Development Workflow
 
 ### Local Development
+
 ```bash
 # Start development environment
 ./docker/run.sh dev
@@ -454,6 +480,7 @@ docker-compose down dev
 ```
 
 ### Testing Changes
+
 ```bash
 # Build and test staging
 ./docker/run.sh staging
@@ -463,6 +490,7 @@ docker-compose down dev
 ```
 
 ### Continuous Integration
+
 ```bash
 # Build and test in CI
 docker build -t timesafari:test .
@@ -479,6 +507,7 @@ docker rm timesafari-test
 ## Best Practices
 
 ### Security
+
 - Always use non-root users
 - Keep base images updated
 - Scan images for vulnerabilities
@@ -486,6 +515,7 @@ docker rm timesafari-test
 - Implement proper access controls
 
 ### Performance
+
 - Use multi-stage builds
 - Optimize layer caching
 - Minimize image size
@@ -493,6 +523,7 @@ docker rm timesafari-test
 - Implement proper caching
 
 ### Monitoring
+
 - Use health checks
 - Monitor resource usage
 - Set up log aggregation
@@ -500,8 +531,9 @@ docker rm timesafari-test
 - Use proper error handling
 
 ### Maintenance
+
 - Regular security updates
 - Monitor for vulnerabilities
 - Keep dependencies updated
 - Document configuration changes
-- Test deployment procedures 
+- Test deployment procedures

electron/README-BUILDING.md

@@ -18,6 +18,7 @@ This guide covers building and running the TimeSafari Electron application for d
 ## Quick Start
 
 ### Development Mode
+
 ```bash
 # Start development server
 npm run build:electron:dev
@@ -28,6 +29,7 @@ npm run electron:start
 ```
 
 ### Production Builds
+
 ```bash
 # Build for current platform
 npm run build:electron:prod
@@ -48,16 +50,19 @@ npm run build:electron:deb       # Linux DEB package
 The Electron app enforces single instance operation to prevent database conflicts and resource contention:
 
 ### Implementation
+
 - Uses Electron's built-in `app.requestSingleInstanceLock()`
 - Second instances exit immediately with user-friendly message
 - Existing instance focuses and shows informational dialog
 
 ### Behavior
+
 - **First instance**: Starts normally and acquires lock
 - **Second instance**: Detects existing instance, exits immediately
 - **User experience**: Clear messaging about single instance requirement
 
 ### Benefits
+
 - Prevents database corruption from concurrent access
 - Avoids resource conflicts
 - Maintains data integrity
@@ -66,6 +71,7 @@ The Electron app enforces single instance operation to prevent database conflict
 ## Build Configuration
 
 ### Environment Modes
+
 ```bash
 # Development (default)
 npm run build:electron:dev
@@ -78,6 +84,7 @@ npm run build:electron:prod
 ```
 
 ### Platform-Specific Builds
+
 ```bash
 # Windows
 npm run build:electron:windows:dev
@@ -96,6 +103,7 @@ npm run build:electron:linux:prod
 ```
 
 ### Package Types
+
 ```bash
 # Linux AppImage
 npm run build:electron:appimage:dev
@@ -116,26 +124,31 @@ npm run build:electron:deb:prod
 ## Platform-Specific Requirements
 
 ### Windows
+
 - Windows 10+ (64-bit)
 - Visual Studio Build Tools (for native modules)
 
 ### macOS
+
 - macOS 10.15+ (Catalina)
 - Xcode Command Line Tools
 - Code signing certificate (for distribution)
 
 ### Linux
+
 - Ubuntu 18.04+ / Debian 10+ / CentOS 7+
 - Development headers for native modules
 
 ## Database Configuration
 
 ### SQLite Integration
+
 - Uses native Node.js SQLite3 for Electron
 - Database stored in user's app data directory
 - Automatic migration from IndexedDB (if applicable)
 
 ### Single Instance Protection
+
 - File-based locking prevents concurrent database access
 - Automatic cleanup on app exit
 - Graceful handling of lock conflicts
@@ -143,11 +156,13 @@ npm run build:electron:deb:prod
 ## Security Features
 
 ### Content Security Policy
+
 - Strict CSP in production builds
 - Development mode allows localhost connections
 - Automatic configuration based on build mode
 
 ### Auto-Updater
+
 - Disabled in development mode
 - Production builds check for updates automatically
 - AppImage builds skip update checks
@@ -157,6 +172,7 @@ npm run build:electron:deb:prod
 ### Common Issues
 
 #### Build Failures
+
 ```bash
 # Clean and rebuild
 npm run clean:electron
@@ -164,6 +180,7 @@ npm run build:electron:dev
 ```
 
 #### Native Module Issues
+
 ```bash
 # Rebuild native modules
 cd electron
@@ -171,16 +188,19 @@ npm run electron:rebuild
 ```
 
 #### Single Instance Conflicts
+
 - Ensure no other TimeSafari instances are running
 - Check for orphaned processes: `ps aux | grep electron`
 - Restart system if necessary
 
 #### Database Issues
+
 - Check app data directory permissions
 - Verify SQLite database integrity
 - Clear app data if corrupted
 
 ### Debug Mode
+
 ```bash
 # Enable debug logging
 DEBUG=* npm run build:electron:dev
@@ -203,6 +223,7 @@ electron/
 ## Development Workflow
 
 1. **Start Development**
+
    ```bash
    npm run build:electron:dev
    ```
@@ -212,11 +233,13 @@ electron/
    - Changes auto-reload in development
 
 3. **Test Build**
+
    ```bash
    npm run build:electron:test
    ```
 
 4. **Production Build**
+
    ```bash
    npm run build:electron:prod
    ```
@@ -224,16 +247,19 @@ electron/
 ## Performance Considerations
 
 ### Memory Usage
+
 - Monitor renderer process memory
 - Implement proper cleanup in components
 - Use efficient data structures
 
 ### Startup Time
+
 - Lazy load non-critical modules
 - Optimize database initialization
 - Minimize synchronous operations
 
 ### Database Performance
+
 - Use transactions for bulk operations
 - Implement proper indexing
 - Monitor query performance
@@ -251,16 +277,19 @@ electron/
 ## Deployment
 
 ### Distribution
+
 - Windows: `.exe` installer
 - macOS: `.dmg` disk image
 - Linux: `.AppImage` or `.deb` package
 
 ### Code Signing
+
 - Windows: Authenticode certificate
 - macOS: Developer ID certificate
 - Linux: GPG signing (optional)
 
 ### Auto-Updates
+
 - Configured for production builds
 - Disabled for development and AppImage
 - Handles update failures gracefully
@@ -269,4 +298,4 @@ electron/
 
 **Last Updated**: 2025-07-11  
 **Version**: 1.0.3-beta  
-**Status**: Production Ready 
+**Status**: Production Ready

electron/README.md

@@ -56,21 +56,25 @@ npm run build:electron:dmg:prod
 ```
 
 **Stage 1: Web Build**
+
 - Vite builds web assets with Electron configuration
 - Environment variables loaded based on build mode
 - Assets optimized for desktop application
 
 **Stage 2: Capacitor Sync**
+
 - Copies web assets to Electron app directory
 - Syncs Capacitor configuration and plugins
 - Prepares native module bindings
 
 **Stage 3: TypeScript Compile**
+
 - Compiles Electron main process TypeScript
 - Rebuilds native modules for target platform
 - Generates production-ready JavaScript
 
 **Stage 4: Package Creation**
+
 - Creates platform-specific installers
 - Generates distribution packages
 - Signs applications (when configured)
@@ -82,6 +86,7 @@ npm run build:electron:dmg:prod
 **Purpose**: Local development and testing
 **Command**: `npm run build:electron:dev`
 **Features**:
+
 - Hot reload enabled
 - Debug tools available
 - Development logging
@@ -92,6 +97,7 @@ npm run build:electron:dmg:prod
 **Purpose**: Staging and testing environments
 **Command**: `npm run build:electron -- --mode test`
 **Features**:
+
 - Test API endpoints
 - Staging configurations
 - Optimized for testing
@@ -102,6 +108,7 @@ npm run build:electron:dmg:prod
 **Purpose**: Production deployment
 **Command**: `npm run build:electron -- --mode production`
 **Features**:
+
 - Production optimizations
 - Code minification
 - Security hardening
@@ -116,6 +123,7 @@ npm run build:electron:dmg:prod
 **Command**: `npm run build:electron:windows:prod`
 
 **Features**:
+
 - NSIS installer with custom options
 - Desktop and Start Menu shortcuts
 - Elevation permissions for installation
@@ -128,6 +136,7 @@ npm run build:electron:dmg:prod
 **Command**: `npm run build:electron:mac:prod`
 
 **Features**:
+
 - Universal binary (x64 + arm64)
 - DMG installer with custom branding
 - App Store compliance (when configured)
@@ -140,6 +149,7 @@ npm run build:electron:dmg:prod
 **Command**: `npm run build:electron:linux:prod`
 
 **Features**:
+
 - AppImage for universal distribution
 - DEB package for Debian-based systems
 - RPM package for Red Hat-based systems
@@ -152,6 +162,7 @@ npm run build:electron:dmg:prod
 **Format**: Self-contained Linux executable
 **Command**: `npm run build:electron:appimage:prod`
 **Features**:
+
 - Single file distribution
 - No installation required
 - Portable across Linux distributions
@@ -162,6 +173,7 @@ npm run build:electron:dmg:prod
 **Format**: Debian package installer
 **Command**: `npm run build:electron:deb:prod`
 **Features**:
+
 - Native package management
 - Dependency resolution
 - System integration
@@ -172,6 +184,7 @@ npm run build:electron:dmg:prod
 **Format**: macOS disk image
 **Command**: `npm run build:electron:dmg:prod`
 **Features**:
+
 - Native macOS installer
 - Custom branding and layout
 - Drag-and-drop installation
@@ -293,6 +306,7 @@ Local Electron scripts for building:
 ### Environment Variables
 
 **Development**:
+
 ```bash
 VITE_API_URL=http://localhost:3000
 VITE_DEBUG=true
@@ -301,6 +315,7 @@ VITE_ENABLE_DEV_TOOLS=true
 ```
 
 **Testing**:
+
 ```bash
 VITE_API_URL=https://test-api.timesafari.com
 VITE_DEBUG=false
@@ -309,6 +324,7 @@ VITE_ENABLE_DEV_TOOLS=false
 ```
 
 **Production**:
+
 ```bash
 VITE_API_URL=https://api.timesafari.com
 VITE_DEBUG=false
@@ -347,6 +363,7 @@ electron/
 ### Common Issues
 
 **TypeScript Compilation Errors**:
+
 ```bash
 # Clean and rebuild
 npm run clean:electron
@@ -354,18 +371,21 @@ cd electron && npm run build
 ```
 
 **Native Module Issues**:
+
 ```bash
 # Rebuild native modules
 cd electron && npm run build
 ```
 
 **Asset Copy Issues**:
+
 ```bash
 # Verify Capacitor sync
 npx cap sync electron
 ```
 
 **Package Creation Failures**:
+
 ```bash
 # Check electron-builder configuration
 # Verify platform-specific requirements
@@ -375,16 +395,19 @@ npx cap sync electron
 ### Platform-Specific Issues
 
 **Windows**:
+
 - Ensure Windows Build Tools installed
 - Check NSIS installation
 - Verify code signing certificates
 
 **macOS**:
+
 - Install Xcode Command Line Tools
 - Configure code signing certificates
 - Check app notarization requirements
 
 **Linux**:
+
 - Install required packages (rpm-tools, etc.)
 - Check AppImage dependencies
 - Verify desktop integration
@@ -394,11 +417,13 @@ npx cap sync electron
 ### Build Performance
 
 **Parallel Builds**:
+
 - Use concurrent TypeScript compilation
 - Optimize asset copying
 - Minimize file system operations
 
 **Caching Strategies**:
+
 - Cache node_modules between builds
 - Cache compiled TypeScript
 - Cache web assets when unchanged
@@ -406,11 +431,13 @@ npx cap sync electron
 ### Runtime Performance
 
 **Application Startup**:
+
 - Optimize main process initialization
 - Minimize startup dependencies
 - Use lazy loading for features
 
 **Memory Management**:
+
 - Monitor memory usage
 - Implement proper cleanup
 - Optimize asset loading
@@ -420,16 +447,19 @@ npx cap sync electron
 ### Code Signing
 
 **Windows**:
+
 - Authenticode code signing
 - EV certificate for SmartScreen
 - Timestamp server configuration
 
 **macOS**:
+
 - Developer ID code signing
 - App notarization
 - Hardened runtime
 
 **Linux**:
+
 - GPG signing for packages
 - AppImage signing
 - Package verification
@@ -437,12 +467,14 @@ npx cap sync electron
 ### Security Hardening
 
 **Production Builds**:
+
 - Disable developer tools
 - Remove debug information
 - Enable security policies
 - Implement sandboxing
 
 **Update Security**:
+
 - Secure update channels
 - Package integrity verification
 - Rollback capabilities
@@ -496,4 +528,4 @@ npx cap sync electron
 **Status**: Production ready
 **Last Updated**: 2025-01-27
 **Version**: 1.0
-**Maintainer**: Matthew Raymer 
+**Maintainer**: Matthew Raymer

index.html

@@ -11,6 +11,6 @@
   </head>
   <body>
     <div id="app"></div>
-    <script type="module" src="/src/main.web.ts"></script>
+    <script type="module" src="/src/main.ts"></script>
   </body>
 </html>

ios/App/App.xcodeproj/project.pbxproj

@@ -403,7 +403,7 @@
 			buildSettings = {
 				ASSETCATALOG_COMPILER_APPICON_NAME = AppIcon;
 				CODE_SIGN_STYLE = Automatic;
-				CURRENT_PROJECT_VERSION = 39;
+				CURRENT_PROJECT_VERSION = 40;
 				DEVELOPMENT_TEAM = GM3FS5JQPH;
 				ENABLE_APP_SANDBOX = NO;
 				ENABLE_USER_SCRIPT_SANDBOXING = NO;
@@ -413,7 +413,7 @@
 					"$(inherited)",
 					"@executable_path/Frameworks",
 				);
-				MARKETING_VERSION = 1.0.6;
+				MARKETING_VERSION = 1.0.7;
 				OTHER_SWIFT_FLAGS = "$(inherited) \"-D\" \"COCOAPODS\" \"-DDEBUG\"";
 				PRODUCT_BUNDLE_IDENTIFIER = app.timesafari;
 				PRODUCT_NAME = "$(TARGET_NAME)";
@@ -430,7 +430,7 @@
 			buildSettings = {
 				ASSETCATALOG_COMPILER_APPICON_NAME = AppIcon;
 				CODE_SIGN_STYLE = Automatic;
-				CURRENT_PROJECT_VERSION = 39;
+				CURRENT_PROJECT_VERSION = 40;
 				DEVELOPMENT_TEAM = GM3FS5JQPH;
 				ENABLE_APP_SANDBOX = NO;
 				ENABLE_USER_SCRIPT_SANDBOXING = NO;
@@ -440,7 +440,7 @@
 					"$(inherited)",
 					"@executable_path/Frameworks",
 				);
-				MARKETING_VERSION = 1.0.6;
+				MARKETING_VERSION = 1.0.7;
 				PRODUCT_BUNDLE_IDENTIFIER = app.timesafari;
 				PRODUCT_NAME = "$(TARGET_NAME)";
 				SWIFT_ACTIVE_COMPILATION_CONDITIONS = "";

ios/App/App/Assets.xcassets/SplashDark.imageset/Contents.json

@@ -0,0 +1,23 @@
+{
+  "images" : [
+    {
+      "filename" : "splash@1x.png",
+      "idiom" : "universal",
+      "scale" : "1x"
+    },
+    {
+      "filename" : "splash@2x.png",
+      "idiom" : "universal",
+      "scale" : "2x"
+    },
+    {
+      "filename" : "splash@3x.png",
+      "idiom" : "universal",
+      "scale" : "3x"
+    }
+  ],
+  "info" : {
+    "author" : "xcode",
+    "version" : 1
+  }
+}

ios/App/app_privacy_manifest_fixer/CHANGELOG.md

@@ -1,30 +1,38 @@
 ## 1.4.1
+
 - Fix macOS app re-signing issue.
 - Automatically enable Hardened Runtime in macOS codesign.
 - Add clean script.
 
 ## 1.4.0
+
 - Support for macOS app ([#9](https://github.com/crasowas/app_privacy_manifest_fixer/issues/9)).
 
 ## 1.3.11
+
 - Fix install issue by skipping `PBXAggregateTarget` ([#4](https://github.com/crasowas/app_privacy_manifest_fixer/issues/4)).
 
 ## 1.3.10
+
 - Fix app re-signing issue.
 - Enhance Build Phases script robustness.
 
 ## 1.3.9
+
 - Add log file output.
 
 ## 1.3.8
+
 - Add version info to privacy access report.
 - Remove empty tables from privacy access report.
 
 ## 1.3.7
+
 - Enhance API symbols analysis with strings tool.
 - Improve performance of API usage analysis.
 
 ## 1.3.5
+
 - Fix issue with inaccurate privacy manifest search.
 - Disable dependency analysis to force the script to run on every build.
 - Add placeholder for privacy access report.
@@ -32,27 +40,34 @@
 - Add examples for privacy access report.
 
 ## 1.3.0
+
 - Add privacy access report generation.
 
 ## 1.2.3
+
 - Fix issue with relative path parameter.
 - Add support for all application targets.
 
 ## 1.2.1
+
 - Fix backup issue with empty user templates directory.
 
 ## 1.2.0
+
 - Add uninstall script.
 
 ## 1.1.2
+
 - Remove `Templates/.gitignore` to track `UserTemplates`.
 - Fix incorrect use of `App.xcprivacy` template in `App.framework`.
 
 ## 1.1.0
+
 - Add logs for latest release fetch failure.
 - Fix issue with converting published time to local time.
 - Disable showing environment variables in the build log.
 - Add `--install-builds-only` command line option.
 
 ## 1.0.0
-- Initial version.
+
+- Initial version.

ios/App/app_privacy_manifest_fixer/README.md

@@ -150,6 +150,7 @@ The privacy manifest templates are stored in the [`Templates`](https://github.co
 ### Template Types
 
 The templates are categorized as follows:
+
 - **AppTemplate.xcprivacy**: A privacy manifest template for the app.
 - **FrameworkTemplate.xcprivacy**: A generic privacy manifest template for frameworks.
 - **FrameworkName.xcprivacy**: A privacy manifest template for a specific framework, available only in the `Templates/UserTemplates` directory.
@@ -157,20 +158,24 @@ The templates are categorized as follows:
 ### Template Priority
 
 For an app, the priority of privacy manifest templates is as follows:
+
 - `Templates/UserTemplates/AppTemplate.xcprivacy` > `Templates/AppTemplate.xcprivacy`
 
 For a specific framework, the priority of privacy manifest templates is as follows:
+
 - `Templates/UserTemplates/FrameworkName.xcprivacy` > `Templates/UserTemplates/FrameworkTemplate.xcprivacy` > `Templates/FrameworkTemplate.xcprivacy`
 
 ### Default Templates
 
 The default templates are located in the `Templates` root directory and currently include the following templates:
+
 - `Templates/AppTemplate.xcprivacy`
 - `Templates/FrameworkTemplate.xcprivacy`
 
 These templates will be modified based on the API usage analysis results, especially the `NSPrivacyAccessedAPIType` entries, to generate new privacy manifests for fixes, ensuring compliance with App Store requirements.
 
 **If adjustments to the privacy manifest template are needed, such as in the following scenarios, avoid directly modifying the default templates. Instead, use a custom template. If a custom template with the same name exists, it will take precedence over the default template for fixes.**
+
 - Generating a non-compliant privacy manifest due to inaccurate API usage analysis.
 - Modifying the reason declared in the template.
 - Adding declarations for collected data.
@@ -198,6 +203,7 @@ The privacy access API categories and their associated declared reasons in `Fram
 ### Custom Templates
 
 To create custom templates, place them in the `Templates/UserTemplates` directory with the following structure:
+
 - `Templates/UserTemplates/AppTemplate.xcprivacy`
 - `Templates/UserTemplates/FrameworkTemplate.xcprivacy`
 - `Templates/UserTemplates/FrameworkName.xcprivacy`
@@ -205,6 +211,7 @@ To create custom templates, place them in the `Templates/UserTemplates` director
 Among these templates, only `FrameworkTemplate.xcprivacy` will be modified based on the API usage analysis results to adjust the `NSPrivacyAccessedAPIType` entries, thereby generating a new privacy manifest for framework fixes. The other templates will remain unchanged and will be directly used for fixes.
 
 **Important Notes:**
+
 - The template for a specific framework must follow the naming convention `FrameworkName.xcprivacy`, where `FrameworkName` should match the name of the framework. For example, the template for `Flutter.framework` should be named `Flutter.xcprivacy`.
 - For macOS frameworks, the naming convention should be `FrameworkName.Version.xcprivacy`, where the version name is added to distinguish different versions. For a single version macOS framework, the `Version` is typically `A`.
 - The name of an SDK may not exactly match the name of the framework. To determine the correct framework name, check the `Frameworks` directory in the application bundle after building the project.

ios/App/app_privacy_manifest_fixer/README.zh-CN.md

@@ -40,7 +40,7 @@
    ```shell
    sh install.sh <project_path>
    ```  
-   
+
    - 如果是 Flutter 项目，`project_path`应为 Flutter 项目中的`ios/macos`目录路径。
    - 重复运行安装命令时，工具会先移除现有安装（如果有）。若需修改命令行选项，只需重新运行安装命令，无需先卸载。
 
@@ -150,6 +150,7 @@ sh clean.sh
 ### 模板类型
 
 模板分为以下几类：
+
 - **AppTemplate.xcprivacy**：App 的隐私清单模板。
 - **FrameworkTemplate.xcprivacy**：通用的 Framework 隐私清单模板。
 - **FrameworkName.xcprivacy**：特定的 Framework 隐私清单模板，仅在`Templates/UserTemplates`目录有效。
@@ -157,20 +158,24 @@ sh clean.sh
 ### 模板优先级
 
 对于 App，隐私清单模板的优先级如下：
+
 - `Templates/UserTemplates/AppTemplate.xcprivacy` > `Templates/AppTemplate.xcprivacy`
 
 对于特定的 Framework，隐私清单模板的优先级如下：
+
 - `Templates/UserTemplates/FrameworkName.xcprivacy` > `Templates/UserTemplates/FrameworkTemplate.xcprivacy` > `Templates/FrameworkTemplate.xcprivacy`
 
 ### 默认模板
 
 默认模板位于`Templates`根目录，目前包括以下模板：
+
 - `Templates/AppTemplate.xcprivacy`
 - `Templates/FrameworkTemplate.xcprivacy`
 
 这些模板将根据 API 使用分析结果进行修改，特别是`NSPrivacyAccessedAPIType`条目将被调整，以生成新的隐私清单用于修复，确保符合 App Store 要求。
 
 **如果需要调整隐私清单模板，例如以下场景，请避免直接修改默认模板，而是使用自定义模板。如果存在相同名称的自定义模板，它将优先于默认模板用于修复。**
+
 - 由于 API 使用分析结果不准确，生成了不合规的隐私清单。
 - 需要修改模板中声明的理由。
 - 需要声明收集的数据。
@@ -198,6 +203,7 @@ sh clean.sh
 ### 自定义模板
 
 要创建自定义模板，请将其放在`Templates/UserTemplates`目录，结构如下：
+
 - `Templates/UserTemplates/AppTemplate.xcprivacy`
 - `Templates/UserTemplates/FrameworkTemplate.xcprivacy`
 - `Templates/UserTemplates/FrameworkName.xcprivacy`
@@ -205,6 +211,7 @@ sh clean.sh
 在这些模板中，只有`FrameworkTemplate.xcprivacy`会根据 API 使用分析结果对`NSPrivacyAccessedAPIType`条目进行调整，以生成新的隐私清单用于 Framework 修复。其他模板保持不变，将直接用于修复。
 
 **重要说明：**
+
 - 特定的 Framework 模板必须遵循命名规范`FrameworkName.xcprivacy`，其中`FrameworkName`需与 Framework 的名称匹配。例如`Flutter.framework`的模板应命名为`Flutter.xcprivacy`。
 - 对于 macOS Framework，应遵循命名规范`FrameworkName.Version.xcprivacy`，额外增加版本名称用于区分不同的版本。对于单一版本的 macOS Framework，`Version`通常为`A`。
 - SDK 的名称可能与 Framework 的名称不完全一致。要确定正确的 Framework 名称，请在构建项目后检查 App 包中的`Frameworks`目录。
@@ -229,7 +236,7 @@ sh Report/report.sh <app_path> <report_output_path>
 |------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------|
 | ![Original App Report](https://img.crasowas.dev/app_privacy_manifest_fixer/20241218230746.png) | ![Fixed App Report](https://img.crasowas.dev/app_privacy_manifest_fixer/20241218230822.png) |
 
-## 💡 重要考量 
+## 💡 重要考量
 
 - 如果最新版本的 SDK 支持隐私清单，请尽可能升级，以避免不必要的风险。
 - 此工具仅为临时解决方案，不应替代正确的 SDK 管理实践。