Version Unification:
- Updated README.md version from 2.2.0 → 1.0.11
- Updated src/definitions.ts version from 2.0.0 → 1.0.11
- Documented package.json as source of truth
Repo Hygiene:
- Added *.tar.gz and docs.tar.gz to .gitignore
- Added build/reports/ and .gradle/nb-cache/ to .gitignore
- Strengthened Android .gradle exclusions
Created docs/FEEDBACK-RESPONSE-PLAN.md with action plan for
addressing ChatGPT feedback.
Verification:
- Version headers now match package.json ✅
- .gitignore strengthened ✅
Added test run entry to 03-TEST-RUNS.md documenting the
TypeScript error fix verification.
Includes:
- Command executed
- Result (PASS)
- Root cause and fix details
- Verification status
Updated:
- docs/progress/01-CHANGELOG-WORK.md: Added TypeScript error fix entry
- docs/progress/00-STATUS.md: Added TypeScript error fix to completed items
- docs/progress/03-TEST-RUNS.md: Added test run entry for TypeScript fix verification
All progress docs now reflect the successful resolution of the TypeScript
JSDoc parse error.
Changed cron expression from '0 0 */6 * *' to '0 0,6,12,18 * * *'
to avoid TypeScript parser confusion. The '*/' sequence was being
interpreted as the end of a JSDoc comment, causing parse errors.
Verification:
- TypeScript compiles ✅
- Build passes ✅
Removed JSDoc example from saveContentCache that was causing
TypeScript parser to fail with 'Unterminated template literal' error.
The example code block was being parsed as actual code instead of
JSDoc comment, causing parse errors.
Verification:
- TypeScript compiles ✅
- Build passes ✅
Changed template literal in getSchedulesWithStatus JSDoc example
from template literal syntax to string concatenation to avoid
TypeScript parser confusion.
The template literal inside JSDoc code block was being parsed as
actual code, causing 'Unterminated template literal' error.
Verification:
- TypeScript compiles ✅
- Build passes ✅
Created docs/GETTING_STARTED.md with:
- Installation instructions (npm/yarn/pnpm)
- Platform setup (iOS and Android)
- Basic usage examples
- Links to authoritative documentation
- Next steps and support resources
Updated docs/00-INDEX.md to link getting started guide.
Verification:
- Documentation created and linked ✅
- Follows established doc structure ✅
P3.4-A: Enhanced public API JSDoc
- Enhanced createSchedule() with detailed parameter docs and examples
- Enhanced updateSchedule() with examples and error documentation
- Enhanced deleteSchedule() with error documentation
- Enhanced enableSchedule() with examples
P3.4-B: Created troubleshooting guide
- docs/TROUBLESHOOTING.md with common issues and solutions
- Covers CI failures, packaging, platform tests, build, permissions, recovery, performance
- Linked in docs/00-INDEX.md
Verification:
- TypeScript compiles ✅
- JSDoc generates in .d.ts files ✅
- Documentation created and linked ✅
Created:
- docs/examples/QUICK_START.md: Minimal working example with platform setup
- docs/examples/COMMON_PATTERNS.md: Common patterns (error handling, scheduling, recovery)
Updated docs/00-INDEX.md to link examples section.
Verification:
- Documentation created and linked ✅
- Examples follow best practices ✅
With set -euo pipefail, run_check returning 1 causes script to exit immediately.
Added || true to all run_check calls in main() to allow script to continue
and collect all failures before exiting at the end with proper summary.
Note: Script may still have other issues causing early exit - needs further
investigation. Build and TypeScript checks pass independently.
Android build check was causing verify script to exit early due to set -euo pipefail.
Fixed by:
- Using set +e / set -e around gradle command
- Treating Android build failure as warning (expected in standalone context)
- Adding explanatory message about Capacitor app context requirement
Gradle wrapper exists and works - the build failure is expected when Capacitor Android is not available as a dependency (only available in Capacitor app context).
Created src/core/metrics.ts with:
- PerformanceMetric interface
- MetricsCollector interface
- InMemoryMetricsCollector implementation
Updated src/core/index.ts to export metrics.
Note: Web stub (src/web.ts) doesn't need timing instrumentation since it throws immediately. Real instrumentation will be in platform implementations (P3.1-C).
Verification:
- TypeScript compiles ✅
- Core purity check passes ✅
- No new dependencies ✅
Created detailed, file-by-file, function-by-function execution plan for P3.
Includes:
- Exact files to modify
- Exact functions to instrument
- Exact event codes to add
- Exact JSDoc patterns
- Exact commands to run
- Batch-by-batch execution plan
Ready for Cursor execution after approval.
Created P3-DESIGN.md with scope for:
- P3.1: Performance optimization & metrics
- P3.2: Enhanced observability
- P3.3: Developer experience improvements
- P3.4: Documentation polish
Updated baseline tag reference to v1.0.11-p2.3-p1.5b-complete
P3 focuses on polish, performance, and developer experience while maintaining all established invariants.
Moved legacy iOS test harness from ios/App/ to test-apps/ios-app-legacy/
Rationale:
- Test harness should not be in published package tree
- Active test app remains at test-apps/ios-test-app/
- Legacy test harness preserved for reference
Verification:
- Confirmed ios/App no longer appears in npm pack --dry-run
- Build passes successfully
- Package structure cleaner
Progress Docs:
- Updated 00-STATUS.md: marked P1.5b complete
- Updated 01-CHANGELOG-WORK.md: added P1.5b completion entry
Updated 03-TEST-RUNS.md with actual test execution results:
- All 3 combined edge case tests passing (100% success rate)
- Test execution command documented
- Robolectric configuration fix noted
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.
Exclude temporary archive files (*.zip, *.gz) from version control.
These are typically temporary extraction artifacts and should not be
committed.
Author: Matthew Raymer
Add three test buttons (Empty, Invalid, Negative) below the "Test Notification"
button to test invalid time format handling. Each button attempts to schedule
a notification with invalid values: empty string, "25:00" (invalid hour), and
"-1:30" (negative time).
Improve TEST 3 error detection in test-phase1.sh by:
- Making grep case-insensitive to catch ERROR/invalid patterns
- Adding DNP-* error prefix patterns for plugin error logs
- Documenting that Capacitor bridge errors (⚡️ logs) appear in Xcode console
but not in system logs captured by xcrun simctl
The script was using 'local' keyword outside of function scope,
which caused "local: can only be used in a function" error when
running test-phase2.sh. Removed 'local' from three variable
assignments (device_id and logs) at script top level, as 'local'
is only valid inside functions in bash/zsh.
- Fix getNextNotificationTime() to find earliest scheduled notification
instead of using first request (pendingNotificationRequests doesn't
guarantee order)
- Add comprehensive logging for rollover tracking with DNP-ROLLOVER
prefix for Xcode console filtering
- Reset all notifications and rollover state when scheduling new
notification via scheduleDailyNotification() to ensure clean test
state
- Fix userInfo scope error in handleNotificationDelivery error handler
- Update test app UI to refresh status every 5-10 seconds and
immediately after notification delivery to reflect rollover changes
- Add console logging in UI to debug getNotificationStatus() results
This ensures the UI correctly displays the next notification time after
rollover completes, and test notifications start with a clean slate.
Fixed multiple issues in iOS test script and added logging for test compatibility:
Test Script Fixes:
- Fixed get_simulator_id() to correctly extract UUID from booted devices
- Fixed get_app_logs() to use log show (historical) instead of log stream (live) to avoid hanging
- Improved check_plugin_configured() with multiple detection methods (app container, app listing, data directory)
- Added ensure_plugin_configured() function matching Android pattern for consistent user interaction flow
- Fixed integer comparison error in booted device check (removed newlines from count)
- Removed 'local' keyword from variables in main script body (local can only be used in functions)
- Fixed APP_BUNDLE_ID to match actual bundle identifier
Pending Notification Detection:
- Improved get_pending_notifications() to parse pendingCount from plugin logs
- Added direct log query without restrictive predicate to catch plugin logs
- Added multiple fallback methods for detecting pending count
Plugin Logging Enhancement:
- Added explicit pendingCount logging in DailyNotificationScheduler after scheduling
- Uses both NSLog() and print() to ensure logs appear in system logs and Xcode console
- Matches Android's alarm count logging pattern for test script compatibility
This resolves script crashes and enables reliable detection of pending notifications
for automated testing.
Fixed Swift compilation errors preventing iOS build:
- Added explicit self capture [self] in closures in DailyNotificationReactivationManager
- Removed invalid BGTaskScheduler.shared.registeredTaskIdentifiers API call
- Fixed initialization order in DailyNotificationModel (verifyEntities after container init)
Added missing configureNativeFetcher method to iOS plugin:
- Implemented method matching Android functionality
- Stores configuration in UserDefaults for persistence
- Registered method in pluginMethods array
- Supports both jwtToken and jwtSecret parameters for compatibility
This resolves the runtime error "configureNativeFetcher is not a function"
that was preventing the test app from configuring the plugin.
Implement comprehensive data access layer for Core Data entities:
- Add NotificationContentDAO, NotificationDeliveryDAO, and NotificationConfigDAO
with full CRUD operations and query helpers
- Add DailyNotificationDataConversions utility for type conversions
(Date ↔ Int64, Int ↔ Int32, JSON, optional strings)
- Update PersistenceController with entity verification and migration policies
- Add comprehensive unit tests for all DAO classes and data conversions
- Update Core Data model with NotificationContent, NotificationDelivery,
and NotificationConfig entities (relationships and indexes)
- Integrate ReactivationManager into DailyNotificationPlugin.load()
DAO Features:
- Create/Insert methods with dictionary support
- Read/Query methods with predicates (by timesafariDid, notificationType,
scheduledTime range, deliveryStatus, etc.)
- Update methods (touch, updateDeliveryStatus, recordUserInteraction)
- Delete methods (by ID, by key, delete all)
- Relationship management (NotificationContent ↔ NotificationDelivery)
- Cascade delete support
Test Coverage:
- 328 lines: DailyNotificationDataConversionsTests (time, numeric, string, JSON)
- 490 lines: NotificationContentDAOTests (CRUD, queries, updates)
- 415 lines: NotificationDeliveryDAOTests (CRUD, relationships, cascade delete)
- 412 lines: NotificationConfigDAOTests (CRUD, queries, active filtering)
All tests use in-memory Core Data stack for isolation and speed.
Completes sections 4.4, 4.5, and 6.0 of iOS implementation checklist.
Adds complete iOS documentation suite to support iOS implementation
parity with Android features. Includes implementation directives,
recovery scenario mappings, database migration guide, troubleshooting
guide, and test scripts.
New Documentation:
- iOS Implementation Directive: Phase-based implementation guide
mirroring Android structure with iOS-specific considerations
- iOS Recovery Scenario Mapping: Maps Android recovery scenarios
to iOS equivalents with detection logic comparisons
- iOS Core Data Migration Guide: Complete Room → Core Data entity
mappings with implementation checklist for missing entities
- iOS Troubleshooting Guide: Common issues, debugging techniques,
and error code reference
Enhanced Documentation:
- API.md: Added iOS-only methods (permissions, background tasks,
pending notifications), platform differences table, and iOS-specific
error types. Updated version to 2.3.0.
Test Infrastructure:
- iOS test scripts for Phase 1 (cold start), Phase 2 (termination),
and Phase 3 (boot recovery) testing scenarios
All documentation addresses gaps identified in iOS Implementation
Documentation Review and provides foundation for iOS recovery feature
implementation (currently pending).
Note: iOS recovery features (ReactivationManager, scenario detection)
are NOT yet implemented. Documentation is ready to guide implementation.
