feat(monthly-recap): Monthly Recap module — metrics engine, personalization, playback and dashboard card

[vaibhav45sktech]

Adds an on-device Monthly Recap that celebrates an ASHA’s verified work from the previous month through personalised Hindi/Assamese stories. It uses read-only Room queries, freezes results for consistent replay, and remains hidden in release builds until rollout controls are added. Includes an additive database migration and automated tests.

Summary by CodeRabbit

• New Features

  • Added a Monthly Recap experience on the home screen, available in Hindi and Assamese.
  • View personalized summaries of activity from the previous month through animated story playback.
  • Resume, replay, pause, navigate, mute music, or close recap stories at any time.
  • Added accessibility support, reduced-motion behavior, progress tracking, and localized controls.
  • Recap content remains privacy-safe and excludes personal names and health details.

• Tests

  • Added comprehensive coverage for recap availability, calculations, content validation, playback, persistence, and date boundaries.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 9fe166a7-0f57-4835-b705-7b662566a1ab

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

📝 Walkthrough

Walkthrough

Added an offline Monthly Recap feature. It stores monthly snapshots, calculates activity metrics, validates localized content, composes deterministic scenes, and provides a dashboard strip with animated playback, controls, accessibility support, and persistence.

Changes

Monthly Recap

Layer / File(s)	Summary
Recap contracts and persistence app/src/main/java/org/piramalswasthya/sakhi/model/*, database/room/*, helpers/RecapClock.kt, helpers/MonthlyRecapAvailability.kt, helpers/MonthlyRecapDataReadiness.kt, di/AppModule.kt	Added recap models, Room storage and migration, calendar windows, availability gates, readiness rules, preferences, and dependency providers.
Activity metrics and snapshot repository app/src/main/java/org/piramalswasthya/sakhi/database/room/dao/*, repositories/*RecapDataSource.kt, MonthlyRecapMetricsCalculator.kt, MonthlyRecapRepo.kt, app/src/androidTest/*, app/src/test/*	Added activity count queries, IO data sources, metric aggregation, snapshot lifecycle handling, metric freezing, and database-backed tests.
Content validation and scene composition app/src/main/java/org/piramalswasthya/sakhi/helpers/RecapContentCodec.kt, RecapSceneComposer.kt, RecapStoryGate.kt, model/RecapContent.kt, app/src/main/res/raw/recap_content.json, app/src/main/res/raw/recap_*.json	Added strict content validation, Hindi and Assamese content, Lottie assets, deterministic scene generation, language fallback, and related tests.
Dashboard strip and playback app/src/main/java/org/piramalswasthya/sakhi/ui/home_activity/*, app/src/main/res/layout/*, navigation/nav_home.xml, values/*, drawable/*, app/src/test/java/.../MonthlyRecap*Test.kt	Added the home strip, navigation destination, animated playback, progress restoration, gestures, music controls, accessibility behavior, localized resources, and UI tests.

Estimated code review effort: 5 (Critical) | ~120 minutes

Sequence Diagram(s)

sequenceDiagram
  participant HomeIconsFragment
  participant MonthlyRecapStripViewModel
  participant MonthlyRecapRepo
  participant RecapStoryGate
  participant MonthlyRecapPlaybackFragment

  HomeIconsFragment->>MonthlyRecapStripViewModel: refresh()
  MonthlyRecapStripViewModel->>MonthlyRecapRepo: observe recap snapshot
  MonthlyRecapStripViewModel->>RecapStoryGate: hasStory()
  RecapStoryGate->>MonthlyRecapRepo: composeStory()
  MonthlyRecapStripViewModel-->>HomeIconsFragment: ready, resume, or replay state
  HomeIconsFragment->>MonthlyRecapPlaybackFragment: navigate to playback
  MonthlyRecapPlaybackFragment->>MonthlyRecapRepo: persist scene progress

Loading

Possibly related PRs

• PSMRI/FLW-Mobile-App#558: Adds the Monthly Recap foundation extended by this change.

Suggested reviewers: ritik-bizbrolly, ishwarchouhan07

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 40.53% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly summarizes the Monthly Recap module and its main metrics, personalization, playback, and dashboard-card changes.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[vaibhav45sktech]

@coderabbitai review

[coderabbitai]

✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[coderabbitai]

Actionable comments posted: 11

🧹 Nitpick comments (9)

app/src/main/java/org/piramalswasthya/sakhi/helpers/RecapContentCodec.kt (1)

104-112: 🗄️ Data Integrity & Integration | 🔵 Trivial | 💤 Low value

Extra band ids in a category are accepted.

missingBands only checks that every declared band exists in the category. A category that also declares an unknown band id passes validation. The composer then never selects that band, so the content push is silently partly dead. Reject unknown band ids for symmetry with the language and category checks.

♻️ Proposed refactor

                 val missingBands = bandIds.toSet() - categoryBandIds.toSet()
                 if (missingBands.isNotEmpty()) {
                     return "${language.id}/${category.id}: missing bands $missingBands"
                 }
+                val unknownBands = categoryBandIds.toSet() - bandIds.toSet()
+                if (unknownBands.isNotEmpty()) {
+                    return "${language.id}/${category.id}: unknown bands $unknownBands"
+                }

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@app/src/main/java/org/piramalswasthya/sakhi/helpers/RecapContentCodec.kt`
around lines 104 - 112, Update the category validation in RecapContentCodec so
it rejects band IDs that are not declared in the language-level bandIds
collection, in addition to detecting duplicates and missing bands. Add an
extra-band check alongside missingBands and return a validation error
identifying the language and category when unknown IDs are present.

app/src/test/java/org/piramalswasthya/sakhi/ui/home_activity/monthly_recap/MonthlyRecapPlaybackViewModelTest.kt (1)

103-110: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Reference the saved-state key from production code instead of repeating the literal.

The literal "recap_playback_scene_index" appears three times in this test. If MonthlyRecapPlaybackViewModel renames the key, these tests still pass for the wrong reason or fail without a clear cause. Expose the key as an internal constant in the ViewModel and use it here.

Also applies to: 177-198

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In
`@app/src/test/java/org/piramalswasthya/sakhi/ui/home_activity/monthly_recap/MonthlyRecapPlaybackViewModelTest.kt`
around lines 103 - 110, Expose the saved-state key used by
MonthlyRecapPlaybackViewModel as an internal constant, then replace all three
occurrences of the literal "recap_playback_scene_index" in
MonthlyRecapPlaybackViewModelTest, including the additional references around
the later test block, with that production constant.

app/src/test/java/org/piramalswasthya/sakhi/helpers/RecapClockTest.kt (1)

18-51: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Pin the time zone so the calendar assertions stay deterministic.

cal() uses Calendar.getInstance(), which uses the JVM default time zone. The CI machine may use a zone with a DST transition. The day count in leap-year february window spans 29 days uses integer division by a fixed 24-hour value, so a DST shift changes the result. Set a fixed time zone for the test class.

♻️ Proposed test fix

+import java.util.TimeZone
+
 class RecapClockTest {
 
+    private val zone: TimeZone = TimeZone.getTimeZone("Asia/Kolkata")
+
     private fun cal(year: Int, month0: Int, day: Int, hour: Int = 0, minute: Int = 0): Calendar =
-        Calendar.getInstance().apply {
+        Calendar.getInstance(zone).apply {
             clear()
             set(year, month0, day, hour, minute, 0)
             set(Calendar.MILLISECOND, 0)
         }

If previousMonthWindow uses Calendar.getInstance() internally, also set the default zone in a @Before method and restore it in @After.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@app/src/test/java/org/piramalswasthya/sakhi/helpers/RecapClockTest.kt` around
lines 18 - 51, Make RecapClockTest use a fixed, non-DST time zone for all
Calendar assertions by configuring cal() with that zone instead of the JVM
default. If previousMonthWindow relies on Calendar.getInstance(), also set the
default time zone in test setup and restore the original zone in teardown.

app/src/main/java/org/piramalswasthya/sakhi/ui/home_activity/monthly_recap/MonthlyRecapPlaybackFragment.kt (1)

238-260: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value

Align the KDoc with the actual clamp values.

The comment states "~8s for a short welcome", but MIN_SCENE_MS is 7000. A short welcome line therefore lasts 7s, not ~8s. The class KDoc at Line 38 also states "welcome 3.5s, category scenes 6s", which no longer matches BASE_READ_MS, PER_WORD_MS, MIN_SCENE_MS, and MAX_SCENE_MS. Update both comments so the documented timings match the constants.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In
`@app/src/main/java/org/piramalswasthya/sakhi/ui/home_activity/monthly_recap/MonthlyRecapPlaybackFragment.kt`
around lines 238 - 260, Update the KDoc above readingDurationMs and the class
KDoc near the fragment declaration to accurately describe the durations produced
by BASE_READ_MS, PER_WORD_MS, MIN_SCENE_MS, and MAX_SCENE_MS, including the 7000
ms minimum instead of ~8 seconds. Keep the implementation unchanged and ensure
the welcome/category timing claims reflect the current adaptive calculation and
clamp values.

app/src/main/res/values-as/strings.xml (1)

1463-1463: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value

Remove the unused Monthly Recap screen description strings.

monthly_recap_lang_screen_cd only appears in app/src/main/res/values/strings.xml, values-hi/strings.xml, and values-as/strings.xml. The code comments indicate the recap language screen is gone, so remove this resource from all three string files.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@app/src/main/res/values-as/strings.xml` at line 1463, Remove the unused
monthly_recap_lang_screen_cd string resource from the base, Hindi, and Assamese
strings files, leaving all other resources unchanged.

app/src/main/java/org/piramalswasthya/sakhi/repositories/MonthlyRecapRepo.kt (1)

295-303: 🚀 Performance & Scalability | 🔵 Trivial | 💤 Low value

Reuse a single RecapSceneComposer and avoid the second snapshot read.

buildPersonalizedScenes builds a new composer on every call and reads the snapshot again through getOrCreateCurrentRecap(). ensureCurrentRecapMetrics() has already loaded that row. You can return the seed from the metrics path or read the row once and pass it down.

This is a minor cleanup and does not change behavior.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@app/src/main/java/org/piramalswasthya/sakhi/repositories/MonthlyRecapRepo.kt`
around lines 295 - 303, Update buildPersonalizedScenes and the related
ensureCurrentRecapMetrics flow to reuse one RecapSceneComposer and avoid calling
getOrCreateCurrentRecap() for a second snapshot read. Propagate the
already-loaded recap row or its variantSeed from ensureCurrentRecapMetrics,
while preserving the existing null handling and composition behavior.

app/src/test/java/org/piramalswasthya/sakhi/repositories/MonthlyRecapRepoTest.kt (1)

199-207: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value

This test does not exercise a race.

The two getOrCreateCurrentRecap() calls run sequentially, so the second call returns early on the read at line 73 and never reaches the insert. The lost-insert path is not covered. The concurrency case is covered by the test at lines 410-420.

Rename this test to describe repeated sequential calls, or force the insert path by clearing the read result for the first lookup only.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In
`@app/src/test/java/org/piramalswasthya/sakhi/repositories/MonthlyRecapRepoTest.kt`
around lines 199 - 207, Rename the test around getOrCreateCurrentRecap to
describe repeated sequential calls, since both invocations read the existing row
and do not exercise a concurrent insert race. Keep the assertions verifying
identical IDs, variantSeed values, and a single DAO row; do not label this test
as a winner/loser concurrency scenario.

app/src/main/java/org/piramalswasthya/sakhi/repositories/MonthlyRecapMetricsCalculator.kt (1)

47-156: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value

Consider parallelizing the six independent counts and extracting the repeated builder.

The six data source calls are independent reads. They run sequentially, so the freeze path pays six serialized IO round trips. You can wrap them in coroutineScope { async { ... } } and await them together. The six category blocks also repeat the same shape; a small private helper that takes categoryId, activityId, unit, and count removes the repetition.

This is a non-blocking suggestion. The current code is correct.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In
`@app/src/main/java/org/piramalswasthya/sakhi/repositories/MonthlyRecapMetricsCalculator.kt`
around lines 47 - 156, In the calculator method containing the six recap
data-source calls, parallelize the independent count operations with
coroutineScope and async, then await all results before constructing categories.
Extract the repeated RecapCategoryMetric/RecapActivityMetric construction into a
private helper accepting categoryId, activityId, unit, and count, and use it for
all six metrics without changing results.

app/src/androidTest/java/org/piramalswasthya/sakhi/database/room/dao/CbacDaoMonthlyRecapTest.kt (1)

297-337: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Extract the duplicated insertMinimalRow and dummyForType test helpers.

Four instrumented test classes each carry an identical PRAGMA-driven minimal-insert helper and dummy-value mapper. Any schema change or fixture fix must be applied four times. Move both functions into one shared androidTest utility, for example a RecapDaoTestFixtures file in the same package, and let each test class call it.

• app/src/androidTest/java/org/piramalswasthya/sakhi/database/room/dao/CbacDaoMonthlyRecapTest.kt#L297-L337: remove the local insertMinimalRow and dummyForType and call the shared helper with support.
• app/src/androidTest/java/org/piramalswasthya/sakhi/database/room/dao/EligibleCoupleRecapDaoTest.kt#L128-L166: remove the local copies and call the shared helper.
• app/src/androidTest/java/org/piramalswasthya/sakhi/database/room/dao/MaternalHealthRecapDaoTest.kt#L183-L221: remove the local copies and call the shared helper.
• app/src/androidTest/java/org/piramalswasthya/sakhi/database/room/dao/RegistrationRecapDaoTest.kt#L178-L216: remove the local copies and call the shared helper.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In
`@app/src/androidTest/java/org/piramalswasthya/sakhi/database/room/dao/CbacDaoMonthlyRecapTest.kt`
around lines 297 - 337, Extract the duplicated insertMinimalRow and dummyForType
helpers into a shared RecapDaoTestFixtures utility in the same package,
preserving their PRAGMA-driven insertion behavior and support/database parameter
handling. Remove both local helpers and update
app/src/androidTest/java/org/piramalswasthya/sakhi/database/room/dao/CbacDaoMonthlyRecapTest.kt
lines 297-337, EligibleCoupleRecapDaoTest.kt lines 128-166,
MaternalHealthRecapDaoTest.kt lines 183-221, and RegistrationRecapDaoTest.kt
lines 178-216 to call the shared helper with support.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@app/src/main/java/org/piramalswasthya/sakhi/helpers/RecapSceneComposer.kt`:
- Around line 14-15: Update the KDoc for RecapSceneComposer’s lottieRawRes
property to match compose(): scenes may provide WELCOME_ANIMATION, a category
girl_1..girl_6 animation, or GOODBYE_ANIMATION, and null should be documented
only as the absence of an animation rather than being tied to WELCOME.

In `@app/src/main/java/org/piramalswasthya/sakhi/model/RecapContent.kt`:
- Around line 64-72: Add default values to the id and text fields in
RecapSentence, and to id/minCount in RecapBandDefinition, RecapLanguageContent,
and RecapCategoryContent so Gson’s no-argument construction produces
validator-safe blanks; in
app/src/main/java/org/piramalswasthya/sakhi/helpers/RecapContentCodec.kt:39-53,
move validate(library) inside the existing try block so residual failures return
null.

In
`@app/src/main/java/org/piramalswasthya/sakhi/repositories/MonthlyRecapRepo.kt`:
- Around line 137-145: The updateSafeProgress method currently allows
progressScene to equal totalScenes, but progress must represent the last valid
scene shown. Cap the stored safe value at totalScenes - 1 when totalScenes is
positive, while preserving the existing handling for missing or non-positive
totals and the current DAO update flow.

In
`@app/src/main/java/org/piramalswasthya/sakhi/ui/home_activity/monthly_recap/RecapMusicController.kt`:
- Around line 81-96: Update fadeTo in RecapMusicController so cancellation is
tracked for each ValueAnimator and onEnd is invoked only when that animator
completes normally, not after Animator.cancel() triggers onAnimationEnd.
Preserve the existing fade behavior and ensure a cancelled fade cannot pause or
otherwise change player state after a newer fade starts.

In `@app/src/main/res/layout/fragment_monthly_recap_playback.xml`:
- Around line 121-127: Move the recapTouchOverlay declaration before
recapReplayButton in the layout so the Replay button is later in child order and
receives taps before the gesture layer. Preserve the overlay’s existing
dimensions, accessibility setting, and gesture behavior.

In `@app/src/main/res/raw/recap_content.json`:
- Around line 40-42: Update the category unit values in recap_content.json to
use only units supported by RecapCountingUnit, replacing UNIQUE_COUPLE and
UNIQUE_MOTHER with the appropriate existing metric units. Keep the category
names and countMeaning text unchanged, and do not expand the model unless those
categories genuinely require new counting semantics.

In `@app/src/main/res/raw/recap_girl_3.json`:
- Line 1: Enable Lottie merge paths before loading the recap_girl_3 animation:
configure the playback view with app:lottie_enableMergePathsForKitKatAndAbove or
call enableMergePathsForKitKatAndAbove(true) on its LottieAnimationView. Apply
this to the view that loads recap_girl_3.json, or remove the ty:"mm" merge-path
operators from the Hand and Eye layers during export.

In `@app/src/main/res/values-as/strings.xml`:
- Line 1469: Update the Assamese translation for monthly_recap_playback_pause_cd
to use a distinct word meaning “hold” or “pause,” while leaving
monthly_recap_playback_close_cd unchanged so TalkBack announces different
actions for Pause and Close.

In `@app/src/main/res/values/monthly_recap_debug.xml`:
- Around line 3-13: Update the documentation comment above
monthly_recap_preview_state to state that this preview resource is read only in
debug builds; release builds obtain the strip state from
MonthlyRecapStripViewModel.stripState. Remove the claim that release builds use
this value or always render the strip hidden, while preserving the valid token
guidance.

In `@app/src/test/java/org/piramalswasthya/sakhi/model/MonthlyRecapCacheTest.kt`:
- Around line 45-52: Update MonthlyRecapCache.safeProgressScene() to clamp
progressScene to totalScenes - 1 when totalScenes is known, preserving the
lower-bound clamp and unknown-total behavior. Adjust the corrupted progress test
to expect 9 for progressScene 99 with totalScenes 10.

In
`@app/src/test/java/org/piramalswasthya/sakhi/repositories/MonthlyRecapRepoTest.kt`:
- Around line 36-37: Correct JULY_2026_MILLIS to the UTC epoch value for 1 July
2026, 1_782_864_000_000L, so its name and comment match the test scenario.
Ensure the associated test uses this value to represent installation after the
complete June recap window.

---

Nitpick comments:
In
`@app/src/androidTest/java/org/piramalswasthya/sakhi/database/room/dao/CbacDaoMonthlyRecapTest.kt`:
- Around line 297-337: Extract the duplicated insertMinimalRow and dummyForType
helpers into a shared RecapDaoTestFixtures utility in the same package,
preserving their PRAGMA-driven insertion behavior and support/database parameter
handling. Remove both local helpers and update
app/src/androidTest/java/org/piramalswasthya/sakhi/database/room/dao/CbacDaoMonthlyRecapTest.kt
lines 297-337, EligibleCoupleRecapDaoTest.kt lines 128-166,
MaternalHealthRecapDaoTest.kt lines 183-221, and RegistrationRecapDaoTest.kt
lines 178-216 to call the shared helper with support.

In `@app/src/main/java/org/piramalswasthya/sakhi/helpers/RecapContentCodec.kt`:
- Around line 104-112: Update the category validation in RecapContentCodec so it
rejects band IDs that are not declared in the language-level bandIds collection,
in addition to detecting duplicates and missing bands. Add an extra-band check
alongside missingBands and return a validation error identifying the language
and category when unknown IDs are present.

In
`@app/src/main/java/org/piramalswasthya/sakhi/repositories/MonthlyRecapMetricsCalculator.kt`:
- Around line 47-156: In the calculator method containing the six recap
data-source calls, parallelize the independent count operations with
coroutineScope and async, then await all results before constructing categories.
Extract the repeated RecapCategoryMetric/RecapActivityMetric construction into a
private helper accepting categoryId, activityId, unit, and count, and use it for
all six metrics without changing results.

In
`@app/src/main/java/org/piramalswasthya/sakhi/repositories/MonthlyRecapRepo.kt`:
- Around line 295-303: Update buildPersonalizedScenes and the related
ensureCurrentRecapMetrics flow to reuse one RecapSceneComposer and avoid calling
getOrCreateCurrentRecap() for a second snapshot read. Propagate the
already-loaded recap row or its variantSeed from ensureCurrentRecapMetrics,
while preserving the existing null handling and composition behavior.

In
`@app/src/main/java/org/piramalswasthya/sakhi/ui/home_activity/monthly_recap/MonthlyRecapPlaybackFragment.kt`:
- Around line 238-260: Update the KDoc above readingDurationMs and the class
KDoc near the fragment declaration to accurately describe the durations produced
by BASE_READ_MS, PER_WORD_MS, MIN_SCENE_MS, and MAX_SCENE_MS, including the 7000
ms minimum instead of ~8 seconds. Keep the implementation unchanged and ensure
the welcome/category timing claims reflect the current adaptive calculation and
clamp values.

In `@app/src/main/res/values-as/strings.xml`:
- Line 1463: Remove the unused monthly_recap_lang_screen_cd string resource from
the base, Hindi, and Assamese strings files, leaving all other resources
unchanged.

In `@app/src/test/java/org/piramalswasthya/sakhi/helpers/RecapClockTest.kt`:
- Around line 18-51: Make RecapClockTest use a fixed, non-DST time zone for all
Calendar assertions by configuring cal() with that zone instead of the JVM
default. If previousMonthWindow relies on Calendar.getInstance(), also set the
default time zone in test setup and restore the original zone in teardown.

In
`@app/src/test/java/org/piramalswasthya/sakhi/repositories/MonthlyRecapRepoTest.kt`:
- Around line 199-207: Rename the test around getOrCreateCurrentRecap to
describe repeated sequential calls, since both invocations read the existing row
and do not exercise a concurrent insert race. Keep the assertions verifying
identical IDs, variantSeed values, and a single DAO row; do not label this test
as a winner/loser concurrency scenario.

In
`@app/src/test/java/org/piramalswasthya/sakhi/ui/home_activity/monthly_recap/MonthlyRecapPlaybackViewModelTest.kt`:
- Around line 103-110: Expose the saved-state key used by
MonthlyRecapPlaybackViewModel as an internal constant, then replace all three
occurrences of the literal "recap_playback_scene_index" in
MonthlyRecapPlaybackViewModelTest, including the additional references around
the later test block, with that production constant.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 9cb14f3c-e9c8-4bc5-a506-d3261f6f57cd

📥 Commits

Reviewing files that changed from the base of the PR and between 9297a67 and c279f12.

⛔ Files ignored due to path filters (2)

• app/src/main/res/drawable-nodpi/img_recap_character.png is excluded by !**/*.png
• app/src/main/res/raw/recap_bg_music.mp3 is excluded by !**/*.mp3

📒 Files selected for processing (89)

• app/build.gradle
• app/src/androidTest/java/org/piramalswasthya/sakhi/database/room/dao/CbacDaoMonthlyRecapTest.kt
• app/src/androidTest/java/org/piramalswasthya/sakhi/database/room/dao/EligibleCoupleRecapDaoTest.kt
• app/src/androidTest/java/org/piramalswasthya/sakhi/database/room/dao/ImmunizationRecapDaoTest.kt
• app/src/androidTest/java/org/piramalswasthya/sakhi/database/room/dao/MaternalHealthRecapDaoTest.kt
• app/src/androidTest/java/org/piramalswasthya/sakhi/database/room/dao/RegistrationRecapDaoTest.kt
• app/src/debug/res/values/monthly_recap_debug.xml
• app/src/main/java/org/piramalswasthya/sakhi/database/room/InAppDb.kt
• app/src/main/java/org/piramalswasthya/sakhi/database/room/dao/BenDao.kt
• app/src/main/java/org/piramalswasthya/sakhi/database/room/dao/CbacDao.kt
• app/src/main/java/org/piramalswasthya/sakhi/database/room/dao/EcrDao.kt
• app/src/main/java/org/piramalswasthya/sakhi/database/room/dao/HouseholdDao.kt
• app/src/main/java/org/piramalswasthya/sakhi/database/room/dao/ImmunizationDao.kt
• app/src/main/java/org/piramalswasthya/sakhi/database/room/dao/MaternalHealthDao.kt
• app/src/main/java/org/piramalswasthya/sakhi/database/room/dao/MonthlyRecapDao.kt
• app/src/main/java/org/piramalswasthya/sakhi/database/shared_preferences/PreferenceDao.kt
• app/src/main/java/org/piramalswasthya/sakhi/di/AppModule.kt
• app/src/main/java/org/piramalswasthya/sakhi/helpers/MonthlyRecapAvailability.kt
• app/src/main/java/org/piramalswasthya/sakhi/helpers/MonthlyRecapDataReadiness.kt
• app/src/main/java/org/piramalswasthya/sakhi/helpers/MonthlyRecapMetricsCodec.kt
• app/src/main/java/org/piramalswasthya/sakhi/helpers/RecapClock.kt
• app/src/main/java/org/piramalswasthya/sakhi/helpers/RecapContentCodec.kt
• app/src/main/java/org/piramalswasthya/sakhi/helpers/RecapSceneComposer.kt
• app/src/main/java/org/piramalswasthya/sakhi/helpers/RecapStoryGate.kt
• app/src/main/java/org/piramalswasthya/sakhi/model/MonthlyRecapCache.kt
• app/src/main/java/org/piramalswasthya/sakhi/model/MonthlyRecapMetrics.kt
• app/src/main/java/org/piramalswasthya/sakhi/model/RecapContent.kt
• app/src/main/java/org/piramalswasthya/sakhi/repositories/BeneficiaryRecapDataSource.kt
• app/src/main/java/org/piramalswasthya/sakhi/repositories/CbacRecapDataSource.kt
• app/src/main/java/org/piramalswasthya/sakhi/repositories/EligibleCoupleRecapDataSource.kt
• app/src/main/java/org/piramalswasthya/sakhi/repositories/HouseholdRecapDataSource.kt
• app/src/main/java/org/piramalswasthya/sakhi/repositories/ImmunizationRecapDataSource.kt
• app/src/main/java/org/piramalswasthya/sakhi/repositories/MaternalHealthRecapDataSource.kt
• app/src/main/java/org/piramalswasthya/sakhi/repositories/MonthlyRecapMetricsCalculator.kt
• app/src/main/java/org/piramalswasthya/sakhi/repositories/MonthlyRecapRepo.kt
• app/src/main/java/org/piramalswasthya/sakhi/ui/home_activity/home/HomeIconsFragment.kt
• app/src/main/java/org/piramalswasthya/sakhi/ui/home_activity/home/MonthlyRecapStrip.kt
• app/src/main/java/org/piramalswasthya/sakhi/ui/home_activity/home/MonthlyRecapStripViewModel.kt
• app/src/main/java/org/piramalswasthya/sakhi/ui/home_activity/monthly_recap/MonthlyRecapPlaybackFragment.kt
• app/src/main/java/org/piramalswasthya/sakhi/ui/home_activity/monthly_recap/MonthlyRecapPlaybackViewModel.kt
• app/src/main/java/org/piramalswasthya/sakhi/ui/home_activity/monthly_recap/RecapMusicController.kt
• app/src/main/res/drawable/bg_monthly_recap_strip.xml
• app/src/main/res/drawable/bg_recap_badge.xml
• app/src/main/res/drawable/bg_recap_badge_new.xml
• app/src/main/res/drawable/bg_recap_playback.xml
• app/src/main/res/drawable/ic_recap_close.xml
• app/src/main/res/drawable/ic_recap_music_off.xml
• app/src/main/res/drawable/ic_recap_music_on.xml
• app/src/main/res/drawable/ic_recap_next.xml
• app/src/main/res/drawable/ic_recap_pause.xml
• app/src/main/res/drawable/ic_recap_play.xml
• app/src/main/res/drawable/ic_recap_prev.xml
• app/src/main/res/drawable/recap_bubble_tail.xml
• app/src/main/res/layout/fragment_monthly_recap_playback.xml
• app/src/main/res/layout/monthly_recap_strip.xml
• app/src/main/res/layout/rv_icon_grid.xml
• app/src/main/res/navigation/nav_home.xml
• app/src/main/res/raw/recap_content.json
• app/src/main/res/raw/recap_didi_dashboard.json
• app/src/main/res/raw/recap_didi_welcome.json
• app/src/main/res/raw/recap_girl_1.json
• app/src/main/res/raw/recap_girl_2.json
• app/src/main/res/raw/recap_girl_3.json
• app/src/main/res/raw/recap_girl_4.json
• app/src/main/res/raw/recap_girl_5.json
• app/src/main/res/raw/recap_girl_6.json
• app/src/main/res/raw/recap_girl_7.json
• app/src/main/res/raw/recap_girl_8.json
• app/src/main/res/values-as/strings.xml
• app/src/main/res/values-hi/strings.xml
• app/src/main/res/values/colors.xml
• app/src/main/res/values/monthly_recap_debug.xml
• app/src/main/res/values/strings.xml
• app/src/test/java/org/piramalswasthya/sakhi/helpers/MonthlyRecapDataReadinessTest.kt
• app/src/test/java/org/piramalswasthya/sakhi/helpers/MonthlyRecapMetricsCodecTest.kt
• app/src/test/java/org/piramalswasthya/sakhi/helpers/RecapClockTest.kt
• app/src/test/java/org/piramalswasthya/sakhi/helpers/RecapContentCodecTest.kt
• app/src/test/java/org/piramalswasthya/sakhi/helpers/RecapSceneComposerTest.kt
• app/src/test/java/org/piramalswasthya/sakhi/model/MonthlyRecapCacheTest.kt
• app/src/test/java/org/piramalswasthya/sakhi/repositories/AshaProfileRepoTest.kt
• app/src/test/java/org/piramalswasthya/sakhi/repositories/BeneficiaryRecapDataSourceTest.kt
• app/src/test/java/org/piramalswasthya/sakhi/repositories/CbacRecapDataSourceTest.kt
• app/src/test/java/org/piramalswasthya/sakhi/repositories/EligibleCoupleRecapDataSourceTest.kt
• app/src/test/java/org/piramalswasthya/sakhi/repositories/HouseholdRecapDataSourceTest.kt
• app/src/test/java/org/piramalswasthya/sakhi/repositories/ImmunizationRecapDataSourceTest.kt
• app/src/test/java/org/piramalswasthya/sakhi/repositories/MaternalHealthRecapDataSourceTest.kt
• app/src/test/java/org/piramalswasthya/sakhi/repositories/MonthlyRecapRepoTest.kt
• app/src/test/java/org/piramalswasthya/sakhi/ui/home_activity/home/MonthlyRecapStripTest.kt
• app/src/test/java/org/piramalswasthya/sakhi/ui/home_activity/monthly_recap/MonthlyRecapPlaybackViewModelTest.kt

[coderabbitai]

🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

🧩 Analysis chain

🌐 Web query:

Does Android Animator.cancel() invoke AnimatorListener.onAnimationEnd() after onAnimationCancel()?

💡 Result:

Yes, calling Animator.cancel on an Android animation invokes both AnimatorListener.onAnimationCancel and AnimatorListener.onAnimationEnd [1][2]. When cancel is called, the animation stops, and the system sends an onAnimationCancel(Animator) message to its listeners, which is immediately followed by an onAnimationEnd(Animator) message [1][2]. Consequently, any code within your onAnimationEnd listener will be executed regardless of whether the animation finished naturally or was canceled [3].

Citations:

• 1: https://developer.android.com/reference/android/animation/Animator
• 2: https://developer.android.com/reference/androidx/core/animation/Animator
• 3: https://developer.android.com/develop/ui/views/animations/prop-animation

---

🏁 Script executed:

#!/usr/bin/env bash
set -euo pipefail

# Locate and inspect the controller around the reported lines.
file="$(git ls-files | grep -Fx 'app/src/main/java/org/piramalswasthya/sakhi/ui/home_activity/monthly_recap/RecapMusicController.kt' || true)"
if [ -z "${file:-}" ]; then
  echo "Could not find RecapMusicController.kt"
  exit 0
fi
echo "FILE=$file"
wc -l "$file"
sed -n '1,140p' "$file" | nl -ba

echo
echo "Usages of fadeTo/onEnd related symbols:"
rg -n "fadeTo\(|onEnd|cancelFade|maxVolume|minVolume|muted|unmute|mute|player" "$file" || true

Repository: PSMRI/FLW-Mobile-App

Length of output: 406

---

🏁 Script executed:

#!/usr/bin/env bash
set -euo pipefail

file="app/src/main/java/org/piramalswasthya/sakhi/ui/home_activity/monthly_recap/RecapMusicController.kt"
wc -l "$file"
awk '{printf "%5d\t%s\n", NR, $0}' "$file" | sed -n '1,140p'

echo
echo "Usages of fadeTo/onEnd related symbols:"
rg -n "fadeTo\(|onEnd|cancelFade|maxVolume|minVolume|muted|unmute|mute|player" "$file" || true

Repository: PSMRI/FLW-Mobile-App

Length of output: 5714

---

Ignore cancelled fade end callbacks.

Animator.cancel() calls onAnimationEnd() after onAnimationCancel(), so setAudible(false) followed by setAudible(true) can pause the player even though a new fade-in starts. Track cancellation so onEnd runs only after normal animation completion.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In
`@app/src/main/java/org/piramalswasthya/sakhi/ui/home_activity/monthly_recap/RecapMusicController.kt`
around lines 81 - 96, Update fadeTo in RecapMusicController so cancellation is
tracked for each ValueAnimator and onEnd is invoked only when that animator
completes normally, not after Animator.cancel() triggers onAnimationEnd.
Preserve the existing fade behavior and ensure a cancelled fade cannot pause or
otherwise change player state after a newer fade starts.

[coderabbitai]

🎯 Functional Correctness | 🟠 Major | ⚡ Quick win

The gesture overlay blocks taps on the Replay button.

recapTouchOverlay is declared after recapReplayButton. ConstraintLayout dispatches touch events in reverse child order, so the overlay receives ACTION_DOWN first. setUpGestures() in MonthlyRecapPlaybackFragment.kt returns true for ACTION_DOWN once scenes are loaded, so the overlay consumes the whole gesture and recapReplayButton never receives a click. The Replay button is the only forward action on the goodbye scene, so the story ends in a dead end for touch users.

The comment at Line 12 already documents the intended z-order for the progress row, close button and controls row. Add the Replay button to that group by declaring the overlay before it.

🐛 Proposed fix: declare the overlay before the Replay button

     </com.google.android.material.card.MaterialCardView>
 
+    <!-- Full-screen gesture layer (hold to pause, tap left/right). Hidden from
+         accessibility: the visible controls below are the accessible path. It is
+         declared before the Replay button and the controls so it never steals
+         their clicks. -->
+    <View
+        android:id="@+id/recapTouchOverlay"
+        android:layout_width="match_parent"
+        android:layout_height="match_parent"
+        android:importantForAccessibility="no" />
+
     <com.google.android.material.button.MaterialButton
         android:id="@+id/recapReplayButton"

-    <!-- Full-screen gesture layer (hold to pause, tap left/right). Hidden from
-         accessibility: the visible controls below are the accessible path. -->
-    <View
-        android:id="@+id/recapTouchOverlay"
-        android:layout_width="match_parent"
-        android:layout_height="match_parent"
-        android:importantForAccessibility="no" />
-
     <!-- Segmented story progress (segments added in code, one per scene). -->

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@app/src/main/res/layout/fragment_monthly_recap_playback.xml` around lines 121
- 127, Move the recapTouchOverlay declaration before recapReplayButton in the
layout so the Replay button is later in child order and receives taps before the
gesture layer. Preserve the overlay’s existing dimensions, accessibility
setting, and gesture behavior.

[coderabbitai]

🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Description: Check whether merge paths are enabled anywhere and which recap assets rely on them.
set -euo pipefail

# Assets that use merge paths.
fd -t f 'recap_.*\.json' -p app/src/main/res/raw --exec sh -c 'grep -l "\"ty\":\"mm\"" "$1" || true' _ {}

# Is the flag enabled in code or layouts?
rg -n 'enableMergePathsForKitKatAndAbove|lottie_enableMergePaths' -g '!**/build/**'

Repository: PSMRI/FLW-Mobile-App

Length of output: 236

---

🏁 Script executed:

#!/bin/bash
# Check repository references to merge-path support without depending on repository commands.
set -u

echo "== merge path / flag references =="
rg -n 'mergePaths|merge paths|merge paths|EnableMerge|enableMergePathsForKitkatAndAbove|enableMergePathsForKitKatAndAbove|lottie_enableMergePaths' -g '!**/build/**' . || true

echo
echo "== recap raw assets with merge paths =="
while IFS= read -r -d '' file; do
  if grep -q '"ty":"mm"' "$file"; then
    echo "$file"
  fi
done < <(find app/src/main/res/raw -maxdepth 1 -type f -print0 2>/dev/null | sort -z | head -zn 50)

echo
echo "== Lottie dependency declarations =="
rg -n 'com\.airbnb\.android:lottie|lottie' -g '!**/build/**' .

Repository: PSMRI/FLW-Mobile-App

Length of output: 3653

---

🏁 Script executed:

#!/bin/bash
set -u

echo "== fragments using LottieAnimationView =="
for f in app/src/main/java/org/piramalswasthya/sakhi/ui/home_activity/monthly_recap/MonthlyRecapPlaybackFragment.kt \
         app/src/main/java/org/piramalswasthya/sakhi/ui/home_activity/monthly_recap/strips/*.kt \
         app/src/main/java/org/piramalswasthya/sakhi/ui/home_activity/monthly_recap/MonthlyRecapPlaybackViewModel.kt \
         app/src/main/java/org/piramalswasthya/sakhi/helpers/RecapSceneComposer.kt; do
  if [ -f "$f" ]; then echo "--- $f"; fi
done

echo
rg -n "\.setRawFile|\.setAnimation|\.animation|setAnimation|LottieAnimationView|setRawFileWith" app/src/main app/src/test -g '!**/build/**' || true

echo
echo "== layout snippets =="
sed -n '20,40p' app/src/main/res/layout/fragment_monthly_recap_playback.xml || true
sed -n '160,175p' app/src/main/java/org/piramalswasthya/sakhi/ui/home_activity/monthly_recap/MonthlyRecapPlaybackFragment.kt || true

Repository: PSMRI/FLW-Mobile-App

Length of output: 4420

---

🌐 Web query:

Lottie Android 6.4.0 LottieAnimationView enableMergePathsForKitKatAndAbove documentation

💡 Result:

In Lottie for Android 6.4.0, merge paths are a feature that must be manually enabled using the enableMergePathsForKitKatAndAbove(boolean) method [1][2]. Key documentation and usage details include: Purpose and Compatibility: Merge paths are only supported on devices running Android KitKat (API level 19) and above [1][2]. Because they can introduce performance overhead due to the use of Path.Op, they are disabled by default [1][2]. Implementation: You can enable this feature either programmatically or via XML [3][4]. Programmatic: lottieAnimationView.enableMergePathsForKitKatAndAbove(true); XML: <com.airbnb.lottie.LottieAnimationView... app:lottie_enableMergePathsForKitKatAndAbove="true" /> Limitations: Merge paths do not function correctly if the operand shape is entirely contained within the first shape [5][6]. If your goal is to cut one shape out of another, it is recommended to use an even-odd fill type instead [5][6]. Warning: If an animation contains merge paths but they have not been enabled, Lottie will log a warning indicating that they are disabled [3][4].

Citations:

• 1: https://airbnb.gitbook.io/lottie/android
• 2: https://github.com/airbnb/lottie/blob/master/android.md
• 3: Add support for merge paths airbnb/lottie-android#101
• 4: https://stackoverflow.com/questions/51493427/android-lottie-animation-lags
• 5: https://github.com/airbnb/lottie-android/blob/c5b8318c7cf205e95db143955acbfc69f86bc339/lottie/src/main/java/com/airbnb/lottie/LottieDrawable.java
• 6: https://github.com/airbnb/lottie-android/blob/master/lottie/src/main/java/com/airbnb/lottie/LottieAnimationView.java

---

Enable merge paths before loading recap_girl_3.json.

recap_girl_3.json uses "ty":"mm" merge paths in the Hand and Eye layers. lottie-android 6.4.0 disables merge paths by default, and this playback view does not set app:lottie_enableMergePathsForKitKatAndAbove or call enableMergePathsForKitKatAndAbove(true). Enable it, or export the animation without merge-path operators.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@app/src/main/res/raw/recap_girl_3.json` at line 1, Enable Lottie merge paths
before loading the recap_girl_3 animation: configure the playback view with
app:lottie_enableMergePathsForKitKatAndAbove or call
enableMergePathsForKitKatAndAbove(true) on its LottieAnimationView. Apply this
to the view that loads recap_girl_3.json, or remove the ty:"mm" merge-path
operators from the Hand and Eye layers during export.

[coderabbitai]

🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

Use a distinct Assamese word for "Pause".

monthly_recap_playback_pause_cd is "বন্ধ কৰক". monthly_recap_playback_close_cd at Line 1464 uses the same verb, "বন্ধ কৰক". TalkBack users then hear the same action word for the Pause button and the Close button. Pause and Close have different results: Pause holds the story, Close leaves the screen. Use a word that means "hold" for the Pause button.

✏️ Proposed wording change

-    <string name="monthly_recap_playback_pause_cd">বন্ধ কৰক</string>
+    <string name="monthly_recap_playback_pause_cd">সাময়িকভাৱে ৰখাওক</string>

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	<string name="monthly_recap_playback_pause_cd">বন্ধ কৰক</string>
	<string name="monthly_recap_playback_pause_cd">সাময়িকভাৱে ৰখাওক</string>

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@app/src/main/res/values-as/strings.xml` at line 1469, Update the Assamese
translation for monthly_recap_playback_pause_cd to use a distinct word meaning
“hold” or “pause,” while leaving monthly_recap_playback_close_cd unchanged so
TalkBack announces different actions for Pause and Close.

[coderabbitai]

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Correct the comment: release builds do not read this value.

HomeIconsFragment.setUpMonthlyRecapStrip() reads monthly_recap_preview_state only inside if (BuildConfig.DEBUG). In release builds the strip state comes from MonthlyRecapStripViewModel.stripState. The comment states that release builds use this value and always render HIDDEN. That statement is wrong and can hide a rollout gap.

📝 Proposed comment fix

-        Release builds use THIS value and therefore always render the strip HIDDEN
-        until the real eligibility source is implemented in a later Phase. Debug builds
-        override this via app/src/debug/res/values/monthly_recap_debug.xml.
+        Debug builds read this value (overridden in
+        app/src/debug/res/values/monthly_recap_debug.xml) to force a preview state.
+        Release builds ignore this value: the strip state comes from
+        MonthlyRecapStripViewModel, which fails closed to HIDDEN until the real
+        eligibility source is implemented in a later Phase.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	<!--
	Monthly Recap strip preview state (main = release-safe default).
	Release builds use THIS value and therefore always render the strip HIDDEN
	until the real eligibility source is implemented in a later Phase. Debug builds
	override this via app/src/debug/res/values/monthly_recap_debug.xml.
	Valid tokens: hidden | ready | resume | replay
	(see MonthlyRecapStripState.fromToken — anything unknown is treated as hidden).
	-->
	<string name="monthly_recap_preview_state" translatable="false">hidden</string>
	<!--
	Monthly Recap strip preview state (main = release-safe default).
	Debug builds read this value (overridden in
	app/src/debug/res/values/monthly_recap_debug.xml) to force a preview state.
	Release builds ignore this value: the strip state comes from
	MonthlyRecapStripViewModel, which fails closed to HIDDEN until the real
	eligibility source is implemented in a later Phase.
	Valid tokens: hidden | ready | resume | replay
	(see MonthlyRecapStripState.fromToken — anything unknown is treated as hidden).
	-->
	<string name="monthly_recap_preview_state" translatable="false">hidden</string>

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@app/src/main/res/values/monthly_recap_debug.xml` around lines 3 - 13, Update
the documentation comment above monthly_recap_preview_state to state that this
preview resource is read only in debug builds; release builds obtain the strip
state from MonthlyRecapStripViewModel.stripState. Remove the claim that release
builds use this value or always render the strip hidden, while preserving the
valid token guidance.

[coderabbitai]

🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Inspect the clamp implementation and every consumer of progressScene.
fd 'MonthlyRecapCache.kt' -t f --exec rg -n -C6 'safeProgressScene|progressScene|totalScenes' {}
rg -n 'safeProgressScene|updateSafeProgress|progressScene' --type kotlin -g '!**/test/**'

Repository: PSMRI/FLW-Mobile-App

Length of output: 1228

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "Find MonthlyRecapCache-related files:"
fd 'MonthlyRecapCache' -t f

echo
echo "Inspect MonthlyRecapCache file outlines:"
for f in $(fd 'MonthlyRecapCache' -t f); do
  echo "--- $f"
  ast-grep outline "$f" --view compact || true
  echo "--- relevant sections"
  sed -n '1,180p' "$f" | cat -n
done

echo
echo "Production consumers:"
rg -n -C4 'safeProgressScene|updateSafeProgress|progressScene' --type kotlin -g '!**/test/**' || true

echo
echo "Test files:"
fd 'MonthlyRecap.*Test.kt|MonthlyRecapCacheTest.kt' -t f
for f in $(fd 'MonthlyRecap.*Test.kt|MonthlyRecapCacheTest.kt' -t f); do
  echo "--- $f"
  ast-grep outline "$f" --view compact || true
  sed -n '1,220p' "$f" | cat -n
done

Repository: PSMRI/FLW-Mobile-App

Length of output: 7713

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "Diff stat and MonthlyRecapCache diff context:"
git diff --stat || true
git diff -- app/src/main/java/org/piramalswasthya/sakhi/model/MonthlyRecapCache.kt app/src/test/java/org/piramalswasthya/sakhi/model/MonthlyRecapCacheTest.kt || true

echo
echo "All repository references to MonthlyRecapCache and safeProgressScene:"
rg -n 'MonthlyRecapCache|safeProgressScene|progressScene' . || true

echo
echo "Behavioral probe of current clamp inputs:"
python3 - <<'PY'
import sys
values = [(-4, None), (3, 10), (99, 10), (99, None)]
for progress_scene, total_scenes in values:
    upper = total_scenes if (total_scenes is not None and total_scenes > 0) else None
    coerced = progress_scene if progress_scene >= 0 else 0
    result = coerced if upper is None else min(coerced, upper)
    print(f"progressScene={progress_scene}, totalScenes={total_scenes} -> safeProgressScene={result}")
PY

Repository: PSMRI/FLW-Mobile-App

Length of output: 8501

---

Clamp progressScene to the last valid scene index.

progressScene is documented as the last completed scene index, and MonthlyRecapPlaybackViewModel resumes from that value for the scene index. For a 10-scene recap, the valid index range is 0..9; this should coerce 99 to 9 when totalScenes = 10, so update both the clamp and the test.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@app/src/test/java/org/piramalswasthya/sakhi/model/MonthlyRecapCacheTest.kt`
around lines 45 - 52, Update MonthlyRecapCache.safeProgressScene() to clamp
progressScene to totalScenes - 1 when totalScenes is known, preserving the
lower-bound clamp and unknown-total behavior. Adjust the corrupted progress test
to expect 9 for progressScene 99 with totalScenes 10.

[coderabbitai]

🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

JULY_2026_MILLIS does not hold 1 July 2026.

1_782_000_000_000L is approximately 21 June 2026 UTC, not 1 July 2026. 1 July 2026 UTC is 1_782_864_000_000L. The tests still pass because the value is after the 1 June window start, so DEVICE_MISSED_PART_OF_MONTH still fires. The name and the comment are wrong, and the constant no longer proves the "install after the whole recap month" case.

🐛 Proposed fix

 /** 1 July 2026 UTC — after the June window, so the install missed part of the month. */
-private const val JULY_2026_MILLIS = 1_782_000_000_000L
+private const val JULY_2026_MILLIS = 1_782_864_000_000L

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	/** 1 July 2026 UTC — after the June window, so the install missed part of the month. */
	private const val JULY_2026_MILLIS = 1_782_000_000_000L
	/** 1 July 2026 UTC — after the June window, so the install missed part of the month. */
	private const val JULY_2026_MILLIS = 1_782_864_000_000L

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In
`@app/src/test/java/org/piramalswasthya/sakhi/repositories/MonthlyRecapRepoTest.kt`
around lines 36 - 37, Correct JULY_2026_MILLIS to the UTC epoch value for 1 July
2026, 1_782_864_000_000L, so its name and comment match the test scenario.
Ensure the associated test uses this value to represent installation after the
complete June recap window.

[sonarqubecloud]

Quality Gate passed

Issues
8 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud