# pitt500/clockapp architecture

> Architecture diagram of the GitHub repository pitt500/clockapp, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2026-03-30). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/pitt500/clockapp
- Repository: https://github.com/pitt500/clockapp

## Overview

1. **Repo shape and targets**
   - This is an iOS app built with **SwiftUI**, **Swift Concurrency**, and **ActivityKit/Live Activities**.
   - It has three relevant targets: the main **ClockApp** app, the **TimerLiveActivity** extension for lock screen/Dynamic Island UI, and **ClockAppTests** for behavior/integration coverage.

2. **App entry and screen composition**
   - `ClockApp.swift` is the app entry point and routes into `RootView`.
   - The main timer experience lives in `TimersScreen`, with a UIKit bridge in `TimersScreenUIKit` where needed.
   - The screen layer is mostly presentation-only: it renders timers, detail views, and controls, but does not own business logic.

3. **Central orchestration layer**
   - `TimersStore` is the app’s state/workflow hub.
   - It owns the user-facing state: active timers, recent timers, and the current draft/input state.
   - All user actions funnel through this store, which coordinates timer execution, persistence, and Live Activity updates.

4. **Timer execution engine**
   - `TimerManager` is the countdown engine.
   - It models timer lifecycle states such as running, paused, and idle, and computes remaining time from an `endDate` rather than decrementing a counter.
   - This makes the countdown resilient to delays, backgrounding, and rendering jitter.
   - Completion is callback-driven, so the store can react when a timer finishes.

5. **Domain model boundaries**
   - The domain layer defines the core timer abstractions: `TimerItem`, `TimerProgressSnapshot`, and provider protocols.
   - `TimerProgressProviding` and `TimerDetailProviding` describe what the UI needs without binding it to concrete timer logic.
   - `TimerRowProgressProviderFromManager` and `TimerDetailProviderFromManager` adapt the manager into those domain-facing views of state.

6. **Persistence boundary**
   - `FileTimersPersistence` implements `TimersPersistence` and stores timer recents on disk as a file-backed model.
   - The repo explicitly separates **recents** from **active timers**: recents are persisted, active timers are ephemeral runtime state.
   - This keeps the persistence model simple and avoids trying to serialize live execution state.

7. **Live Activity policy and adapter layers**
   - Live Activities are split into two pieces:
     - `TimerLiveActivityPrioritizer` decides which timer should be surfaced when multiple timers exist.
     - `TimerActivityController` performs the ActivityKit operations to start, update, and end the activity.
   - `NoopTimerActivityHandler` provides a safe non-system or disabled behavior path.
   - This separation keeps “which timer matters” distinct from “how to talk to ActivityKit.”

8. **System integration via App Intents**
   - `TimerAlertCommandCenter` and `TimerLiveActivityCommandCenter` act as command surfaces for timer-related system actions.
   - These are the bridge points for triggering alerts and Live Activity behavior from outside the main SwiftUI flow.
   - The architecture treats them as integration adapters rather than core business logic.

9. **Shared Live Activity rendering**
   - `TimerAttributes` and the views under `Timers/Shared/Views` are shared between the app and the Live Activity extension.
   - These include lock screen and Dynamic Island-specific UI pieces such as compact time, progress rings, control buttons, and timer titles.
   - Shared formatting helpers keep the app and extension visually and behaviorally aligned.

10. **TimerLiveActivity extension boundary**
   - The `TimerLiveActivity` target is a separate widget-style extension package that renders system surfaces.
   - `TimerLiveActivityBundle` and `TimerLiveActivityConfiguration` define the extension entry and configuration.
   - This target is responsible only for system presentation; it does not own timer state or persistence.

11. **Assets and runtime assumptions**
   - The app includes a custom alarm sound (`alarm_pitt.caf`) and standard asset catalogs for app icon, accent color, and widget background.
   - The project targets modern iOS behavior: **iOS 18+**, **Swift 6**, and Live Activities on physical devices.
   - These platform constraints materially shape the architecture because Live Activities and ActivityKit are first-class system integration points.

12. **Testing strategy**
   - Tests focus on behavior: timer countdown logic, store workflows, Live Activity prioritization, and integration scenarios with real time delays.
   - `ClockAppTests` exercises the architecture at subsystem boundaries, which reflects the repo’s emphasis on system design over UI snapshot testing.

