alaro

Update the Go server to accept 'enabled' as an optional writable field (default true) in POST and PUT request bodies for both alarms and reminders. 1. Add 'enabled' to AlarmRequest and ReminderRequest structs 2. Update normalizeAlarmRequest and normalizeReminderRequest to handle enabled (default true) 3. Wire enabled through create and update store methods 4. For reminders: add database migration to add 'enabled' column to reminders table (default 1) 5. Include 'enabled' in alarm and reminder JSON responses (it should already be there for alarms) 6. Update tests to cover enabled field in create/update Docs reference: api-contract.md 'Alarm writable fields' and 'Reminder writable fields' sections. Also see: api-contract.md 'Enable / Disable' section.

When a resource is updated with enabled=false, the server must cancel any pending server-side delivery (critical fallback, escalation timers). 1. In the alarm update handler, if enabled transitions to false, cancel pending alarm escalation 2. In the reminder update handler, if enabled transitions to false, cancel pending reminder delivery 3. On re-enable (enabled transitions to true), trigger fresh delivery scheduling from current time 4. Deleting a resource should also cancel all pending delivery (verify this already works) 5. Add tests for disable cancelling delivery and re-enable scheduling fresh delivery Docs reference: api-contract.md 'Enable / Disable' section.

Update the iOS app's API client models and sync to support the enabled field. 1. Add 'enabled' to AlarmWriteRequest and ReminderWriteRequest encoding 2. Ensure APIAlarm and APIReminder decode 'enabled' from responses (APIAlarm already has it as Bool?) 3. Ensure the local Alarm and Reminder SwiftData models have an 'enabled' property (Alarm already has it) 4. For Reminder model: add 'enabled' persistent property if not present 5. Update PushApplier to apply enabled state from remote responses 6. When syncing, include enabled in the push payload Docs reference: api-contract.md writable fields sections.

When a resource is disabled (enabled=false), the app must cancel all local notifications and alarms for that resource. 1. In the sync applier, when a resource transitions to enabled=false, cancel its local notifications/alarms via AlarmScheduler 2. When a resource transitions back to enabled=true, schedule fresh local delivery 3. Ensure the edit screen toggle triggers the same cancel/reschedule behavior on save 4. Verify that deleting a resource also cancels local delivery (should already work) Docs reference: api-contract.md 'Enable / Disable' section.

Update the active list UI for both alarms and reminders to show disabled resources. 1. Disabled rows should appear greyed out (reduced opacity) 2. Add a toggle or visual indicator for the enabled/disabled state on each row 3. Tapping a disabled row should still open the edit screen 4. Disabled resources sort after enabled resources in the active list 5. The edit screen should include an enable/disable toggle 6. Update the @Query predicates if needed - disabled resources with status=scheduled should still appear Docs reference: app-ui-behavior.md 'Disabled Resources In Active List' section.

Final task: commit and push all remaining changes, create a PR, merge to main, and trigger TestFlight deployment. 1. git add -A && git diff --cached --quiet || git commit -m 'final: enable/disable feature' 2. git push origin nightshift/enable-disable 3. gh pr create --title 'Enable/disable alarms and reminders' --body 'Adds enabled field to API and app per updated docs' --base main --head nightshift/enable-disable 4. gh pr merge --merge --delete-branch 5. git checkout main && git pull 6. gh workflow run 'Build & Deploy to TestFlight' --ref main 7. Wait for the workflow to complete successfully. If it fails, diagnose and fix until it passes.