trent_larson/crowd-funder-for-time-pwa - crowd-funder-for-time-pwa - Gitea: Git with a cup of tea

Author	SHA1	Message	Date
Matthew Raymer	831532739c	feat: implement 72-hour JWT token refresh for daily notification plugin - Add accessTokenForBackground() with 72-hour default expiration - Supports offline-first prefetch operations - Balances security with offline capability - Implement proactive token refresh strategy - Refresh on component mount (DailyNotificationSection) - Refresh on app resume (Capacitor 'resume' event) - Refresh when notifications are enabled - Automatic refresh without user interaction - Update CapacitorPlatformService.configureNativeFetcher() - Automatically retrieves activeDid from database - Generates 72-hour JWT tokens for background operations - Includes starred plans in configuration - Add BroadcastReceivers to AndroidManifest.xml - DailyNotificationReceiver for scheduled notifications - BootReceiver for rescheduling after device reboot - Add comprehensive documentation - JSDoc comments for all token-related functions - Inline comments explaining refresh strategy - Documentation section on authentication & token management Benefits: - No app wake-up required (refresh when app already open) - Works offline (72-hour validity supports extended periods) - Automatic (no user interaction required) - Graceful degradation (uses cached content if refresh fails)	7 days ago
Matthew Raymer	45eff4a9ac	docs: add plugin state sync, time update logic, and component extraction - Update initialization to sync with plugin state on mount (checks for pre-existing schedules) - Add updateNotificationTime() method to update schedule when time changes (cancel old, schedule new) - Extract DailyNotificationSection into dedicated component using vue-facing-decorator - Update component architecture to show DailyNotificationSection.vue structure - Update Phase 2 tasks to reflect component creation and AccountViewView integration - Add acceptance criteria for plugin state sync and time update functionality - Update verification checklist with new requirements	1 week ago
Matthew Raymer	ae5f1a33a7	docs: add checkboxes to all actionable items in integration plan - Add checkboxes to Phase 1, 2, 3 task sub-items - Add checkboxes to Milestone success criteria - Add checkboxes to Testing Strategy test items - Add checkboxes to Risk Mitigation mitigation items - Add checkboxes to Next Steps - All actionable items now have checkboxes for tracking progress	1 week ago
Matthew Raymer	95ac1afcd2	docs: remove independent views, focus on AccountViewView integration only - Remove ScheduleView, NotificationsView, NotificationHistoryView, NotificationSettingsView - Remove router routes for independent views - Remove Pinia store (not needed - state managed locally) - Remove HomeView diagnostics integration - Remove native fetcher configuration integration - Keep only AccountViewView integration with optional supporting components - Update all phases to focus on AccountViewView only - Update milestones and testing strategy - Update dependencies to remove router/pinia references - Clarify supporting components are optional and only if AccountViewView exceeds length limits	1 week ago
Matthew Raymer	7ae3b241dd	docs: add explicit requirement for components to hide on unsupported platforms - Add CRITICAL REQUIREMENT in Platform Detection Strategy section - Add Component Visibility Requirements listing all components - Add Component Visibility Requirements section in Implementation Notes - Include required pattern with code examples for component hiding - Add verification checklist for component hiding - Update Phase 2 tasks to require platform support checks - Update Phase 3 tasks to require hiding for all notification views - Add Risk 6 for components visible on unsupported platforms - Update acceptance criteria to verify component hiding - Update success criteria to verify hiding on Web/Electron platforms	1 week ago
Matthew Raymer	ced8248436	docs: merge AccountViewView integration strategy into main plan - Consolidate AccountViewView integration strategy into unified plan - Add comprehensive AccountViewView Integration Strategy section - Include UI component design, data flow, and implementation decisions - Remove separate strategy document to follow meta_feature_planning structure - Update Phase 2 to include AccountViewView integration tasks	1 week ago
Matthew Raymer	d576920810	docs: add daily notification plugin integration planning documents - Add comprehensive integration plan following meta_feature_planning workflow - Add AccountViewView integration strategy with PlatformService approach - Document architecture decisions: PlatformService interface integration - Remove web/push notification references - Document implementation phases and acceptance criteria	1 week ago