Implement P0-P5 directives for operator clarity, consistent outcomes, and
easy evidence capture across all test phases.
Changes:
- alarm-test-lib.sh: Add evidence collection (capture_alarms, capture_logcat,
capture_screenshot), verdict functions (verdict_pass/warn/fail), run directory
management, and release gating support (RELEASE_GATE_PHASE3)
- test-phase1.sh: Refactor to unified framework with CLI modes (--setup,
--run, --smoke, --all, --ci), micro-prompts, evidence capture, and verdict
blocks for all 5 tests
- test-phase2.sh: Add evidence capture, verdict blocks, and STRICTNESS policy
(soft/hard) for warn vs fail behavior
- test-phase3.sh: Add evidence capture, verdict blocks, release gating
(--gate-phase3), and fatigue reduction (time estimates, automation hints)
- RUNBOOK-TESTING.md: New comprehensive operator guide (669 lines) covering
prerequisites, all phases, evidence locations, verdict interpretation,
common failures, and troubleshooting
All test scripts now use consistent UI helpers (section, substep, info, ok,
warn, error), standardized evidence collection, and clear verdict reporting.
Evidence is saved to timestamped run directories (runs/<RUN_ID>/) with alarms,
logs, and screenshots organized by test phase and scenario.
Tests pass with consistent presentation and reproducible evidence collection.
Add documentation files for P2.1 Batch A refactoring:
- BATCH_A_COMPLETION_SUMMARY.md: Summary of 7 completed refactorings
- SESSION_RECONSTITUTION.md: Session reconstitution notes and verification
These documents track the completion of Batch A work and provide context
for future reference and session continuation.
Refs: docs/progress/P2.1-BATCH-A-STATE.md
P2.1: iOS Schema Versioning Strategy
- Added SCHEMA_VERSION constant and checkSchemaVersion() method in PersistenceController
- Version stored in NSPersistentStore metadata (observability contract, not migration gate)
- CoreData auto-migration remains authoritative; version mismatches logged, not blocked
- Documentation added to ios/Plugin/README.md with migration contract
P2.2: Combined Edge Case Tests
- Added 3 resilience test scenarios to DailyNotificationRecoveryTests.swift:
- test_combined_dst_boundary_duplicate_delivery_cold_start()
- test_combined_rollover_duplicate_delivery_cold_start()
- test_combined_schema_version_cold_start_recovery()
- All tests labeled with @resilience @combined-scenarios comments
- Tests verify idempotency and correctness under combined stressors
P2.3: Android Combined Tests Design
- Created P2.3-DESIGN.md with scope, invariants, and acceptance criteria
- Created P2.3-IMPLEMENTATION-CHECKLIST.md with step-by-step execution plan
- Design ready for implementation to achieve parity with iOS P2.2
Documentation Updates
- Fixed parity matrix: iOS invalid data handling now correctly shows "✅ Recovery tested" with test references
- Updated progress docs (00-STATUS.md, 01-CHANGELOG-WORK.md, 03-TEST-RUNS.md, 04-PARITY-MATRIX.md)
- Updated P2-DESIGN.md to reflect P2.3 scope (Android combined tests)
- Updated SYSTEM_INVARIANTS.md baseline tag references
Baseline Tag
- Created and pushed v1.0.11-p2-complete tag
- Tag represents P2.x completion (schema versioning + combined resilience tests)
All invariants preserved. CI passes. Tests runnable via xcodebuild on macOS.
Fix issue where prefetch worker saved content to ContentCache but didn't
create NotificationContentEntity, causing notification worker to skip
notifications with "content_not_found" error.
Changes:
- Extract notificationTime from input data in doWork()
- Create NotificationContentEntity with matching notification_id when
notificationTime > 0 (prefetch operations)
- Add parsePayload() helper to extract title/body from JSON or plain text
- Save entity to Room database so notification worker can find it
The notification_id format matches NotifyReceiver.kt: "notify_${notificationTime}",
ensuring the notification worker can retrieve content when the alarm fires.
Fixes issue where alarms triggered correctly but notifications were skipped
because DailyNotificationWorker couldn't find content in storage.
Fix reflection-based permission check that was failing with NoSuchMethodException.
Add multiple fallback strategies to ensure permission check works reliably.
Changes:
- Add getDeclaredMethod() fallback when getMethod() fails
- Add heuristic fallback: if exact alarms not allowed, assume they can be requested
- Improve error handling: catch NoSuchMethodException separately from other exceptions
- Add debug logging to track which reflection path is taken
- Change reflection failure log level from ERROR to WARNING (we have fallback)
The heuristic fallback is safe because:
- If exact alarms are not currently allowed, we should try to request them
- Only edge case is permanently denied (rare), worst case is unnecessary Settings redirect
- Better than failing silently or blocking permission requests
Fixes reflection failures seen in logcat where Settings.canRequestScheduleExactAlarms()
method lookup was failing, causing unnecessary Settings redirects.
Add comprehensive exact alarm permission handling for Android 12+ (API 31+)
and fix critical bugs preventing notifications from triggering.
Features:
- Add checkExactAlarmPermission() and requestExactAlarmPermission() plugin methods
- Add canScheduleExactAlarms() and canRequestExactAlarmPermission() helper methods
- Update all scheduling methods to check/request permission before scheduling
- Use reflection for canRequestScheduleExactAlarms() to avoid compilation issues
Bug Fixes:
- Fix receiver mismatch: change alarm intents from NotifyReceiver to DailyNotificationReceiver
- Fix coroutine compilation error: wrap getLatest() suspend call in runBlocking
- Store notification content in database before scheduling alarms
- Update intent action to match manifest registration
The permission request flow opens Settings intent when SCHEDULE_EXACT_ALARM
permission is not granted, providing clear user guidance. All scheduling
methods now check permission status and request it if needed before proceeding.
Version bumped to 1.0.8
- Add cancelAllNotifications() method to DailyNotificationPlugin
- Cancels all AlarmManager alarms (exact and inexact)
- Cancels all WorkManager prefetch/fetch jobs by tag
- Clears notification schedules from database (sets enabled=false)
- Idempotent - safe to call multiple times
- Implementation details:
- Reads scheduled notifications from database
- Uses NotifyReceiver.cancelNotification() for each scheduled alarm
- Includes fallback cleanup for orphaned alarms
- Cancels WorkManager jobs with tags: prefetch, daily_notification_fetch,
daily_notification_maintenance, soft_refetch, daily_notification_display,
daily_notification_dismiss
- Disables all notification and fetch schedules in database
- Add required imports:
- android.app.PendingIntent for alarm cancellation
- androidx.work.WorkManager for job cancellation
- Error handling:
- Gracefully handles missing alarms/jobs (logs warnings, doesn't fail)
- Continues cleanup even if individual operations fail
- Comprehensive logging for debugging
Fixes:
- 'not implemented' error when host app calls cancelAllNotifications()
- Enables users to update notification time without errors
- Allows users to disable notifications completely
- Prevents orphaned alarms and jobs after cancellation
The method matches TypeScript interface and is ready for use.
- Fix MainActivity ClassNotFoundException by using dynamic package launcher intent
- Replace hardcoded MainActivity class references with getLaunchIntent() helper
- Uses packageManager.getLaunchIntentForPackage() to work with any host app
- Removes dependency on specific MainActivity package/class name
- Fixes 3 occurrences in NotifyReceiver.kt (alarm clock, notification click, reminder click)
- Add exact alarm permission check before scheduling (Android 12+)
- Add canScheduleExactAlarms() helper to check SCHEDULE_EXACT_ALARM permission
- Check permission before scheduling exact alarms in scheduleExactNotification()
- Gracefully fall back to inexact alarms when permission not granted
- Prevents SecurityException and provides clear logging
- Bump version to 1.0.2
Fixes:
- ClassNotFoundException when plugin tries to resolve hardcoded MainActivity path
- SecurityException on Android 12+ when exact alarm permission not granted
- Plugin now works with any host app regardless of MainActivity package/class
All changes maintain backward compatibility and improve reliability.
- Update JWT section to reflect current status:
- JWT Generation: ✅ COMPLETE (TypeScript generates ES256K correctly)
- JWT Verification: 🟡 PARTIAL (generation works, server verification fails)
- Document verification issue:
- Error: 'no matching public key found'
- Root cause: Server cannot resolve DID to get public key
- JWT signature is cryptographically valid
- Issue is DID resolution, not JWT generation
- Add verification status table:
- Component-level status breakdown
- Clear distinction between generation (✅) and verification (❌)
- Add next steps checklist:
- Verify DID registration on resolver
- Test with known DID
- Check server resolver config
- Verify test API server supports DID-based JWT verification
- Update implementation status:
- Mark TypeScript JWT generation as complete
- Mark DID resolution as pending verification
- Remove outdated HMAC-SHA256 references
- Fix TestNativeFetcher to read from same SharedPreferences as plugin
- Changed PREFS_NAME from 'DailyNotificationPrefs' to 'daily_notification_timesafari'
- Changed KEY_STARRED_PLAN_IDS from 'starred_plan_ids' to 'starredPlanIds'
- Updated getStarredPlanIds() to read from plugin's SharedPreferences location
- Added diagnostic logging for plan ID loading
- Add updateStarredPlans() call in App.vue mounted() hook
- Ensures starred plan IDs are persisted to native storage on app startup
- Allows native fetcher to read plan IDs from SharedPreferences
- Added diagnostic logging for configuration flow
- Document cross-platform storage pattern
- Created docs/CROSS_PLATFORM_STORAGE_PATTERN.md with architecture flow
- Documented TypeScript → Capacitor bridge → Plugin → Native storage → Native fetcher flow
- Added iOS implementation checklist with code examples
- Clarified why native storage is needed (background workers can't use bridge)
- Add JWT generation logging to test-user-zero.ts
- Log JWT algorithm (ES256K) and DID when token is generated
- Helps diagnose JWT verification issues
Fixes:
- Empty planIds array in native fetcher requests
- SharedPreferences key mismatch between plugin and native fetcher
- Missing documentation for iOS implementation
All changes maintain backward compatibility.
- Move native fetcher configuration from HomeView.vue to App.vue mounted() hook
- Single source of truth for configuration on app startup
- Removed duplicate configuration logic from HomeView
- Added diagnostic logging to trace configuration flow
- Fix ES module compatibility issue with Capacitor CLI
- Replace direct logger import with lazy async loading in test-user-zero.ts
- Prevents 'exports is not defined' error when Capacitor CLI loads config
- Update refreshToken() and setBaseUrl() methods to async for logger access
- Add centralized logger utility (src/lib/logger.ts)
- Single ESLint whitelist location for console usage
- Structured logging with levels and emoji support
- Updated router/index.ts and stores/app.ts to use logger
- Enhance Android notification deduplication
- Add within-batch duplicate detection in fetch workers
- Improve storage deduplication with alarm cancellation
- Cancel alarms for removed duplicate notifications
- Update UserZeroView.vue to await async refreshToken() call
Fixes:
- npx cap sync android ES module error
- Duplicate notification accumulation
- Console statement lint warnings
All changes maintain backward compatibility and improve debugging visibility.
Fix critical bug where NotificationContent deserializer was corrupting
notification data every time storage was loaded:
1. Deserializer was creating new NotificationContent() which:
- Generated new random UUIDs (losing original IDs)
- Set fetchedAt to current time (losing original timestamps)
- Caused excessive debug logging (40+ log lines per load)
2. This caused:
- Notifications to appear as 'new' on every app restart
- Duplicate notification detection to fail (different IDs)
- Log spam making debugging difficult
- 40+ notifications accumulating over time
Changes:
- Add package-private constructor NotificationContent(id, fetchedAt) to
preserve original data during deserialization
- Update NotificationContentDeserializer to read fetchedAt from JSON
and use new constructor to preserve original values
- Remove excessive constructor logging that caused log spam
- Preserve notification IDs during deserialization
This ensures notifications maintain their original identity and timestamps
when loaded from persistent storage, preventing data corruption and
duplicate accumulation.
Fixes issue where prefetch correctly skipped but 40+ notifications
accumulated due to deserializer corruption.
Add eslint-disable-next-line comments for intentional console.log statements
in test configuration and router files. These console statements are
intentional for debugging and testing purposes.
Files updated:
- test-user-zero.ts: 5 console statements suppressed
- router/index.ts: 2 console statements suppressed
All lint warnings resolved.
Add comprehensive documentation and implementation artifacts for refactoring
the plugin to use app-provided content fetchers instead of hardcoded TimeSafari
integration.
Changes:
- Add integration-point-refactor-analysis.md with complete ADR, interfaces,
migration plan, and 7-PR breakdown
- Add INTEGRATION_REFACTOR_QUICK_START.md for quick reference on new machines
- Add src/types/content-fetcher.ts with TypeScript SPI interfaces
- Add examples/native-fetcher-android.kt with Kotlin implementation skeleton
- Add examples/js-fetcher-typescript.ts with TypeScript implementation skeleton
- Add tests/fixtures/test-contract.json for golden contract testing
Architecture Decisions:
- Dual-path SPI: Native Fetcher (background) + JS Fetcher (foreground only)
- Background reliability: Native SPI only, no JS bridging in workers
- Reversibility: Legacy code behind feature flag for one minor release
- Test contract: Single JSON fixture for both fetcher paths
This provides complete specification for implementing the refactor in 7 PRs,
starting with SPI shell and progressing through background workers, deduplication,
failure policies, and finally legacy code removal.
All documentation is self-contained and ready for implementation on any machine.
Add comprehensive implementation guide for creating PlanAction claims
via hydratePlan() function pattern, following established hydrateGive()
and hydrateOffer() patterns.
Changes:
- Add hydrate-plan-implementation-guide.md with complete implementation
details, usage examples, and testing recommendations
- Link implementation guide from getting-valid-plan-ids.md Method 6
- Link implementation guide from localhost-testing-guide.md Option B
The guide provides:
- Complete hydratePlan() function implementation
- PlanActionClaim interface structure
- Helper functions (createAndSubmitPlan, editAndSubmitPlan)
- Usage examples and edge cases
- Testing recommendations and security considerations
This complements plan creation documentation by showing how to
programmatically construct valid PlanAction JWTs for POST /api/v2/claim.
Plans are created by importing JWT claims with @type: PlanAction via
POST /api/v2/claim, not through a dedicated plan creation endpoint.
Changes:
- Document POST /api/v2/claim route in localhost-testing-guide.md
- Add Method 6 (PlanAction JWT import) to getting-valid-plan-ids.md
- Update seed-test-projects.js with warnings about PlanAction JWT requirements
- Clarify that seed script cannot create plans (requires DID signing)
This reflects the actual TimeSafari API architecture where plans are
created as a side effect of importing PlanAction claims.
- Update plan handle ID format to match TimeSafari specification
- Default format: https://endorser.ch/entity/{26-char-ULID}
- ULID: 26 characters, Crockford base32 encoded
- Validates RFC 3986 URI format
- Add ULID generation functions
- generateULID() creates 26-character Crockford base32 strings
- generateValidPlanHandleId() creates full URI format IDs
- Auto-generates valid IDs for testing
- Update DEFAULT_TEST_PROJECT_IDS
- Now generates valid URI format IDs automatically
- Removes placeholder warnings (IDs are now valid format)
- Add URI validation to seed scripts
- Validates plan IDs match RFC 3986 URI format
- Error messages with format examples
- Blocks seeding with invalid formats
- Update test-user-zero.ts config
- Auto-generates valid URI format plan IDs
- Clear documentation of required format
- Note that real IDs from database should replace test IDs
- Update documentation
- Document default URI format specification
- Explain ULID structure and encoding
- Show examples of valid formats
This ensures all test project IDs match the actual TimeSafari plan
handle ID format, preventing validation errors during prefetch testing.
- Replace placeholder plan IDs with explicit warnings
- Change from test_project_X to PLACEHOLDER_ID_X
- Add validation to prevent seeding with placeholders
- Add helpful error messages with usage examples
- Add comprehensive guide for getting valid plan IDs
- Methods: Create projects, query database, check account settings
- Format examples: UUID, hash, custom formats
- Step-by-step instructions for each method
- Troubleshooting common issues
- Update test-user-zero.ts with placeholder warnings
- Clear instructions on how to get real plan IDs
- Links to documentation
- Notes about plan ID format variations
- Improve test server startup
- Warn when using placeholder IDs
- Allow plan IDs via command line argument
- Provide guidance on updating config
The previous test_project_X IDs were not valid for real TimeSafari
databases. Users must now provide actual plan handle IDs from their
TimeSafari setup, making testing more realistic and avoiding silent
failures with invalid IDs.
- Add seed-test-projects.js utility script
- Generates test project data matching API schema
- Creates projects with handleIds, jwtIds, planSummary, previousClaim
- Supports export, seed, and generate commands
- Can seed projects to localhost API server
- Add test-api-server-with-seed.js
- Standalone Express server for localhost testing
- Auto-seeds test projects on startup
- Implements /api/v2/report/plansLastUpdatedBetween endpoint
- Includes debugging endpoints (/api/test/projects, /api/test/health)
- Ready to use immediately without database setup
- Update localhost testing guide
- Add seeding instructions and examples
- Document test API server usage
- Explain how to integrate with existing API servers
This enables testing prefetch functionality even when your localhost
API has no project data. The test server can be started immediately
and provides 5 seeded test projects ready for prefetch queries.
- Add serverMode configuration to test-user-zero config
- Supports: localhost, staging, production, mock, custom
- Auto-detects platform (Android/iOS/Web) for localhost URLs
- Android emulator uses 10.0.2.2 for host machine localhost
- Add getApiServerUrl() helper function
- Returns correct URL based on serverMode and platform
- Handles Android emulator special case (10.0.2.2)
- Update TestUserZeroAPI to respect serverMode
- Checks mock mode before making network calls
- Uses getApiServerUrl() for base URL resolution
- Allows runtime URL switching via setBaseUrl()
- Add localhost testing configuration
- Configurable port and HTTPS settings
- Development mode headers support
- Create localhost testing guide
- Step-by-step setup instructions
- Platform-specific localhost addresses explained
- Quick test API server example
- Troubleshooting common issues
- Monitoring prefetch execution commands
- Update Capacitor config to use getApiServerUrl()
- Fixes breaking change from api.server removal
This enables testing prefetch functionality with a local development
API server running on localhost, perfect for development and debugging
of the 5-minute prefetch scheduling feature.
- Add updateStarredPlans() method to update plan IDs from TimeSafari app
- Stores plan IDs in SharedPreferences for persistence
- Integrated with TimeSafariIntegrationManager for prefetch operations
- Includes comprehensive logging for debugging
- Add getStarredPlans() method to retrieve current stored plan IDs
- Allows TimeSafari app to verify synchronization
- Returns count and last update timestamp
- Update TimeSafariIntegrationManager to load starred plan IDs
- Reads from SharedPreferences when building TimeSafariUserConfig
- Used automatically by EnhancedDailyNotificationFetcher for API calls
- Enables dynamic updates without requiring app restart
- Add TypeScript definitions for new methods
- Includes JSDoc documentation for integration guidance
- Matches Android implementation return types
- Create integration example for TimeSafari app
- Shows how to sync plan IDs from account settings
- Demonstrates star/unstar action handling
- Includes verification and error handling patterns
This allows the TimeSafari app to dynamically update starred project
IDs when users star or unstar projects, without requiring plugin
configuration changes or app restarts. The stored IDs are automatically
used by the prefetch system to query for project updates.
- Add comprehensive logging to scheduleBackgroundFetch method
- Log scheduledTime and currentTime for comparison
- Log calculated fetch time and delay in ms, hours, and minutes
- Log detailed timing information for future vs past fetch times
- Add fallback path logging for immediate fetch scenarios
- Add logging to scheduleDailyNotification callback
- Log scheduled notification result with content details
- Log when scheduleBackgroundFetch is called
- Add error logging when notification scheduling fails
- Add WorkManager status logging in DailyNotificationFetcher
- Log work ID when work is enqueued
- Log detailed timing information (delay_ms, delay_hours)
- Add past time detection with duration logging
- Improve immediate fetch fallback logging
- Add prefetch scheduling trace documentation
- Document complete code flow from notification to prefetch
- Include debugging checklist and log search patterns
- Add ADB commands for troubleshooting
These changes enable better debugging of prefetch scheduling issues
by providing detailed timing and execution information at every
decision point in the prefetch scheduling flow.
- Add eslint-disable-next-line no-console comments for development console statements
- Resolve all linting warnings in test-user-zero.ts and router/index.ts
- Maintain clean code quality while allowing debugging output
- Add comprehensive User Zero configuration based on TimeSafari crowd-master
- Implement stars querying API client with JWT authentication
- Create UserZeroView testing interface with mock mode toggle
- Add 5-minute fetch timing configuration for notification scheduling
- Include comprehensive documentation and TypeScript type safety
- Fix readonly array and property access issues
- Add proper ESLint suppressions for console statements
Files added:
- docs/user-zero-stars-implementation.md: Complete technical documentation
- src/config/test-user-zero.ts: User Zero configuration and API client
- src/views/UserZeroView.vue: Testing interface for stars querying
Files modified:
- capacitor.config.ts: Added TimeSafari integration configuration
- src/components/layout/AppHeader.vue: Added User Zero navigation tab
- src/router/index.ts: Added User Zero route
- src/lib/error-handling.ts: Updated type safety
Features:
- Stars querying with TimeSafari API integration
- JWT-based authentication matching crowd-master patterns
- Mock testing system for offline development
- 5-minute fetch timing before notification delivery
- Comprehensive testing interface with results display
- Type-safe implementation with proper error handling
TypeScript Import Fixes:
- Use type-only imports for interfaces in all lib files
- Fix import statements in schema-validation.ts, error-handling.ts, typed-plugin.ts, diagnostics-export.ts, StatusView.vue
ESLint Error Fixes:
- Replace all 'any' types with proper type annotations
- Use 'unknown' for unvalidated inputs with proper type guards
- Use Record<string, unknown> for object properties
- Add proper type casting for Performance API and Navigator properties
- Fix deprecated Vue filter by replacing type assertion with function
StatusCard Component Fixes:
- Fix prop type mismatch by changing template structure
- Add getStatusType() function for type-safe status conversion
- Add getStatusDescription() function for descriptive text
- Update HomeView.vue to use multiple StatusCard components in grid
Android Build Fix:
- Fix capacitor.settings.gradle plugin path from 'android' to 'android/plugin'
- Resolve Gradle dependency resolution issue
- Enable successful Android APK generation
Key improvements:
- Full type safety with proper TypeScript interfaces
- ESLint compliance with no remaining errors
- Successful web and Android builds
- Better error handling with typed error objects
- Improved developer experience with IntelliSense support
StatusView.vue:
- Complete status matrix with 5 core capabilities (postNotifications, exactAlarm, channelEnabled, batteryOptimizations, canScheduleNow)
- Real-time status collection from plugin methods
- Actionable buttons for fixing issues (Request Permission, Open Settings, etc.)
- Comprehensive diagnostics export with JSON copy-to-clipboard
- Error handling and user feedback
- Responsive design with modern UI
StatusCard.vue:
- Redesigned as individual status item cards
- Color-coded status indicators (success/warning/error/info)
- Action buttons for each status item
- Hover effects and smooth transitions
- Mobile-responsive layout
Features implemented:
- Dynamic plugin import and status collection
- Parallel status checking (notificationStatus, permissions, exactAlarmStatus)
- Action handling for permission requests and settings navigation
- Diagnostics export with app version, platform, timezone, capabilities
- Error display and recovery
- Modern glassmorphism UI design
This completes the Status Matrix Module from the implementation plan.
Mark off items that are already implemented in the current codebase:
Phase 1 (Foundation):
- Status Matrix Module: Modular architecture already implemented
- Exact-Alarm Gate: DailyNotificationExactAlarmManager exists
- BootReceiver Idempotent: DailyNotificationRebootRecoveryManager exists
Phase 2 (Testing & Reliability):
- Error handling improvements: DailyNotificationErrorHandler exists
- Structured logging: Event IDs already implemented
Phase 3 (Security & Performance):
- Security hardening: PermissionManager, HTTPS enforcement exist
- Performance optimizations: Multiple optimizers exist
- Diagnostics system: Comprehensive error handling and metrics exist
Acceptance Criteria:
- Error Handling: Most items resolved via error handler
- Reliability: All items resolved via existing managers
- Security: All items resolved via existing security measures
This shows the codebase is much more advanced than the plan suggested - most architectural work is already complete!
Implementation plan hardening:
- Document force-stop limitation: system cancels alarms until next explicit launch
- Add force-stop test case: no delivery until launch, then rescheduler restores schedules
- Make Doze degradation unmistakable: fixed string badge 'Degraded (Doze)' with EVT_DOZE_FALLBACK_TAKEN
- Freeze PendingIntent flags rule as Security AC: FLAG_IMMUTABLE unless mutation required
Analysis doc clarification:
- Add closed vs force-stopped distinction: closing/swiping doesn't affect alarms, force-stopping cancels them
These edits harden edge-cases around force-stop behavior and make Doze degradation UI requirements crystal clear for QA testing.
Implementation plan upgrades:
- Add timezone & manual clock change resilience: TimeChangeReceiver with TIME_SET/TIMEZONE_CHANGED
- Codify PendingIntent flags security: FLAG_IMMUTABLE vs FLAG_MUTABLE with examples
- Add notification posting invariants: channel validation and small icon requirements
- Clarify battery optimization UX limits: no ACTION_REQUEST_IGNORE_BATTERY_OPTIMIZATIONS prompt
- Move MAX_RESPONSE_SIZE to config: Config.NETWORK_MAX_RESPONSE_SIZE with diagnostics inclusion
- Make Room migrations testable: fallbackToDestructiveMigration(false) test requirement
- Enforce event IDs in PR checklist: CI lint script validation for Log. calls
- Make degraded mode UI unmissable: visual badge + one-tap link to exact-alarm settings
- Add channelId snapshot to diagnostics: include channelId, importance, areNotificationsEnabled()
- Add manual clock skew test case: +10m clock move without timezone change
Analysis doc correctness polish:
- Add safe Application class example: show minimal <application> without android:name
- Show minimal BOOT_COMPLETED example: remove android:priority attribute
- Tighten WAKE_LOCK guidance: revisit only if introducing foreground services
- Mirror Cordova guard in Build Config: already present (no change needed)
- Add error surfaces to Mermaid flow: annotate @PluginMethod and Use Case Handler with → Canonical Error
All changes maintain existing structure with surgical precision edits for correctness, resilience, and reviewer clarity.
Implementation plan improvements:
- Fix event name consistency: DOZE_FALLBACK → EVT_DOZE_FALLBACK_TAKEN in Test Matrix
- Lock receiver export policy as AC: only BootReceiver exported
- Handle unknown Content-Length: add streaming guard for -1 responses
- Ensure single joined error mirrors AC: validation failures return one joined message
- Add webDir echo and device idle hint to diagnostics: include webDir path and isDeviceIdleMode
- Make degradation visible in UI AC: matrix shows 'Degraded timing (Doze)' when fallback active
- Add Room migrations guard: no-op migration and fallbackToDestructiveMigration(false) test
Analysis doc improvements:
- Trim WAKE_LOCK guidance: not required unless explicitly acquiring/releasing wakelocks
- Add Boot receiver priority note: android:priority has no effect for BOOT_COMPLETED
- Fix application android:name accuracy: only set if custom Application class exists
- Mirror Cordova compat note in Build section: include only when using Cordova plugins
- Annotate Mermaid flow with canonical errors: show where canonical errors are produced
- Link Truth Table to test UI buttons: integrate with Open Channel/Exact Alarm Settings buttons
All changes maintain existing structure with surgical precision edits.
Analysis doc improvements:
- Unify runtime naming: fix tree diagram cordova.js → capacitor.js
- Make manifest receivers explicit: add exported attributes and intent filters
- Surface exact-alarm user rule: add decision rule for QA/ops reasoning
- Guard Cordova dependency: add note about Cordova shims requirement
- Add error surfacing to runtime flow: show validation and use-case error paths
- Add auto-generated note to capacitor.plugins.json section
Implementation plan improvements:
- Add diagnostics button to Phase 1 DoD
- Add Doze/Idle case to Test Matrix for false negative prevention
- Make unknown field rejection explicit acceptance criterion
- Link receivers export policy to Manifest Hygiene checklist
- Add event ID requirement to PR checklist for grep-able logs
All changes maintain existing structure with surgical precision edits.
- Replace empty TODO with actual plugin integration
- Add dynamic import of DailyNotification plugin
- Implement proper error handling with try/catch
- Add user feedback via alert dialogs
- Add comprehensive logging for debugging
- Fix TypeScript priority type with 'high' as const
- Successfully schedules notifications with AlarmManager
- Verified alarm appears in dumpsys alarm output
The Schedule Notification button now actually calls the native
plugin and schedules notifications instead of being a placeholder.
- Add requestPermissions method alias to fix Vue app compatibility
- Fix permission response format to include both string and boolean values
- Add comprehensive debugging for permission request flow
- Implement permission request throttling to prevent app crashes
- Fix capacitor.settings.gradle plugin path configuration
- Enhance Vue app logging for permission status debugging
Resolves permission dialog not appearing and UI showing incorrect status.
All permission functionality now works end-to-end with proper status updates.
- Fix StatusCard component to properly react to prop changes by using computed() instead of ref()
- Improve plugin detection in HomeView using proper ES6 import instead of window object access
- Add comprehensive status mapping from plugin response to app store format
- Add detailed logging for plugin status, permissions, and exact alarm status
- Add separate Permissions status line in system status display
- Enhance error handling and debugging information for plugin operations
This resolves the issue where StatusCard was not updating when plugin status changed,
and improves the overall reliability of plugin detection and status reporting.
- Import @capacitor/core for Capacitor platform detection
- Import @timesafari/daily-notification-plugin for plugin availability
- Resolves "Plugin: Not Available" issue in test app
Plugin now properly registers and becomes available at runtime.
- Add capacitor.plugins.json for main plugin registration
- Add plugin dependency to test app build configuration
- Add local plugin dependency to test app package.json
- Update package-lock.json with plugin dependency resolution
Enables proper plugin discovery and integration in test environment.
- Fix plugin path in capacitor.settings.gradle to point to correct npm package location
- Remove duplicate local dailynotification module causing class conflicts
- Remove duplicate plugin dependency from app build.gradle
- Resolves Android SDK configuration and build system issues
Build now succeeds with proper plugin integration from npm package.
- Add HomeViewSimple.vue for debugging performance issues
- Configure Vite with decorator support and optimization settings
- Add babelParserPlugins for legacy decorator support
- Optimize dependencies for vue-facing-decorator compatibility
Enables debugging of performance issues and optimizes build process.
- Convert HistoryView, NotFoundView, NotificationsView to Class API
- Convert SettingsView and StatusView to Class API
- Add proper @Component decorators and toNative exports
- Simplify all views for consistent Class API usage
Completes view component conversion to vue-facing-decorator pattern.
- Convert HomeView to Class API with simplified navigation methods
- Convert LogsView to Class API with clipboard functionality and proper types
- Convert ScheduleView to Class API with notification scheduling logic
- Add proper TypeScript types for all view data and methods
- Simplify complex logic for better testing and maintainability
Establishes consistent Class API pattern for main application views.
- Convert ErrorDialog to Class API with proper event handling
- Convert LoadingOverlay to Class API with visibility prop
- Add proper @Prop decorators and event emission methods
- Simplify component logic for better maintainability
Completes UI component conversion to vue-facing-decorator pattern.
- Convert ActionCard to Class API with proper @Prop decorators
- Convert StatusCard to Class API with simplified status management
- Convert AppHeader to Class API with navigation item types
- Convert AppFooter to Class API with platform info display
- Add proper TypeScript types for all component props and data
Ensures consistent Class API usage across all UI components.
- Add reflect-metadata import to main.ts for decorator support
- Convert App.vue to Class API with proper error handling properties
- Simplify router configuration for debugging performance issues
- Remove complex plugin initialization logic for cleaner testing
Establishes foundation for consistent Class API usage across the app.
- Add experimentalDecorators and emitDecoratorMetadata to tsconfig.app.json
- Configure useDefineForClassFields: false for proper class field handling
- Add comprehensive type declarations for vue-facing-decorator@3.0.4
- Create global type declarations for Capacitor and DailyNotification plugin
- Add reflect-metadata support for decorator functionality
Enables proper TypeScript support for Class API components.
- Reorder exports to put 'types' first for proper TypeScript resolution
- Update @types/node to ^20.19.0 to resolve Vite compatibility
- Align Capacitor dependencies to ^6.2.1 for consistency
- Fix npm install conflicts in test app
Resolves build warnings about unreachable 'types' conditions in exports.
- Add GPU-accelerated launch scripts with NVIDIA optimization
- Implement network connectivity troubleshooting and fixes
- Add CPU cores and memory allocation for better performance
- Disable Bluetooth to prevent hangs and ANRs
- Create comprehensive troubleshooting documentation
- Add multiple launch modes: GPU, OpenGL, ANGLE, Mesa, Network Fix
- Include network verification and diagnostic tools
- Add maximum performance mode for high-end systems
- Update documentation with detailed configuration options
Key improvements:
- GPU acceleration with Vulkan support
- Explicit DNS servers (8.8.8.8, 1.1.1.1) for network reliability
- CPU cores allocation (6-8 cores) for better performance
- Memory allocation (4-6GB) for smooth operation
- Bluetooth disabled (-feature -Bluetooth) to prevent hangs
- Clean state launches (-no-snapshot-load, -wipe-data)
- Comprehensive troubleshooting guides and verification scripts
All scripts include proper error checking, environment validation,
and detailed performance monitoring instructions.
- Update @types/node from ^18.15.0 to ^20.19.0 to resolve Vite 7.1.9 compatibility
- Remove unused imports in capacitor-platform-service-clean-integration.ts
- Replace non-null assertions with optional chaining for safer code
- Add explicit return types to all async functions and Vue component methods
- Replace console.log statements with comments for better code quality
- Fix unused parameters by prefixing with underscore
- Change Promise<any> to Promise<unknown> for better type safety
- All 31 linting errors resolved, build now passes cleanly
The plugin is now ready for integration with crowd-funder-for-time-pwa project
with clean TypeScript compilation and zero linting warnings.
- Update AAR file verification path from 'build/outputs/aar/daily-notification-release.aar'
to 'capacitor-cordova-android-plugins/build/outputs/aar/capacitor-cordova-android-plugins-release.aar'
- Fixes build script error where it couldn't find the generated AAR file
- Android builds now complete successfully without false error messages
The build script was looking for a non-existent file path, causing the build to fail
even though the Android compilation was successful. This aligns the verification
path with the actual Gradle output structure.
- Add implementation status table showing all components complete
- Include testing and quality metrics (58 tests, build status)
- Update version information with production-ready status
- Clarify that all platforms have complete feature parity
- Highlight enterprise-grade functionality across Android, iOS, Web
- Add complete Service Worker implementation with IndexedDB storage
- Implement background sync for content fetch and notification delivery
- Add Service Worker Manager for registration and communication
- Include push notification support with VAPID key handling
- Implement TTL-at-fire logic with IndexedDB persistence
- Add callback management with HTTP and local callback support
- Include comprehensive error handling and fallback mechanisms
- Support for periodic sync and background task scheduling
- Mirror Android SQLite and iOS Core Data schema in IndexedDB
BREAKING CHANGE: Web implementation requires Service Worker support and HTTPS
- Add complete iOS plugin implementation with BGTaskScheduler integration
- Implement Core Data model mirroring Android SQLite schema (ContentCache, Schedule, Callback, History)
- Add background task handlers for content fetch and notification delivery
- Implement TTL-at-fire logic with Core Data persistence
- Add callback management with HTTP and local callback support
- Include comprehensive error handling and structured logging
- Add Info.plist configuration for background tasks and permissions
- Support for dual scheduling with BGAppRefreshTask and BGProcessingTask
BREAKING CHANGE: iOS implementation requires iOS 13.0+ and background task permissions
- Add complete SQLite schema with Room database (content_cache, schedules, callbacks, history)
- Implement WorkManager FetchWorker with exponential backoff and network constraints
- Add AlarmManager NotifyReceiver with TTL-at-fire logic and notification delivery
- Create BootReceiver for automatic rescheduling after device reboot
- Update AndroidManifest.xml with necessary permissions and receivers
- Add Room, WorkManager, and Kotlin coroutines dependencies to build.gradle
feat(callback-registry)!: implement callback registry with circuit breaker
- Add CallbackRegistryImpl with HTTP, local, and queue callback support
- Implement circuit breaker pattern with exponential backoff retry logic
- Add CallbackEvent interface with structured event types
- Support for exactly-once delivery semantics with retry queue
- Include callback status monitoring and health checks
feat(observability)!: add comprehensive observability and health monitoring
- Implement ObservabilityManager with structured logging and event codes
- Add performance metrics tracking (fetch, notify, callback times)
- Create health status API with circuit breaker monitoring
- Include log compaction and metrics reset functionality
- Support for DNP-* event codes throughout the system
feat(web)!: enhance web implementation with new functionality
- Integrate callback registry and observability into web platform
- Add mock implementations for dual scheduling methods
- Implement performance tracking and structured logging
- Support for local callback registration and management
- Enhanced error handling and event logging
BREAKING CHANGE: New Android dependencies require Room, WorkManager, and Kotlin coroutines
- Updated directive to accurately reflect Phase 1 completion
- Added status indicators (✅ COMPLETE, 🔄 NEXT PHASE, ❌ NOT IMPLEMENTED)
- Documented current implementation vs pending requirements
- Added summary section for model comparison
- Clarified 85% consistency with perfect API alignment
- Identified next phase: platform-specific implementation
BREAKING CHANGE: Directive now reflects actual codebase state
rather than aspirational requirements
- Added missing configuration methods to all test mocks
- Fixed TypeScript compilation errors in test suite
- All 58 tests now passing successfully
- Ensures test coverage for complete plugin interface
Methods added:
- configure, maintainRollingWindow, getRollingWindowStats
- getExactAlarmStatus, requestExactAlarmPermission, openExactAlarmSettings
- getRebootRecoveryStatus
BREAKING CHANGE: Test mocks now match complete plugin interface
- Reduced from 688 lines to 157 lines (77% reduction)
- Maintained all essential information and architecture
- Applied @markdown_core.mdc formatting standards
- Removed redundant content and verbose explanations
- Focused on actionable next steps and clear requirements
- Single source of truth for research findings
BREAKING CHANGE: Consolidated 5 separate research documents
into single RESEARCH_COMPLETE.md file
- Add comprehensive dual scheduling interfaces to definitions.ts
- Implement ContentFetchConfig, UserNotificationConfig, and DualScheduleConfiguration
- Add new plugin methods for dual scheduling, content management, and callbacks
- Update web implementations with mock functionality for all new methods
- Fix all test files to include new dual scheduling method mocks
- Ensure TypeScript compilation and all tests pass successfully
Resolves: Plugin API design for dual scheduling system implementation
- Remove UI framework considerations (Tailwind, etc.) as irrelevant for Capacitor plugins
- Focus on plugin API design, data models, and platform integration
- Update implementation phases to reflect actual plugin development needs
- Correct conclusion to emphasize plugin architecture over UI components
- Clarify that plugins provide backend functionality, not visual presentation
Resolves: Misunderstanding of Capacitor plugin architecture and UI responsibilities
- Focus plan on implementation phases and priorities
- Update package-lock.json with markdownlint-cli2 dependency
Resolves: Streamline feature planning to focus on implementation approach
- Remove 'Next 1-2 days' from Immediate Actions
- Remove 'Next 1 week' from Short-Term Actions
- Remove 'Next 2-4 weeks' from Medium-Term Actions
- Remove 'timeline' references from action items
- Clean up all time-based language while maintaining structure
- Document now focuses on phases and priorities without misleading estimates
Resolves: Complete removal of unrealistic time estimates
- Fix line length to never exceed 80 characters
- Remove trailing spaces from wrapped lines
- Ensure consistent spacing around all structural elements
- Pass markdownlint validation (0 errors)
- Maintain proper markdown structure and readability
Resolves: Markdown formatting compliance and readability
- Update markdown:check and markdown:fix scripts to only validate project files
- Exclude node_modules from markdown validation to reduce noise
- Focus validation on doc/*.md and root *.md files only
Resolves: Markdown validation noise from external dependencies
- Upgrade Android Gradle Plugin from 8.0.0 to 8.4.0
- Upgrade Google Services plugin from 4.3.15 to 4.4.0
- Upgrade Android SDK from API 33 to API 34
- Upgrade Gradle wrapper from 8.13 to 8.14
- Upgrade Android Gradle wrapper from 8.0.2 to 8.6
- Update AndroidX library versions for API 34 compatibility
- Fix Jest environment configuration issue
- All tests passing (58/58) after upgrades
Resolves: Gradle upgrade requirements for callback system implementation
- Replace 5 separate research documents with single consolidated file
- Eliminate document duplication and overlapping information
- Move documentation from 'docs/' to 'doc/' folder
- Maintain all essential research findings and implementation details
- Improve maintainability with single source of truth
- Follow responsible documentation principles
Resolves: Document multiplication and organization issues
- Add consistent blank lines between sections for better readability
- Clean up formatting for improved document structure
- Maintain all content while improving visual organization
- Create README for research branch with document overview
- Provide index of all research documents and their purposes
- Include key findings and implementation recommendations
- Add technical architecture overview and next steps
- Document security, performance, and testing requirements
- Provide contact information and status updates
Resolves: Complete research documentation overview and navigation
- Create executive summary of research findings
- Document detailed requirements analysis and gap assessment
- Include proposed architecture and implementation strategy
- Add realistic time estimation with detailed effort breakdown
- Include complexity assessment and risk analysis
- Provide next steps and implementation recommendations
- Document security, performance, and testing requirements
Resolves: Complete research documentation for callback system enhancement
- Add consistent blank lines between sections for better readability
- Clean up formatting for improved document structure
- Maintain all content while improving visual organization
- Create detailed implementation plan with task breakdown
- Include realistic time estimates for each phase
- Add technical implementation details and code examples
- Include testing strategy and success criteria
- Add risk mitigation strategies and timeline
- Provide immediate next steps and action items
Resolves: Implementation planning for callback system and dual scheduling
- Create detailed analysis of callback system requirements
- Document dual scheduling method architecture (content fetch vs user notification)
- Include implementation approach with realistic time estimates
- Add complexity assessment and risk analysis
- Provide technical considerations and security guidelines
- Include testing strategy and performance impact analysis
- Document design patterns and platform-specific resources
Resolves: User feedback on callback system and dual scheduling needs
- Add comprehensive analysis of new callback and API integration requirements
- Include dual scheduling method requirements (content fetch vs user notification)
- Conform to realistic time estimation standards with proper phase breakdown
- Add complexity assessment and milestone definitions
- Include technical considerations and risk mitigation strategies
- Update status to research & analysis phase
- Estimated completion: 3-5 days for full implementation
Resolves: User feedback on callback system and dual scheduling needs
- Reorganize cursor rules into logical directories (app/, docs/, features/, etc.)
- Move project.mdc to app/ directory for better organization
- Enhance documentation.mdc with base_context.mdc principles and markdown standards
- Improve time.mdc with comprehensive time handling guidelines
- Remove outdated/unused rule files (general_development, logging, progress_reports, version_control, versioning)
- Establish new documentation standards emphasizing human competence and collaboration
- Ensure all documentation follows markdown.mdc linting rules
This restructuring improves rule discoverability and establishes consistent documentation
standards across the project while maintaining the human competence first approach.
- Fix TypeScript compilation errors and interface mismatches
- Update interface definitions with complete type safety
- Resolve build system issues with Rollup configuration
- Fix web implementation and method signatures
- Update test files to match current interfaces
- Remove duplicate Jest configuration
- Add comprehensive project assessment documentation
Core Improvements:
- Complete interface definitions with proper type safety
- Fix validation logic in daily-notification.ts
- Update web platform implementation with all required methods
- Resolve module import/export issues
- Convert Rollup config to CommonJS for compatibility
Documentation:
- Add PROJECT_ASSESSMENT.md with comprehensive analysis
- Create CRITICAL_IMPROVEMENTS.md with detailed roadmap
- Add IMPROVEMENT_SUMMARY.md with current status
- Document missing Android implementation requirements
- Outline priority improvements and timeline
Build System:
- Fix Rollup configuration syntax
- Remove duplicate Jest configuration
- Ensure successful TypeScript compilation
- Resolve all module resolution issues
Testing:
- Update test files to match current interfaces
- Fix mock implementations and expectations
- Align test structure with actual implementation
Breaking Changes:
- Updated interface definitions for better type safety
- Removed non-existent method references
- Fixed timestamp types (string vs number)
Dependencies:
- No new dependencies added
- Build system compatibility improved
- TypeScript configuration optimized
The project now builds successfully and has a clear roadmap for
restoring the missing Android implementation and completing
production-ready features.
- Update package.json with modern build tooling and dependencies
- Streamline and enhance TypeScript definitions for better type safety
- Reorganize plugin structure for better maintainability
- Add comprehensive interface definitions for notification features
- Implement proper build configuration with rollup
- Update tsconfig.json for stricter type checking and ES2020 modules
Breaking Changes:
- Changed module structure to use ES modules
- Updated interface definitions with stricter typing
- Removed redundant notification options
- Simplified API surface while maintaining core functionality
Dependencies:
- Upgrade @capacitor dependencies to v5.7.8
- Add rollup and typescript build tools
- Update test framework configuration
- Add BatteryOptimizationSettings class for centralized power management
- Implement adaptive scheduling based on power state and battery level
- Add comprehensive battery monitoring and status tracking
- Improve notification reliability with WorkManager integration
- Add maintenance worker for background tasks
- Enhance logging with structured DailyNotificationLogger
- Add configuration management with DailyNotificationConfig
- Define constants in DailyNotificationConstants
- Improve error handling and recovery mechanisms
Security:
- Add proper permission checks for battery optimization
- Implement secure wake lock management
- Add validation for notification parameters
- Use FLAG_IMMUTABLE for PendingIntents
- Implement proper cleanup in handleOnDestroy
Testing:
- Add test coverage for battery optimization features
- Add test coverage for notification scheduling
- Add test coverage for power state management
- Add test coverage for maintenance tasks
Documentation:
- Add comprehensive file-level documentation
- Add method-level documentation
- Add security considerations
- Add performance optimization notes
This commit improves the Android implementation's reliability and battery
efficiency while maintaining feature parity with iOS. It adds robust
error handling, logging, and configuration management to make the plugin
more maintainable and debuggable.
- Add build scripts for Android and iOS platforms
- Remove duplicate web implementation (src/web.ts)
- Add proper TypeScript configuration
- Add module documentation to index.ts
- Clean up package.json scripts
This commit improves the project structure and build process by:
1. Adding dedicated build scripts for native platforms
2. Removing redundant web implementation
3. Adding proper TypeScript configuration with strict mode
4. Improving code documentation
5. Organizing package.json scripts
The changes maintain backward compatibility while improving
the development experience and code quality.
Matthew Raymer