Context:
Across recent releases, several dashboard/reporting issues were reported where counts shown differed across devices or counters (e.g., mismatched TB Suspected, TB Confirmed, and Examine counts between tablets/laptops at the same or different camps). With 2.0 shipping the Contact Tracing and Counselling modules alongside the existing screening and referral counters, the underlying aggregation logic now spans a wider set of data points and needs a dedicated validation pass before 2.1 goes out.

Objective:
Validate that reporting and dashboard aggregation logic is accurate and consistent end-to-end across all counters (e.g., Screening, Referral/Diagnostics, TB Suspected/Confirmed, TPT, Contact Tracing, Counselling) and across all devices/camps feeding into them.

Scope:

• Confirm counter values match the underlying source records (no double-counting, no drops) after sync.
• Confirm counts stay consistent across devices/tablets and after reconnect/offline-sync scenarios.
• Confirm dashboard totals reconcile correctly when aggregating across multiple counters/camps.
• Spot-check edge cases: app reinstall, data clear, and multi-device sync for the same beneficiary.

Out of scope:
UI/display-only issues already covered by closed defects in 2.0 This ticket is about verifying the fix holistically, not re-litigating individual bugs.

Acceptance Criteria:

• [ ] Reporting/dashboard counts verified accurate against source data across at least 3 counters and 2+ devices.
• [ ] No discrepancies found after sync, reconnect, or reinstall scenarios, or discrepancies logged as new bugs with steps to reproduce.
• [ ] Sign-off from QA and Dev recorded on this ticket.