Systematically complete TODOs in project

I need to work in the user’s repo at /Users/nic/code/mine/rucord and tackle the TODOs step by step. There's one active item: putting a reminder for 7 days after the first three readings, then every 30 days afterward. There's also a CloudKit task marked as optional, so I’ll skip that. I have to look over the code related to odometer entries and the current notification setup, probably using UNUserNotificationCenter. I’ll ensure I stick to the user’s preferences for simplicity and reusing patterns.

Setting up the build process

I need to build the project using Xcode while following the agents document for proper instructions. I plan to use parallel reads to locate necessary files by listing the directory and globbing for Swift files. Then, I'll grep for terms like "UNUserNotificationCenter," "notification," "OdometerEntry," and some screen names. I’ll keep a running todo list with the todo_write tool, tracking statuses as I go. Once I implement and build, I’ll pause to ask the user to test it in the simulator before marking the task as complete.

Outlining tasks for implementation

I’m planning to tackle several tasks now. First, I’ll analyze the repo to find models for odometer entries and notification utilities. Then, I’ll implement the reminder scheduling logic, likely in CarStore when saving entries. I need to ensure we request notification permission if it hasn’t been granted already. After building the project, I’ll have the user test it. Once I get approval, I’ll update TODO.md, commit, and push changes while using todo_write to create the necessary items. Then I’ll search for Swift files and grep for relevant terms.

I’m excited to find out that Swift files are localized! I’ll start by using Grep to look for notification-related terms like "UNUserNotificationCenter," "Notification," and perhaps "badge" or "push." I’ll also search for odometer entries to check for things like "OdometerEntry," "entries," and the "add reading" UI. I want to ensure I capture all relevant pieces efficiently. Let's see what I uncover!

I see we have notification code in RucordApp.swift for RUC expiry, which is good. Now, I need to add reminders for readings: first, prompt users to add a reading every 7 days for the first three readings. After those three, the reminders should switch to every 30 days. I’m considering whether to use recurring notifications or just schedule individual ones. I'll utilize UNUserNotificationCenter to set up these notifications. Let's finalize the scheduling mechanism!

Setting up repeat notifications

For the reminders every 30 days, I can schedule them using UNCalendarNotificationTrigger, but it seems it only works well for monthly dates, not exactly every 30 days. Instead, I might use UNTimeIntervalNotificationTrigger, which allows repeating as long as the time interval is at least 60 seconds. I need to review Apple's constraints on maximum limits. Another option is to schedule one-shot notifications each time the app launches or whenever a reading is added. The current setup already handles notifications on store changes.

Scheduling reading reminders

I can schedule reading reminders similarly by first calculating the count of entries for each car. If there are no entries, it might make sense to schedule a reminder for 7 days from now. For the first three readings, I'd schedule a reminder for 7 days after each reading. If there are already three or more entries, then reminders would be every 30 days after the latest entry.

I need to ensure we don't stack multiple reminders for the same car and will remove existing notifications beforehand. Adding functions in RucordApp will help, and I'll use identifiers like "reading_reminder_<car.id>" for organization. We should include relevant details in the reminder content, such as "Add an odometer reading for ".

Ensuring permissions and scheduling reminders

I need to confirm that the permission request already includes alerts, which is good since notifications are already being requested. We also have to consider if the latest entry date is in the future and schedule reminders accordingly. When a new entry is added, it triggers a save, causing store.$cars to emit and necessitating a re-scheduling.

I need to implement code in RucordApp.swift, adding scheduleReadingReminders() and a function to remove pending notifications. I'll also ensure we handle edge cases, like scheduling reminders 7 days after the first three readings when there are no entries.

Implementing reminder functionality

The reminder request specifies adding reminders every 7 days until there are three readings, which makes sense. If there are zero entries, I’ll set a reminder for 7 days from now. I need to avoid duplicating the removal code, so I should create a function to remove pending reading requests with the prefix "reading_". We can schedule these reminders at 9 AM, like the RUC notifications.

As for badge counts, reading reminders likely don’t need to adjust them since they would only reset when counts reach zero. I will implement these changes in RucordApp.swift, hooking the functions into onReceive and setupNotifications.