feat(reminder): add timeflow-alarm native module and Expo wiring

[gac0812]

Summary

• 新增 frontend/modules/timeflow-alarm Android 原生库（精确闹钟、响铃 UI、停铃、原生事件）
• 增加 Expo config plugin withTimeflowAlarm 与 react-native.config.js autolinking
• 加厚 TimeflowAlarmBridge / NativeAlarmScheduler：三参 schedule、cancelAll、stopRinging、subscribe、consumeNativeDispositions
• 新增 ExpoSystemNotification（expo-notifications 懒加载），并补 scheduler / 系统通知单测

Merge Order

• 下一个：feat(reminder): wire LocalReminderApplication with in-memory adapters #238

Scope

• frontend/modules/timeflow-alarm/**
• frontend/plugins/withTimeflowAlarm.js
• frontend/react-native.config.js
• frontend/app.json、frontend/package.json、frontend/eslint.config.js、frontend/.prettierignore
• frontend/src/infrastructure/notifications/native/TimeflowAlarmBridge.ts
• frontend/src/infrastructure/notifications/NativeAlarmScheduler.ts
• frontend/src/infrastructure/notifications/ExpoSystemNotification.ts
• frontend/src/features/reminder/application/interfaces/AlarmSchedulerPort.ts（可选原生事件方法）
• frontend/tests/unit/infrastructure/notifications/nativeAlarmScheduler.test.ts
• frontend/tests/unit/infrastructure/notifications/expoSystemNotification.test.ts

Out of scope

• 组合根切换到 LocalReminderApplication（见 feat(reminder): wire LocalReminderApplication with in-memory adapters #238）
• 百度定位与启动定位权限（见 feat(reminder): add Baidu location module and native monitor #239）
• 音频 / 震动 / IntervalTimeListener（feat(reminder): add interval time, expo-audio and vibration adapters #215）
• presenter / 强度分流 / expo 围栏（feat(reminder): wire presenter, strength delivery and native location #230）

Verification

• npm run check
• npm ci

Closes #232

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
timeflow	Ready	Preview	Aug 14, 2026 1:44am

[fennoai]

Found one high-confidence build blocker in the new Android module. TypeScript typecheck, focused Jest tests (18 tests), and ESLint pass; an Android Gradle build was not available in this workspace because no Android SDK/project wrapper is mounted.

[gac0812]

@fennoai /review

[fennoai]

Review Complete

• Reviewed the fixed range ac37def20a925c28b9927ed124763ff002c72332...b268e19b776c0184f271379881da10c6c419cae5.
• Posted one non-blocking PR review finding: overlapping alarms share a singleton AlarmSoundService, which can suppress the second alarm’s fired event and couple dismissal/audio lifecycles.
• Verification passed: targeted Jest tests (18), TypeScript typecheck, ESLint, and Prettier check.
• npm ci completed successfully; npm reported an engine warning and 13 existing audit vulnerabilities.

View job run

[fennoai]

Found one correctness issue in the native alarm service. The targeted JS tests and static checks pass.

[gac0812]

@fennoai /review

[fennoai]

Review Complete

• Reviewed the fixed range ac37def20a925c28b9927ed124763ff002c72332...83ba3b0b01c64b571806611e33ffe75b60053ef1.
• The new overlap serialization correctly addresses the prior missing fired event, but one residual P1 lifecycle issue remains: the previous RingActivity is not closed when the service switches to a new overlapping alarm, so its controls can dismiss the wrong alarm and stop the new one.
• Verification passed: targeted Jest tests (18), TypeScript typecheck, ESLint, Prettier check, and git diff --check.

View job run

[fennoai]

The previous overlap-event issue is improved, but one lifecycle correctness issue remains. Targeted tests and static checks pass.

[fennoai]

P1 — The previous RingActivity is not torn down when replacing an overlapping alarm. RingActivity is launched with FLAG_ACTIVITY_MULTIPLE_TASK and keeps its own alarmId/requestCode, while this replacement block only releases the service audio and overlay. If alarm B fires while alarm A’s activity is visible, the visible UI still belongs to A but the service now plays B; pressing confirm/snooze on A calls AlarmNativeBridge.notify* with A’s IDs and AlarmSoundService.stop() stops B as well. RingActivity.finishIfOpen() already exists, so close the current activity before switching the service to the new alarm (or otherwise make the activity/service state atomic).