Points from chores count towards all configured achievements

[bnzj2fw82v-hash]

Hello,
I have just set up the ChoreOps, created multiple achievements of "Chore Total" type and assigned each of them different related chore. However when I complete any of the chores, it counts towards ALL achievements, event though every achievement is assigned to different chore. What did I do wrong? It looks like the related chore configured in the achievements is ignored.

See picture below, very first 2 chores were completed and all achievements now have 2 points.

This is what I see in diagnostic data - chore is assigned to the achievement indeed and there is a progress on the achievement. But still the progress is updated from any chore which is completed, not just from the one assigned to the achievement.

Version 1.5.0 is used.

Thanks a lot for support!

UPDATE:
Asked AI to analyze the repo and try to find if there is any issue. It might be completely wrong but here is what I got:

The issue is:

• When an achievement has a selected_chore_id, the _map_achievement_to_canonical_target correctly sets tracked_chore_ids in the canonical target
• The _build_source_runtime_context uses tracked_chores to compute today_stats, today_completion, and tracked_current_streak correctly
• BUT the chore_periods_all_time in the base context (from _build_evaluation_context) is the global all-time stats for the assignee, not filtered by the tracked chores
• When CANONICAL_TARGET_TYPE_TOTAL_WITH_BASELINE is evaluated, it uses this global chore_periods_all_time instead of chore-specific stats

The fix needs to be in _build_source_runtime_context - it should compute a chore-specific chore_periods_all_time when tracked_chore_ids is specified.

UPDATE 2:
This is a patch which seem to fix the issue:
fix-achievement-chore-scoping.patch

Please check it for correctness. Originally started this as discussion but may be a bug in the end.

[ccpk1]

Thank you, sorry I somehow missed this thread previously. It definitely looks like a bug I'll get fixed. Thanks for the research and submitting.

[ccpk1]

Created this as a formal issue for further investigation. #245

[ccpk1]

This should be resolved in the newest release. https://github.com/ccpk1/ChoreOps/releases/tag/1.5.1