13. **Primary data flow**
   - User interaction begins in `TimersScreen`.
   - The UI dispatches actions into `TimersStore`.
   - The store coordinates `TimerManager` for time progression, `FileTimersPersistence` for recents, and `TimerActivityController` for Live Activity updates.
   - When a timer completes, the manager notifies the store, which then finalizes state and updates system surfaces.

14. **Architectural theme**
   - The codebase is organized around **clear separation of concerns**: presentation, orchestration, domain, persistence, and system integration.
   - The main diagram should emphasize that the app is not “just a screen”; it is a timer coordination system with a dedicated execution engine and a separate system-UI extension.

Main entry points: [`ClockApp/Timers/Presentation/State/TimersStore.swift`](https://github.com/pitt500/clockapp/blob/main/ClockApp/Timers/Presentation/State/TimersStore.swift) (Timers store), [`ClockApp/Timers/Presentation/Logic/TimerManager.swift`](https://github.com/pitt500/clockapp/blob/main/ClockApp/Timers/Presentation/Logic/TimerManager.swift) (Timer manager), [`ClockApp/Timers/Data/Activities/TimerActivityController.swift`](https://github.com/pitt500/clockapp/blob/main/ClockApp/Timers/Data/Activities/TimerActivityController.swift) (Activity controller), [`ClockApp/Timers/Presentation/Views/TimersScreen.swift`](https://github.com/pitt500/clockapp/blob/main/ClockApp/Timers/Presentation/Views/TimersScreen.swift) (Timers screen)

## Diagram (Mermaid)

```mermaid
flowchart TD

subgraph group_app["ClockApp"]
  node_clockapp_entry["App entry<br/>[ClockApp.swift]"]
  node_root_view["Root view<br/>app shell<br/>[RootView.swift]"]
end

subgraph group_timers["Timers"]
  node_timers_screen["Timers screen<br/>SwiftUI screen<br/>[TimersScreen.swift]"]
  node_timers_screen_uikit["UIKit bridge<br/>UI adapter"]
  node_timers_store["Timers store<br/>workflow store<br/>[TimersStore.swift]"]
  node_timer_manager["Timer manager<br/>countdown engine<br/>[TimerManager.swift]"]
  node_timer_item["Timer item<br/>domain model<br/>[TimerItem.swift]"]
  node_progress_snapshot["Progress snapshot<br/>domain model"]
  node_progress_provider["Progress provider<br/>protocol"]
  node_detail_provider["Detail provider<br/>protocol"]
  node_row_provider["Row provider<br/>adapter"]
  node_detail_provider_mgr["Detail adapter"]
  node_timers_persistence[("Timers persistence<br/>persistence interface")]
  node_file_persistence[("File storage<br/>file-backed persistence")]
  node_activity_prioritizer["Prioritizer<br/>activity policy"]
  node_activity_controller["Activity controller<br/>ActivityKit adapter"]
  node_noop_activity["No-op handler<br/>safe fallback"]
  node_alert_command_center["Alert commands<br/>App Intents bridge"]
  node_live_activity_commands["Live Activity cmds<br/>App Intents bridge"]
  node_timer_attributes["Timer attributes<br/>Live Activity model"]
  node_shared_live_views["Shared views<br/>shared UI"]
end

subgraph group_extension["Live Activity"]
  node_timer_live_bundle["Activity bundle<br/>extension entry"]
  node_timer_live_config["Activity config<br/>widget configuration"]
end

subgraph group_tests["Tests"]
  node_manager_tests["Manager tests<br/>behavior tests"]
  node_manager_integration_tests["Manager integration<br/>integration tests"]
  node_store_tests["Store tests<br/>behavior tests"]
  node_activity_coord_tests["Activity tests<br/>behavior tests"]
end

node_clockapp_entry -->|"boots"| node_root_view
node_root_view -->|"hosts"| node_timers_screen
node_timers_screen -->|"dispatches"| node_timers_store
node_timers_screen -->|"bridges"| node_timers_screen_uikit
node_timers_store -->|"controls"| node_timer_manager
node_timers_store -->|"persists recents"| node_timers_persistence
node_timers_store -->|"updates"| node_activity_controller
node_timers_store -->|"exposes"| node_alert_command_center
node_timers_store -->|"exposes"| node_live_activity_commands
node_timer_manager -->|"executes"| node_timer_item
node_timer_manager -->|"produces"| node_progress_snapshot
node_timer_manager -->|"adapts to"| node_row_provider
node_timer_manager -->|"adapts to"| node_detail_provider_mgr
node_row_provider -->|"implements"| node_progress_provider
node_detail_provider_mgr -->|"implements"| node_detail_provider
node_file_persistence -->|"implements"| node_timers_persistence
node_activity_controller -->|"uses"| node_activity_prioritizer
node_activity_controller -->|"drives"| node_timer_attributes
node_activity_controller -->|"renders"| node_shared_live_views
node_activity_controller -->|"falls back to"| node_noop_activity
node_shared_live_views -->|"binds to"| node_timer_attributes
node_timer_live_bundle -->|"configures"| node_timer_live_config
node_timer_live_config -->|"renders"| node_shared_live_views
node_manager_tests -->|"verifies"| node_timer_manager
node_manager_integration_tests -->|"verifies"| node_timer_manager
node_store_tests -->|"verifies"| node_timers_store
node_activity_coord_tests -->|"verifies"| node_activity_prioritizer
node_activity_coord_tests -->|"verifies"| node_activity_controller

click node_clockapp_entry "https://github.com/pitt500/clockapp/blob/main/ClockApp/App/ClockApp.swift"
click node_root_view "https://github.com/pitt500/clockapp/blob/main/ClockApp/App/RootView.swift"
click node_timers_screen "https://github.com/pitt500/clockapp/blob/main/ClockApp/Timers/Presentation/Views/TimersScreen.swift"
click node_timers_screen_uikit "https://github.com/pitt500/clockapp/blob/main/ClockApp/Timers/Presentation/Views/TimersScreenUIKit.swift"
click node_timers_store "https://github.com/pitt500/clockapp/blob/main/ClockApp/Timers/Presentation/State/TimersStore.swift"
click node_timer_manager "https://github.com/pitt500/clockapp/blob/main/ClockApp/Timers/Presentation/Logic/TimerManager.swift"
click node_timer_item "https://github.com/pitt500/clockapp/blob/main/ClockApp/Timers/Domain/Entities/TimerItem.swift"
click node_progress_snapshot "https://github.com/pitt500/clockapp/blob/main/ClockApp/Timers/Domain/Entities/TimerProgressSnapshot.swift"
click node_progress_provider "https://github.com/pitt500/clockapp/blob/main/ClockApp/Timers/Domain/Interfaces/TimerProgressProviding.swift"
click node_detail_provider "https://github.com/pitt500/clockapp/blob/main/ClockApp/Timers/Domain/Interfaces/TimerDetailProviding.swift"
click node_row_provider "https://github.com/pitt500/clockapp/blob/main/ClockApp/Timers/Domain/Entities/TimerRowProgressProviderFromManager.swift"
click node_detail_provider_mgr "https://github.com/pitt500/clockapp/blob/main/ClockApp/Timers/Domain/Entities/TimerDetailProviderFromManager.swift"
click node_timers_persistence "https://github.com/pitt500/clockapp/blob/main/ClockApp/Timers/Data/Persistence/TimersPersistence.swift"
click node_file_persistence "https://github.com/pitt500/clockapp/blob/main/ClockApp/Timers/Data/Persistence/FileTimersPersistence.swift"
click node_activity_prioritizer "https://github.com/pitt500/clockapp/blob/main/ClockApp/Timers/Data/Activities/TimerLiveActivityPrioritizer.swift"
click node_activity_controller "https://github.com/pitt500/clockapp/blob/main/ClockApp/Timers/Data/Activities/TimerActivityController.swift"
click node_noop_activity "https://github.com/pitt500/clockapp/blob/main/ClockApp/Timers/Data/Activities/NoopTimerActivityHandler.swift"
click node_alert_command_center "https://github.com/pitt500/clockapp/blob/main/ClockApp/Timers/Shared/AppIntents/TimerAlertCommandCenter.swift"
click node_live_activity_commands "https://github.com/pitt500/clockapp/blob/main/ClockApp/Timers/Shared/AppIntents/TimerLiveActivityCommandCenter.swift"
click node_timer_attributes "https://github.com/pitt500/clockapp/blob/main/ClockApp/Timers/Shared/LiveActivities/TimerAttributes.swift"
click node_shared_live_views "https://github.com/pitt500/clockapp/blob/main/ClockApp/Timers/Shared/Views/LockScreenTimerLiveActivityView.swift"
click node_timer_live_bundle "https://github.com/pitt500/clockapp/blob/main/TimerLiveActivity/TimerLiveActivityBundle.swift"
click node_timer_live_config "https://github.com/pitt500/clockapp/blob/main/TimerLiveActivity/TimerLiveActivityConfiguration.swift"
click node_manager_tests "https://github.com/pitt500/clockapp/blob/main/ClockAppTests/TimerManagerTests.swift"
click node_manager_integration_tests "https://github.com/pitt500/clockapp/blob/main/ClockAppTests/TimerManagerIntegrationTests.swift"
click node_store_tests "https://github.com/pitt500/clockapp/blob/main/ClockAppTests/TimersStoreRecentsAndActivesTests.swift"
click node_activity_coord_tests "https://github.com/pitt500/clockapp/blob/main/ClockAppTests/TimerLiveActivityCoordinatorTests.swift"

classDef toneNeutral fill:#f8fafc,stroke:#334155,stroke-width:1.5px,color:#0f172a
classDef toneBlue fill:#dbeafe,stroke:#2563eb,stroke-width:1.5px,color:#172554
classDef toneAmber fill:#fef3c7,stroke:#d97706,stroke-width:1.5px,color:#78350f
classDef toneMint fill:#dcfce7,stroke:#16a34a,stroke-width:1.5px,color:#14532d
classDef toneRose fill:#ffe4e6,stroke:#e11d48,stroke-width:1.5px,color:#881337
classDef toneIndigo fill:#e0e7ff,stroke:#4f46e5,stroke-width:1.5px,color:#312e81
classDef toneTeal fill:#ccfbf1,stroke:#0f766e,stroke-width:1.5px,color:#134e4a
class node_clockapp_entry,node_root_view toneBlue
class node_timers_screen,node_timers_screen_uikit,node_timers_store,node_timer_manager,node_timer_item,node_progress_snapshot,node_progress_provider,node_detail_provider,node_row_provider,node_detail_provider_mgr,node_timers_persistence,node_file_persistence,node_activity_prioritizer,node_activity_controller,node_noop_activity,node_alert_command_center,node_live_activity_commands,node_timer_attributes,node_shared_live_views toneAmber
class node_timer_live_bundle,node_timer_live_config toneMint
class node_manager_tests,node_manager_integration_tests,node_store_tests,node_activity_coord_tests toneRose
```

## Components

### ClockApp

Main iOS app target and presentation layer

- [App entry](https://github.com/pitt500/clockapp/blob/main/ClockApp/App/ClockApp.swift): SwiftUI app entry · Launches the app and routes into the root view. · `ClockApp/App/ClockApp.swift`
- [Root view](https://github.com/pitt500/clockapp/blob/main/ClockApp/App/RootView.swift): app shell · Top-level composition for the app UI. · `ClockApp/App/RootView.swift`

### Timers

Core timer feature split into domain, orchestration, persistence, and shared integrations

- [Timers screen](https://github.com/pitt500/clockapp/blob/main/ClockApp/Timers/Presentation/Views/TimersScreen.swift): SwiftUI screen · Primary timer experience and presentation surface. · `ClockApp/Timers/Presentation/Views/TimersScreen.swift`
- [UIKit bridge](https://github.com/pitt500/clockapp/blob/main/ClockApp/Timers/Presentation/Views/TimersScreenUIKit.swift): UI adapter · UIKit-backed bridge used where SwiftUI needs platform interop. · `ClockApp/Timers/Presentation/Views/TimersScreenUIKit.swift`
- [Timers store](https://github.com/pitt500/clockapp/blob/main/ClockApp/Timers/Presentation/State/TimersStore.swift): workflow store · Central orchestration for active timers, recents, draft state, persistence, and system updates. · `ClockApp/Timers/Presentation/State/TimersStore.swift`
- [Timer manager](https://github.com/pitt500/clockapp/blob/main/ClockApp/Timers/Presentation/Logic/TimerManager.swift): countdown engine · Tracks running, paused, and idle timers using end dates and completion callbacks. · `ClockApp/Timers/Presentation/Logic/TimerManager.swift`
- [Timer item](https://github.com/pitt500/clockapp/blob/main/ClockApp/Timers/Domain/Entities/TimerItem.swift): domain model · Core timer entity used across the feature. · `ClockApp/Timers/Domain/Entities/TimerItem.swift`
- [Progress snapshot](https://github.com/pitt500/clockapp/blob/main/ClockApp/Timers/Domain/Entities/TimerProgressSnapshot.swift): domain model · Immutable timer progress state for rendering and coordination. · `ClockApp/Timers/Domain/Entities/TimerProgressSnapshot.swift`
- [Progress provider](https://github.com/pitt500/clockapp/blob/main/ClockApp/Timers/Domain/Interfaces/TimerProgressProviding.swift): protocol · UI-facing contract for row progress data. · `ClockApp/Timers/Domain/Interfaces/TimerProgressProviding.swift`
- [Detail provider](https://github.com/pitt500/clockapp/blob/main/ClockApp/Timers/Domain/Interfaces/TimerDetailProviding.swift): protocol · UI-facing contract for timer detail data. · `ClockApp/Timers/Domain/Interfaces/TimerDetailProviding.swift`
- [Row provider](https://github.com/pitt500/clockapp/blob/main/ClockApp/Timers/Domain/Entities/TimerRowProgressProviderFromManager.swift): adapter · Adapts the manager into row progress state. · `ClockApp/Timers/Domain/Entities/TimerRowProgressProviderFromManager.swift`
- [Detail adapter](https://github.com/pitt500/clockapp/blob/main/ClockApp/Timers/Domain/Entities/TimerDetailProviderFromManager.swift): adapter · Adapts the manager into timer detail state. · `ClockApp/Timers/Domain/Entities/TimerDetailProviderFromManager.swift`
- [Timers persistence](https://github.com/pitt500/clockapp/blob/main/ClockApp/Timers/Data/Persistence/TimersPersistence.swift): persistence interface · Boundary for storing timer recents. · `ClockApp/Timers/Data/Persistence/TimersPersistence.swift`
- [File storage](https://github.com/pitt500/clockapp/blob/main/ClockApp/Timers/Data/Persistence/FileTimersPersistence.swift): file-backed persistence · Disk-backed implementation for recent timers. · `ClockApp/Timers/Data/Persistence/FileTimersPersistence.swift`
- [Prioritizer](https://github.com/pitt500/clockapp/blob/main/ClockApp/Timers/Data/Activities/TimerLiveActivityPrioritizer.swift): activity policy · Chooses which timer should be surfaced to Live Activities. · `ClockApp/Timers/Data/Activities/TimerLiveActivityPrioritizer.swift`
- [Activity controller](https://github.com/pitt500/clockapp/blob/main/ClockApp/Timers/Data/Activities/TimerActivityController.swift): ActivityKit adapter · Starts, updates, and ends Live Activities. · `ClockApp/Timers/Data/Activities/TimerActivityController.swift`
- [No-op handler](https://github.com/pitt500/clockapp/blob/main/ClockApp/Timers/Data/Activities/NoopTimerActivityHandler.swift): safe fallback · Disabled or non-system path for activity handling. · `ClockApp/Timers/Data/Activities/NoopTimerActivityHandler.swift`
- [Alert commands](https://github.com/pitt500/clockapp/blob/main/ClockApp/Timers/Shared/AppIntents/TimerAlertCommandCenter.swift): App Intents bridge · System command surface for timer alert actions. · `ClockApp/Timers/Shared/AppIntents/TimerAlertCommandCenter.swift`
- [Live Activity cmds](https://github.com/pitt500/clockapp/blob/main/ClockApp/Timers/Shared/AppIntents/TimerLiveActivityCommandCenter.swift): App Intents bridge · System command surface for Live Activity actions. · `ClockApp/Timers/Shared/AppIntents/TimerLiveActivityCommandCenter.swift`
- [Timer attributes](https://github.com/pitt500/clockapp/blob/main/ClockApp/Timers/Shared/LiveActivities/TimerAttributes.swift): Live Activity model · Shared ActivityKit attributes and state definitions. · `ClockApp/Timers/Shared/LiveActivities/TimerAttributes.swift`
- [Shared views](https://github.com/pitt500/clockapp/blob/main/ClockApp/Timers/Shared/Views/LockScreenTimerLiveActivityView.swift): shared UI · Shared rendering for lock screen, Dynamic Island, and app-aligned timer visuals. · `ClockApp/Timers/Shared/Views/LockScreenTimerLiveActivityView.swift`

### Live Activity

Widget-style extension for lock screen and Dynamic Island surfaces

- [Activity bundle](https://github.com/pitt500/clockapp/blob/main/TimerLiveActivity/TimerLiveActivityBundle.swift): extension entry · Widget extension entry point for Live Activity surfaces. · `TimerLiveActivity/TimerLiveActivityBundle.swift`
- [Activity config](https://github.com/pitt500/clockapp/blob/main/TimerLiveActivity/TimerLiveActivityConfiguration.swift): widget configuration · Configures the Live Activity extension presentation. · `TimerLiveActivity/TimerLiveActivityConfiguration.swift`

### Tests

Behavior and integration coverage

- [Manager tests](https://github.com/pitt500/clockapp/blob/main/ClockAppTests/TimerManagerTests.swift): behavior tests · Covers countdown lifecycle and timing behavior. · `ClockAppTests/TimerManagerTests.swift`
- [Manager integration](https://github.com/pitt500/clockapp/blob/main/ClockAppTests/TimerManagerIntegrationTests.swift): integration tests · Exercises timer manager behavior across real timing scenarios. · `ClockAppTests/TimerManagerIntegrationTests.swift`
- [Store tests](https://github.com/pitt500/clockapp/blob/main/ClockAppTests/TimersStoreRecentsAndActivesTests.swift): behavior tests · Validates recents and active timer workflow boundaries. · `ClockAppTests/TimersStoreRecentsAndActivesTests.swift`
- [Activity tests](https://github.com/pitt500/clockapp/blob/main/ClockAppTests/TimerLiveActivityCoordinatorTests.swift): behavior tests · Covers Live Activity coordination and prioritization behavior. · `ClockAppTests/TimerLiveActivityCoordinatorTests.swift`

## Connections

- App entry → Root view: boots · App entry composes the root view.
- Root view → Timers screen: hosts · Root view presents the main timers screen.
- Timers screen → Timers store: dispatches · User actions flow into the orchestration store.
- Timers screen → UIKit bridge: bridges · SwiftUI uses UIKit where needed.
- Timers store → Timer manager: controls · Store coordinates timer execution and lifecycle.
- Timers store → Timers persistence: persists recents · Store saves and restores recent timers through the persistence boundary.
- Timers store → Activity controller: updates · Store drives Live Activity updates.
- Timers store → Alert commands: exposes · Store-integrated command surface for alert actions.
- Timers store → Live Activity cmds: exposes · Store-integrated command surface for Live Activity actions.
- Timer manager → Timer item: executes · Manager operates on timer domain items.
- Timer manager → Progress snapshot: produces · Manager computes current progress state.
- Timer manager → Row provider: adapts to · Row-facing progress is provided from the manager.
- Timer manager → Detail adapter: adapts to · Detail-facing state is provided from the manager.
- Row provider → Progress provider: implements · Adapter fulfills the row progress contract.
- Detail adapter → Detail provider: implements · Adapter fulfills the detail contract.
- File storage → Timers persistence: implements · File-backed storage implements the persistence boundary.
- Activity controller → Prioritizer: uses · Controller relies on prioritization to choose the surfaced timer.
- Activity controller → Timer attributes: drives · ActivityKit operations are built around shared attributes.
- Activity controller → Shared views: renders · Controller feeds shared Live Activity UI surfaces.
- Activity controller → No-op handler: falls back to · Safe no-op path when activity handling is disabled or unavailable.
- Shared views → Timer attributes: binds to · Shared views consume the Live Activity model.
- Activity bundle → Activity config: configures · Extension bundle owns the configuration entry.
- Activity config → Shared views: renders · Extension configuration uses shared UI components.
- Manager tests → Timer manager: verifies · Tests cover countdown lifecycle behavior.
- Manager integration → Timer manager: verifies · Integration tests cover real-time manager behavior.
- Store tests → Timers store: verifies · Tests cover store workflow and state boundaries.
- Activity tests → Prioritizer: verifies · Tests cover which timer is surfaced.
- Activity tests → Activity controller: verifies · Tests cover ActivityKit coordination behavior.
